Initial setup

Procedure: Login and update the system

  1. SSH into your Microsoft Azure instance.

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

    sudo -i
zypper refresh
zypper update

1. Network Configuration

Before initiating yast2 susemanager_setup, ensure the network is correctly configured for Microsoft Azure.

For SUSE Manager PAYG setup it is required, that a new Virtual Network and a new subnet is configured. It is impossible to setup the instance in an existing network. 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.

If you want to manage systems in an already existing network, you must configure peering.
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.internal.cloudapp.net

  3. Edit /etc/sysconfig/network/config and append internal.cloudapp.net 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 15 SP5, it’s crucial to ensure that they are configured within the same subnet as the SUSE Manager instance. 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

  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 with the mgr-storage-server tool or in the case of the proxy use mgr-storage-proxy. For more information, see mgr-storage-server --help or mgr-storage-proxy --help. This tool simplifies creating the container storage and database volumes.

  5. Format the command in the following manner:

    mgr-storage-server <storage-disk-device> [<database-disk-device>]

#For example:

mgr-storage-server /dev/nvme1n1 /dev/nvme2n1

    This command will create the following persistent storage volumes at /var/lib/containers/storage/volumes:

    For more information, see List of persistent storage volumes.

  6. As root run mgradm install podman <FQDN> to deploy.