Multi-node OpenStack Charms Deployment Guide 0.0.1.dev303-18--backup backup

Original link:

TrilioVault Data Protection

TrilioVault data protection

Overview

TrilioVault is a data protection solution integrated with OpenStack. It allows end users to backup and restore point-in-time snapshots of their own workloads (cloud instances). TrilioVault is realized through the Trilio super buttons.

note

TrilioVault is not part of the OpenStack project. It is a product of commercial support behavior

Prerequisites

  • Ubuntu 18.04 LTS or 20.04 LTS

  • OpenStack Queens,Stein,Train或Ussuri

  • NFS server for snapshot storage

  • License (see the homepage of the project)

deploy

The TrilioVault solution includes three core services:

  • TrilioVault Workload
    Manager: Main API-used to manage snapshots (for example, create and restore). This is achieved through the trilio-wlm charm
  • TrilioVault Data Mover: Deployed with OpenStack Nova-responsible for managing the instance snapshot process at the cloud level. This is achieved through the trilio-data-mover charm.
  • TrilioVault Data Mover API: API used to manage TrilioVault Data Mover service, used by Workload Manager. This is achieved through the trilio-dm-api charm.

An OpenStack dashboard plug-in is also provided, allowing snapshot management through the Web UI. This is achieved through the trilio-horizon-plugin charm.

The overlay bundle is used to deploy to an existing OpenStack cloud. An example is provided below.

Note: Make sure that the value of openstack-origin matches the currently deployed OpenStack version.

The ceph-mon:client relationship is only required if the cloud has been configured to use a VM image supported by Ceph (via Cinder or Nova).

series: bionic
applications:
  trilio-wlm:
    charm: cs:~openstack-charmers/trilio-wlm
    num_units: 1
    options:
      openstack-origin: cloud:bionic-train
      triliovault-pkg-source: 'deb [trusted=yes] https://apt.fury.io/triliodata-4-1/ /'
  trilio-data-mover:
    charm: cs:~openstack-charmers/trilio-data-mover
    options:
      triliovault-pkg-source: 'deb [trusted=yes] https://apt.fury.io/triliodata-4-1/ /'
  trilio-dm-api:
    charm: cs:~openstack-charmers/trilio-dm-api
    num_units: 1
    options:
      openstack-origin: cloud:bionic-train
      triliovault-pkg-source: 'deb [trusted=yes] https://apt.fury.io/triliodata-4-1/ /'
  trilio-horizon-plugin:
    charm: cs:~openstack-charmers/trilio-horizon-plugin
    options:
      triliovault-pkg-source: 'deb [trusted=yes] https://apt.fury.io/triliodata-4-1/ /'
relations:
  - - trilio-horizon-plugin:dashboard-plugin
    - openstack-dashboard:dashboard-plugin
  - - trilio-dm-api:identity-service
    - keystone:identity-service
  - - trilio-dm-api:shared-db
    - percona-cluster:shared-db
  - - trilio-dm-api:amqp
    - rabbitmq-server:amqp
  - - trilio-data-mover:amqp
    - rabbitmq-server:amqp
  - - trilio-data-mover:juju-info
    - nova-compute:juju-info
  - - trilio-wlm:shared-db
    - percona-cluster:shared-db
  - - trilio-wlm:amqp
    - rabbitmq-server:amqp
  - - trilio-wlm:identity-service
    - keystone:identity-service
  - - trilio-data-mover:ceph
    - ceph-mon:client
  - - trilio-data-mover:shared-db
    - percona-cluster:shared-db

note:

The openstack-origin> ='cloud:bionic-train'deployment trilio-wlm and trilio-dm-api charms must be used -even for the deployment of the queens version.
These parts of the TrilioVault deployment only apply to Python 3, and have dependent version requirements that are only supported starting from Train.

NFS file

After the deployment is complete, the trilio-wlm and trilio-data-mover applications will be in a blocked state (see juju state). To solve this problem, a valid NFS share (on the provided NFS server) must be configured for both applications. E.g:

juju config trilio-wlm nfs-shares=10.40.3.20:/srv/triliovault
juju config trilio-data-mover nfs-shares=10.40.3.20:/srv/triliovault

The two services must be configured with the same NFS share.

Authorization

The TrilioVault service account must be granted access to multiple users and resources in the project to perform backups. This will involve providing it with a cloud administrator password (set by the keystone app). This is done through the create-cloud-admin-trust operation of the trilio-wlm charm:

juju run-action trilio-wlm/leader create-cloud-admin-trust password=cloudadminpassword

licensing

TrilioVault deployment must be licensed. This is done by uploading the license file (attached as a charm resource) and running the create-license operation of trilio-wlm charm:

juju attach trilio-wlm license=mycorp_tv.lic
juju run-action trilio-wlm/leader create-license

The trilio-wlm and trilio-data-mover applications should now be "active" and ready to use.

Guess you like

Origin blog.csdn.net/m0_49212388/article/details/115238168