IBM Cloud Manager
with OpenStack
Download Trial Guide
Cloud Solutions Team:
Table of Contents
Chapter 1: Introduction... 3
Development cycle release scope...3
Development cycle release limitations...4
Chapter 2: Getting Started...5
Request for IBM Cloud Manager with OpenStack Download Trial:...5
Before Using IBM Cloud Manager with OpenStack Installer...9
Chapter 1: Introduction
Welcome to the IBM Cloud Manager with OpenStack v4.1 download trial guide. With IBM Cloud Manager with OpenStack, you can maintain control over the allocation of resources with a web-based application. This download trial allows you to preview and interact with new features that are being developed for the 4.1 version of IBM Cloud Manager with OpenStack. In contrast to the hosted trial, that does not require any hardware allocation; the download trial enables you to install an IBM Cloud Manager with OpenStack environment on a premise of your choice.
IBM Cloud Manager with OpenStack v4.1 features:
• Support for the latest OpenStack community release (Icehouse) • Full access to the OpenStack APIs across all core projects • Chef deployment for rapid installation and configuration
Development cycle release scope
The intended scope of this trial is to implement this topology:
• A deployment server
• An openstack controller server (x86 KVM w RHEL 6.5) • n * openstack/KVM x86_64 compute nodes
The download trial is intended for RHEL 6.5 x86_64. The deployment server and the controller can be implemented as virtual machine, while the compute nodes are expected to be implemented on RHELs 6.5 running directly on physical hardware. The PRS scheduler is available for use and users have the option of using the PRS scheduler for their scheduling needs.
Development cycle release limitations
• While the product will ship a rich set of supported cloud targets, this development cycle release is limited to openstack/KVM/RHELs 6.5 x86_64 only.
For more information about some of the features that are included in the product, you can reference the existing documentation for IBM SmartCloud Entry on the Documentation page.
Chapter 2: Getting Started
Request for IBM Cloud Manager with OpenStack Download Trial:
Go to the following site and request access to the download trial.
http://www.ibm.com/developerworks/servicemanagement/cvm/sce/downloads.html
Step 2): If you do not have a universal IBM User ID, click “register here” to create an IBM ID. Then, log in using your IBM ID and Password.
You can download the installer files using either Download Director or http. Make sure to select all of the files shown below:
Step 3): Select the preferred installer file(s) and click on “Download now”. If you are downloading using Download Director make sure to click on “Run” to enable the Download Director applet and allow access for IBM Download Director.
Before Using IBM Cloud Manager with OpenStack Installer
Please make sure to review the prerequisites before using the installer. IBM Cloud Manager with OpenStack hardware prerequisites:
Component Minimum hardware requirements Recommended hardware requirements
IBM Cloud Manager with OpenStack deployment server
• 0.5 CPUs
• Free disk space: 4 GB for /opt/ibm/cmwo
• Free disk space: 4.5 GB of tempor-ary space while installing, 2 GB for the chef server and running the product.
• 16 GB physical memory (using 7.8 GB with system idle)
• 2 CPUs
• 25 GB free disk space
• 16 GB physical memory
OpenStack controller
• 4 CPUs
• 16 GB physical memory
• 6 GB free disk space for installed code and empty databases
• 4 CPUs
• 16 GB physical memory
• 6 GB free disk space for in-stalled code and empty databases (4 GB for DB2 and databases) Standalone DB2® 4 GB for DB2 and empty databases 4 GB for DB2 and empty databases
Compute nodes
For specific requirements, see information about the applicable virtualization
environment from the latest product administrator guide.
Supported IBM Cloud Manager with OpenStack operating systems:
Operating system Versions Notes
Red Hat Enterprise
Linux Version 6.4 and 6.5 (64-bit) • With latest fix pack
Supported IBM Cloud Manager with OpenStack databases:
Database Versions Notes
DB2® 10.5 • With service pack 3
MySQL 5.1.x • For Red Hat Enterprise Linux versions 6.4 and 6.5 on x86 systems
Supported IBM Cloud Manager with OpenStack web browsers:
Browser Versions Notes
Internet Explorer 9.0 or 10.0
• With latest fix pack
• Minimum resolution of 1024x768 (or greater)
• Internet Explorer 9 or 10 compatibility view is not supported
Firefox ESR 18, 24 • With latest fix pack
• Minimum resolution of 1024x768 (or greater) Chrome 24, 30 • With latest fix pack
Safari 6 • With latest fix pack
Supported IBM Cloud Manager with OpenStack user registries
User registry Versions Notes
IBM Cloud Manager with OpenStack
Local identity storage and authentication
• The IBM Cloud Manager with OpenStack database is used to store identity artifacts including credentials.
• Intended for small-scale usage, such as proof-of-concept scenarios, demonstrations, or environments with up to 30 users and projects
Lightweight Directory Access Protocol (LDAP) Version 3
IBM Tivoli® Directory
Server Version 6.1 • Intended for production environments to provide the highest level of security.
• Scales to hundreds or thousands of users and projects.
• Supports TLS (transaction level security). Microsoft Active Directory
6.1.7601.17514
OpenLDAP Version 2.4.x
When you install IBM Cloud Manager with OpenStack the installation process sets up the system as a deployment server. The installation process completes the following tasks:
• Installs and configures the chef-server
• Installs the IBM OpenStack RPM files in a yum repository on the management server • Uploads the OpenStack cookbooks, roles, data bags and sample environments to the
chef-server
• Installs an IBM extension to the chef knife command that enables IBM OpenStack topology deployments
You can install IBM Cloud Manager with OpenStack on Linux by using console, graphical user
interface, or silent installation. For detailed instructions please consult the latest product administrator guide from the Documentation page.
Installing the deployment server on RHEL 6.5 x86_64
Note: Please follow the simple instructions to get started. For detailed instructions please consult the latest product administrator guide from the Documentation page.
Before installing the Chef server make sure that the nodes have a fully qualified domain name that includes the domain suffix. For example, a fully qualified domain name is
mydeploymentserver.ibm.com, not mydeploymentserver. To verify that the deployment system hostname is a fully qualified domain name, run the following command:
> hostname
If the hostname is a fully qualified domain name, it will return something like: mydeploymentserver.ibm.com
The hostname must be resolvable. Add the hostname for the deployment server to the DNS system. To verify that a hostname is resolvable, run the following command:
> hostname -f
If the hostname is resolvable it will return something like: mydeploymentserver.ibm.com
If the hostname is not resolvable, refer to the networking documentation for the platform to get specific guidance on how to add the hostname to the DNS system.
1) Make sure that both the cmwo410_xlinux_install.bin and
cmwo410_xlinux_install_pkg_01.tar.gz, cmwo410_xlinux_install_pkg_02.tar.gz, and cmwo410_xlinux_install_pkg_03.tar.gz files are in the same directory.
2) Issue the following commands with root: > chmod +x ./cmwo410_xlinux_install.bin > ./cmwo410_xlinux_install.bin
3) You will be guided through a set of console installation screens. At the completion of the install, you can view the installation logs in /opt/ibm/cmwo/_installation/Logs/.
4) To verify that Chef server is up and running use the following command: > chef-server-ctl status
You should see the following: > chef-server-ctl status
run: bookshelf: (pid 17198) 201s; run: log: (pid 17197) 201s run: chef-expander: (pid 17145) 207s; run: log: (pid 17144) 207s run: chef-server-webui: (pid 17357) 187s; run: log: (pid 17356) 187s run: chef-solr: (pid 17112) 209s; run: log: (pid 17111) 209s
run: erchef: (pid 17535) 180s; run: log: (pid 17239) 199s run: nginx: (pid 17518) 181s; run: log: (pid 17517) 181s run: postgresql: (pid 17015) 220s; run: log: (pid 17014) 220s run: rabbitmq: (pid 16685) 236s; run: log: (pid 16684) 236s