17 Software Repository Setup #
Software repositories containing products, extensions, and the respective updates for all software need to be available to all nodes in SUSE OpenStack Cloud in order to complete the deployment. These can be managed manually, or they can be hosted on the Cloud Lifecycle Manager server. In this configuration step, these repositories are made available on the Cloud Lifecycle Manager server. There are two types of repositories:
Product Media Repositories: Product media repositories are copies of the installation media. They need to be directly copied to the Cloud Lifecycle Manager server, “loop-mounted” from an iso image, or mounted from a remote server via NFS. Affected are SUSE Linux Enterprise Server 12 SP4 and SUSE OpenStack Cloud 9. These are static repositories; they do not change or receive updates. See Section 17.1, “Copying the Product Media Repositories” for setup instructions.
Update and Pool Repositories: Update and Pool repositories are provided by the SUSE Customer Center. They contain all updates and patches for the products and extensions. To make them available for SUSE OpenStack Cloud they need to be mirrored from the SUSE Customer Center. Their content is regularly updated, so they must be kept in synchronization with SUSE Customer Center. For these purposes, SUSE provides the Subscription Management Tool (SMT). See Section 17.2, “Update and Pool Repositories” for setup instructions.
17.1 Copying the Product Media Repositories #
The files in the product repositories for SUSE OpenStack Cloud do not
change, therefore they do not need to be synchronized with a remote
source. If you have installed the product media from a downloaded ISO image,
the product repositories will automatically be made available to the client
nodes and these steps can be skipped. These steps can also be skipped if you
prefer to install from the Pool repositories provided by SUSE Customer Center. Otherwise,
it is sufficient to either copy the data (from a remote host or the
installation media), to mount the product repository from a remote server
via NFS, or to loop mount a copy of the installation
images.
If you choose to install from the product media rather than from the SUSE Customer Center repositories, the following product media needs to reside in the specified directories:
|
Repository |
Directory |
|---|---|
|
SUSE OpenStack Cloud 9 DVD #1 |
|
The data can be copied by a variety of methods:
- Copying from the Installation Media
We recommend using
rsyncfor copying. If the installation data is located on a removable device, make sure to mount it first (for example, after inserting the DVD1 in the Cloud Lifecycle Manager and waiting for the device to become ready):SUSE OpenStack Cloud 9 DVD#1 #
mkdir -p /srv/www/suse-12.4/x86_64/repos/Cloud mount /dev/dvd /mnt rsync -avP /mnt/ /srv/www/suse-12.4/x86_64/repos/Cloud/ umount /mnt
- Copying from a Remote Host
If the data is provided by a remote machine, log in to that machine and push the data to the Cloud Lifecycle Manager (which has the IP address
192.168.245.10in the following example):SUSE OpenStack Cloud 9 DVD#1 #
mkdir -p /srv/www/suse-12.4/x86_64/repos/Cloud rsync -avPz /data/SUSE-OPENSTACK-CLOUD//DVD1/ 192.168.245.10:/srv/www/suse-12.4/x86_64/repos/Cloud/
- Mounting from an NFS Server
If the installation data is provided via NFS by a remote machine, mount the respective shares as follows. To automatically mount these directories either create entries in
/etc/fstabor set up the automounter.SUSE OpenStack Cloud 9 DVD#1 #
mkdir -p /srv/www/suse-12.4/x86_64/repos/Cloud/ mount -t nfs nfs.example.com:/exports/SUSE-OPENSTACK-CLOUD/DVD1/ /srv/www/suse-12.4/x86_64/repos/Cloud
17.2 Update and Pool Repositories #
Update and Pool Repositories are required on the Cloud Lifecycle Manager server to set up and maintain the SUSE OpenStack Cloud nodes. They are provided by SUSE Customer Center and contain all software packages needed to install SUSE Linux Enterprise Server 12 SP4 and the extensions (pool repositories). In addition, they contain all updates and patches (update repositories).
The repositories can be made available on the Cloud Lifecycle Manager server using one or more of the following methods:
17.2.1 Repositories Hosted on an SMT Server Installed on the Cloud Lifecycle Manager #
When all update and pool repositories are managed by an SMT server installed on the Cloud Lifecycle Manager server (see Chapter 16, Installing and Setting Up an SMT Server on the Cloud Lifecycle Manager server (Optional)), the Cloud Lifecycle Manager automatically detects all available repositories. No further action is required.
17.2.2 Alternative Ways to Make the Repositories Available #
If you want to keep your SUSE OpenStack Cloud network as isolated from the company network as possible, or your infrastructure does not allow accessing a SUSE Manager or an SMT server, you can alternatively provide access to the required repositories by one of the following methods:
Mount the repositories from a remote server.
Synchronize the repositories from a remote server (for example via
rsyncand cron).Manually synchronize the update repositories from removable media.
The repositories must be made available at the default locations on the Cloud Lifecycle Manager server as listed in Table 17.3, “Repository Locations on the Cloud Lifecycle Manager server”.
17.3 Repository Locations #
The following tables show the locations of all repositories that can be used for SUSE OpenStack Cloud.
|
Repository |
Directory |
|---|---|
|
Mandatory Repositories | |
|
SLES12-SP4-Pool |
|
|
SLES12-SP4-Updates |
|
|
SUSE-OpenStack-Cloud-9-Pool |
|
|
SUSE-OpenStack-Cloud-9-Updates |
|
The following table shows the required repository locations to use when manually copying, synchronizing, or mounting the repositories.
|
Channel |
Directory on the Cloud Lifecycle Manager |
|---|---|
|
Mandatory Repositories | |
|
SLES12-SP4-Pool |
|
|
SLES12-SP4-Updates |
|
|
SUSE-OpenStack-Cloud-9-Pool |
|
|
SUSE-OpenStack-Cloud-9-Updates |
|