Procedure 5.1. Quick Start Deployment using PackStack

1. • Single-node Deployment

     Run PackStack with the --allinone parameter to perform an "all in one" deployment on the local host. You are prompted to enter the password of the root user to facilitate SSH key installation.
     ⁠

     Example 5.1. Single-node Deployment using OpenStack Networking (default)

     In this example, PackStack is instructed to deploy an "all in one" installation to the local system, which results in the following:

     • OpenStack Networking is enabled by default.
     • An admin Identity service tenant is created along with a keystonerc_admin file. The admin password and other information are stored in the keystonerc_admin file, which is located in the /root directory, and also in the directory from which PackStack is run, if different from /root. The admin password is also stored as CONFIG_KEYSTONE_ADMIN_PW in PackStack's answer file.
     • A demo Identity service tenant is created, with its associated keystonerc_demo file, which can be sourced like the keystonerc_admin file. The demo password is also stored as CONFIG_KEYSTONE_DEMO_PW in PackStack's answer file.
     • The keys CONFIG_PROVISION_DEMO and CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE are automatically enabled in PackStack's answer file. This answer file will have a file name similar to /root/packstack-answers-20130306-051043.txt.
     • The OpenStack Dashboard is automatcially installed. After the installation is finished, you should log into the Dashboard using the demo account instead of the admin account due to the ownership of the private and public networks.

     # packstack --allinone

     ⁠

     Example 5.2. Single-Node Deployment without OpenStack Networking

     In this example, PackStack is instructed to deploy an "all in one" installation to the local system, but using only Compute networking.

     # packstack --allinone --os-neutron-install=n

   • Multiple-node Deployment

     Important

     Red Hat Enterprise Linux OpenStack Platform requires that each system in the OpenStack environment is running Red Hat Enterprise Linux Server, and that all systems are signed up to receive updates from Red Hat Network using Subscription Manager.

     See Section 2.1.2.2, “Register to Red Hat Network” for information on registering to Red Hat Network.

     • You can ssh into each node and register it, attach an OpenStack subscription, and enable the required OpenStack repository. This allows PackStack to install OpenStack on each node.
     • Alternatively, you can get PackStack to generate an answer file, then edit the answer file to contain your Red Hat subscription username and password, using the parameters CONFIG_RH_USER and CONFIG_RH_PW. Running PackStack with this answer file configures each node to receive updates from Red Hat Network using Subscription Manager. This allows PackStack to install OpenStack on each node.
       For instructions on generating and editing an answer file, see Section 5.3.1, “Generating a PackStack Answer File”.
     Run PackStack with the --install-hosts parameter. The parameter expects a comma-separated list of IP addresses. You will be prompted to enter the password of the root user of each system to facilitate SSH key installation.

     # packstack --install-hosts=CONTROLLER_ADDRESS,NODE_ADDRESSES

     Replace CONTROLLER_ADDRESS with the IP address of the system that you intend to use as a Controller node. Replace NODE_ADDRESSES with IP addresses of the systems that you intend to use as Compute nodes.
     ⁠

     Example 5.3. Multiple Node Deployment

     In this example, PackStack is instructed to deploy a controller node on the system with IP address 192.168.43.10.

     Additional Compute nodes are deployed on the systems with IP addresses 192.168.43.11 and 192.168.43.12.

     # packstack --install-hosts=192.168.43.10,192.168.43.11,192.168.43.12

2. PackStack will prompt you to enter the password of the root user for each system in the deployment. This is required to connect to the system and install Puppet which is the tool used to facilitate the rest of the deployment.

   root@192.168.43.10's password:

3. The Puppet manifests used to deploy each component will be run on each of the target systems. The amount of time this takes to complete varies based on the hardware and existing workload of each system. The time can be significant.
   PackStack provides continuous updates indicating which manifests are being deployed as it progresses through the deployment process. Once the process is completed, a confirmation message similar to the one shown below will be displayed:

   **** Installation completed successfully ******

   Additional information regarding the locations of the answer file and other files is given. Depending on the options you chose, the following screen's content will vary:

   Additional information:
    * A new answerfile was created in: /root/packstack-answers-20131205-155916.txt
    * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
    * File /root/keystonerc_admin has been created on OpenStack client host 192.168.43.10. To use the command line tools you need to source the file.
    * To use the console, browse to http://192.168.43.10/dashboard
    * To use Nagios, browse to http://192.168.43.10/nagios username : nagiosadmin, password : abcdefgh12345678
    * The installation log file is available at: /var/tmp/packstack/20131205-155915-tZ0BTD/openstack-setup.log
    * The generated manifests are available at: /var/tmp/packstack/20131205-155915-tZ0BTD/manifests

Procedure 5.2. Viewing the created network

1. Retrieve the URL shown in the "Additional information" output shown above, and the demo tenant password in /root/keystonerc_demo.
2. Type the URL into a browser to access the Dashboard:

   http://HOSTNAME/dashboard/

   Replace HOSTNAME with the host name or IP address of the server on which you ran PackStack.
   ⁠

   

   Figure 5.1. Log In Screen

3. Type demo as the User Name and the password in /root/keystonerc_demo as the Password.
4. Click Sign In.
5. After signing in to the Dashboard, you can see details of the "all in one" deployment. For example, to see the basic network set-up, select the Project tab and choose Network Topology.
   ⁠

   

   Figure 5.2. Default deployed network