aboutsummaryrefslogtreecommitdiff
path: root/ansible/roles/nova/tasks/start_compute.yml
AgeCommit message (Collapse)AuthorFilesLines
2016-11-15Remove Ansible from KollaSteven Dake1-103/+0
Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b
2016-11-07Allow cinder-volume to be configured to use NFSxionglingfeng1-0/+3
Allow cinder-volume, nova-compute and nova-libvirtd to be configured to use NFS. In order to mount and work with NFS shares, several containers needed the NFS packages installed during build time. One somewhat significant change is the addition of an explicit bind volume for nova-compute that has shared mounts enabled. According to docker-run(1), the shared mount propagation flag can only be specified for bind mounted Docker volumes and not named volumes. In an NFS setup, cinder-volume mounts the NFS shares so that it can create and manage the Cinder volumes. When a new instance is created with a Cinder volume or a Cinder volume is attached to an existing instance, nova-compute mounts the Cinder volume from the NFS share for nova-libvirtd. In order for nova-libvirtd to then see those Cinder volumes the shared mounts flag must be enabled for the Docker volume. Remove the rpcbind container as it is only necessary for operators who are using NFSv3 or lower. There is no known need for this currently however, this container can be added in the future should an operator require it. Co-authored-by: Ryan Hallisey <rhallise@redhat.com> Co-authored-by: Andrew Widdersheim <amwiddersheim@gmail.com> Change-Id: Iad77c05bce8876bdcc69b7ec22edd50e3bf48b9f Closes-Bug: #1530515 Partially implements: blueprint nfs-support-in-cinder
2016-10-18Bump retries in starting nova-libvirt to 5Jeffrey Zhang1-2/+2
retries: 1 won't really retry in part of ansible release. Bumping the number to 5 ensure it works as expected Change-Id: I9f131001bd96ed33832b42cc8143327f249e916a Closes-Bug: #1634401
2016-10-15Fix stale namespace removal issueJeffrey Zhang1-3/+3
When using both /run and /run/netns in docker container, mount propagation won't work when delete namespace after the containers are restarted. This PS makes /run mount as shared. Closes-Bug: #1616268 Change-Id: Ie16699e1b193b2bf1263d89ea634e89ea69add9e
2016-10-03Fix ironic failedJeffrey Zhang1-0/+1
* Mount system folder in ironic-conductor * Add package need in ironic-conductor * Fix the log path issue * Add ironic sudoer in ironic-base * Fix credential issue * Do not start nova-compute when enable ironic Closes-Bug: #1629334 Change-Id: If9d478c6513de37465403d458a88cf0da7ebd8a6
2016-09-21Cinder cannot use external non-LVM iSCSI storageVladislav Belogrudov1-1/+1
Currently Cinder enables iscsid service only when LVM is choosen as backend. This fix will allow to specify external iSCSI storage via configuration add-on and to run iscsid independently of LVM settings. Change-Id: Iaae0f8025534e5ab1c5f9d5e812a7d41129915ef Closes-Bug: 1614125
2016-08-29Fix removing nova_libvirt container issueJeffrey Zhang1-0/+5
Retry once when removing or upgrading nova_libvirt to ensure it is removed Closes-Bug: #1617741 Change-Id: I8b5046a438c0ef3599a4333bbe77333f0af323ff Signed-off-by: Jeffrey Zhang <zhang.lei.fly@gmail.com>
2016-07-25Simplify the Cinder LVM backendJeffrey Zhang1-1/+1
Remove the unnecessary option in the group_vars/all.yml file. * removed some cinder.conf options like volume_backend_name, iscsi_helper, iscsi_protocol etc. these value can be configured by custom cinder.conf file, no need export as global variables. * remove meaningless iscsi_ip_addess, which is not used in LVM driver * force start iscsi relate when enable_cinder_backend_lvm is yes TrivialFix Change-Id: Ifcbfdad15e4d68bc5f20fc77e0315a09983ef022
2016-06-21Merge "Add named volume for nova-libvirt"Jenkins1-0/+1
2016-06-20Add named volume for nova-libvirtHui Kang1-0/+1
VM instance state (e.g., instance.xml) should be persistent regardless of nova-libvirt container. Change-Id: I4463d0634db2aaefde7dc2c45a144e920d9cb1ac Closes-Bug: #1569828
2016-05-03map the host localtime to the containerJeffrey Zhang1-0/+5
Closes-Bug: #1577148 Change-Id: I636cefc63cf532434a41af3898b63dffa711e280
2016-04-15Merge "Adds ansible code for iscsid and tgtd containers"Jenkins1-7/+14
2016-04-12Adds ansible code for iscsid and tgtd containersSerguei Bezverkhi1-7/+14
This partially implements iscsi and lvm2 support for cinder in Kolla. Adds ansible code for iscsid and tgtd containers. Change-Id: I2a4cfcf104397396ea61a09637d9ef3fc77b515f Partially-Implements: blueprint iscsi-lvm2-docker
2016-04-04Correct typoSwapnil Kulkarni (coolsvap)1-1/+1
The typo was missed and the code got merged. Added commit to correct it TrivialFix Change-Id: Ice33bcb5fb2f8826054feeae41370038f86bcf6b
2016-04-03Implement nova-ssh containerJeffrey Zhang1-0/+15
Add a nova-ssh container to handle the `nova migrate` and `nova resize` case, in which the nova will use ssh to copy files between machines. Change-Id: Ie6675943f3aeabfbba8589d308d55b9c89d732db Closes-Bug: #1562141
2016-03-22Make heka collect libvirtd.log in nova_libvirt containerVikram Hosakote1-0/+1
Test results of this patch set are at: http://paste.openstack.org/show/491382/ Change-Id: I1bc8bdb3180f30dc69af28a35fa057ac801bde0f Closes-Bug: #1560298
2016-03-15Change libvirt volume name to libvirtdSamYaple1-2/+2
This change is a "futureproofing" thing. It has already been discussed that libvirt should not be a child of nova and should be removed out to the base docker directory (just like openvswitch isn't a child of neutron). That is not going to happen this cycle but when it does we can't change the name of the volume. This updates the volumes to the proper name of libvirtd. This is in contrast with the libvirtlogd volume that will be needed in newton due to libvirt 1.3 Of note, the container can remain named nova_libvirt since we can change that on the fly later without breaking instances. This wont break liberty as named_volumes are not backported yet. TrivialFix Change-Id: I16cf9e1b1dbba9b5a9f5cc883494580e276d4f72
2016-02-19Make Heka collect Nova logsÉric Lemoine1-3/+3
Partially implements: blueprint heka Change-Id: I67dfc5d762d74454e4a852dd61c57fe9cd4b78c8
2016-02-19Playbook for nova upgradeMichal Jastrzebski1-0/+65
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