Initial Preparation and Configuration of the Microsoft Azure Image

Procedure: Configuring your Uyuni instance
  1. Start by logging into your Azure account at Azure Portal.

  2. In the Azure Portal, find the menu:[Virtual Machines] section. This can be done either through the dashboard or by using the search bar.

  3. Select menu:[Create a resource] in the top left corner of the portal.

  4. Choose menu:[Compute] and then select menu:[Virtual Machine].

  5. You will be guided through the Create a virtual machine process.

  6. Fill in the required details such as subscription, resource group, and VM name.

  7. Choose a region for your VM. Ensure it complies with any geo-fencing policies you might have.

  8. In the Image dropdown, select the manager-server-4-3-ltd or the manager-server-4-3-llc image for your VM. If the image is not listed, select Browse all public and private images to find the required image.

  9. Suggested sizes are selected by default for this VM. Configure optional features such as virtual CPUs, memory as required.

  10. Set up an administrator account for the VM. For SUSE Linux Enterprise Server, this can be a username and SSH public key.

  11. Ensure the VM is connected to the appropriate virtual network (VNet) and subnet, especially if it needs to communicate with other specific services like Uyuni. For network requirements, see Azure Server Setup: Network Configuration.

  12. Configure additional settings such as storage, monitoring, or any extensions you may need. The following partitions are created by default when initializing the Microsoft Azure image:

    • 100 GB for the root partition

    • 500 GB for spacewalk storage

    • 80 GB for the database.

  13. Once all configurations are set, review the settings.

  14. Click "Create" to deploy your VM.

  15. After the VM is deployed, you can access it via SSH.

Usage and Costs

Keep in mind that since this is a PAYG image, you will be billed according to your actual usage, including the number of systems you manage and monitor with this instance. It’s essential to regularly track and review your usage to prevent unexpected costs and ensure alignment with your needs.