Decide the source of the base images
Bug #1765432 reported by
Jean-Philippe Evrard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Confirmed
|
Low
|
Jesse Pretorius |
Bug Description
We have decided to use lxc images from certain urls, but it's not documented.
We also have URLs that aren't stable, so we should:
- Document the source of the image, and why we chose the image in the reference architecture.
- Make sure the image URL is consistent.
Changed in openstack-ansible: | |
assignee: | nobody → Jesse Pretorius (jesse-pretorius) |
Changed in openstack-ansible: | |
status: | New → Confirmed |
importance: | Undecided → Low |
To post a comment you must log in.
We had the opensuse URL change today and had to do this emergency patch to stop all our tests failing: https:/ /review. openstack. org/562599
Whatever we do, we need a stable interface that works.
LXC has a buggy DNS resolution, but it has worked reasonably well.
LXC's images need quite a bit of adjusting (package removals and such) to use.
We could bite the bullet and implement a playbook to use the ansible- role-diskimage- builder role to prepare the base image, breaking it out of the lxc_hosts/ nspawn_ hosts roles. This would also allow us to unify the trove/octavia diskimage-build processes. I expect the base image build will be very quick given that we require very few things in the image. I'll see if I can find some time to prototype it.