Installing on RHOSP10
The Red Hat Openstack Platform Director is the supported and recommended method to deploy and maintain any RHOSP installation.
Trilio is integrating natively into the RHOSP Director. Manual deployment methods are not supported for RHOSP.
Prepare for deployment
Depending whether the RHOSP environment is already installed or is getting installed for the first time different steps are done to be able to deploy Trilio.
Overcloud is not yet deployed
If overcloud is not deployed already, in that case user should install trilio rpms on overcloud image before starting deployment. Trilio RPM packages are provided through yum repo hosted on the Trilio VM.
To inject the Trilio yum repository on the overcloud image do the following commands:
Afterwards will the overcloud image be created.
Overcloud is already deployed
If overcloud is deployed already it is necessary to prepare the artifacts to install on the overcloud.
All commands need to be run as user 'stack'
Firstly the github repository needs to be synced with the undercloud.
Afterwards are those artifacts created and pushed to the overcloud nodes using the upload-swift-artifacts tool. This tool is provided on the undercloud and the prepare_artifacts.sh is created for it.
Update overcloud roles data file to include Trilio services
Trilio contains of multiple services. Add these services to your roles_data.yaml.
In case of uncostomized roles_data.yaml can the default file be found on the undercloud at:
/usr/share/openstack-tripleo-heat-templates/roles_data.yaml
Add the following services to the roles_data.yaml
Trilio Datamover Api Service
This service needs to share the same role as the nova-api
service.
In case of the pre-defined roles will the nova-api
service run on the role Controller
.
In case of custom defined roles, it is necessary to use the role the nova-api
service is using.
Add the following line to the identified role:
Trilio Horizon Plugin
This service needs to share the same role as the openstack horizon
service.
In case of the pre-defined roles will the openstack horizon
service run on the role Controller
.
In case of custom defined roles, it is necessary to use the role the openstack horizon
service is using.
Add the following line to the identified role:
Trilio Datamover Service
This service needs to share the same role as the nova-compute
service.
In case of the pre-defined roles will the nova-compute
service run on the role Compute
.
In case of custom defined roles, it is necessary to use the role the nova-compute
service is using.
Add the following line to the identified role:
Provide environment details to trilio_env.yaml
Provide backup target details like NFS share, S3 bucket details and other necessary details in trilio_env.yaml environment file. This environment file will be used in overcloud deployment to configure trilio components.
Sample trilio_env.yaml
Deploy overcloud with trilio environment
Use the following heat environment file and roles data file in overcloud deploy command:
trilio_env.yaml
roles_data.yaml
To include new environment files use '-e' option and for roles data file use '-r' option. An example overcloud deploy command is shown below:
Verify deployment
The following packages should be installed on nodes with the role that contains the nova-api
:
The following packages should be installed nodes with the role that contains the openstack horizon
:
The following packages should be installed on nodes with the role that contain nova-compute
:
On the same nodes that contain the nova-compute service a new systemd service tvault-contego
should have been registered and running.
Further should the following mount be visible: /var/triliovault-mounts/<hash>
Lastly login into the Horizon Dashboard as admin user. Two new tabs should be visible:
Backups
Backups-Admin
If any rpm packages are missing or other verification steps fail verify that the given steps have been followed.
Troubleshooting for overcloud deployment failures
Trilio components will be deployed using puppet scripts.
In case of the overcloud deployment failing does the following command provide the list of errors:
Further commands that can help identifying any errors.
Cinder backend is Ceph - additional steps
Add Ceph details to configuration file
If Cinder backend is Ceph it is necessary to manually add the ceph details to tvault-contego.conf on all compute nodes.
The file can be found here:
/var/lib/config-data/puppet-generated/triliodm/etc/tvault-contego/tvault-contego.conf
Add the following information:
The same block of information can be found in the nova.conf file.
Give nova user read permission
In case that the user nova does not have permission to read and use the ceph conf and keyring files, run the following commands to provide the necessary access:
Last updated