3 Installing the Administration Server #

Start the installation by booting into the SUSE Linux Enterprise Server 12 SP4 installation system. For an overview of a default SUSE Linux Enterprise Server installation, refer to https://documentation.suse.com/sles/15-SP1/single-html/SLES-deployment/#cha-install.

The following sections will only cover the differences from the default installation process.

Registering SUSE Linux Enterprise Server 12 SP4 during the installation process is required for getting product updates and for installing the SUSE OpenStack Cloud Crowbar extension.

After a successful registration you will be asked whether to add the update repositories. If you agree, the latest updates will automatically be installed, ensuring that your system is on the latest patch level after the initial installation. We strongly recommend adding the update repositories immediately. If you choose to skip this step you need to perform an online update later, before starting the SUSE OpenStack Cloud Crowbar installation.

Note: SUSE Login Required

To register a product, you need to have a SUSE login. If you do not have such a login, create it at http://www.suse.com/.

SUSE OpenStack Cloud is an extension to SUSE Linux Enterprise Server. Installing it during the SUSE Linux Enterprise Server installation is the easiest and recommended way to set up the Administration Server. To get access to the extension selection dialog, you need to register SUSE Linux Enterprise Server 12 SP4 during the installation. After a successful registration, the SUSE Linux Enterprise Server 12 SP4 installation continues with the Extension & Module Selection. Choose SUSE OpenStack Cloud Crowbar 9 and provide the registration key you obtained by purchasing SUSE OpenStack Cloud Crowbar. The registration and the extension installation require an Internet connection.

Alternatively, install the SUSE OpenStack Cloud Crowbar after the SUSE Linux Enterprise Server 12 SP4 installation via YaST › Software › Add-On Products. For details, refer to the section https://documentation.suse.com/sles/15-SP1/single-html/SLES-deployment/#sec-yast-install-modules.

Currently, Crowbar requires /opt to be writable. We recommend creating a separate partition or volume formatted with XFS for /srv with a size of at least 30 GB.

The default file system on SUSE Linux Enterprise Server 12 SP4 is Btrfs with snapshots enabled. SUSE OpenStack Cloud Crowbar installs into /opt, a directory that is excluded from snapshots. Reverting to a snapshot may therefore break the SUSE OpenStack Cloud Crowbar installation. We recommend disabling Btrfs snapshots on the Administration Server.

Help on using the partitioning tool is available at the section https://documentation.suse.com/sles/15-SP1/single-html/SLES-deployment/#sec-expert-partitioner.

In the final installation step, Installation Settings, you need to adjust the software selection and the firewall settings for your Administration Server setup. For more information refer to the https://documentation.suse.com/sles/15-SP1/single-html/SLES-deployment/#sec-yast-install-perform.

3.5.1 Software Selection #

 

Installing a minimal base system is sufficient to set up the Administration Server. The following patterns are the minimum required:

• Base System

• Minimal System (Appliances)

• Meta Package for Pattern cloud_admin (in case you have chosen to install the SUSE OpenStack Cloud Crowbar Extension)

• Subscription Management Tool (optional, also see Tip: Installing a Local SMT Server (Optional))

Tip: Installing a Local SMT Server (Optional)

If you do not have a SUSE Manager or SMT server in your organization, or are planning to manually update the repositories required for deployment of the SUSE OpenStack Cloud nodes, you need to set up an SMT server on the Administration Server. Choose the pattern Subscription Management Tool in addition to the patterns listed above to install the SMT server software.

3.5.2 Firewall Settings #

 

SUSE OpenStack Cloud Crowbar requires disabling the firewall on the Administration Server. You can disable the firewall during installation in the Firewall and SSH section. If your environment requires a firewall to be active at this stage of the installation, you can disable the firewall during your final network configuration (see Chapter 6, Service Configuration: Administration Server Network Configuration). Optionally, you can also enable SSH access to the Administration Server in this section.

Warning: HTTP_PROXY and NO_PROXY

Setting HTTP_PROXY without properly configuring NO_PROXY for the Administration Server might result in chef-client failing in non-obvious ways.