Download the latest SUSE CaaS Platform for OpenStack image (for example, SUSE-CaaS-Platform-3.0-OpenStack-Cloud.x86_64-1.0.0-GM.qcow2) from https://download.suse.com.

Upload the image to Glance:

openstack image create --public --disk-format qcow2 --container-format \
bare --file SUSE-CaaS-Platform-3.0-OpenStack-Cloud.x86_64-1.0.0-GM.qcow2 \
CaaSP-3

Install the caasp-openstack-heat-templates package on a machine with SUSE OpenStack Cloud Crowbar repositories:

zypper in caasp-openstack-heat-templates

The installed templates are located in /usr/share/caasp-openstack-heat-templates.

Alternatively, you can get official Heat templates by cloning the appropriate Git repository:

git clone https://github.com/SUSE/caasp-openstack-heat-templates

In Horizon, go to Project › Stacks › Launch Stack.

Select File from the Template Source drop-down box and upload the caasp-stack.yaml file.

In the Launch Stack dialog, provide the required information (stack name, password, flavor size, external network of your environment, etc.).

Click Launch to launch the stack. This creates all required resources for running SUSE CaaS Platform in an OpenStack environment. The stack creates one Admin Node, one Master Node, and server worker nodes as specified.

Specify the appropriate flavor and network settings in the caasp-environment.yaml file.

Create a stack in Heat by passing the template, environment file, and parameters:

openstack stack create -t caasp-stack.yaml -e caasp-environment.yaml \
--parameter image=CaaSP-3 caasp-stack

After the stack has been created, the Velum SUSE CaaS Platform dashboard runs on the Admin Node. You can access it using the Admin Node's floating IP address.

Create an account and follow the steps in the Velum SUSE CaaS Platform dashboard to complete the SUSE CaaS Platform installation.

Specify the appropriate flavor and network settings in the caasp-multi-master-environment.yaml file.

Set master_count to the desired number in the caasp-multi-master-environment.yaml file. The master count must be set to an odd number of nodes.

master_count: 3

Create a stack in Heat by passing the template, environment file, and parameters:

tux > openstack stack create -t caasp-multi-master-stack.yaml \
-e caasp-multi-master-environment.yaml --parameter image=CaaSP-3 caasp-multi-master-stack

Find the floating IP address of the load balancer. This is necessary for accessing the Velum SUSE CaaS Platform dashboard.

1. tux > openstack loadbalancer list --provider

2. From the output, copy the id and enter it in the following command as shown in the following example:

   tux > openstack loadbalancer show id

   +---------------------+------------------------------------------------+
   | Field               | Value                                          |
   +---------------------+------------------------------------------------+
   | admin_state_up      | True                                           |
   | description         |                                                |
   | id                  | 0d973d80-1c79-40a4-881b-42d111ee9625           |
   | listeners           | {"id": "c9a34b63-a1c8-4a57-be22-75264769132d"} |
   |                     | {"id": "4fa2dae0-126b-4eb0-899f-b2b6f5aab461"} |
   | name                | caasp-stack-master_lb-bhr66gtrx3ue             |
   | operating_status    | ONLINE                                         |
   | pools               | {"id": "8c011309-150c-4252-bb04-6550920e0059"} |
   |                     | {"id": "c5f55af7-0a25-4dfa-a088-79e548041929"} |
   | provider            | haproxy                                        |
   | provisioning_status | ACTIVE                                         |
   | tenant_id           | fd7ffc07400642b1b05dbef647deb4c1               |
   | vip_address         | 172.28.0.6                                     |
   | vip_port_id         | 53ad27ba-1ae0-4cd7-b798-c96b53373e8b           |
   | vip_subnet_id       | 87d18a53-ad0c-4d71-b82a-050c229b710a           |
   +---------------------+------------------------------------------------+

3. Search the floating IP list for vip_address

   tux > openstack floating ip list | grep 172.28.0.6
   | d636f3...481b0c | fd7ff...deb4c1 | 172.28.0.6  | 10.84.65.37  | 53ad2...373e8b |

4. The load balancer floating ip address is 10.84.65.37

Spin up a SUSE CaaS Platform cluster using Heat templates following the instructions in Section 15.1, “SUSE CaaS Platform Heat Installation Procedure”. Do not go through the bootstrapping steps, because the SUSE CaaS Platform Maintenance Update (MU) must be applied first. After the maintenance update process below succeeds, return to the SUSE CaaS Platform installation instructions and follow the admin node bootstrapping steps.

Apply the SUSE CaaS Platform 3.0 Maintenance Update with the following steps:

1. Log in to each node and add the update repository.

   tux > sudo zypper ar http://nu.novell.com/SUSE/Updates/SUSE-CAASP/3.0/x86_64/update/ caasp_update

2. With root privileges, run transactional-update on each node.

3. Reboot each node

4. Verify that the Velum image packages were updated

   tux > zypper se --detail velum-image
   i | sles12-velum-image | package    | 3.1.7-3.27.3  | x86_64 | update_caasp

Upload a valid trust certificate that can validate a certificate presented by Keystone at the specified keystone_auth_url in the system-wide certificate section of Velum. If the SSL certificate provided by Keystone cannot be verified, bootstrapping fails with the error message x509: certificate signed by unknown authority.

Note

If your OpenStack endpoints operate on the Internet, or if the SSL certificates in use have been signed by a public authority, no action is needed to enable secure communication with them.

If your OpenStack services operate in a private network using SSL certificates signed by an organizational certificate authority, provide that CA certificate as the system-wide certificate.

If your OpenStack service SSL infrastructure was self-signed during the installation of SUSE OpenStack Cloud Crowbar (as is done by default), its CA certificate (with the file extension .pem) can be retrieved from the admin node in the /etc/ssl/certs/ directory. The filename should match the node name of your primary controller node. Download this file and provide it as the system-wide certificate.

After the nodes come up, continue with the installation instructions in Section 15.1, “SUSE CaaS Platform Heat Installation Procedure” following the admin node cluster bootstrapping steps.