Azure HPC Pack configuration management series (PART11)

Azure HPC Pack configuration management series (PART1)

Azure HPC Pack configuration management series (PART2)

Azure HPC Pack configuration management series (PART3)

Azure HPC Pack configuration management series (PART4)

Azure HPC Pack configuration management series (PART5)

Azure HPC Pack configuration management series (PART6)

  1. During startup, the secondary node host state changes from never deployed to ready for configuration. If you want to track the progress of settings, select one of the nodes, and then in the details pane, click the settings log tab (Figure 86).

 

5/10/2018 5:23:01 PM Moving node AZURE\AzureCN-000* from state Provisioning to state Offline

5/10/2018 5:23:01 PM Moving node AZURE\AzureCN-000* from state Provisioning to state Offline

5/10/2018 5:23:00 PM Moving node AZURE\AzureCN-000* from state Provisioning to state Offline

5/10/2018 5:23:00 PM Node AZURE\AzureCN-0004 has become available

5/10/2018 5:23:00 PM Node AZURE\AzureCN-0003 has become available

5/10/2018 5:23:00 PM Node AZURE\AzureCN-0005 has become available

5/10/2018 5:13:00 PM Updating scheduler data for node AZURE\AzureCN-0004

5/10/2018 5:13:00 PM Updating the scheduler configuration for node AZURE\AzureCN-0004

5/10/2018 5:13:00 PM Updating scheduler data for node AZURE\AzureCN-0003

5/10/2018 5:13:00 PM Updating the scheduler configuration for node AZURE\AzureCN-0003

5/10/2018 5:13:00 PM Updating scheduler data for node AZURE\AzureCN-0005

5/10/2018 5:13:00 PM Updating the scheduler configuration for node AZURE\AzureCN-0005

5/10/2018 5:13:00 PM Updating the scheduler configuration for creating deployment bbf25bf7-dfaf-4574-b966-41b27879dd43.

5/10/2018 5:13:00 PM Windows Azure operation succeeded

5/10/2018 5:12:05 PM Waiting for Windows Azure deployment to start

5/10/2018 5:12:05 PM The Operation Id for transitioning Windows Azure deployment to state Running is 9fe3c16cb86476fd8265cbd37a9633a3

5/10/2018 5:12:04 PM Transitioning Windows Azure deployment to the Running state

5/10/2018 5:12:00 PM Windows Azure operation succeeded

5/10/2018 5:10:55 PM Waiting for Windows Azure deployment creation to complete

5/10/2018 5:10:55 PM Configuring HPC cluster storage in Windows Azure

5/10/2018 5:10:54 PM Windows Azure deployment started: bbf25bf7-dfaf-4574-b966-41b27879dd43. Operation Id for this deployment is 44f97c4625f4742e8e67c72d6d55026d

5/10/2018 5:10:54 PM Deployment bbf25bf7-dfaf-4574-b966-41b27879dd43 is locked.

5/10/2018 5:10:49 PM Starting Windows Azure deployment

5/10/2018 5:10:48 PM Uploading HPC cluster certificate to Windows Azure storage

5/10/2018 5:10:47 PM Uploading Windows Azure proxy certificate to the Windows Azure certificate store

5/10/2018 5:10:47 PM The HPC cluster runtime package is present in Windows Azure storage

5/10/2018 5:10:46 PM Skipping *** validation because a *** gateway is not configured in the Windows Azure Virtual Network.

Figure 86 configuration log of a node

Figure 87 auxiliary nodes in Provisioning state

The status of Azure Paas VM is displayed in Azure Management Portal (Figure 88-89)

Figure 88 querying the initial status of Azure computing nodes and agents in the deployment phase

Figure 89 creating a pas VM during the deployment phase

  1. To bring a node online, select the node in the offline state in the HPC management console, right-click, and then click online (Figure 90).

Figure 90 bringing Azure work nodes Online

When the work node starts successfully, the node status changes to offline.

Be careful

Each time a group of Windows Azure nodes are started, Windows Azure will automatically configure two (or more) other proxy role instances to facilitate communication between the HEAD node and the Windows Azure node (Figure 91). After the node is set up, it is displayed in HPC Cluster Manager.

Figure 91 automatic configuration of HPC agent from HPC HEAD node

The deployment with two Azure computing agents and two Azure work roles is shown in Figure 92.

Figure 92 HPC computing agent and HPC Azure roles

Figure 93 HPC heat map with HEAD node and three Azure work nodes

If you want to delete a group of role instances in Windows Azure, use HPC cluster manager to stop the node (apply the stop operation). This will remove the role instance from the service and change the status of the work nodes in the HPC cluster to undeployed.

Figure 94 operation of deleting Azure node in Azure cloud service

 

Figure 95 stop operation of Azure computing node

Figure 96 detection node operation status

Figure 97 Azure node is in undeployed state

When the Azure node reaches the undeployed state, the corresponding Azure cloud service is empty.

7 reference

  • Use Microsoft HPC Pack to explode to Windows Azure

https://docs.microsoft.com/en-us/powershell/high-performance-computing/burst-to-azure-worker-instances-with-microsoft-hpc-pack?view=hpc16-ps

  • Virtual machine and cloud service size of Windows Azure

https://docs.microsoft.com/en-us/azure/cloud-services/cloud-services-sizes-specs

  • A8 and A9 computing intensive examples: getting started with HPC Pack

https://docs.microsoft.com/en-us/powershell/high-performance-computing/overview?view=hpc16-ps

  • To set up a hybrid cluster using Microsoft HPC Pack:

https://docs.microsoft.com/en-us/powershell/high-performance-computing/set-up-hybrid-hpcpack-cluster-paas?view=hpc16-ps

Azure HPC Pack configuration management series (PART1)

Azure HPC Pack configuration management series (PART2)

Azure HPC Pack configuration management series (PART3)

Azure HPC Pack configuration management series (PART4)

Azure HPC Pack configuration management series (PART5)

Azure HPC Pack configuration management series (PART6)

Azure HPC Pack configuration management series (PART7)

Azure HPC Pack configuration management series (PART8)

Azure HPC Pack configuration management series (PART9)

Azure HPC Pack configuration management series (PART10)

Tags: Windows network

Posted on Tue, 10 Mar 2020 00:21:56 -0400 by bschwarz