
Due to the rather terrible virt_net module, only one action can be done on the virt networks at any one time. This means that the current action of setting them to autostart has no effect, because the module does not do it. Also, the current action of disabling the default network and disabling it from autostarting also does not take full effect. As such, after a host reboot, the default network autostarts, and the other networks are not started and the VM's cannot start. When trying to resolve this by re-running the host setup, the play ignores any existing virt networks - so the issue cannot be fixed. This patch does the following: 1. Ensures that the default network does not autostart. This is done by splitting the disabling of the network, and the disabling of autostart into two tasks. 2. Changes the define/create action into a single action which will not change the network configuration if it is defined. 3. Implements the setting of the network as active, and the setting of it to autostart as two seperate tasks. This ensures that both actions are actually implemented. Change-Id: I608f2607824fac649f4e018d89094d57047134b3
Team and repository tags
OpenStack-Ansible Operator Tooling
This repository is a collecting point for various scripts and tools which OpenStack-Ansible Developers and Operators have found to be useful and want to share and collaboratively improve.
The contents of this repository are not strictly quality managed and are only tested by hand by the contributors and consumers. Anyone using the tooling is advised to very clearly understand what it is doing before using it on a production environment.
- Documentation for the project can be found at:
- Release notes for the project can be found at:
-
https://docs.openstack.org/releasenotes/openstack-ansible-ops/
- The project source code repository is located at:
-
https://git.openstack.org/cgit/openstack/openstack-ansible-os_ops
- The project home is at:
Galaxy roles
OpenStack Ansible backup
This role will perform backups for OpenStack-Ansible deployments and it needs to run on the deploy node. It will backup data on container and then synchronize backup files to the deploy node.