Jump to: navigation, search

Difference between revisions of "Zun"

(Agenda for 2017-07-11 0300 UTC)
Line 49: Line 49:
* Roll Call
* Roll Call
* Announcements
* Announcements
** Hongbin, Kevin and Shengqin will be at OpenStack China Day 2017-07-25.
** No meeting at 2017-07-25 due to OpenStack Days China.
*** Someone volunteer to hold the team meeting? or cancel it?
*** #link http://openstackdaychina.org/
** New BPs created
** New BPs created
*** #link https://blueprints.launchpad.net/zun/+spec/internal-dns-resolution Neutron DNS Using Container hostname
*** #link https://blueprints.launchpad.net/zun/+spec/show-container-engine-info Introduce an API to show container engine info
*** #link https://blueprints.launchpad.net/zun/+spec/multi-node-ci Setup CI for multi-node Zun deployment
*** #link https://blueprints.launchpad.net/zun/+spec/container-actions-api Introduce API to track status of each container actions
* Review Action Items
* Review Action Items
** hongbin figure out why project logo is missing in Project Navigator (DONE)
*** #link https://www.openstack.org/software/project-navigator The logo is there now
** hongbin figure out why project logo is missing in LB as well (DONE)
*** #link https://launchpad.net/zun The logo is there now.
* Cinder integration (hongbin)
* Cinder integration (hongbin)
** #link https://blueprints.launchpad.net/zun/+spec/direct-cinder-integration Direct Cinder integration
** #link https://blueprints.launchpad.net/zun/+spec/direct-cinder-integration Direct Cinder integration

Revision as of 14:59, 13 July 2017

Zun (ex. Higgins) is a Container Management service for OpenStack. It aims to provide an OpenStack API for launching and managing containers backed by different container technologies.


  • 2016-04-20 According to the discussion in the OpenStack Austin design summit, we are going to create a new project (which is Higgins) for providing OpenStack container service. The Magnum project (another OpenStack project for containers) will focus on deployment and management of Container Orchestration Engines (COEs).
  • 2016-06-07 We renamed the project from "Higgins" to "Zun"



Our developers use IRC in #openstack-zun on freenode for development discussion.


The Zun team holds public meetings. We meet in #openstack-meeting on Tuesday on the following schedule:

2017-07-18 UTC 0300 Tuesday http://www.timeanddate.com/worldclock/fixedtime.html?msg=Zun+Team+Meeting&iso=20170718T03
2017-07-25 N/A Cancel due to OpenStack China Day
2017-08-01 UTC 0300 Tuesday http://www.timeanddate.com/worldclock/fixedtime.html?msg=Zun+Team+Meeting&iso=20170801T03

Agenda for 2017-07-11 0300 UTC


Previous Meetings

Frequently Asked Questions

1) What is the relationship between Zun and Magnum?

Zun and Magnum are two independent projects. Zun aims to provide APIs to manage containers, while Magnum provides APIs to provision and manage Container Orchestration Engine (COEs), such as Kubernetes.

2) Who is Zun for? In comparison, who is Magnum for?

Zun is for users who want to create and manage containers as OpenStack-managed resource. Containers managed by Zun are supposed to be integrated well with other OpenStack resources, such as Neutron network and Cinder volume. Users are provided a simplified APIs to manage containers without the need to explore the complexities of different container technologies. Magnum is for users who want a self-service solution to provision and manage a Kubernetes (or other COEs) cluster.

3) What is the difference between Zun and nova-docker?

Nova-docker allows accessing containers via Nova's API, while Zun is not bounded by Nova's API.

4) Does Zun compete with Kubernetes (or other COEs)?

We do not intend to compete with Kubernetes or other COEs. In fact, Kubernetes provides Container Orchestration and many other advanced features (i.e. keep container alive, load balancing, etc.). In comparison, Zun will start with basic container operations (i.e. CRUD) and focus on tight integration with OpenStack.