Revision as of 13:52, 12 May 2015

Weekly Containers Team Meeting

The OpenStack Containers Team holds public meetings. We meet in #openstack-meeting-alt on alternating Tuesdays on the following schedule:

Please feel free to add items to the agenda below with your name and we'll cover them.

Agenda for 2015-05-12 1600 UTC

• Roll Call
• Announcements
  • 1) Reminder: Our IRC Meeting will be skipped on 2015-05-19 because we will be at the Vancouver Design Summit
• Review Action Items
  • (none)
• It is essential we finish design session planning (#link https://etherpad.openstack.org/p/liberty-magnum-topics)
• Discuss adopting nova-docker as an in-tree Nova driver
  • #link http://lists.openstack.org/pipermail/openstack-dev/2015-May/063727.html ML Thread about in-tree nova-docker
  • Magnum plans to get all of its Nodes from Nova through Heat. Ideally, these would come from whatever virt-driver Nova has loaded. Over time, we should become more and more agnostic about what instance types Nova produces. One valid use case is running Magnum Bays on Nodes that were created using the nova-docker virt driver such that the Bay Nodes are actually containers, and when we run containers on the Bay, we are actually running nested containers. This leads to more densely packed workloads in situations where workload consolidation is the key goal, and security isolation is a non-goal.
  • Note that use of nova-docker assumed that you use the Nova API to treat a (docker container) Nova instance as a machine, not as a container. All container specific features that reach beyond the scope of the Nova API should be implemented in Magnum, not Nova.
  • Note that nova-docker started within the Nova tree, and was pulled out into a Stackforge project so it could be worked on as a separate effort with a high commit velocity. It needed more test coverage, and additional features. Current commit velocity is low, and there are not a ton of bugs to deal with. Those were added, and now would be a good time to consider bringing it back into the Nova tree again. I think this is a good idea, and I want your input.
  • Let's discuss the possibility of adopting nova-docker to maintain it within the Nova tree so that it does not fall into disrepair. Do we think this is something we would be willing to take on as part of the Magnum team responsibilities?
  • #link https://bugs.launchpad.net/nova-docker/ nova-docker bug list
  • As you can see, the bug list is mostly full of wishlist items for additional features. One approach might be to adopt this as maintainers, not as feature developers. In that case, we would commit to fixing defects, and reviewing new features, but that we would not necessarily allocate any resources into feature development. Thoughts?
• Blueprint/Task Review
• Open Discussion

Agenda Template

• Roll Call
• Announcements
• Review Action Items
• Blueprint Review
• Open Discussion

Previous Meetings

• 2015 Containers Team Meeting Archive
• 2014 Containers Team Meeting Archive