Skip to content

Commit 4470ad6

Browse files
Updates
1 parent bb03034 commit 4470ad6

File tree

3 files changed

+31
-23
lines changed

3 files changed

+31
-23
lines changed

content/learning-paths/servers-and-cloud-computing/cobalt/1-create-cobalt-vm.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -20,14 +20,17 @@ To create a Cobalt 100 VM, follow these steps:
2020

2121
1. Sign in to the [Azure Portal](https://portal.azure.com/).
2222
2. Select **Create a resource → Compute → Virtual machine**.
23-
3. Complete the **Basics** tab as shown in the figure below:
23+
3. Complete the fields in the **Basics** tab with the values shown in the figure below:
24+
2425
![Azure Portal – Basics tab for the VM wizard#center](images/create-cobalt-vm.png "Configuring the Basics tab")
25-
Cobalt 100 powers the Dpsv6-series. Selecting **Standard_D4ps_v6** creates a Cobalt VM with four physical cores. You can select a different size if you need more or fewer cores.
26+
27+
Cobalt 100 powers the Dpsv6-series. Selecting **Standard_D4ps_v6** creates a Cobalt VM with four physical cores.
28+
You can choose a different size if you need more or fewer cores.
2629
4. Upload your public SSH key or generate a new one in the wizard.
27-
5. For **Public inbound ports**, select **None**.
30+
5. For the **Public inbound ports** field, select **None**.
2831
6. On the **Disks** tab, accept the default options.
29-
7. On the **Networking** tab, ensure that a **Public IP** is selected. You will need it to connect later. Leave the NSG settings as **Basic** for now.
32+
7. On the **Networking** tab, ensure that a **Public IP** is selected. You will need it to connect to the VM later. Leave the NSG settings as **Basic**.
3033

31-
Click **Review + create** followed by **Create**. Azure now deploys the VM and the automatically-generated Network Security Group (NSG). Provisioning takes ~2 minutes.
34+
8. Select **Review + create**, then **Create**. Azure now deploys the VM and the automatically-generated Network Security Group (NSG). Provisioning takes ~2 minutes.
3235

33-
Navigate to the **Deployment in progress** pane or open the **Notifications** panel to track progress. When the deployment succeeds, proceed to the next step to expose an inbound port.
36+
9. Navigate to the **Deployment in progress** pane or open the **Notifications** panel to track progress. When the deployment succeeds, proceed to the next step to expose an inbound port.

content/learning-paths/servers-and-cloud-computing/cobalt/2-open-port.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,17 @@ layout: learningpathall
1010

1111
Every new virtual machine created through the Azure wizard is associated with a **Network Security Group (NSG)**. An NSG acts as a stateful firewall – if no rule explicitly allows traffic, Azure blocks it by default.
1212

13-
In this step you will open port 22 for SSH, as well as port 8080 so that a web application running on the VM is reachable from your IP for testing. Substitute a different port if required by your workload, or a different IP range if you'd like broader accessibility.
13+
In this step, you'll open port 22 for SSH and port 8080 so that a web application running on the VM is reachable from your IP for testing. Substitute a different port if required by your workload, or a different IP range if you'd like broader accessibility.
1414

15-
1. In the Azure Portal, open the newly created VM resource and click **Networking → Network settings** in the left nav.
15+
1. In the Azure Portal, open the newly-created VM resource and select **Networking → Network settings** from the left-hand menu.
1616
2. Select the **Network security group**.
17-
3. Click on **Create Port Rule** and from the drop-down menu select **Inbound port rule**
18-
4. Fill in the form, specifying **My IP address** as the source and 22 as the destination port:
17+
3. Select **Create Port Rule**, then choose **Inbound port rule** from the drop-down menu.
18+
19+
4. Fill in the form with **My IP address** as the source and 22 as the destination port:
20+
1921
![Add inbound security rule with source of my IP and destination port 22#center](images/create-nsg-rule.png)
20-
5. Click **Add**.
21-
To open port 8080, follow steps 3 through 5 again, but instead choose port 8080 for the destination port.
2222

23-
You have now opened ports 22 and 8080 to your IP. In the next step, you will verify connectivity.
23+
5. Select **Add**.
24+
To open port 8080, repeat steps 3-5 and enter 8080 as the destination port.
25+
26+
You have now opened ports 22 and 8080 to your IP. In the next step, you will verify connectivity from your local machine.

content/learning-paths/servers-and-cloud-computing/cobalt/3-verify-connectivity.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -8,20 +8,20 @@ layout: learningpathall
88

99
## Connect over SSH and test the open port
1010

11-
1. On the **Overview** page for the VM copy the **Public IP address**.
11+
1. On the **Overview** page of the VM, copy the **Public IP address**.
1212
2. Open a terminal on your local machine and SSH to the VM (replace *azureuser* if you chose a different admin username):
1313

1414
```bash
1515
ssh -i [path to your pem file] azureuser@[public IP]
1616
```
1717

18-
Where `[public IP]` is your public IP and `[path to your pem file]` is the path to your SSH key file.
18+
Replace `[public IP]` with your VM's public IP address, and `[path to your pem file]` with the path to your SSH private key file.
1919

20-
Accept the prompt to add the host to *known_hosts* the first time you connect.
20+
When prompted, confirm the connection to add the VM to your *known_hosts* file.
2121

22-
### Start a simple HTTP server
22+
### Start a temporary HTTP server
2323

24-
If you do not already have an application listening on TCP 8080 you can start one temporarily:
24+
If you don't already have an application listening on TCP 8080, you can start one temporarily:
2525

2626
```bash
2727
sudo apt update -y && sudo apt install -y python3
@@ -32,16 +32,18 @@ Leave this terminal open – the server runs in the foreground.
3232

3333
### Test from your local machine
3434

35-
In a second local terminal run `curl` to confirm you can reach the server through the NSG rule you created:
35+
In a second local terminal run `curl` to confirm that you can reach the server through the NSG rule you created:
3636

3737
```bash
3838
curl http://[public IP]:8080
3939
```
4040

41-
Where `[public IP]` is your public IP.
41+
Replace `[public IP]` with your VM's public IP address.
4242

43-
You should see an HTML directory listing (or your application response). Receiving a response verifies that TCP 8080 is open and the VM is reachable from the public internet.
43+
You should see an HTML directory listing (or your application response). A successful response confirms that TCP port 8080 is open and the VM is reachable from the public internet.
4444

45-
Terminate the Python server when you are finished testing (press `Ctrl + C`).
45+
To stop the server, press `Ctrl + C`.
4646

47-
You now have an Arm-based Cobalt 100 VM with an exposed port 8080 that you can use to run any test server. To learn about optimizing .NET workloads on Cobalt, check out [Migrating a .NET application to Azure Cobalt](../../dotnet-migration/).
47+
You now have an Arm-based Cobalt 100 VM with port 8080 open and ready to receive external traffic. You can use it to run any test server or deploy your own application.
48+
49+
To learn about optimizing .NET workloads on Cobalt, check out [Migrating a .NET application to Azure Cobalt](../../dotnet-migration/).

0 commit comments

Comments
 (0)