Public Cloud

Some public cloud environments provide images for Uyuni Server and Proxy. This section discusses what you will require to run Uyuni in a public cloud, and how to set up your installation.

Public clouds provide Uyuni under a Bring Your Own Subscription (BYOS) model. This means that you must register them with the SUSE Customer Center. For more information about registering Uyuni with SUSE Customer Center, see installation:general-requirements.adoc.

Depending on the public cloud network you are using, you can locate the Uyuni installation images by searching for the keywords suse, manager, proxy, or BYOS.

Instance Requirements

Select a public cloud instance that meets the hardware requirements in installation:hardware-requirements.adoc.

In addition, be aware of these considerations:

  • The Uyuni setup procedure performs a forward-confirmed reverse DNS lookup. This must succeed in order for the setup procedure to complete successfully and for Uyuni to operate as expected. Therefore, it is important to perform hostname and IP configuration prior to running the Uyuni setup procedure.

  • Uyuni server and proxy instances are expected to run in a network configuration that provides you control over DNS entries, but cannot access the wider internet. Within this network configuration DNS resolution must be provided: hostname -f must return the fully-qualified domain name (FQDN). DNS resolution is also important for connecting clients. DNS is dependent on the cloud framework you choose, refer to the cloud service provider documentation for detailed instructions.

  • We recommend that you locate software repositories, the server database, and the proxy squid cache on an external virtual disk. This prevents data loss if the instance is unexpectedly terminated. Instructions for setting up an external virtual disk are contained in this section.

Network Setup

On a public cloud service, you must run Uyuni within a restricted network, such as VPC private subnet with an appropriate firewall setting. The instance must only be able to be accessed by machines in your specified IP ranges.

A world-accessible Uyuni instance violates the terms of the Uyuni EULA, and it will not be supported by SUSE.

To access the Uyuni Web UI, allow HTTPS when you set up your networking environment.

Set the Hostname

Uyuni requires a stable and reliable hostname. Changing the hostname at a later point can create errors.

In most public cloud environments, the method shown in this section will work correctly. However, you will have to perform the same modification for every client.

You might prefer to manage DNS resolution by creating a DNS entry in your network environment instead.

You can also manage hostname resolution by editing the /etc/resolv.conf file. Depending on the order of your setup, if you start the Uyuni instance prior to setting up DNS services the file may not contain the appropriate search directive. Check that the proper search directive exists in /etc/resolv.conf and add it if it is missing.

Procedure: Setting the hostname locally
  1. Disable hostname setup by editing the DHCP configuration file at /etc/sysconfig/network/dhcp, and adding this line:

    DHCLIENT_SET_HOSTNAME="no"
  2. Set the hostname locally with the hostnamectl command. Ensure you use the system name, not the FQDN. For example, if the FQDN is system_name.example.com, the system name is system_name, and the domain name is example.com.

    # hostnamectl set-hostname system_name
  3. Create a DNS entry in your network environment for domain name resolution, or force correct resolution by editing the /etc/hosts file:

    # echo "${local_address} suma.cloud.net suma" >> /etc/hosts

    You can find the local address by checking your public cloud web console, or from the command line:

    • Amazon EC2 instance:

      # ec2metadata --local-ipv4
    • Google Compute Engine:

      # gcemetadata --query instance --network-interfaces --ip
    • Microsoft Azure:

      # azuremetadata --internal-ip

Set up DNS Resolution

You will need to update the DNS records for the instance within the DNS service of your network environment. Refer to the cloud service provider documentation for detailed instructions: * DNS setup on Amazon EC2 * DNS setup on Google Compute Engine * DNS setup on Microsoft Azure

If you run a Uyuni Server instance, ensure the external storage is attached and prepared correctly, and that DNS resolution is set up as described. Start the susemanager_setup with YaST:

# /sbin/yast2 susemanager_setup