Setting Up

We have tested these instructions on Amazon EC2, Google Compute Engine, and Microsoft Azure, but they should work on other providers as well, with some variation.

You need to start by logging in to your chosen public cloud provider, and launching a Uyuni instance.

Depending on the public cloud you are using, you can usually locate the Uyuni Server images by searching for suse manager. In EC2, you will need to search within the Community AMIs. In GCE and Azure, search the marketplace.

As you prepare your new instance, pay attention to these settings:

For hardware, select an instance with at least:

  • 32 GB RAM

  • 8 cores

For more information about hardware requirements, see Hardware Requirements.

For network security and access settings, you will need to enable HTTPS access. This allows you to access the Uyuni Web UI.

In EC2 and Azure, create a new security group, and add inbound and outbound rules for HTTPS. In GCE, check the Allow HTTPS traffic box under the Firewall section.

When running Uyuni on public clouds, make sure you apply security measures to limit access to the right people. A world-accessible Uyuni would give access to your infrastructure to anyone, and could breach your SUSE support agreement.

For storage settings, ensure the root volume of the Uyuni Server is 100 GB or larger. Add an additional storage disk of 500 GB or more, and choose SSD storage if you can. The cloud images for Uyuni Server use a script to assign this separate volume when your instance is launched. The name of the device node will vary depending on your provider, and the instance type you selected.

When you launch your instance, you can log in to the Uyuni Server and use this command to find all available storage devices:

hwinfo --disk | grep -E "Device File:"

If you are not sure which device to choose, use the lsblk command to see the name and size of each device. Choose the name that matches with the size of the virtual disk you are looking for.

You can set up the external disk with the suma-storage command. This creates an XFS partition mounted at /manager_storage and uses it as the location for the database and repositories:

/usr/bin/suma-storage <devicename>

For more information about setting up a public cloud instance, see Public Cloud Requirements.