starlingx/docs
Code Issues Proposed changes
docs/doc/source/backup/running-ansible-backup-playbook-remotely.rst
Stone e1180949ca Backup and Restore 
Patch 2 review edits.

Stripped spaces at EOLs. Deleted vscode hidden directory.

Initial review and resolved supporting additions to source/shared/strings.txt

Signed-off-by: Stone <ronald.stone@windriver.com>
Change-Id: I21895e0f451d1a11b8f9813034c31a049d4f9ad8
Signed-off-by: Stone <ronald.stone@windriver.com>
2020-12-08 15:44:08 -05:00

1.9 KiB
Raw Blame History

Run Ansible Backup Playbook Remotely

In this method you can run Ansible Backup playbook on a remote workstation and target it at controller-0.

  • You need to have Ansible installed on your remote workstation, along with the Ansible Backup/Restore playbooks.
  • Your network has IPv6 connectivity before running Ansible Playbook, if the system configuration is IPv6.

  1. Log in to the remote workstation.

  2. Provide an Ansible hosts file, either, a customized one that is specified using the -i option, or the default one that resides in the Ansible configuration directory (that is, /etc/ansible/hosts). You must specify the floating IP of the controller host. For example, if the host name is _Cluster, the inventory file should have an entry _Cluster, for example:

    ---all:
    hosts:
    wc68:

    ansible_host: 128.222.100.02

    _Cluster:

    ansible_host: 128.224.141.74

  3. Run Ansible Backup playbook:

    ~(keystone_admin)$ ansible-playbook <path-to-backup-playbook-entry-file> --limit host-name -i <inventory-file> -e <optional-extra-vars>

    The generated backup tar file can be found in <host_backup_dir>, that is, /home/sysadmin, by default. You can overwrite it using the -e option on the command line or in an override file.

    Warning

    If a backup of the local registry images file is created, the file is not copied from the remote machine to the local machine.