os-*-* tools should be containerised
Bug #1424969 reported by
yuanying
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Triaged
|
High
|
Drago |
Bug Description
os-*-* tools only run from packages at this moment.
it causes that software deployment resource (which is heat resource) doesn't work on micro os (such as atomic or coreos).
we want to use software deployment resource in our heat templates to build bay.
so we need containerized os-*-* tools.
Changed in magnum: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Changed in magnum: | |
importance: | Wishlist → High |
Changed in magnum: | |
milestone: | none → mitaka-1 |
Changed in magnum: | |
assignee: | nobody → Drago (dragorosson) |
milestone: | mitaka-1 → none |
To post a comment you must log in.
Note we already implemented an approach where the required os-* tools are built into a "agent container" image, that is then deployed and used to deploy subsequent containers:
https:/ /github. com/openstack/ heat-templates/ tree/master/ hot/software- config/ heat-container- agent
https:/ /github. com/openstack/ heat-templates/ blob/master/ hot/software- config/ boot-config/ templates/ install_ container_ agent.yaml
The basic approach is to use cloud-init to start the agent container on boot, then heat drives all subsequent launching of containers via the os-* tools running in the agent container.
We used a somewhat modified version of this to implement containerized compute services on TripleO compute nodes, so the basic approach is proven:
https:/ /github. com/openstack/ tripleo- heat-templates/ tree/master/ docker