Installing engines in silent mode

In silent mode, you install Heat orchestration engines for the blueprint design server by specifying configuration information in command-line arguments.

Before you begin

You must install the engine on a host that runs a specific version of Red Hat Enterprise Linux (RHEL).
- In version 6.2.1.1 and later, the IBM® UrbanCode™ Deploy installer can install engines for the blueprint design server only on RHEL version 7. No other operating system is supported, including RHEL version 6 or earlier.
- In versions before 6.2.1.1, the IBM UrbanCode Deploy installer can install engines for the blueprint design server only on RHEL version 6. No other operating system is supported, including RHEL version 7.
To use a different operating system, you can install an OpenStack Heat engine manually on that operating system and then extend that engine for use with the blueprint design server; see Extending Heat orchestration engines.
The engine installer installs only a specific version of the OpenStack Heat orchestration engine.
- In version 6.2.1.1 and later, the installer installs only OpenStack Kilo engines.
- In versions before 6.2.1.1, the installer installs only OpenStack Juno engines.
To use a different version of the OpenStack Heat orchestration engine, you can extend an existing engine of that version; see Extending Heat orchestration engines. You can extend OpenStack Icehouse, Juno, Kilo, Liberty, and Mitaka engines for use with the blueprint design server.
The operating system must have the most recent package updates. For more information, see Installing and Managing Software in the Red Hat Enterprise Linux customer portal.
Ensure that there is no limit on the maximum memory size and virtual memory size. For example, on most Linux systems, you can run the commands ulimit -m and ulimit -v and ensure that they both return the value unlimited. To find out how to remove the limit on the maximum memory size and virtual memory size, see the documentation for the operating system.
Root access is required for installation.
The engine installs a database automatically.
- In version 6.2.1.1 and later, the engine installer installs MariaDB.
- In versions before 6.2.1.1, the engine installer installs MySQL.
You must install the engine on a system on which the specified database is not installed. If the specified database is installed on the system, the engine installation fails.
The operating system must be configured with required packages and dependencies before you install the engine. The system might need network access to install these packages. Make sure that the system is connected to a package manager, such as a Yum server.
Make sure that your system meets the system requirements. See System requirements and performance considerations.
Make sure that your networks and firewalls allow communication on the required ports. See Firewall and communication configuration.
Install the following prerequisite packages:
- In versions before 6.2.1.1, run the following command:
```
 yum update -y python python-libs ; yum install -y genisoimage
```
- In versions 6.2.1.1 and later, run the following command:
```
yum install -y genisoimage
```
In version 6.2.1.1 and later, enable the optional repository "rhel-7-server-optional-rpms."
- On RHEL systems that use the Red Hat Network subscription-based package manager, use the following command:
```
subscription-manager repos --enable=rhel-7-server-optional-rpms
```
- On virtual machines that are hosted on Amazon Web Services, run the following command:
```
yum-config-manager --enable rhui-REGION-rhel-server-optional
```
Remove the package akonadi if it is installed:
```
yum remove -y akonadi
```
Determine whether the program qpid is installed on the system.
- On RHEL version 7, run the following command:
```
systemctl status qpidd.service
```
- On RHEL version 6, run the following command:
```
service qpidd status
```
If the program qpid is running on the system, stop its service.
- On RHEL version 7, run the following command:
```
systemctl stop qpidd.service
```
- On RHEL version 6, run the following command:
```
service qpidd stop
```
Gather the URL and account information for the OpenStack Keystone service, if available. Rather than having its own list of users, the blueprint design server imports accounts from authentication realms, including OpenStack Keystone services and LDAP servers. This Keystone service is required regardless of the type of cloud you are using. If you do not have a Keystone server, you can install one that uses Identity API v3 during the engine installation.

About this task

If you already have an engine, you can extend it for use with the blueprint designer. See Extending Heat orchestration engines.

If you already use a Keystone server, you can use it as your identity service for the blueprint design server. If you do not use a Keystone server, you can install one with the engine.

Procedure

Download and extract the installation files for the engine. These files are available for download from the IBM Passport Advantage® website. See the IBM UrbanCode Deploy download document.
Change to the /ibm-ucd-patterns-install/engine-install/ directory.
Read the license agreement, which is in the following folder: ibm-ucd-patterns-install/engine-install/resources/.

From the command line, run the following command. This command must be on a single line.

Note: The -l option indicates that you have read and accepted the license agreement.

./install.sh
  -l options

For options, include the following arguments:

Argument	Required or optional	Description
`-a openstack_URL`	Required	Specify the complete URL of the Keystone server that you are using for your identity service, such as `http://cloud.example.com:5000/v3`. Do not include a trailing slash. If you do not have a Keystone server, specify the default URL to use the Keystone server instance that is installed when you install the engine. In version 6.2.1.1 and later, the default URL is http://`public_host_name`:5000/v3, and in versions before 6.2.1.1, the default URL is http://`public_host_name`:5000/v2.0.
`-b bind_address`	Required	Specify the IP address that the engine listens for requests on. Specify `0.0.0.0` to listen on all addresses that are available to the system.
`-i engine_hostname`	Required	Specify the public IP address or host name that other systems, such as the blueprint design server, use to access this system.
`-s Yes or No`	Required	Specify `Yes` to start the required OpenStack Heat and Keystone services or `No` to not start the services.

For example:

./ibm-ucd-patterns-install/engine-install/install.sh -l
-a http://cloud.example.com:5000/v2.0
-i engine.example.com
-b 0.0.0.0
-s Yes

These examples are split onto separate lines for clarity, but the command must be entered on a single line. If you omit a required argument, the installation program prompts for the value, which means that the silent installation becomes interactive.

Optional: After the installation program is complete, add an automated task to remove expired keys from the database. Having too many expired keys in the database can degrade system performance. For example, the following command creates an automated task in the Linux program cron to remove old keys. This command must be written on a single line.
```
 (crontab -l -u keystone 2>&1 | grep -q token_flush) 
  || echo '@hourly /usr/bin/keystone-manage token_flush 
  >/var/log/keystone/keystone-tokenflush.log 2>&1' 
  >> /var/spool/cron/keystone
```

Results

The installation program installs the engine.

What to do next

If you did not start the engine services during installation, start them. See Starting the blueprint designer, cloud discovery service, and engine.

The Keystone server's default administrative tenant user name is admin and password is openstack1. The authorization token is listed in the /etc/keystone/keystone.conf and /root/keystonerc file.

Required backend services for the engine started during installation. If you stop the backend services while the OpenStack services for the Heat engine are running, the OpenStack services for the Heat engine fail. If you did not start the engine, then you can stop these services. For example, the following commands terminate the backend services in RHEL 7:

systemctl stop rabbitmq-server.service

systemctl stop mariadb.service

systemctl stop openstack-keystone.service

To interact with the Heat engine, you use its provided credentials in your user directory. The clientrc file that contains the Heat engine credentials also contains the credentials for the Keystone identity service. Run the following commands:

source ~/clientrc

openstack endpoint list

heat stack-list

You can also interact with only the Keystone identity service by using its prepared credentials files in your user directory. Run this command to load the credentials file:

source ~/keystonerc

For version 6.2.1.1 and later versions, run the following command:
```
openstack endpoint list
```
For versions before 6.2.1.1, run the following command:
```
keystone endpoint-list
```

After you start the OpenStack services for the Heat engine, you can access the REST API at the following URL: http://host_name:8004.

Feedback