Initial Setup

Procedure: Log in and Update the System

  1. Within the Managed Resource group you have set up, you will find the virtual machine. To get the details, click on the name of the virtual machine. Here you can see the (public) IP address which you need to connect to the running instance. SSH into your Microsoft Azure instance.

  2. Switch to the root user and update the system .

    sudo -i
transactional-update

  3. Reboot the system.

1. Network Configuration

Remember, the SUSE Manager PAYG setup requires, that a new Virtual Network and a new subnet is configured, which was performed in the previous step.

Because SUSE Manager PAYG is deployed as a 'Managed Application' it is not possible to deploy into an existing network.

Before moving on to the next step, ensure the network is correctly configured:

When you setup new clients which should be managed, take care that you put them into the private subnet which is configured with SUSE Manager PAYG or peer your networks.

If you want to manage systems in an already existing network, you must configure peering.

For more information, see Azure documentation.
Procedure: Network Configuration

  1. Ensure the network configuration aligns such that hostname -f yields the identical name as the reverse DNS lookup of the private IP address. For instance, when executing nslookup 10.0.0.X.

  2. Insert the private IP with its Fully Qualified Domain Name (FQDN) into /etc/hosts.

    For example:

    10.0.0.4 instancename.location.internal.cloudapp.azure.com

  3. Edit /etc/sysconfig/network/config and append internal.cloudapp.azure.com to NETCONFIG_DNS_STATIC_SEARCHLIST.

  4. Execute netconfig update.

  5. Subsequently, hostname -f should return the same FQDN as obtained from nslookup 10.0.0.X.

When adding new virtual machines (VMs), such as SUSE Linux Enterprise Server, it’s crucial to ensure that they are configured within the same subnet as the SUSE Manager instance, or that you have setup network peering. This step is essential for successful network setup and integration.

Additionally, be mindful of the geographical restrictions associated with your plans. Make sure to utilize the appropriate Azure accounts which correspond to the specific geographic zones of your project.

2. Configure Storage

Procedure: Configuring Storage

  1. SSH into your Microsoft Azure instance.

  2. Switch to the root user and update the system:

    sudo -i
transactional-update

  3. Reboot the system.

  4. Configure storage using the appropriate tool:

    • For a standard setup, use mgr-storage-server.

    • For a proxy configuration, use mgr-storage-proxy.

      For more details, run:

      mgr-storage-server --help
mgr-storage-proxy --help

    These tools simplify the creation of container storage and database volumes.

  5. Identify the block devices:

    ls /dev/disk/azure/scsi1/

    This command lists the disks created during deployment. Typically:

    • lun3 is the storage disk.

    • lun4 is the database disk.

  6. Configure storage using the identified devices:

    mgr-storage-server /dev/disk/azure/scsi1/lun3 /dev/disk/azure/scsi1/lun4

    This command creates persistent storage volumes at:

    /var/lib/containers/storage/volumes

    For more details, see List of persistent storage volumes.

  7. Deploy using mgradm as root:

    mgradm install podman <FQDN>