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. By default, the Cloud is set to Public/Standard. Azure Government Cloud supports the following regions:

   • US Government
   • China
   • Germany
6. In the Client ID field, enter your Application or client ID.
7. In the Client Secret field, enter your client secret.
8. In the Subscription ID field, enter your subscription ID.
9. In the Tenant ID field, enter your Directory or tenant ID.
10. Click Load Regions. This tests if your connection to Azure Resource Manager is successful and loads the regions available in your subscription.
11. From the Azure Region list, select the Azure region to use.
12. 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 base operating system of the image.
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 Azure Image Name field, enter an image name in the format prefix://UUID.

   • For a custom image, use the prefix custom. For example, custom://image-name.
   • For a shared gallery image, use the prefix gallery. For example, gallery://image-name.

   • For public and RHEL Bring Your Own Subscription (BYOS) images, use the prefix marketplace. For example, marketplace://OpenLogicCentOS:7.5:latest.

     For more information, see Find Linux VM images in the Azure Marketplace with the Azure CLI.

9. Optional: Select the User Data checkbox 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.
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 checkbox.
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. Optional: You can add a NVIDIA Driver by selecting the NVIDIA driver / CUDA checkbox. For more information, refer to the following Microsoft Azure documentation:

    • NVIDIA GPU Driver Extension for Linux
    • NVIDIA GPU Driver Extension for Windows

14. Optional: If you want to create an additional volume on the VM, click the Add Volume button, enter the Size in GB and select the Data Disk Caching method.

    • Note that the maximum number of these disks depends on the VM Size selected. For more information on Microsoft Azure VM storage requirements, see the Microsoft Azure documentation.

15. Click Add Interface.

    Important

    The maximum number of interfaces depends on the VM Size selected. For more information, see the Microsoft Azure documentation link above.

16. From the Azure Subnet list, select the Azure subnet to provision to.
17. From the Public IP list, select the public IP setting.
18. Optional: If you want the virtual machine to use a static private IP, select the Static Private IP checkbox.
19. Click Submit.

CLI procedure

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-attributes="resource_group=resource_group,vm_size=Standard_B1s,username=azure_user,password=azure_password,platform=Linux,script_command=touch /var/tmp/text.txt" \
   --compute-profile "compute_profile_name" \
   --compute-resource azure_cr_name \
   --interface="compute_public_ip=Dynamic,compute_network=mysubnetID,compute_private_ip=false" \
   --volume="disk_size_gb=5,data_disk_caching=None"

   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. Optional: Click the Organization tab and change the organization context to match your requirement.
4. Optional: Click the Location tab and change the location context to match your requirement.
5. From the Host Group list, select a host group that you want to assign your host to. That host group will populate the form.
6. From the Deploy on list, select the Microsoft Azure Resource Manager connection.
7. From the Compute Profile list, select a profile to use to automatically populate virtual machine settings.
8. From the Lifecycle Environment list, select the environment.
9. Click the Interfaces tab, and on the interface of the host, click Edit.

10. Verify that the fields are populated with values. Note in particular:

    • Satellite automatically assigns an IP address for the new host.
    • Ensure that the MAC address field is blank. Microsoft Azure Resource Manager assigns a MAC address to the host during provisioning.
    • The Name from the Host tab becomes the DNS name.
    • The Azure Subnet field is populated with the required Azure subnet.
    • 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.
    • Ensure that Satellite automatically selects the Managed, Primary, and Provision options for the first interface on the host. If not, select them.
11. Click OK to save. To add another interface, click Add Interface. You can select only one interface for Provision and Primary.
12. Click the Operating System tab, and confirm that all fields automatically contain values.
13. For Provisioning Method, ensure Image Based is selected.
14. From the Image list, select the Azure Resource Manager image that you want to use for provisioning.
15. In the Root Password field, enter the root password to authenticate with.
16. Click Resolve in Provisioning templates to check the new host can identify the right provisioning templates to use.
17. 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.
18. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.
19. Click Submit to save the host entry.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources.
2. Select your Microsoft Azure provider.
3. On the Virtual Machines tab, click Delete from the Actions menu. This deletes the virtual machine from the Microsoft Azure compute resource while retaining any associated hosts within Satellite. If you want to delete the orphaned host, navigate to Hosts > All Hosts and delete the host manually.

Procedure

1. Uninstall the Azure compute resource provider from your Satellite Server:

   # satellite-maintain packages remove rubygem-foreman_azure_rm rubygem-ms_rest_azure
   # satellite-installer --no-enable-foreman-plugin-azure

2. Optional: In the Satellite web UI, navigate to Administer > About and select the Available Providers tab to verify the removal of the Microsoft Azure plugin.