Operations-related content for OpenStack-Ansible
ce29ea23d1
Currently, attempting to use Trusty (14.04) VMs causes VMs to not provision correctly due to a grub-install error. With respect to this specific issue, this commit updates vm.preseed.j2 by removing some grub-installer options which were not present before the ansible rewrite. Secondly, with that change in place, VMs do not come online on their 10.0.236 addresses as something is overwriting /etc/networking/interfaces, which wipes out the source of the /etc/network/interfaces.d directory. Bug [1] seems to indicate this is in fact an issue and has been resolved, however attempts at using this preseed option (netcfg/target_network_config) were not successful. As a workaround, we simply chattr +i the interfaces file in vm-post-install-script.sh.j2, and then remove the attr in deploy-vms.yml when the instance is up an accessible. [1] https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1361902 Change-Id: I12d0c5108d1df0ab02b69d1b8cdb271a02999602 |
||
---|---|---|
ansible_tools | ||
bowling_ball | ||
cluster_metrics | ||
doc | ||
generate_requirements | ||
leap-upgrades | ||
multi-node-aio | ||
osa-gate-profile | ||
releasenotes | ||
tests | ||
.gitignore | ||
.gitreview | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
LICENSE | ||
multi-node-aio-xenial-ansible | ||
README.rst | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
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.
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.