Export (0) Print
Expand All

Modify the Sample Deployment

Updated: April 10, 2013

This section contains information about how to perform administrative operations on the Windows Azure HPC Scheduler deployment.

In this section:

Delete the Windows Azure HPC Scheduler deployment

You can delete the Windows Azure HPC Scheduler deployment when you are no longer using it. To do this, in the Windows Azure Management Portal, perform the operations listed below.

CautionCaution
  • Before you delete a storage account or drop a SQL Azure database, ensure that it is not used to store other valuable data for your subscription.

  • Ensure that the name of the Windows Azure cloud service, storage account, and SQL Azure database for the deployment correspond to the name that you selected in Step 2. Build and configure the sample applications in this guide.

  • Delete the deployment for the Windows Azure cloud service that you used to deploy the Windows Azure HPC Scheduler

  • Delete the storage account that you used to deploy the Windows Azure HPC Scheduler

  • Drop the SQL Azure database that you used to deploy the Windows Azure HPC Scheduler

For information about how to perform these operations, see the online Help for the Windows Azure Management Portal.

Additional considerations

  • You do not need to delete the cloud service that you used for the deployment. However, you may want to do this if you are close to reaching your cloud service quota.

  • If you want, you can redeploy the Windows Azure HPC Scheduler at a later date by using the original configuration for the deployment.

Change the number of role instances

You can use one of several methods to change the number of the role instances that are in the Windows Azure HPC Scheduler deployment:

  • Before a deployment, use the Configure and Publish a Sample Windows Azure Application form to specify the number of nodes.

  • Before a deployment, specify the value of Instances count for each role in the ServiceConfiguration.Cloud.cscfg file in the AzureSampleService project.

  • Before a deployment, right-click a role in the AzureSampleService project, and then click Properties. On the Configuration page, specify the Instance count.

  • After a deployment, modify the instance count in the Management Portal. To do this, select the cloud service for the deployment, click Scale on the ribbon, and change the number of instances of each node.

Change the size of the role instances

By default, the role instances that are in the Windows Azure HPC Scheduler deployment have a vmsize attribute of Small. To change the size of the role instances that are deployed, set the value of the vmsize attribute for each role in the ServiceDefinition.csdef file.

You can use the following methods to change the size of the role instances:

  • Before a deployment, set the value of the vmsize attribute for each role in the ServiceDefinition.csdef file

  • Before a deployment, right-click a role in the AzureSampleService project, and then click Properties. On the Configuration page, specify the VM size.

ImportantImportant
Instances of size ExtraSmall are not supported in the Windows Azure HPC Scheduler.

For information about the specifications for each virtual machine size, see How to Configure Virtual Machine Sizes.

Disable support for SOA applications

You can disable support for SOA applications in the sample service if you do not need to deploy them. To do this, in the CreateCscfgFile.cs file in the AppConfigure project, comment out the following code:

    config.EnableSOA();

Additional considerations

  1. If you do no longer need the SOA applications that are included in the Windows Azure sample service, you can delete the SOA Sample project from the AzureSampleService.sln file.

Add users after the Windows Azure HPC Scheduler deployment

By default the Windows Azure HPC Scheduler is configured with a single administrative user. After the deployment, the administrator can add accounts to the local users or local administrators group on the nodes, so that users other the default administrator can submit jobs or perform other operations.

To add a user or administrator to the Windows Azure HPC Scheduler

  1. If you have not already done so, make a remote desktop connection to a head node in the deployment.

  2. Open a command prompt.

  3. Do one of the following:

    • To add a user account on the head node, type the following command:

      ManageAzureUser AddUser –h <ClusterName> <UserName> <Password>
      
      
    • To add an administrator account on the head node, type the following command:

      ManageAzureUser AddAdmin –h <ClusterName>  <UserName> <Password>
      
      

    Where

    <ClusterName> is the name of the deployment and the value of the CCP_SCHEDULER environment variable on the nodes

    <UserName> is the name of the user or administrator account that you are adding

    <Password> is the password of the account that you are adding

  4. After you add a user, to ensure that the user account is added on all the compute nodes, run a command similar to the following:

    job submit /user:<UserName> /numnodes:<NumberOfNodes> mpiexec hostname
    
    ImportantImportant
    • In the default Windows Azure sample service deployment, run the preceding command by specifying /numnodes:1.

    • When prompted for the password for the user account, type the password that you configured on the head node.

See Also



Show:
© 2014 Microsoft