Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
ContentsContents
Deployment Guide using Cloud Lifecycle Manager
  1. I Planning an Installation using Cloud Lifecycle Manager
    1. 1 Registering SLES
    2. 2 Hardware and Software Support Matrix
    3. 3 Recommended Hardware Minimums for the Example Configurations
    4. 4 High Availability
  2. II Cloud Lifecycle Manager Overview
    1. 5 Input Model
    2. 6 Configuration Objects
    3. 7 Other Topics
    4. 8 Configuration Processor Information Files
    5. 9 Example Configurations
    6. 10 Modifying Example Configurations for Compute Nodes
    7. 11 Modifying Example Configurations for Object Storage using Swift
    8. 12 Alternative Configurations
  3. III Pre-Installation
    1. 13 Overview
    2. 14 Pre-Installation Checklist
    3. 15 Installing the Cloud Lifecycle Manager server
    4. 16 Installing and Setting Up an SMT Server on the Cloud Lifecycle Manager server (Optional)
    5. 17 Software Repository Setup
    6. 18 Boot from SAN and Multipath Configuration
  4. IV Cloud Installation
    1. 19 Overview
    2. 20 Preparing for Stand-Alone Deployment
    3. 21 Installing with the Install UI
    4. 22 Using Git for Configuration Management
    5. 23 Installing a Stand-Alone Cloud Lifecycle Manager
    6. 24 Installing Mid-scale and Entry-scale KVM
    7. 25 DNS Service Installation Overview
    8. 26 Magnum Overview
    9. 27 Installing ESX Computes and OVSvAPP
    10. 28 Integrating NSX for vSphere
    11. 29 Installing Baremetal (Ironic)
    12. 30 Installation for SUSE OpenStack Cloud Entry-scale Cloud with Swift Only
    13. 31 Installing SLES Compute
    14. 32 Installing manila and Creating manila Shares
    15. 33 Installing SUSE CaaS Platform heat Templates
    16. 34 Installing SUSE CaaS Platform v4 using terraform
    17. 35 Integrations
    18. 36 Troubleshooting the Installation
    19. 37 Troubleshooting the ESX
  5. V Post-Installation
    1. 38 Post Installation Tasks
    2. 39 UI Verification
    3. 40 Installing OpenStack Clients
    4. 41 Configuring Transport Layer Security (TLS)
    5. 42 Configuring Availability Zones
    6. 43 Configuring Load Balancer as a Service
    7. 44 Other Common Post-Installation Tasks
  6. VI Support
    1. 45 FAQ
    2. 46 Support
    3. 47 Applying PTFs (Program Temporary Fixes) Provided by SUSE L3 Support
    4. 48 Testing PTFs (Program Temporary Fixes) on a Single Node
Navigation
Applies to SUSE OpenStack Cloud 9

40 Installing OpenStack Clients Edit source

If you have a standalone deployer, the OpenStack CLI and other clients will not be installed automatically on that node. If you require access to these clients, you will need to follow the procedure below to add the appropriate software.

  1. [OPTIONAL] Connect to your standalone deployer and try to use the OpenStack CLI:

    source ~/keystone.osrc
    openstack project list
    
    -bash: openstack: command not found
  2. Edit the configuration file containing details of your Control Plane, typically ~/openstack/my_cloud/definition/data/control_plane.yml.

  3. Locate the stanza for the cluster where you want to install the client(s). For a standalone deployer, this will look like the following extract:

          clusters:
            - name: cluster0
              cluster-prefix: c0
              server-role: LIFECYCLE-MANAGER-ROLE
              member-count: 1
              allocation-policy: strict
              service-components:
                - ntp-server
                - lifecycle-manager
  4. Choose the client(s) you wish to install from the following list of available clients:

     - barbican-client
     - ceilometer-client
     - cinder-client
     - designate-client
     - glance-client
     - heat-client
     - ironic-client
     - keystone-client
     - magnum-client
     - manila-client
     - monasca-client
     - neutron-client
     - nova-client
     - ntp-client
     - octavia-client
     - openstack-client
     - swift-client
  5. Add the client(s) to the list of service-components - in this example, we add the openstack-client to the standalone deployer:

          clusters:
            - name: cluster0
              cluster-prefix: c0
              server-role: LIFECYCLE-MANAGER-ROLE
              member-count: 1
              allocation-policy: strict
              service-components:
                - ntp-server
                - lifecycle-manager
                - openstack-client
                - cinder-client
                - designate-client
                - glance-client
                - heat-client
                - ironic-client
                - keystone-client
                - neutron-client
                - nova-client
                - swift-client
                - monasca-client
                - barbican-client
    
  6. Commit the configuration changes:

    cd ~/openstack/ardana/ansible
    git add -A
    git commit -m "Add explicit client service deployment"
  7. Run the configuration processor, followed by the ready-deployment playbook:

    cd ~/openstack/ardana/ansible
    ansible-playbook -i hosts/localhost config-processor-run.yml -e encrypt="" \
      -e rekey=""
    ansible-playbook -i hosts/localhost ready-deployment.yml
  8. Add the software for the clients using the following command:

    cd ~/scratch/ansible/next/ardana/ansible
    ansible-playbook -i hosts/verb_hosts clients-upgrade.yml
  9. Check that the software has been installed correctly. In this instance, connect to your standalone deployer and try to use the OpenStack CLI:

    source ~/keystone.osrc
    openstack project list

    You should now see a list of projects returned:

    stack@ardana-cp1-c0-m1-mgmt:~$ openstack project list
    
    +----------------------------------+------------------+
    | ID                               | Name             |
    +----------------------------------+------------------+
    | 076b6e879f324183bbd28b46a7ee7826 | kronos           |
    | 0b81c3a9e59c47cab0e208ea1bb7f827 | backup           |
    | 143891c2a6094e2988358afc99043643 | octavia          |
    | 1d3972a674434f3c95a1d5ed19e0008f | glance-swift     |
    | 2e372dc57cac4915bf06bbee059fc547 | glance-check     |
    | 383abda56aa2482b95fb9da0b9dd91f4 | monitor          |
    | 606dd3b1fa6146668d468713413fb9a6 | swift-monitor    |
    | 87db9d1b30044ea199f0293f63d84652 | admin            |
    | 9fbb7494956a483ca731748126f50919 | demo             |
    | a59d0c682474434a9ddc240ddfe71871 | services         |
    | a69398f0f66a41b2872bcf45d55311a7 | swift-dispersion |
    | f5ec48d0328d400992c1c5fb44ec238f | cinderinternal   |
    +----------------------------------+------------------+
Print this page