You can install the IBM Cloud Manager with OpenStack application on 64-bit Linux by using one of three installation types: console, graphical, or silent.
The default installation type is console. To install IBM Cloud Manager with OpenStack using a
non-default installation type, start the installer from the command line and run -i <install type> where
<install type>is console, silent, or gui for graphical.
Installing IBM Cloud Manager with OpenStack on Linux
To install IBM Cloud Manager with OpenStack on the deployment server, follow the steps that are outlined in these topics.
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:
v Installs and configures the chef-server
v Installs the IBM OpenStack RPM files in a yum repository on the deployment server
v Uploads the OpenStack cookbooks, roles, data bags and sample environments to the chef-server v Installs an IBM extension to the chef knife command that enables IBM OpenStack topology
deployments
Installing IBM Cloud Manager with OpenStack on Linux by using console installation
You can install IBM Cloud Manager with OpenStack on Linux by using a console.
Before you begin
The hostname for the deployment server must meet the following requirements:
v The host where you install the management server must 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
v 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.
© Copyright IBM Corp. 2012, 2014 19
Important: You need root authority to run the installer.
The product installer requires a functional Upstart environment. Upstart is used to manage the service state of the Chef server.
Note: This may not be the case in Docker containers or chroot environments that are common in deployment phases that use Anaconda/Kickstart.
You can verify that Upstart is running with the following command:
initctl list
About this task
To install IBM Cloud Manager with OpenStack, follow these steps:
Procedure
1. Download the following installation packages:
v Linux: cmwo410_xlinux_install.bin and all cmwo410_xlinux_install_pkgnn.tar.gz files
v Linux on Power: cmwo410_plinux_install.bin and all cmwo410_plinux_install_pkgnn.tar.gz files Copy all of the downloaded files to the same directory on the deployment system:
INSTALLER_LAUNCH_DIR.
2. Optional: You can define a response file for the silent installation. The sample installation response file, cmwo-install-sample.rsp that is provided at the download site and on the installation media defines various keyword attributes that can be changed for the installation process. The sample response file includes information in the comments on the use and purpose of each keyword. It includes examples of how to specify the response file when you start the installation.
3. Navigate to the INSTALLER_LAUNCH_DIR directory from a terminal session and run the following commands:
Platform Installation commands
Linux chmod +x ./cmwo410_xlinux_install.bin ./cmwo410_xlinux_install.bin
Linux on Power chmod +x ./cmwo410_plinux_install.bin ./cmwo410_plinux_install.bin
4. Follow the installation instructions.
5. The installation log, IBM_Cloud_Manager_with_OpenStack_Install_MM_DD_YYYY_HH_mm_ss.log, is located in the following directory: /opt/ibm/cmwo/_installation/Logs/
Note: Low-level detail can be found in the following file: /tmp/cmwo-installer.log
6. To verify that the Chef server installed successfully, you can run the following command to check the Chef server status:
chef-server-ctl status
The command should return output similar to the following example:
[root@elvis-chef3 ]# 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
What to do next
When the installation completes, the components that are necessary for creating a cloud environment are installed.
Important: Download and install the latest fix pack for the IBM Cloud Manager with OpenStack from Fix Central. For more information, see “Getting fixes from Fix Central” on page 249.
To continue, you must create an operating system yum repository. Then, select and deploy a topology for your cloud configuration.
Installing IBM Cloud Manager with OpenStack on Linux by using graphical installation
You can install IBM Cloud Manager with OpenStack on Linux by using a graphical user interface.
Before you begin
The hostname for the deployment server must meet the following requirements:
v The host where you install the management server must 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
v 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.
Important: You need root authority to run the installer.
The product installer requires a functional Upstart environment. Upstart is used to manage the service state of the Chef server.
Chapter 3. Installing and uninstalling 21
Note: This may not be the case in Docker containers or chroot environments that are common in deployment phases that use Anaconda/Kickstart.
You can verify that Upstart is running with the following command:
initctl list
About this task
To install IBM Cloud Manager with OpenStack, follow these steps:
Procedure
1. Download the following installation packages:
v Linux: cmwo410_xlinux_install.bin and all cmwo410_xlinux_install_pkgnn.tar.gz files
v Linux on Power: cmwo410_plinux_install.bin and all cmwo410_plinux_install_pkgnn.tar.gz files Copy all of the downloaded files to the same directory on the deployment system:
INSTALLER_LAUNCH_DIR.
2. Optional: You can define a response file for the silent installation. The sample installation response file, cmwo-install-sample.rsp that is provided at the download site and on the installation media defines various keyword attributes that can be changed for the installation process. The sample response file includes information in the comments on the use and purpose of each keyword. It includes examples of how to specify the response file when you start the installation.
3. Navigate to the INSTALLER_LAUNCH_DIR directory from a terminal session and run the following commands:
Platform Installation commands
Linux chmod +x ./cmwo410_xlinux_install.bin ./cmwo410_xlinux_install.bin -i gui Linux on Power chmod +x ./cmwo410_plinux_install.bin
./cmwo410_plinux_install.bin -i gui
4. Follow the installation instructions.
5. The installation log, IBM_Cloud_Manager_with_OpenStack_Install_MM_DD_YYYY_HH_mm_ss.log, is located in the following directory: /opt/ibm/cmwo/_installation/Logs/
Note: Low-level detail can be found in the following file: /tmp/cmwo-installer.log
6. To verify that the Chef server installed successfully, you can run the following command to check the Chef server status:
chef-server-ctl status
The command should return output similar to the following example:
[root@elvis-chef3 ]# 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
What to do next
When the installation completes, the components that are necessary for creating a cloud environment are installed.
Important: Download and install the latest fix pack for the IBM Cloud Manager with OpenStack from Fix Central. For more information, see “Getting fixes from Fix Central” on page 249.
To continue, you must create an operating system yum repository. Then, select and deploy a topology for your cloud configuration.
Installing IBM Cloud Manager with OpenStack on Linux by using silent installation
You can use a response file to install IBM Cloud Manager with OpenStack on Linux silently.
Before you begin
The hostname for the deployment server must meet the following requirements:
v The host where you install the management server must 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
v 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.
Important: You need root authority to run the installer.
The product installer requires a functional Upstart environment. Upstart is used to manage the service state of the Chef server.
Note: This may not be the case in Docker containers or chroot environments that are common in deployment phases that use Anaconda/Kickstart.
You can verify that Upstart is running with the following command:
initctl list
About this task Procedure
1. Download the following installation packages:
v Linux: cmwo410_xlinux_install.bin and all cmwo410_xlinux_install_pkgnn.tar.gz files
Chapter 3. Installing and uninstalling 23
v Linux on Power: cmwo410_plinux_install.bin and all cmwo410_plinux_install_pkgnn.tar.gz files Copy all of the downloaded files to the same directory on the deployment system:
INSTALLER_LAUNCH_DIR.
2. Define a response file for the silent installation. The sample installation response file,
cmwo-install-sample.rspthat is provided at the download site and on the installation media defines various keyword attributes that can be changed for the installation process. The sample response file includes information in the comments on the use and purpose of each keyword. It includes examples of how to specify the response file when you start the installation.
3. Navigate to the INSTALLER_LAUNCH_DIR directory from a terminal session and run the following commands:
Platform Silent installation command
Linux chmod +x ./cmwo410_xlinux_install.bin echo LICENSE_ACCEPTED=true >
./installer.rsp; ./cmwo410_xlinux_install.bin -i silent -f ./installer.rsp
Linux on Power chmod +x ./cmwo410_plinux_install.bin echo LICENSE_ACCEPTED=true >
./installer.rsp; ./cmwo410_plinux_install.bin -i silent -f ./installer.rsp
4. The installation process takes several minutes to complete.
5. Check the status of the installation by running the following command:
echo $?
If the return code is 0, the installation was successful. If the return code is something other than 0, refer to the installation logs to determine the problem.
6. The installation log, IBM_Cloud_Manager_with_OpenStack_Install_MM_DD_YYYY_HH_mm_ss.log, is located in the following directory: INSTALLER_LAUNCH_DIR.
Note: Low-level detail can be found in the following file: /tmp/cmwo-installer.log
7. To verify that the Chef server installed successfully, you can run the following command to check the Chef server status:
chef-server-ctl status
The command should return output similar to the following example:
[root@elvis-chef3 ]# 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
What to do next
When the installation completes, the components that are necessary for creating a cloud environment are installed.
Important: Download and install the latest fix pack for the IBM Cloud Manager with OpenStack from Fix Central. For more information, see “Getting fixes from Fix Central” on page 249.
To continue, you must create an operating system yum repository. Then, select and deploy a topology for your cloud configuration.
Installing IBM Cloud Manager with OpenStack self-service portal on Windows
You have the option to install IBM Cloud Manager with OpenStack self-service portal on Microsoft Windows. If you want to use the web-based self-service portal, follow the steps that are outlined in these topics.
Notes:
v Any Microsoft Windows user with administrator authority can install IBM Cloud Manager with OpenStack self-service portal.
v In previous releases, IBM Cloud Manager with OpenStack self-service portal was known as IBM SmartCloud®Entry web interface.
Graphical installation (default)
You can complete the installation through a graphical user interface.
Procedure
1. Go to the location of the Windows installer and double-click the installer icon.
2. On the first screen, select the language that you want the installer that is displayed in from the drop-down menu and click OK.
Note:
v If you see an error message similar to Executing java permission denied, verify that you are using the correct installer for your operating system.
v If you see Windows error 183, you are using am unsupported 32-bit operating system.
3. On the Introduction screen, read the introduction for information about the installer and click Next.
4. On the License Agreement window, read the contract and accept the license. Click Next.
5. On the Choose Shortcut Location window, select the check boxes next to the locations where you want a IBM Cloud Manager with OpenStack link and then click Next.
6. To choose the location for your installation, click Choose on the Choose Install Folder window, specify your chosen location, and click Next.
Note: The installation path cannot contain non-English characters.
7. To select the location of your property files, on the Choose Property File Install Folder window, click Chooseand click Next.
Note: The installation path cannot contain non-English characters.
8. Review your selected options on the Pre-Installation Summary window. If you are satisfied with your selections, click Next.
9. After the installation is finished, the Install Finished window opens.
You have three options:
v You can follow the installer to configure important properties.
v You can use the installer to migrate the property files and database from a previous release.
v You can manually migrate the configuration property files and data from a previous release at a later time.
Click Next after making your selection.
Chapter 3. Installing and uninstalling 25
Console installation
You can complete the installation by using a console.
Procedure
1. Click Start and then select Run.
2. In the run window, type cmd and click OK.
3. In the console window, navigate to the windows installer and run the following command:
cmwo_ui410_windows_installer.exe -i console
4. On the Choose Locale screen, choose the language for the installer by typing the number
corresponding to your chosen language and pressing Enter. If your preferred language is the default, press Enter.
Note:
v If you see an error message similar to Executing java permission denied, verify that you are using the correct installer for your operating system.
v If you see Windows error 183, you are using an unsupported 32-bit operating system.
5. On the Introduction screen, read the information about the installer and press Enter.
6. On the License Agreement screen, read the contract and accept the license by entering Y.
7. Choose your location for the links to IBM Cloud Manager with OpenStack. To choose any combination of locations, separate each number with a comma.
8. On the Choose Install Folder screen, press Enter to accept the default location. To choose a different location for the application files, type in the full path to that folder and press Enter.
Note: The installation path cannot contain non-English characters.
9. On the Choose Property File Install Folder screen, press Enter to accept the default location. To choose a different location for the property files, type in the full path to that folder and press Enter.
Note: The installation path cannot contain non-English characters.
10. Review your selected options on the Pre-Installation Summary screen. If you are satisfied with your selections, press Enter.
11. When the installation is complete, the Install Finished window opens.
You have three options:
v You can follow the installer to configure important properties.
v You can use the installer to migrate the property files and database from a previous release.
v You can manually migrate the configuration property files and data from a previous release later.
Silent installation
Create a silent installation response file and use it to install IBM Cloud Manager with OpenStack self-service portal on Windows.
About this task
To create a silent installation response file, follow either “Console installation” or “Graphical installation (default)” on page 25 on Windows. On the final screen, you can create a silent installation response file.
Creating a silent installation response file creates a property file that is called installer.properties in the installation location.
To install on Windows by using a silent installation response file, follow these steps:
Procedure
1. Open the response file and double check all of the properties. Notice that the passwords are not in the file. Notice that all paths have "\\" instead of a single "\". Make any updates and then save the file.
2. Press Start and then Run.
3. In the run prompt, type cmd and press Enter.
4. A console window opens. In the console window, navigate to the Windows installer.
5. Run the installer with the command cmwo_ui410_windows_installer.exe -i silent -f <response file location>, where <response file location> is the path to the response file, which defines the installation.
Note:
v If you see an error message similar to Executing java permission denied, verify that you are using the correct installer for your operating system.
v If you see Windows error 183, you are using am unsupported 32-bit operating system.
Installing and uninstalling IBM Cloud Manager with OpenStack agents
IBM Cloud Manager with OpenStack can manage hypervisors by using OpenStack technology. To manage certain hypervisors, you must install a IBM Cloud Manager with OpenStack agent on the endpoint server. This section contains the procedures for installing and uninstalling these IBM Cloud Manager with OpenStack agents.
Installing and uninstalling the IBM Cloud Manager with OpenStack Hyper-V Agent
IBM Cloud Manager with OpenStack can manage Microsoft Hyper-V hypervisors from OpenStack technology. To manage these hypervisors, an IBM Cloud Manager with OpenStack Hyper-V Agent must be installed on the Hyper-V endpoint server.
IBM Cloud Manager with OpenStack can manage Microsoft Hyper-V hypervisors from OpenStack technology. To manage these hypervisors, an IBM Cloud Manager with OpenStack Hyper-V Agent must be installed on the Hyper-V endpoint server.