You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/digital-twins/quickstart-view-occupancy-dotnet.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ services: digital-twins
9
9
ms.devlang: csharp
10
10
ms.topic: quickstart
11
11
ms.custom: mvc seodec18
12
-
ms.date: 11/12/2019
12
+
ms.date: 01/10/2020
13
13
# As a developer new to Azure Digital Twins, I need to understand how to send motion and carbon dioxide telemetry to a space in Azure Digital Twins and how to find available rooms with fresh air by using a back-end application.
14
14
---
15
15
@@ -19,7 +19,7 @@ The Azure Digital Twins service allows you to re-create a digital image of your
19
19
20
20
This quickstart uses [a pair of .NET samples](https://github.com/Azure-Samples/digital-twins-samples-csharp) to digitize an imaginary office building. It shows you how to find available rooms in that building. With Digital Twins, you can associate many sensors with your environment. You also can find out if the air quality of your available room is optimal with the help of a simulated sensor for carbon dioxide. One of the sample applications generates random sensor data to help you visualize this scenario.
21
21
22
-
The following video summarizes quickstart setup:
22
+
The following video summarizes the quickstart setup:
@@ -80,11 +80,11 @@ The spatial graph is provisioned by using the [provisionSample.yaml](https://git
80
80
81
81
1. The provisioning step might take a few minutes. It also provisions an IoT Hub within your Digital Twins instance. It loops through until the IoT Hub shows Status=`Running`.
82
82
83
-
[](media/quickstart-view-occupancy-dotnet/digital-twins-provision-sample.png#lightbox)
83
+
[](media/quickstart-view-occupancy-dotnet/azure-digital-twins-quickstart-provision-sample.png#lightbox)
84
84
85
85
1. At the end of the execution, copy the `ConnectionString` of the device for use in the device simulator sample. Copy only the string outlined in this image.
86
86
87
-
[](media/quickstart-view-occupancy-dotnet/digital-twins-connection-string.png#lightbox)
87
+
[](media/quickstart-view-occupancy-dotnet/azure-digital-twins-quickstart-connection-string.png#lightbox)
88
88
89
89
>[!TIP]
90
90
> You can view and modify your spatial graph using the [Azure Digital Twins Graph Viewer](https://github.com/Azure/azure-digital-twins-graph-viewer).
@@ -101,7 +101,7 @@ Build and run the sensor simulator device application by following these steps.
101
101
1. Edit [appsettings.json](https://github.com/Azure-Samples/digital-twins-samples-csharp/blob/master/device-connectivity/appsettings.json) to update **DeviceConnectionString** with the previous `ConnectionString`. Save the updated file.
102
102
1. Run `dotnet run` to start sending sensor data. It will be sent to Azure Digital Twins as shown in the following image.
1. Let this simulator run so that you can view results side by side with the next step action. This window shows you the simulated sensor data sent to Digital Twins. The next step queries in real time to find available rooms with fresh air.
107
107
@@ -121,7 +121,7 @@ The sensor sample simulates random data values for two sensors. They're motion a
121
121
-`Room is available and air is fresh`
122
122
-`Room is not available or air quality is poor`
123
123
124
-
[](media/quickstart-view-occupancy-dotnet/digital-twins-get-available.png#lightbox)
124
+
[](media/quickstart-view-occupancy-dotnet/azure-digital-twins-quickstart-get-available.png#lightbox)
125
125
126
126
To understand what happened in this quickstart and what APIs were called, open [Visual Studio Code](https://code.visualstudio.com/Download) with the code workspace project found in `digital-twins-samples-csharp`. Use the following command:
Copy file name to clipboardExpand all lines: articles/digital-twins/tutorial-facilities-setup.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: bertvanhoof
8
8
ms.custom: seodec18
9
9
ms.service: digital-twins
10
10
ms.topic: tutorial
11
-
ms.date: 11/12/2019
11
+
ms.date: 01/10/2020
12
12
#Customer intent: As an Azure IoT developer, I want to walk through a sample application to learn how to use the features of Digital Twins to create a spatially aware intelligent IoT solution.
13
13
---
14
14
@@ -125,7 +125,6 @@ public static async Task<IEnumerable<ProvisionResults.Space>> ProvisionSample(Ht
125
125
126
126
return results;
127
127
}
128
-
129
128
```
130
129
131
130
This function uses [provisionSample.yaml](https://github.com/Azure-Samples/digital-twins-samples-csharp/blob/master/occupancy-quickstart/src/actions/provisionSample.yaml) in the same folder. Open this file, and note the hierarchy of an office building: *Venue*, *Floor*, *Area*, and *Rooms*. Any of these physical spaces can contain *devices* and *sensors*. Each entry has a predefined `type`—for example, Floor, Room.
@@ -146,7 +145,7 @@ The **provisionSample.yaml** file contains the following nodes:
146
145
147
146
-**devices**: Spaces can contain `devices`, which are physical or virtual entities that manage a number of sensors. For example, a device might be a user’s phone, a Raspberry Pi sensor pod, or a gateway. In the imaginary building in your sample, note how the room named **Focus Room** contains a **Raspberry Pi 3 A1** device. Each device node is identified by a unique `hardwareId`, which is hardcoded in the sample. To configure this sample for an actual production, replace these with values from your setup.
148
147
149
-
-**sensors**: A device can contain multiple `sensors`. They can detect and record physical changes like temperature, motion, and battery level. Each sensor node is uniquely identified by a `hardwareId`, hardcoded here. For an actual application, replace these by using the unique identifiers of the sensors in your setup. The provisionSample.yaml file has two sensors to record *Motion* and *CarbonDioxide*. Add another sensor to record *Temperature*, by adding the following lines, below the lines for the CarbonDioxide sensor. Note that these are provided in provisionSample.yaml as commented-out lines. You can uncomment them by removing the `#` character in the front of each line.
148
+
-**sensors**: A device can contain multiple `sensors`. They can detect and record physical changes like temperature, motion, and battery level. Each sensor node is uniquely identified by a `hardwareId`, hardcoded here. For an actual application, replace these by using the unique identifiers of the sensors in your setup. The provisionSample.yaml file has two sensors to record *Motion* and *CarbonDioxide*. Add another sensor to record *Temperature*, by adding the following lines, below the lines for the CarbonDioxide sensor. These are provided in provisionSample.yaml as commented-out lines. You can uncomment them by removing the `#` character in the front of each line.
Copy file name to clipboardExpand all lines: articles/digital-twins/tutorial-facilities-udf.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: bertvanhoof
8
8
ms.custom: seodec18
9
9
ms.service: digital-twins
10
10
ms.topic: tutorial
11
-
ms.date: 11/13/2019
11
+
ms.date: 01/10/2020
12
12
#Customer intent: As an Azure IoT developer, I want to walk through a sample application to monitor a space using Azure Digital Twins.
13
13
---
14
14
@@ -34,7 +34,7 @@ This tutorial assumes that you have [finished your Azure Digital Twins setup](tu
34
34
-[.NET Core SDK version 2.1.403 or later](https://www.microsoft.com/net/download) on your development machine to build and run the sample. Run `dotnet --version` to verify that the right version is installed.
35
35
-[Visual Studio Code](https://code.visualstudio.com/) to explore the sample code.
36
36
37
-
>[!TIP]
37
+
>[!TIP]
38
38
> Use a unique Digital Twins instance name if you're provisioning a new instance.
39
39
40
40
## Define conditions to monitor
@@ -70,7 +70,7 @@ Also note the section named **roleassignments**. It assigns the Space Administra
70
70
71
71
Modify the JavaScript file to monitor temperature and other conditions. Add the following lines of code to look for conditions when no motion is detected in the room, carbon dioxide levels are below 1,000 ppm, and temperature is below 78 degrees Fahrenheit.
72
72
73
-
>[!NOTE]
73
+
>[!NOTE]
74
74
> This section modifies the file *src\actions\userDefinedFunctions\availability.js* so you can learn in detail one way to write a user-defined function. However, you can choose to directly use the file [src\actions\userDefinedFunctions\availabilityForTutorial.js](https://github.com/Azure-Samples/digital-twins-samples-csharp/blob/master/occupancy-quickstart/src/actions/userDefinedFunctions/availabilityForTutorial.js) in your setup. This file has all the changes required for this tutorial. If you use this file instead, make sure to use the correct file name for the **script** key in [src\actions\provisionSample.yaml](https://github.com/Azure-Samples/digital-twins-samples-csharp/blob/master/occupancy-quickstart/src/actions/provisionSample.yaml).
75
75
76
76
a. At the top of the file, add the following lines for temperature below the comment `// Add your sensor type here`:
@@ -174,7 +174,7 @@ Also note the section named **roleassignments**. It assigns the Space Administra
174
174
dotnet run ProvisionSample
175
175
```
176
176
177
-
>[!IMPORTANT]
177
+
>[!IMPORTANT]
178
178
> To prevent unauthorized access to your Digital Twins Management API, the **occupancy-quickstart** application requires you to sign in with your Azure account credentials. It saves your credentials for a brief period, so you might not need to sign in every time you run it. The first time this program runs, and when your saved credentials expire after that, the application directs you to a sign-in page and gives a session-specific code to enter on that page. Follow the prompts to sign in with your Azure account.
179
179
180
180
1. After your account is authenticated, the application starts creating a sample spatial graph as configured in *provisionSample.yaml*. Wait until the provisioning finishes. It will take a few minutes. After that, observe the messages in the command window and notice how your spatial graph is created. Notice how the application creates an IoT hub at the root node or the `Venue`.
@@ -183,7 +183,7 @@ Also note the section named **roleassignments**. It assigns the Space Administra
> If you get an error message similar to "The I/O operation has been aborted because of either a thread exit or an application request" in the middle of the provisioning, try running the command again. This might happen if the HTTP client timed out from a network issue.
188
188
189
189
## Simulate sensor data
@@ -225,7 +225,7 @@ In this section, you'll use the project named *device-connectivity* in the sampl
225
225
dotnet run
226
226
```
227
227
228
-
>[!NOTE]
228
+
>[!NOTE]
229
229
> Because the simulation sample does not directly communicate with your Digital Twins instance, it does not require you to authenticate.
230
230
231
231
## Get results of the user-defined function
@@ -242,7 +242,7 @@ The user-defined function runs every time your instance receives device and sens
242
242
243
243
The output window shows how the user-defined function runs and intercepts events from the device simulation.
244
244
245
-
[](./media/tutorial-facilities-udf/udf-running.png#lightbox)
245
+
[](./media/tutorial-facilities-udf/adt-tutorial-udf-running.png#lightbox)
246
246
247
247
If the monitored condition is met, the user-defined function sets the value of the space with the relevant message, as we saw [earlier](#create-a-user-defined-function). The `GetAvailableAndFreshSpaces` function prints out the message on the console.
248
248
@@ -252,7 +252,7 @@ If you want to stop exploring Azure Digital Twins at this point, feel free to de
252
252
253
253
1. From the left menu in the [Azure portal](https://portal.azure.com), select **All resources**, select your Digital Twins resource group, and select **Delete**.
254
254
255
-
>[!TIP]
255
+
>[!TIP]
256
256
> If you experienced trouble deleting your Digital Twins instance, a service update has been rolled out with the fix. Please retry deleting your instance.
257
257
258
258
2. If necessary, delete the sample applications on your work machine.
Copy file name to clipboardExpand all lines: articles/hdinsight/hdinsight-release-notes-archive.md
+60-1Lines changed: 60 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.reviewer: jasonh
7
7
ms.service: hdinsight
8
8
ms.topic: conceptual
9
9
ms.custom: hdinsightactive
10
-
ms.date: 12/17/2019
10
+
ms.date: 01/08/2019
11
11
---
12
12
13
13
# Archived release notes
@@ -19,6 +19,65 @@ ms.date: 12/17/2019
19
19
20
20
Azure HDInsight is one of the most popular services among enterprise customers for open-source Apache Hadoop and Apache Spark analytics on Azure.
21
21
22
+
## Release date: 12/17/2019
23
+
24
+
This release applies both for HDInsight 3.6 and 4.0.
25
+
26
+
### New features
27
+
28
+
#### Service tags
29
+
Service tags simplify security for Azure virtual machines and Azure virtual networks by enabling you to easily restrict network access to the Azure services. You can use service tags in your network security group (NSG) rules to allow or deny traffic to a specific Azure service globally or per Azure region. Azure provides the maintenance of IP addresses underlying each tag. HDInsight service tags for network security groups (NSGs) are groups of IP addresses for health and management services. These groups help minimize complexity for security rule creation. HDInsight customers can enable service tag through Azure Portal, PowerShell, and REST API. For more information, see [Network security group (NSG) service tags for Azure HDInsight](https://docs.microsoft.com/azure/hdinsight/hdinsight-service-tags).
30
+
31
+
#### Custom Ambari DB
32
+
HDInsight now allows you to use your own SQL DB for Apache Ambari. You can configure this custom Ambari DB from the Azure portal or through resource manager template. This feature allows you to choose the right SQL DB for your processing and capacity needs. You can also upgrade easily to match business growth requirements. For more information, see [Set up HDInsight clusters with a custom Ambari DB](hdinsight-custom-ambari-db.md).
No deprecations for this release. To get ready for upcoming deprecations, see [Upcoming changes](#upcoming-changes).
38
+
39
+
### Behavior changes
40
+
No behavior changes for this release. To get ready for upcoming behavior changes, see [Upcoming changes](#upcoming-changes).
41
+
42
+
### Upcoming changes
43
+
The following changes will happen in upcoming releases.
44
+
45
+
#### Transport Layer Security (TLS) 1.2 enforcement
46
+
Transport Layer Security (TLS) and Secure Sockets Layer (SSL) are cryptographic protocols that provide communications security over a computer network. For more information, see [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security#SSL_1.0.2C_2.0_and_3.0). While Azure HDInsight clusters accept TLS 1.2 connections on public HTTPS endpoints, TLS 1.1 is still supported for backward compatibility with older clients.
47
+
48
+
Starting from the next release, you will be able to opt-in and configure your new HDInsight clusters to only accept TLS 1.2 connections.
49
+
50
+
Later in the year, starting on 6/30/2020, Azure HDInsight will enforce TLS 1.2 or later versions for all HTTPS connections. We recommend that you ensure that all your clients are ready to handle TLS 1.2 or later versions.
51
+
52
+
#### Moving to Azure virtual machine scale sets
53
+
HDInsight now uses Azure virtual machines to provision the cluster. Starting from Feburary 2020 (exact date will be communicated later), HDInsight will use Azure virtual machine scale sets instead. See more about [Azure virtual machine scale sets](https://docs.microsoft.com/azure/virtual-machine-scale-sets/overview).
54
+
55
+
#### ESP Spark cluster node size change
56
+
In the upcoming release:
57
+
- The minimum allowed node size for ESP Spark cluster will be changed to Standard_D13_V2.
58
+
- A-series VMs will be deprecated for creating new ESP clusters, as A-series VMs could cause ESP cluster issues because of relatively low CPU and memory capacity.
59
+
60
+
#### HBase 2.0 to 2.1
61
+
In the upcoming HDInsight 4.0 release, HBase version will be upgraded from version 2.0 to 2.1.
62
+
63
+
### Bug fixes
64
+
HDInsight continues to make cluster reliability and performance improvements.
65
+
66
+
### Component version change
67
+
We've extended HDInsight 3.6 support to December 31, 2020. You can find more details in [Supported HDInsight versions](hdinsight-component-versioning.md#supported-hdinsight-versions).
68
+
69
+
No component version change for HDInsight 4.0.
70
+
71
+
Apache Zeppelin on HDInsight 3.6: 0.7.0-->0.7.3.
72
+
73
+
You can find the most up-to-date component versions from [this doc](https://docs.microsoft.com/azure/hdinsight/hdinsight-component-versioning#apache-hadoop-components-available-with-different-hdinsight-versions).
74
+
75
+
### New Regions
76
+
77
+
#### UAE North
78
+
The management IPs of UAE North are: `65.52.252.96` and `65.52.252.97`.
79
+
80
+
22
81
## Release date: 11/07/2019
23
82
24
83
This release applies both for HDInsight 3.6 and 4.0.
0 commit comments