Chapter 16. Provisioning Cloud Instances on Microsoft Azure Resource Manager

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click Create Compute Resource.
2. In the Name field, enter a name for the compute resource.
3. From the Provider list, select Azure Resource Manager.
4. Optional: In the Description field, enter a description for the resource.
5. In the Client ID field, enter the Application or client ID.
6. In the Client Secret field, enter the client secret.
7. In the Subscription ID field, enter the subscription ID.
8. In the Tenant ID field, enter the Directory or tenant ID.
9. From the Azure Region list, select the Azure region to use.
10. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click the name of the Microsoft Azure Resource Manager connection.
2. Click Create Image.
3. In the Name field, enter a name for the image.
4. From the Operating System list, select the image’s base operating system.
5. From the Architecture list, select the operating system architecture.
6. In the Username field, enter the SSH user name for image access. You cannot use the root user.
7. Optional: In the Password field, enter a password to authenticate with.
8. In the Marketplace Image URN field, enter a Marketplace URN. For example, RedHat:RHEL:7-RAW:latest. For more information, see Find Linux VM images in the Azure Marketplace with the Azure CLI.
9. Optional: Select the User Data check box if the image supports user data input, such as cloud-init data.
10. Click Submit to save the image details.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles.
2. In the Compute Profiles window, click the name of an existing compute profile, or click Create Compute Profile, enter a Name, and click Submit.
3. Click the name of the Azure compute resource.
4. From the Resource group list, select the resource group to provision to.
5. From the VM Size list, select a size of a virtual machine to provision.
6. From the Platform list, select Linux. Satellite does not support provisioning virtual machines running Microsoft operating systems.
7. In the Username field, enter a user name to authenticate with. Note that the username that you enter for compute profile must be the same that you use when creating an image.

8. To authenticate the user, use one of the following options:

   • To authenticate using a password, enter a password in the Password field.
   • To authenticate using an SSH key, enter an SSH key in the SSH Key field.
9. Optional: If you want the virtual machine to use a premium virtual machine disk, select the Premium OS Disk check box.
10. From the OS Disk Caching list, select the disc caching setting.
11. Optional: In the Custom Script Command field, enter commands to perform on the virtual machine when the virtual machine is provisioned.
12. Optional: If you want to run custom scripts when provisioning finishes, in the Comma separated file URIs field, enter comma-separated file URIs of scripts to use. The scripts must contain sudo at the beginning because Red Hat Satellite downloads files to the /var/lib/waagent/custom-script/download/0/ directory on the host and scripts require sudo privileges to be executed.
13. Click Add Interface.
14. From the Azure Subnet list, select the Azure subnet to provision to.
15. From the Public IP list, select the public IP setting.
16. Optional: If you want the virtual machine to use a static private IP, select the Static Private IP check box.
17. Click Submit.

For CLI Users

1. Create a compute profile to use with the Azure Resource Manager compute resource:

   # hammer compute-profile create --name compute_profile_name

2. Add Azure details to the compute profile. With the username setting, enter the SSH user name for image access. Note that the username that you enter for compute profile must be the same that you use when creating an image.

   # hammer compute-profile values create \
   --compute-profile "compute_profile_name" \
   --compute-resource azure_cr_name \
   --compute-attributes="resource_group=resource_group,vm_size=Standard_B1s,username=azure_user,password=azure_password,platform=Linux,script_command=touch /var/tmp/text.txt" \
   --interface="compute_public_ip=Dynamic,compute_network=mysubnetID,compute_private_ip=false"

   Optional: If you want to run scripts on the virtual machine after provisioning, specify the following settings:

   • To enter the script directly, with the script_command setting, enter a command to be executed on the provisioned virtual machine.
   • To run a script from a URI, with the script_uris setting, enter comma-separated file URIs of scripts to use. The scripts must contain sudo at the beginning because Red Hat Satellite downloads files to the /var/lib/waagent/custom-script/download/0/ directory on the host and therefore scripts require sudo privileges to be executed.

Procedure

1. In the Satellite web UI, navigate to Hosts > Create Host.
2. In the Name field, enter a name for the host.
3. Click the Organization and Location tabs to ensure that the provisioning context is automatically set to the current context.
4. From the Host Group list, select the host group that you want to use to populate the form.
5. From the Deploy on list, select the Microsoft Azure Resource Manager connection.
6. From the Compute Profile list, select a profile to use to automatically populate virtual machine settings.
7. Click the Interface tab and click Edit on the host’s interface.

8. Verify that the fields are automatically populated, particularly the following items:

   • The Name from the Host tab becomes the DNS name.
   • The MAC address field is blank. Microsoft Azure Resource Manager assigns a MAC address to the host during provisioning.
   • The Azure Subnet field is populated with the required Azure subnet.
   • The Managed, Primary, and Provision options are automatically selected for the first interface on the host. If not, select them.
9. Optional: If you want to use a static private IP address, from the IPv4 Subnet list select the Satellite subnet with the Network Address field matching the Azure subnet address. In the IPv4 Address field, enter an IPv4 address within the range of your Azure subnet.
10. Click the Operating System tab, and confirm that all fields automatically contain values.
11. In the Root Password field, enter the root password to authenticate with.
12. Click Resolve in Provisioning templates to check the new host can identify the right provisioning templates to use.
13. Click the Virtual Machine tab and confirm that these settings are populated with details from the host group and compute profile. Modify these settings to suit your needs.
14. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.
15. Click Submit to save the host entry.