Chapter 2. Requirements

2.1. Software Requirements

2.1.1. Host Machines and Access

  • Each host machine in OpenStack must already be running Red Hat Enterprise Linux 7.2. For detailed information on installing Red Hat Enterprise Linux, see the corresponding installation guide at: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/
  • Host machines do not have to be dedicated OpenStack servers.
  • You must know the root password for all machines deployed by Packstack. Any compute node deployed by Packstack must be configured to allow access using the account of the root user over SSH on port 22.

2.1.2. Software Repositories

Each host machine deployed in OpenStack must be registered to receive updates from Red Hat Network using Subscription Manager. To allow Packstack to install OpenStack on each host, you can do either of the following:
  • Before running Packstack, use ssh to connect and manually register each host (see Procedure 2.1, “Manually Register and Subscribe your Host”). After subscribing each machine, you can then run Packstack in any mode.
  • Run Packstack with an edited Packstack answer file that contains your Red Hat subscription user name and password, using the parameters CONFIG_RH_USER and CONFIG_RH_PW. Running Packstack with this answer file configures each host to receive updates from Red Hat Network using Subscription Manager. For instructions on creating and using an answer file, see Section 3.3, “Running Packstack Non-Interactively”.

Note

Packstack registers systems to Red Hat Network using Subscription Manager. You might encounter problems if your systems have already been registered and subscribed to the Red Hat OpenStack channels using RHN Classic.

Procedure 2.1. Manually Register and Subscribe your Host

  1. As a root user, register the host with Customer Portal Subscription Management:
    # subscription-manager register
  2. Subscribe to the most likely entitlements for your user:
    # subscription-manager subscribe --auto

    Note

    If this does not automatically attach the OpenStack entitlement, you can do so manually:
    1. List all entitlements:
      # subscription-manager list --available
    2. Attach the entitlement using its pool ID:
      # subscription-manager attach --pool=POOL_ID
  3. Enable the correct repositories:
    #  subscription-manager repos --enable=rhel-7-server-rpms
    #  subscription-manager repos --enable=rhel-7-server-rh-common-rpms
    #  subscription-manager repos --enable=rhel-7-server-openstack-6.0-rpms
  4. Disable repositories that interfere with the current OpenStack release:
    #  subscription-manager repos --disable="cf-me-*"
    #  subscription-manager repos --disable="rhel-6-server-cf-*"
    #  subscription-manager repos --disable="rhel-6-server-rhev*"
    #  subscription-manager repos --disable="*-eus-rpms"
    #  subscription-manager repos --disable=rhel-6-server-openstack-4.0-rpms
    #  subscription-manager repos --disable=rhel-7-server-openstack-5.0-rpms
  5. Update your local repository information and local environment:
    # yum repolist
    # yum update -y
The system can now receive updates from Customer Portal Subscription Management.

2.1.3. Network Manager

OpenStack Networking currently does not work on systems that have the Network Manager service enabled. Follow the procedure below as the root user on each system in the environment, including the cloud controller (on which you run Packstack) and all compute nodes.

Procedure 2.2. Disable the Network Manager service

  1. Disable NetworkManager, then stop it:
    # systemctl disable NetworkManager.service
    # systemctl stop NetworkManager.service
  2. Start and enable the standard network service:
    # systemctl start network.service
    # systemctl enable network.service