implement magnum bays allowing creation of pods/containers on baremetal or VMs
By creating images for VMs, ironic, and nova-docker that provide the magnum backend service, these images can be started via nova, adding a new host/node/minion for use.
Different images have different advantages/
VM: Has high startup latency and some performance drawbacks but provides much higher security for multi-tenant use cases.
Ironic: May be slightly more difficult to configure and deploy but allows bare metal operation of containers. I suppose it would be possible to have the HW offline when not in use?
nova-docker: Easier to configure as it just needs a nova running with nova-docker plugin installed. Allows running of containers on bare metal. May be more difficult to solve networking issues.
Blueprint information
- Status:
- Complete
- Approver:
- Steven Dake
- Priority:
- Essential
- Drafter:
- Ian Main
- Direction:
- Approved
- Assignee:
- Steven Dake
- Definition:
- Approved
- Series goal:
- Accepted for milestone-1
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Steven Dake
- Completed by
- Steven Dake
Whiteboard
Just curious what is the use case of nova-docker? Why we need to create a nova-docker image here? --jay-lau-513 2014.12.22
Jay,
I don't think we have a clear use case for nova-docker. I think originally the thinking was to use that as a dependency, but IMO it makes more sense to depend on a docker+kubernetes base OS without other dependencies.
Thanks Steven, clear. --jay-lau-513
