A previous commit [1] removed the glance data container. Although this
worked at the time (as evident by it passing the gate) the drop root
patches merged after the gate patch causing the glance service to
not have the proper permissions to create this needed directory
[1] I7f2f5979b01807275908699d1243756cb97d3588
Change-Id: I5044de8d348e401a50970fd77671a79d35d2d595
Config directory for ironic-pxe should be created before copying files into it
Change-Id: I5ad8e44273c3d185cf7fbe94787aff47595aabb0
Closes-Bug: #1518330
Extract the Vagrantfile configuration to a Vagrantfile.custom file, to
permit easy customization of the Vagrant deployment without the need to
modify a file under version control.
Closes-Bug: #1517475
Change-Id: I03e3ef373ec47e3d622b77fa9cf88748db99adaa
All the nodes, with the exception of the operator, are build the same
with maybe different specs. We can remove the duplication with a bit of
metaprogramming.
Also pass all expected arguments to the provisionning script,and get
rid of hardcoded path to it.
Closes-Bug: #1517476
Change-Id: I515ef1d529d7ec49038662001a3e5345a941fea7
That sync broke copying configuration files in Ansible playbooks
and made all changes of configuration inside VM as a change in
kolla git repo on host.
Change-Id: I21ecd9a48c0c3263c05f5dbefea7bbc78a919f0a
Closes-Bug: #1515901
This change ensures commands run in the magnum containers are done as the
'magnum' user rather than root.
Change-Id: I18e2febae98aae6d6fc6c61cc2817442f408cb75
Partially-Implements: blueprint drop-root
It currently has auth_url typoed which results in auth_url being
specified twice
Change-Id: Ia5b6385f8d28a23fc05908ceec75a7e8528894d9
Closes-Bug: #1517141
The drop root change for Glance highlighted the fact that we were
binding volumes from glance_data into the wrong container - it was
glance_registry whereas it should be glance_api. This would result in
all images being lost if the glance_api container happens to restart.
Also, we need a sudoers file to chown the file backend dir to the glance
user.
Change-Id: If04337045bb94b3126e48d1f5bf0ea29e20373ae
Closes-Bug: #1516729
Due the to way network namespaces work, they will not survive a
container restart. This is not an issue related to Kolla or Neutron
but rather an issue with how network namespaces work.
This is putting back into place a workaround that was in correctly
removed in the past. We simply cleanup the namespace cruft when the
neutron-agents container restarts thus avoiding this issue.
Change-Id: Ic16f2f766b4fa46347ea14a1ece5a4653c69d779
Closes-Bug: #1511216
