Installing a standalone engine#
To deploy environments to non-OpenStack clouds, such as Amazon Web Services, SoftLayer, VMware, Google Cloud, and Microsoft Azure, you install the blueprint design server and Heat engine through IBM UrbanCode Deploy. You can install the engine in interactive mode or in silent mode.
- Do not install an engine with these steps to connect to an OpenStack or OpenStack-based cloud. Instead, to extend an existing engine on the OpenStack-based cloud, see Extending an existing OpenStack engine.
- The upgrade-standalone-ucd-heat-engine.sh script can only be used with the provided heat engine that comes with HCL™ Launch blueprint designer. It installs both the HCL Launch plug-in and the ibm-cloud-ext package.
Before you install the engine, ensure that you do the following steps:
You must install the engine on a host that runs a specific version of Red Hat Enterprise Linux™ (RHEL).
- In version 6.2.2 and later, the HCL Launch 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. 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 an existing OpenStack engine.
The engine installer installs only a specific version of the OpenStack Heat orchestration engine.
- In version 6.2.2 and later, the installer installs only OpenStack Kilo engines. To use a different version of the OpenStack Heat orchestration engine, you can extend an existing engine of that version; see Extending an existing OpenStack engine. 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
ulimit -vcommands and ensure that 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 MariaDB database automatically. You must install the engine on a system on which MariaDB is not installed. If the database is already 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 packages:
openssl-develFor example, the command to install these packages might resemble the following code:
yum install -y gcc genisoimage libffi-devel python-devel openssl-devel
Enable the optional "rhel-7-server-optional-rpms" repository.
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:
For RHEL 7.6 and earlier:
yum-config-manager --enable rhui-REGION-rhel-server-optional
For RHEL 7.7 and later:
yum-config-manager --enable rhui-rhel-7-server-rhui-optional-rpms
Determine whether the
akonadipackage is installed on the system.
rpm -ql akonadi
akonadipackage is installed, remove it:
yum remove -y akonadi
Determine whether the program
qpidis installed on the system.
On RHEL version 7, run the following command:
systemctl status qpidd.service
If the program
qpidis running on the system, stop its service.
On RHEL version 7, run the following command:
systemctl stop qpidd.service
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.
Choose to install the engine in interactive mode or in silent mode: