Trilio Installation on RHOSO
The Red Hat OpenStack Services on OpenShift 18.0 is the supported and recommended method to deploy and maintain any RHOSO installation.
Trilio is integrating natively into the RHOSO. Manual deployment methods are not supported for RHOSO.
1. Prepare for deployment
Refer to the link Resources to get release specific values of the placeholders, viz Container URLs, trilio_branch, RHOSO Version and CONTAINER-TAG-VERSION in this document as per the OpenStack environment:
1.1] Clone triliovault-cfg-scripts repository
The following steps are to be done on the bastion node on an already installed RHOSO environment.
The following command clones the triliovault-cfg-scripts github repository.
git clone -b {{ trilio_branch }} https://github.com/trilioData/triliovault-cfg-scripts.git
cd triliovault-cfg-scripts/redhat-director-scripts/rhosp181.2] Create namespace for Trilio control plane services
oc create namespace trilio-openstack1.3] Create the trilio-openstack-secret in the trilio-openstack namespace.
In this trilio-openstack-secret yaml file you need to fill the base64 encoded container registry password, s3-keys and other passwords.
To get base64 encoded string use linux command
echo -n "s3_key_string" | base64DmapiDatabasePassword
User needs to set this value as per their choice, but it must be Base64 encoded.
dDmapiKeystonePassword
User needs to set this value as per their choice, but it must be Base64 encoded.
DmapiRabbitPassword
User needs to set this value as per their choice, but it must be Base64 encoded.
WlmDatabasePassword
User needs to set this value as per their choice, but it must be Base64 encoded.
WlmKeystonePassword
User needs to set this value as per their choice, but it must be Base64 encoded.
WlmRabbitPassword
User needs to set this value as per their choice, but it must be Base64 encoded.
ContainerRegistryPassword
User need to set this right value but it must be Base64 encoded.
BT1_S3_s3_access_key
Parameter name should be in <backup-target-name>_s3_secret_key format. User need to encode the actual value with base64 encoding and set it here.
BT1_S3_s3_secret_key
Parameter name should be in <backup-target-name>_s3_secret_key format. User need to encode the actual value with base64 encoding and set it here.
cd redhat-director-scripts/rhosp18/ctlplane-scripts/
vi trilio-openstack-secret.yaml
oc apply -f trilio-openstack-secret.yaml -n trilio-openstack1.4] Create image pull secret
cd triliovault-cfg-scripts/redhat-director-scripts/rhosp18/ctlplane-scripts/
chmod +x create-image-pull-secret.sh
./create-image-pull-secret.sh <TRILIO_IMAGE_REGISTRY_URL> <TRILIO_IMAGE_REGISTRY_USER>
Note: Use the following URLs for Trilio image registries, as needed.
Docker registry url : docker.io
Redhat registry url : registry.connect.redhat.com2] Install Trilio for OpenStack Operator
2.1] Install operator - tvo-operator
Please get value of parameter TVO_OPERATOR_CONTAINER_IMAGE_URL from this release artifact documentation. This is Trilio for OpenStack Operator container image tag.
cd redhat-director-scripts/rhosp18/ctlplane-scripts
chmod +x install_operator.sh
./install_operator.sh <TVO_OPERATOR_CONTAINER_IMAGE_URL>
Example:-
Redhat_registry_tvo_operator_conatiner_image_Url:- ./install_operator.sh registry.connect.redhat.com/trilio/trilio-openstack-operator-rhoso:6.1.0-rhoso18.0
Docker_tvo_operator_conatiner_image_Url:- ./install_operator.sh docker.io/trilio/tvo-operator:6.1.0-maint-1-rhoso18.02.2] Verify the tvo operator pod got created
oc get pods -A | grep tvo-operator2.3] Verify that operator CRD is installed
oc get crds | grep tvo3] Install Trilio OpenStack Control Plane Services
3.1] Provide necessary Trilio inputs like backup target details, openstack details etc in yaml format.
Run the script below to fill in the details automatically in tvo-operator-inputs.yaml, but the user must edit the backup target details manually and review them using the table parameters below.
cd redhat-director-scripts/rhosp18/ctlplane-scripts
chmod +x set_operator_inputs.py
./set_operator_inputs.py <TRILIO-CONTAINER-IMAGE-TAG>Review file tvo-operator-inputs.yaml and make sure all the details are correct. If there is any change required, you can edit this file. Above script only takes default parameters during script execution
vi tvo-operator-inputs.yamlOperator parameter details from file tvo-operator-inputs.yaml that user need to edit:
images
Please refer to Resources
common
- trustee_role should be creator,member if barbican is enabled. Otherwise trustee_role should be member. Any openstack user that wants to create backup jobs and take backups needs this role in respective openstack project.
- memcached_servers value should be fetched using command oc -n openstack get memcached -o jsonpath='{.items[*].status.serverList[*]}'| tr ' ' ','
triliovault_backup_targets
- User need to choose which backup targets(Where backups taken by TVO will get stored) to use for this TVO deployment. - User can use multiple backup targets of type ‘NFS' or 'S3’ type like NFS share, Amazon S3 bucket, Ceph S3 bucket etc. - For Amazon S3 backup target s3_type: ‘amazon_s3’ - For all other S3 backup targets s3_type: 'other_s3' - For Amazon S3, s3_endpoint_url value will be empty string. Internally we pick it correctly. - For Amazon s3 s3_self_signed_cert is always 'false'
keystone.common
- 'keystone_interface' set it to any of the value [’internal', 'public']. This interface will be used for communication between TVO and OpenStack services. - 'service_project_name': This is project name where all services are registered. - ‘service_project_domain_name': service project’s domain name - 'admin_role_name': Admin role name - 'cloud_admin_user_name': OpenStack cloud admin user name - 'cloud_admin_project_name': Cloud admin project name - 'auth_url': Keystone auth url of respective interface provided in keystone_interface parameter. - ‘auth_uri': Just append '/v3’ to auth_url - 'keystone_auth_protocol': https or http Auth protocol of keystone endpoint url of provided keystone_interface - 'keystone_auth_host': Full host name from keystone auth_url -'is_self_signed_ssl_cert': True/False, Whether the TLS certs used by keystone endpoint url mentioned in auth_url parameter uses self signed certs or not
keystone.datamover_api and keystone.wlm_api
For both components datamover_api and wlm_api we have same set of parameters. - ‘user': This is openstack user that is used by service datamover_api. Please don’t change this one. - ‘service_name': Don’t need to change - 'service_type': Don’t need to change - 'service_desc': Don’t need to change - ‘internal_endpoint': Trilio service internal endpoint. Please refer other openstack service endpoints and set this one accordingly. - ‘public_endpoint': User just need to set replace parameter 'PUBLIC_ENDPOINT_DOMAIN’ here. Please refer other openstack services public endpoint url. - ‘public_auth_host': FQDN mentioned in parameter 'public_endpoint’
database.common
- 'root_user_name': OpenStack database system root user name. Keep this as it is. Don’t need to change unless you know that root username is changed.
- 'host': Database host/FQDN name
oc -n openstack get secret nova-api-config-data -o jsonpath='{.data.01-nova\.conf}' | base64 --decode | awk '/connection =/ {match($0, /@([^?/]+)/, arr); print arr[1]; exit}'
- 'port': Database port
database.datamover_api and database.wlm_api
- 'user': Do not change - 'database': Do not change
rabbitmq.common
- ‘admin_user': Provide rabbitmq admin user name using command. oc -n openstack exec -it rabbitmq-server-0 bash
rabbitmqctl list_users
- 'host': Provide rabbitmq cluster host name using command oc -n openstack get secret rabbitmq-default-user -o jsonpath='{.data.host}' | base64 -d
- 'port': Provide rabbitmq management API port on which it can be connected using rabbitmqadmin command. Generally this is 15671 for RHOSO. So you can keep it as it is. 5671 is not a management API port. Refer command:oc -n openstack get cm rabbitmq-server-conf -o jsonpath='{.data.userDefinedConfiguration\.conf}' | grep management.ssl.port
- 'driver': Rabbitmq driver
- ‘ssl': If SSL/TLS is enabled on rabbitmq, set this to true other wise set it to false. This is boolean parameter.
rabbitmq.datamover_api and rabbitmq.wlm_api
- 'user': Do not change this.
- 'vhost': Do not change this
‘transport_url': User needs to set this. Edit ‘${PASSWORD}' and '${RABBITMQ_HOST}’ from given default url. You can edit SSL and port settings if necessary. oc describe secret rabbitmq-default-user -n openstack
oc get secret rabbitmq-default-user -n openstack -o jsonpath='{.data.username}' | base64 --decode
pod.replicas
These parameters sets number of replicas for Trilio components. Default values are standard. Unless needed you don’t need to change it. Please note that number of replicas for triliovault_wlm_cron pod should always be set to 1.
3.2] Set correct labels to Kubernetes nodes.
Trilio control plane services will be deployed on OpenShift nodes having label trilio-control-plane=enabled . It is recommended to use three Kubernetes nodes for Trilio control plane services. Please use following commands to assign correct labels to nodes.
Get list of OpenShift nodes
oc get nodesAssign ‘trilio-control-plane=enabled' label to any three nodes of your choice where you want to deploy TVO control plane services.
oc label nodes <Openshift_node_name1> trilio-control-plane=enabled
oc label nodes <Openshift_node_name2> trilio-control-plane=enabled
oc label nodes <Openshift_node_name3> trilio-control-plane=enabledVerify list of nodes having 'trilio-control-plane=enabled' label
oc get nodes -l trilio-control-plane=enabled3.3] Create TLS certificate secrets
Following script creates TLS certificates for Trilio services and defines secrets having these certs.
Edit '$PUBLIC_ENDPOINT_DOMAIN' parameter in utils/certicate.yaml file and set it to correct value. Refer openstack keystone service public endpoint.
cd redhat-director-scripts/rhosp18/ctlplane-scripts/
vi certificate.yamlCreate certificates and secrets
cd redhat-director-scripts/rhosp18/ctlplane-scripts/
./create_cert_secrets.shYou can verify if these cert secrets are created in 'trilio-openstack' namespace.
oc -n trilio-openstack describe secret cert-triliovault-datamover-public-svc
oc -n trilio-openstack describe secret cert-triliovault-datamover-internal-svc
oc -n trilio-openstack describe secret cert-triliovault-wlm-public-svc
oc -n trilio-openstack describe secret cert-triliovault-wlm-internal-svc3.4] Run deploy command
cd redhat-director-scripts/rhosp18/ctlplane-scripts/
./deploy_tvo_control_plane.sh3.5] Check logs
oc logs -f tvo-operator-controller-manager-846f46787-5qnm2 -n tvo-operator-system3.6] Check deployment status
oc get tvocontrolplane -n trilio-openstack
oc describe tvocontrolplane <TVO_CONTROL_PLANE_OBEJCT_NAME> -n trilio-openstack3.7] Verify successful deployment of T4O control plane services.
[root@localhost ctlplane-scripts]# oc get pods -n trilio-openstack
NAME READY STATUS RESTARTS AGE
job-triliovault-datamover-api-db-init-ttq46 0/1 Completed 0 6m27s
job-triliovault-datamover-api-keystone-init-2ddh6 0/1 Completed 0 9m6s
job-triliovault-datamover-api-rabbitmq-init-27sx9 0/1 Completed 0 8m51s
job-triliovault-wlm-cloud-trust-lcncp 0/1 Completed 0 4m59s
job-triliovault-wlm-db-init-c48z4 0/1 Completed 0 6m22s
job-triliovault-wlm-keystone-init-gxlmc 0/1 Completed 0 8m7s
job-triliovault-wlm-rabbitmq-init-6g94w 0/1 Completed 0 6m31s
triliovault-datamover-api-6f5fc957c9-j426z 1/1 Running 0 5m
triliovault-datamover-api-6f5fc957c9-sn9z8 1/1 Running 0 5m
triliovault-datamover-api-6f5fc957c9-xmvs5 1/1 Running 0 5m
triliovault-object-store-bt1-s3-9bfdf45d-5pqqh 1/1 Running 0 5m
triliovault-object-store-bt1-s3-9bfdf45d-g6g7m 1/1 Running 0 5m
triliovault-object-store-bt1-s3-9bfdf45d-tc7zb 1/1 Running 0 5m
triliovault-object-store-bt2-s3-68ff4548cc-9kc9s 1/1 Running 0 5m
triliovault-object-store-bt2-s3-68ff4548cc-cj94f 1/1 Running 0 5m
triliovault-object-store-bt2-s3-68ff4548cc-wfkgf 1/1 Running 0 5m
triliovault-object-store-bt3-s3-6bf58b9f77-6sqp7 1/1 Running 0 15m
triliovault-object-store-bt3-s3-6bf58b9f77-9tlh6 1/1 Running 0 15m
triliovault-object-store-bt3-s3-6bf58b9f77-g67cl 1/1 Running 0 15m
triliovault-wlm-api-66b46c7b6-7kjw4 1/1 Running 0 5m
triliovault-wlm-api-66b46c7b6-rsknb 1/1 Running 0 5m
triliovault-wlm-api-66b46c7b6-s8r92 1/1 Running 0 5m
triliovault-wlm-cron-59f8ccfd-fhn8p 1/1 Running 0 5m
triliovault-wlm-scheduler-569ccc654-bphrd 1/1 Running 0 5m
triliovault-wlm-scheduler-569ccc654-jjhjh 1/1 Running 0 5m
triliovault-wlm-scheduler-569ccc654-klbn4 1/1 Running 0 5m
triliovault-wlm-workloads-6869cff4b8-8spmz 1/1 Running 0 4m59s
triliovault-wlm-workloads-6869cff4b8-sf652 1/1 Running 0 4m59s
triliovault-wlm-workloads-6869cff4b8-x8h7z 1/1 Running 0 4m59sVerify if wlm cloud trust created successfully
oc logs <job-triliovault-wlm-cloud-trust> -n trilio-openstack4] Install Trilio Data Plane Services
Set context to ‘openstack' namespace. All the trilio data plane resources will be created in 'openstack’ namespace.
oc config set-context --current --namespace=openstack4.1] Create the trilio-openstack-secret in the openstack namespace. This secret is needed for the Trilio data plane.
cd redhat-director-scripts/rhosp18/dataplane-scripts/
oc -n openstack apply -f ../ctlplane-scripts/trilio-openstack-secret.yaml4.2] User need to review below parameters fill all input parameters needed for Trilio data plane services in following cm-trilio-datamover.yaml file.
Run the script below to fill in the details automatically in cm-trilio-datamover.yaml, but the user must edit the TRILIO-CONTAINER-TAG-VERSION for datamover and wlm images, trilio_container_registry_username, trilio_container_registry_url and review them using the table parameters below.
cd redhat-director-scripts/rhosp18/dataplane-scripts/
chmod +x set_data_plane_inputs.py
./set_data_plane_inputs.pyrabbit_host, rabbit_port, rabbit_ssl
User does not need to change these parameters
database_host, database_port
User does not need to change these parameters
cinder_backend_ceph, libvirt_images_rbd_ceph_conf, ceph_cinder_user and oslomsg_rpc_use_ssl
User does not need to change these parameters
images
Please refer to Resources
trilio_container_registry_username, trilio_container_registry_password and trilio_container_registry_url
User needs to update the following fileds with using either Docker or the Redhat registry details, as per the requirement.
triliovault_backup_targets
- User need to choose which backup targets(Where backups taken by TVO will get stored) to use for this TVO deployment.
- User can use multiple backup targets of type ‘NFS' or 'S3’ type like NFS share, Amazon S3 bucket, Ceph S3 bucket etc.
- For Amazon S3 backup target s3_type: ‘amazon_s3’
- For all other S3 backup targets s3_type: 'other_s3'
- For Amazon S3, s3_endpoint_url value will be empty string. Internally we pick it correctly.
- For Amazon s3 s3_self_signed_cert is always 'false'
- Note:- Please provide the same BTT details that are used in the tvo-operator-inputs.yaml file
Create config map having all input parameters for Trilio data plane services deployment.
cd redhat-director-scripts/rhosp18/dataplane-scripts/
vi cm-trilio-datamover.yaml4.3] Create cm-trilio-datamover config map
## Create config map
oc -n openstack apply -f cm-trilio-datamover.yaml4.4] Edit file ‘trilio-datamover-service.yaml' and set correct tag for container image 'openStackAnsibleEERunnerImage
vi trilio-datamover-service.yaml4.5] Following script creates CRD “OpenStackDataPlaneService“ resource for Trilio
oc -n openstack apply -f trilio-datamover-service.yaml4.6] Trigger Deployment of Trilio data plane services
In this step we will trigger the ansible scripts execution to deploy Trilio data plane components. Get Data Plane NodeSet names using following command
oc -n openstack get OpenStackDataPlaneNodeSetEdit two things in following file
Set Unique ‘name' for every ansible execution for ‘OpenStackDataPlaneDeployment’
Set correct name for 'nodeSets’ parameter. Take nodeSet name from previous step.
vi trilio-data-plane-deployment.yamlTo check list of deployment names alreday used, please use following command
## To check list of deployment names alreday used, please use following command
oc -n openstack get OpenStackDataPlaneDeploymentTrigger Trilio Data plane deployment execution
## Trigger deployment
oc -n openstack apply -f trilio-data-plane-deployment.yaml4.7] Check deployment logs.
Edit parameter name : <OpenStackDataPlaneDeployment_NAME>, use name from above steps.
oc -n openstack get pod -l openstackdataplanedeployment=<OpenStackDataPlaneDeployment_NAME>
oc -n openstack logs -f <trilio-datamover-pod-name>If it fails or completes and you want to run it again, you need to change the name of CR resource ‘OpenStackDataPlaneDeployment' to something new and unique in following template 'trilio-data-plane-deployment.yaml' and create it again using oc create command.
4.8] Verify deployment completed well
Login to one of the compute node and check trilio compute service containers.
podman ps | grep trilio5] Install Trilio Horizon Plugin
Pre-requisite: You should have created image pull secret for Trilio container images.
Get the openstackversion CR
[kni@localhost ~]$ oc get openstackversion -n openstack
NAME TARGET VERSION AVAILABLE VERSION DEPLOYED VERSION
openstack-controlplane 18.0.2-20240923.2 18.0.2-20240923.2 18.0.2-20240923.2Edit the openstackversion CR resource/object and change horizonImage undercustomContainerImages Set 'horizonImage:' to Trilio Horizon Plugin container image url as shown below.
oc edit openstackversion <OPENSTACKVERSION_RESOURCE_NAME> -n openstackFor example: if resource name is 'openstack-controlplane'
oc edit openstackversion openstack-controlplane -n openstackapiVersion: core.openstack.org/v1beta1
kind: OpenStackVersion
metadata:
name: openstack-controlplane
spec:
customContainerImages:
horizonImage: docker.io/trilio/trilio-horizon-plugin:<IMAGE_TAG>
[...]Save changes and exit. [Use escape + Colon + wq like linux vi editor.]
Verify if changes are done correctly using below command.
oc describe openstackversion <OPENSTACKVERSION_RESOURCE_NAME> -n openstackYou can access the OpenStack horizon using your same URL and login using same credentials. This openstack horizon will have Trilio UI components as well by verifying using the UI horizon.
Last updated
Was this helpful?