Skip to content

Commit f2ca456

Browse files
committed
remove note about preview for ARM64
1 parent d542eb6 commit f2ca456

File tree

3 files changed

+10
-15
lines changed

3 files changed

+10
-15
lines changed

articles/iot-edge/how-to-store-data-blob.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Store block blobs on devices - Azure IoT Edge | Microsoft Docs
2+
title: Store block blobs on devices - Azure IoT Edge | Microsoft Docs
33
description: Understand tiering and time-to-live features, see supported blob storage operations, and connect to your blob storage account.
44
author: kgremban
55
ms.author: kgremban
@@ -60,7 +60,7 @@ An Azure IoT Edge device:
6060
* Windows AMD64
6161
* Linux AMD64
6262
* Linux ARM32
63-
* Linux ARM64 (preview)
63+
* Linux ARM64
6464

6565
Cloud resources:
6666

@@ -170,10 +170,10 @@ Specify your IoT Edge device as the blob endpoint for any storage requests that
170170
* `http://<device IP >:11002/<account name>`
171171
* `http://<IoT Edge device hostname>:11002/<account name>`
172172
* `http://<fully qualified domain name>:11002/<account name>`
173-
173+
174174
> [!IMPORTANT]
175175
> Azure IoT Edge is case-sensitive when you make calls to modules, and the Storage SDK also defaults to lowercase. Although the name of the module in the [Azure Marketplace](how-to-deploy-modules-portal.md#deploy-modules-from-azure-marketplace) is **AzureBlobStorageonIoTEdge**, changing the name to lowercase helps to ensure that your connections to the Azure Blob Storage on IoT Edge module aren't interrupted.
176-
176+
177177
## Azure Blob Storage quickstart samples
178178

179179
The Azure Blob Storage documentation includes quickstart sample code in several languages. You can run these samples to test Azure Blob Storage on IoT Edge by changing the blob endpoint to connect to your local blob storage module.

articles/iot-edge/tutorial-csharp-module.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -41,10 +41,8 @@ Use the following table to understand your options for developing and deploying
4141
| C# | Visual Studio Code | Visual Studio |
4242
| -- | ------------------ | ------------- |
4343
| **Linux AMD64** | ![C# modules for LinuxAMD64 in VS Code](./media/tutorial-c-module/green-check.png) | ![C# modules for LinuxAMD64 in Visual Studio](./media/tutorial-c-module/green-check.png) |
44-
| **Linux ARM32** | ![C# modules for LinuxARM32 in VS Code](./media/tutorial-c-module/green-check.png) | ![C# modules for LinuxARM64 in Visual Studio](./media/tutorial-c-module/green-check.png) |
45-
46-
>[!NOTE]
47-
>Support for Linux ARM64 devices is available in [public preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). For more information, see [Develop and debug ARM64 IoT Edge modules in Visual Studio Code (preview)](https://devblogs.microsoft.com/iotdev/develop-and-debug-arm64-iot-edge-modules-in-visual-studio-code-preview).
44+
| **Linux ARM32** | ![C# modules for LinuxARM32 in VS Code](./media/tutorial-c-module/green-check.png) | ![C# modules for LinuxARM32 in Visual Studio](./media/tutorial-c-module/green-check.png) |
45+
| **Linux ARM64** | ![C# modules for LinuxARM64 in VS Code](./media/tutorial-c-module/green-check.png) | ![C# modules for LinuxARM64 in Visual Studio](./media/tutorial-c-module/green-check.png) |
4846

4947
Before beginning this tutorial, you should have gone through the previous tutorial to set up your development environment, [Develop an IoT Edge module using Linux containers](tutorial-develop-for-linux.md). After completing that tutorial, you already should have the following prerequisites:
5048

articles/iot-edge/tutorial-develop-for-linux.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: 'Tutorial - Develop module for Linux devices using Azure IoT Edge'
3-
description: This tutorial walks through setting up your development machine and cloud resources to develop IoT Edge modules using Linux containers for Linux devices
3+
description: This tutorial walks through setting up your development machine and cloud resources to develop IoT Edge modules using Linux containers for Linux devices
44
author: kgremban
55

66
ms.author: kgremban
@@ -37,7 +37,7 @@ A development machine:
3737
* You can use your own computer or a virtual machine, depending on your development preferences.
3838
* Make sure that your development machine supports nested virtualization. This capability is necessary for running a container engine, which you install in the next section.
3939
* Most operating systems that can run a container engine can be used to develop IoT Edge modules for Linux devices. This tutorial uses a Windows computer, but points out known differences on macOS or Linux.
40-
* Install [Git](https://git-scm.com/), to pull module template packages later in this tutorial.
40+
* Install [Git](https://git-scm.com/), to pull module template packages later in this tutorial.
4141
* [C# for Visual Studio Code (powered by OmniSharp) extension](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp).
4242
* [.NET Core 2.1 SDK](https://dotnet.microsoft.com/download/dotnet/2.1).
4343

@@ -67,14 +67,11 @@ The following table lists the supported development scenarios for **Linux contai
6767

6868
| | Visual Studio Code | Visual Studio 2017/2019 |
6969
| - | ------------------ | ------------------ |
70-
| **Linux device architecture** | Linux AMD64 <br> Linux ARM32 | Linux AMD64 <br> Linux ARM32 |
70+
| **Linux device architecture** | Linux AMD64 <br> Linux ARM32 <br> Linux ARM64 | Linux AMD64 <br> Linux ARM32 <br> Linux ARM64 |
7171
| **Azure services** | Azure Functions <br> Azure Stream Analytics <br> Azure Machine Learning | |
7272
| **Languages** | C <br> C# <br> Java <br> Node.js <br> Python | C <br> C# |
7373
| **More information** | [Azure IoT Edge for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-edge) | [Azure IoT Edge Tools for Visual Studio 2017](https://marketplace.visualstudio.com/items?itemName=vsc-iot.vsiotedgetools) <br> [Azure IoT Edge Tools for Visual Studio 2019](https://marketplace.visualstudio.com/items?itemName=vsc-iot.vs16iotedgetools) |
7474

75-
>[!NOTE]
76-
>Support for Linux ARM64 devices is available in [public preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). For more information, see [Develop and debug ARM64 IoT Edge modules in Visual Studio Code (preview)](https://devblogs.microsoft.com/iotdev/develop-and-debug-arm64-iot-edge-modules-in-visual-studio-code-preview).
77-
7875
This tutorial teaches the development steps for Visual Studio Code. If you would rather use Visual Studio, refer to the instructions in [Use Visual Studio 2019 to develop and debug modules for Azure IoT Edge](how-to-visual-studio-develop-module.md).
7976

8077
## Install container engine
@@ -288,7 +285,7 @@ If you encounter errors when building and pushing your module image, it often ha
288285
* Did you run the `docker login` command using the credentials that you copied from your container registry? These credentials are different than the ones that you use to sign in to Azure.
289286
* Is your container repository correct? Does it have your correct container registry name and your correct module name? Open the **module.json** file in the SampleModule folder to check. The repository value should look like **\<registry name\>.azurecr.io/samplemodule**.
290287
* If you used a different name than **SampleModule** for your module, is that name consistent throughout the solution?
291-
* Is your machine running the same type of containers that you're building? This tutorial is for Linux IoT Edge devices, so Visual Studio Code should say **amd64** or **arm32v7** in the side bar, and Docker Desktop should be running Linux containers.
288+
* Is your machine running the same type of containers that you're building? This tutorial is for Linux IoT Edge devices, so Visual Studio Code should say **amd64** or **arm32v7** in the side bar, and Docker Desktop should be running Linux containers.
292289

293290
## Deploy modules to device
294291

0 commit comments

Comments
 (0)