After you complete the prerequisite steps described in Prerequisites, proceed with bootstrapping your OpenStack-based Mirantis Container Cloud management cluster.
To bootstrap an OpenStack-based management cluster:
Log in to the bootstrap node running Ubuntu 18.04 that is configured as described in Prerequisites.
Download and run the Container Cloud bootstrap script:
wget https://binary.mirantis.com/releases/get_container_cloud.sh
chmod 0755 get_container_cloud.sh
./get_container_cloud.sh
Change the directory to the kaas-bootstrap
folder
created by the get_container_cloud.sh
script.
Obtain your license file that will be required during the bootstrap. See step 3 in Getting Started with Mirantis Container Cloud.
Save the license file as mirantis.lic
under the kaas-bootstrap
directory.
Prepare the OpenStack configuration for a new cluster:
Log in to the OpenStack Horizon.
In the Project section, select API Access.
In the right-side drop-down menu Download OpenStack RC File, select OpenStack clouds.yaml File.
Add the downloaded clouds.yaml
file to the directory with the
bootstrap.sh
script.
In clouds.yaml
, add the password
field with your OpenStack
password under the clouds/openstack/auth
section.
Example:
clouds:
openstack:
auth:
auth_url: https://auth.openstack.example.com:5000/v3
username: your_username
password: your_secret_password
project_id: your_project_id
user_domain_name: your_user_domain_name
region_name: RegionOne
interface: public
identity_api_version: 3
Verify access to the target cloud endpoint from Docker. For example:
docker run --rm alpine sh -c "apk add --no-cache curl; \
curl https://auth.openstack.example.com:5000/v3"
The system output must contain no error records. In case of issues, follow the steps provided in Troubleshooting.
Configure the cluster and machines metadata:
Change the directory to the kaas-bootstrap
folder.
In templates/machines.yaml.template
,
modify the spec:providerSpec:value
section for 3 control plane nodes
marked with the cluster.sigs.k8s.io/control-plane
label
by substituting the flavor
and image
parameters
with the corresponding values of the control plane nodes in the related
OpenStack cluster. For example:
spec: &cp_spec
providerSpec:
value:
apiVersion: "openstackproviderconfig.k8s.io/v1alpha1"
kind: "OpenstackMachineProviderSpec"
flavor: kaas.minimal
image: bionic-server-cloudimg-amd64-20190612
Also, modify other parameters as required.
Modify the templates/cluster.yaml.template
parameters to fit your
deployment. For example, add the corresponding values for cidrBlocks
in the spec::clusterNetwork::services
section.
Note
The passwordSalt
and passwordHash
values for the IAM
roles are automatically re-generated during the IAM
configuration described in the next step.
Optional. Skip this step to use the default password password
in the Container Cloud web UI.
Configure the IAM parameters:
Create hashed passwords for every IAM role:
reader
, writer
, and operator
for bare metal deployments:
./bin/hash-generate -i 27500
The hash-generate utility requests you to enter a password and outputs the parameters required for the next step. Save the password that you enter in a secure location. This password will be used to access the Container Cloud web UI with a specific IAM role.
Example of system response:
passwordSalt: 6ibPZdUfQK8PsOpSmyVJnA==
passwordHash: 23W1l65FBdI3NL7LMiUQG9Cu62bWLTqIsOgdW8xNsqw=
passwordHashAlgorithm: pbkdf2-sha256
passwordHashIterations: 27500
Run the tool several times to generate hashed passwords for every IAM role.
Open templates/cluster.yaml.template
for editing.
In the initUsers
section, add the following parameters for each
IAM role that you generated in the previous step:
passwordSalt
- base64-encoded randomly generated sequence of bytes.
passwordHash
- base64-encoded password hash generated using
passwordHashAlgorithm
with passwordHashIterations
.
Supported algorithms include pbkdf2-sha256
and pbkdf-sha512
.
Optional. Configure external identity provider for IAM.
Run the bootstrap script:
./bootstrap.sh all
When the bootstrap is complete, collect and save the following management cluster details in a secure location:
The kubeconfig
file located in the same directory as the bootstrap
script. This file contains the admin credentials
for the management cluster.
The private SSH key openstack_tmp
located in ~/.ssh/
for access to the management cluster nodes.
Note
The SSH key name openstack_tmp
is the same for all cloud
providers. This name will be changed in one of the following
Container Cloud releases to avoid confusion
with a cloud provider name and its related SSH key name.
The URL and credentials for the Container Cloud web UI. The system outputs these details when the bootstrap completes.
The StackLight endpoints. For details, see Operations Guide: Access StackLight web UIs.
The Keycloak URL that the system outputs when the bootstrap completes.
The admin password for Keycloak is located in
kaas-bootstrap/passwords.yml
along with other IAM passwords.
Note
When the bootstrap is complete, the bootstrap cluster resources are freed up.
In case of deployment issues, collect and inspect the bootstrap and management cluster logs as described in Troubleshooting.
Optional. Deploy an additional regional cluster as described in Deploy an additional regional cluster (optional).
Now, you can proceed with operating your management cluster using the Container Cloud web UI and deploying managed clusters as described in Create an OpenStack-based managed cluster.