sastre | Automation Tools for Cisco SD-WAN Powered by Viptela | Continuous Backup library

Create a directory to serve as root for backup files, log files and rc files:. When Sastre is executed, data/ and logs/ directories are created as needed to store backup files and application logs. These are created under the directory where Sastre is run.
Verify that Sastre can run:.
Install required Python packages:.
First, proceed with the GitHub install outlined above.
When set, host proxy environment variables (http_proxy, https_proxy and no_proxy) are used during the build and execution of the container.
The container has a /shared-data volume.
Sastre data/ and logs/ directories are created under /shared-data.
A sample dcloud-lab.sh is copied to /shared-data/rc if no /shared-data/rc directory is present.
Directory structure: /shared-data/data - Used as the vManage backup data repository /shared-data/logs - Where the logs are saved /shared-data/rc - Used to store 'rc' files defining environment variables used by Sastre: VMANAGE_IP, VMANAGE_USER, etc.
The suggested docker run command above bind-mounts the /shared-data volume, i.e. it is mapped to a host system directory. This facilitates transferring of data to/from the container (e.g. vManage backups). The host directory is relative to the location where the docker run command is executed.
Docker run will spin-up the container and open an interactive session to it using the ash shell. Sdwan commands (e.g. sdwan backup all, etc) can be executed at this point. Typing 'exit' will leave the ash shell, stop and remove the container. Everything under data, rc and logs is persisted to the corresponding host system directories.