aboutsummaryrefslogtreecommitdiff
path: root/ansible/roles/nova/tasks/bootstrap.yml
AgeCommit message (Collapse)AuthorFilesLines
2016-11-15Remove Ansible from KollaSteven Dake1-79/+0
Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b
2016-05-13add support for non-default database_port in kolla/ansibleWaldemar Znoinski1-0/+4
This change makes each step of the kolla deployment aware of the port database was configured to listen on. It defaults mariadb_port to database_port. Change-Id: I8e85d5732015afc0a5481cb33e0b629fdfa84a1b Closes-Bug: #1576151 DocImpact
2016-02-19Playbook for nova upgradeMichal Jastrzebski1-47/+1
This creates tree and playbook for nova upgrade. Also other service upgrades will follow standard setup here. Change-Id: Ic31759efaee4986eb87b9ff0968f13189d130d48 Partially-Implements: blueprint upgrade-kolla Implements: blueprint upgrade-nova
2016-02-05Fix two missing toolbox referencesSamYaple1-2/+2
Two patches merged that did not have teh correct name for kolla_toolbox TrivialFix Change-Id: I09e230e29cff496247c32bf227715bfb7caa0a95
2016-02-05Merge "Rename kolla_ansible to kolla_toolbox"Jenkins1-2/+2
2016-02-02Create nova-api databaseSamYaple1-0/+36
This is a required patch. Kilo introduced a nova-api database but didn't use it. [1] Mitaka now uses it and has broken booting instances. [2] [1] https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Compute_.28Nova.29 [2] https://github.com/openstack/nova/blob/df0fca62cf5324f5b6eae0fed1f88c6c9ed61c71/releasenotes/notes/request-spec-api-db-b9cc6e0624d563c5.yaml Change-Id: If0a7f4ba4937fab8d60f5236ca00db06faa768c7 Closes-Bug: #1540579
2016-02-02Rename kolla_ansible to kolla_toolboxSamYaple1-2/+2
This change is needed for clarity. We have a kolla-ansible script. We have a kolla-mesos repo. We plan to have a kolla-ansible repo. Already we have had far too much confusion about whether we are talking about the container or the project. Naming this kolla-toolbox eliminates all of that confusion and its probably a bit more accurate of a name too. Closes-Bug: #1541053 Change-Id: I8fd1f49d5a22b36ede5b10f46b9fe02ddda9007e
2016-01-28Update all bootstraps to use LabelSamYaple1-2/+6
Add bootstrap label to all bootstrap containers to ensure that when the a new container is launched a difference is seen between it and the bootstrap container since we cannot rely on ENV variables for this. This only affects mariadb at this stage, but it is needed to ensure rabbitmq works when we switch to named volumes. Change-Id: Ia022af26212d2e5445c06149848831037a508407 Closes-Bug: #1538136
2016-01-20Fix permissions to /var/lib/nova/Artur Zarzycki1-0/+29
Due to changes with the drop-root work, we lost the ability to write to /var/lib/nova/*. This fixes those permissions and ensures cross container talk works properly between nova_libvirt and nova_compute Additionally, this fixes another issue introduced which saw that nova-compute could not run sudo commands as it did not have a proper sudoers entry Testing from previous deploys means you need a fresh environment. You have to remove all of the named volumes that kolla created in docker. Check these with `docker volume ls` Signed-off-by: Hui Kang <kangh@us.ibm.com> Signed-off-by: Artur Zarzycki <azarzycki@mirantis.com> Co-Authored-By: Sam Yaple <sam@yaple.net> Co-Authored-By: Hui Kang <kangh@us.ibm.com> Closes-Bug: #1533350 Change-Id: I7f864c448a2414e0b5d89f48337be411b891df35
2015-12-31Convert Nova to kolla_dockerSamYaple1-31/+8
Change-Id: I0c6df8e7b732a37ff3cabff8d588f8b7d15df192 Partially-Implements: blueprint kolla-docker-module
2015-11-23Make the database json variable more readableSam Yaple1-6/+11
Additionally remove tty from the container cleanup docker section. It was added in a sed in a previous patchset by serves no purpose. Change-Id: Ib617870616bca687f72ffaa44b2e9a3a11ef1011 Partially-Implements: blueprint cleanup-playbooks
2015-11-23Fix bootstrap for servicesHui Kang1-6/+7
The bootstrap tasks could be started on any node listed in the site.yml The issue is that all the tasks must run on the same node, and the only node that all the tasks can run on is the 'api' node due to needing to start the bootstrap container which binds in the configs. delegate_to is required to ensure that the proper node gets the task. Co-Authored-By: Sam Yaple <sam@yaple.net> Change-Id: Ica04ab366777a571a92212ac22c482f1881d4ecd Closes-Bug: #1513598 Related-Bug: #1513439
2015-11-09Move data container to start.ymlSam Yaple1-18/+0
The original reason for having the data container in the bootstrap.yml was to keep consistency with rabbitmq and mariadb, but in light of this bug we need to move the data container out of the bootstrap.yml role since we will be limiting the hosts that those tasks can run on. Change-Id: I7f2f5979b01807275908699d1243756cb97d3588 Partial-Bug: #1513598
2015-11-09Incorrect parsed variable nameSam Yaple1-1/+1
database_user_create was not correctly referenced when parsing the variable names. This could never actually lead to a situation that reported a false change, but it could break an operation if you were using the --step option with ansible and skipped the database create task. TrivialFix Backport: Liberty Change-Id: Idf69fffcc3814f509448ccea11b7d175f074ccf1
2015-11-05bootstrap takes place on the wrong nodeSam Yaple1-2/+6
The bootstrap must occur on the nova-api node due to binding in the nova-api directory (same goes for all other services) Closes-Bug: #1513439 Backport: Liberty Change-Id: Iab88b49712828085e4d7e7f85e6d8f0b7999a9bf
2015-10-14Add tty to containersSam Yaple1-0/+3
sudo requires a tty to function by default on centos. Instead of tweaking the sudo conf we can just add a tty. This has the added advantage of making the containers more friendly if you have to `docker exec -i <container> bash` into them. Change-Id: If97a02ca1d37c243a787d98ade54bde8d641aecd backport: liberty Partially-Implements: blueprint functional-testing-gate
2015-10-13Bump ansible to 1.9.2Sam Yaple1-2/+0
Ansible 1.9.2 contains the fix needed for docker-py >1.2.0 This is needed for some gate reasons, but it is also a good version bump because it fixes a few issues with delegate_to. Change-Id: Iafbabb3b0232620849d0548c5cd9d8d316c2b0f3 backport: liberty Partially-Implements: blueprint functional-testing-gate
2015-10-06Bring Kolla inline with FHSSam Yaple1-1/+1
This brings Kolla images inline with FHS and should make finding locations of things more consistent and reliable with the linux world at large. Change-Id: Iece5b4da4bace0fb8b1f41a65ab2c852ec73e6f8 Closes-Bug: #1485742
2015-09-23Replace config-external with a JSON file for Novarthallisey1-1/+1
Change-Id: I38c545484a7b1f3906d844eb3a7486e11c4b276a Partially-Implements: blueprint replace-config-external
2015-09-09Enable nova-libvirt to be updatedSteven Dake1-1/+3
Libvirt shuts down existing virtual machines. To solve this problem, the /var/lib/libvirt directory needs to be persisted. By persisting this directory in the nova data container, libvirt can communicate with the sockets setup by the previous data container. Change-Id: I362c533f8493984123686fe6e3f8e43d97434ca6 Closes-Bug: #1494060
2015-09-09Make nova use a data containerSteven Dake1-0/+16
Make nova-libvirt and nova-compute use a data container called nova_data. This data container contains /var/lib/nova/instances data so upgrades to nova-compute work properly. Change-Id: I89362eb0857f7b07503c35178475bc91d0d19ca8 Closes-Bug: #1486333
2015-09-06Properly check failed statusSam Yaple1-5/+1
No need for a new task. Change-Id: I958f87ac9a1434a2f6052e0271f37e5f3109775e Closes-Bug: #1492337
2015-09-04Check exit status of bootstrap containersVladislav Belogrudov1-0/+6
Currently bootstrap containers are waited to exit but are not checked for exit status and ansible runs further tasks. If bootstrapping fails we notice it at much later time. Change-Id: I137fc11b0f9d1f03d2ded08a213e8dbd62741f92 Closes-Bug: #1492337
2015-08-31Fix typo in task bootstrap task namesPaul Bourke1-1/+1
Not quite halloween yet... Change-Id: Ib1973eea0b2dddc0e0845731d1212c4d4447cca5 Closes-Bug: #1490502
2015-08-24Wait for bootstrap containers on the same hosts they runVladislav Belogrudov1-0/+1
Change-Id: Id6a82e6622f712c6fca8205357dec4e5161e46d2 Closes-Bug: #1487387
2015-08-20Use database_user_create in the register operationSteven Dake1-3/+3
The register operation was registering user_database which is a global variable in group_vars/all.yml. This results in glance not being deployable because user_database is overwrriten at keystone task registration time. The result of this is the playbooks fail to deploy. Change-Id: Ic69725fb09aa0a368ec5b0d8f47bfc768c29c70c Closes-Bug: #1486876
2015-08-18Remove Ansible abstraction for NovaSwapnil Kulkarni1-16/+57
Co-Authored-By: Sam Yaple <sam@yaple.net> Change-Id: Iad9fd7010eaf112f169feb54d9a0e97fd693e5f1 Partially-Implements: blueprint remove-abstraction-ansible
2015-07-26Adds glance and nova data volumeSam Yaple1-0/+8
Change-Id: I179a20e637274659cf6e3b2d8a61ff2728fa084b Closes-Bug: #1478315
2015-07-12Ansible Nova w/ libvirt supportSam Yaple1-0/+12
Initial support for Nova in Ansible Partially-Implements: blueprint ansible-service Change-Id: I4b0a74bd3e5daa5664f5e1e622bfb40c3285949e
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 21:40:07 +0000