Difference between revisions of "ContainersTeam"
(Add Network Subteam) |
m |
||
| Line 29: | Line 29: | ||
== Container Networking Subteam == | == Container Networking Subteam == | ||
| − | The container networking subteam is focused on improving networking capabilities within the Magnum project. The subteam is under formation and will initially focus on executing the Native Docker Networking [https://blueprints.launchpad.net/magnum/+spec/native-docker-network Blueprint]. This subteam will be considered successful once Magnum users can seamlessly leverage networking capabilities that are equal to, or better than, running containerized applications in non-OpenStack environments. The subteam currently utilizes the same | + | The container networking subteam is focused on improving networking capabilities within the Magnum project. The subteam is under formation and will initially focus on executing the Native Docker Networking [https://blueprints.launchpad.net/magnum/+spec/native-docker-network Blueprint]. This subteam will be considered successful once Magnum users can seamlessly leverage networking capabilities that are equal to, or better than, running containerized applications in non-OpenStack environments. The subteam currently utilizes the same communication channels as the primary containers team. A separate [https://wiki.openstack.org/wiki/Meetings/Containers#Container_Networking_Subteam_Meeting meeting] has been scheduled to advance the Native Docker Networking [https://blueprints.launchpad.net/magnum/+spec/native-docker-network Blueprint] and understand if additional separate meetings are required. |
[[category: Working_Groups]] | [[category: Working_Groups]] | ||
Revision as of 15:55, 23 June 2015
Contents
OpenStack Containers Team
The Containers team is a cross-functional team for OpenStack community stakeholders interested in adding better support in OpenStack for container technology. The team was initially formed in May 2014, and currently has a clear vision for advancing container technology in existing OpenStack services, and new services and tools that evolve OpenStack to track with new technological advances in this area. This team will be considered successful once users of OpenStack can create and manage containers on OpenStack with an experience consistent with what they expect from using the Nova service to get virtual machines.
This team is actively engaged refining Magnum, a Containers Service for OpenStack.
Membership
Anyone interested in containers support in OpenStack may join the OpenStack Containers Team on Launchpad for meeting invite updates.
If you wish to become a core member of the team, we recommend fixing existing bugs, implementing blueprints, and reviewing the magnum and python-magnumclient repos.
Meetings
This team has a weekly meeting schedule on the main OpenStack meeting schedule:
Top Themes
This team has identified the following areas of focus:
- Container support in OpenStack, with minimum code duplication
- Advance on our vision of container integration with OpenStack
- API support for using features from Containers that are not offered by virtual machines.
Mailing List
Mailing list discussion for this team is on the OpenStack Developers Mailing List. Prepend the topic tag [Containers] or [Magnum] to your subject line depending on the category of your inquiry.
IRC
Team members are encouraged to join the #openstack-containers channel or Freenode. For those also interested in the nova-docker virt driver on Stackforge may also be interested in the #nova-docker channel.
Container Networking Subteam
The container networking subteam is focused on improving networking capabilities within the Magnum project. The subteam is under formation and will initially focus on executing the Native Docker Networking Blueprint. This subteam will be considered successful once Magnum users can seamlessly leverage networking capabilities that are equal to, or better than, running containerized applications in non-OpenStack environments. The subteam currently utilizes the same communication channels as the primary containers team. A separate meeting has been scheduled to advance the Native Docker Networking Blueprint and understand if additional separate meetings are required.
