Jump to: navigation, search

Difference between revisions of "Zun"

(Agenda for 2017-05-23 0300 UTC)
(Resources)
 
(287 intermediate revisions by 4 users not shown)
Line 1: Line 1:
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.
+
Zun (ex. Higgins) is the OpenStack Containers service. It aims to provide an API service for running application containers without the need to manage servers or clusters.
 +
 
 +
<center>
 +
[[File:OpenStack-zun-image.jpeg|600px]]
 +
</center>
  
 
__TOC__
 
__TOC__
Line 12: Line 16:
 
** [http://launchpad.net/zun Zun Launchpad Project]
 
** [http://launchpad.net/zun Zun Launchpad Project]
 
** [https://bugs.launchpad.net/zun Bug Tracker]
 
** [https://bugs.launchpad.net/zun Bug Tracker]
* Mailing List
 
** [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack Mailing List] for project related discussion
 
*** Add [Zun] to the subject line of new posts about this project.
 
** [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Mailing List Archives] for current discussion.
 
 
* Code Repository
 
* Code Repository
** http://git.openstack.org/cgit/openstack/zun
+
** https://opendev.org/openstack/zun
* Design Spec
 
** https://review.openstack.org/#/c/365754/ The sandbox approach
 
 
* Etherpads
 
* Etherpads
 
**  https://etherpad.openstack.org/p/container-management-service
 
**  https://etherpad.openstack.org/p/container-management-service
Line 30: Line 28:
 
** https://etherpad.openstack.org/p/zun-container-composition
 
** https://etherpad.openstack.org/p/zun-container-composition
 
** https://etherpad.openstack.org/p/zun-nfv-use-cases
 
** https://etherpad.openstack.org/p/zun-nfv-use-cases
 +
** https://etherpad.openstack.org/p/zun-multihost-problems
 +
 +
= Mailing List =
 +
Mailing list discussion for this team is on the OpenStack Developers Mailing List. Prepend the topic tag [Zun] to your subject line depending on the category of your inquiry.
 +
* [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss Subscribe to openstack-discuss@lists.openstack.org]
 +
* [http://lists.openstack.org/pipermail/openstack-dev/ Mailing List Archives openstack-dev (2018 and before)]
 +
* [http://lists.openstack.org/pipermail/openstack-discuss/ Mailing List Archives openstack-discuss ]
  
 
= IRC =
 
= IRC =
 
Our developers use IRC in <code>#openstack-zun</code> on freenode for development discussion.
 
Our developers use IRC in <code>#openstack-zun</code> on freenode for development discussion.
  
= Meetings =
+
= Office Hours =
The Zun team holds public meetings. We meet in <code>#openstack-meeting</code> on Tuesday on the following schedule:
+
The Zun team (office hours) holds public meetings. We meet in <code>#openstack-zun</code> on Tuesday on UTC 03:00 every Tuesday.
 
 
{| class="wikitable"
 
|-
 
| 2017-05-23 || UTC 0300 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Zun+Team+Meeting&iso=20170523T03
 
|-
 
| 2017-05-30 || UTC 0300 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Zun+Team+Meeting&iso=20170530T03
 
|-
 
| 2017-06-06 || UTC 0300 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Zun+Team+Meeting&iso=20170606T03
 
|}
 
  
== Agenda for 2017-05-23 0300 UTC ==
+
== Agenda ==
 
* Roll Call
 
* Roll Call
* Announcements
+
* Announcement
 
* Review Action Items
 
* Review Action Items
* Cinder integration
+
* Blueprints
** #link https://blueprints.launchpad.net/zun/+spec/direct-cinder-integration Direct Cinder integration
+
** #link https://blueprints.launchpad.net/zun/stein Stein blueprints
** #link https://blueprints.launchpad.net/zun/+spec/cinder-zun-integration Cinder integration via Fuxi
+
* Bugs
* Introduce container composition (kevinz)
+
** #link https://bugs.launchpad.net/zun/+bugs?orderby=-id&start=0
** #link https://review.openstack.org/#/c/437759/ The design spec
 
** #link https://etherpad.openstack.org/p/zun-container-composition The etherpad
 
* Support floating IP association (pksingh)
 
** #link https://blueprints.launchpad.net/zun/+spec/floating-ip-association
 
* Others
 
** #link https://blueprints.launchpad.net/zun/+spec/make-sandbox-optional Make infra container optional
 
** #link https://blueprints.launchpad.net/zun/+spec/infra-container-in-db Persist infra container in DB
 
** #link https://etherpad.openstack.org/p/zun-nfv-use-cases NFV use cases
 
 
* Open Discussion
 
* Open Discussion
  
 
== Backlog ==
 
== Backlog ==
* Add Zun Resources to Heat
 
** #link https://blueprints.launchpad.net/heat/+spec/heat-plugin-zun
 
* Add documents for Zun rest API
 
** https://blueprints.launchpad.net/zun/+spec/zun-api-doc
 
  
 
== Previous Meetings ==
 
== Previous Meetings ==
* [http://eavesdrop.openstack.org/meetings/zun/2017/ 2017 ZunTeam Meeting Archive]
+
* [http://eavesdrop.openstack.org/meetings/zun/2019/ 2019 Zun Team Meeting Archive]
 +
* [http://eavesdrop.openstack.org/meetings/zun/2018/ 2018 Zun Team Meeting Archive]
 +
* [http://eavesdrop.openstack.org/meetings/zun/2017/ 2017 Zun Team Meeting Archive]
 
* [http://eavesdrop.openstack.org/meetings/zun/2016/ 2016 Zun Team Meeting Archive]
 
* [http://eavesdrop.openstack.org/meetings/zun/2016/ 2016 Zun Team Meeting Archive]
 
* [http://eavesdrop.openstack.org/meetings/higgins/2016/ 2016 Higgins Team Meeting Archive]
 
* [http://eavesdrop.openstack.org/meetings/higgins/2016/ 2016 Higgins Team Meeting Archive]
 +
 +
= Architecture =
 +
 +
* Zun API: Process REST requests and validate inputted parameters.
 +
* Zun Compute: Launch containers and manage compute resources in localhost.
 +
* Keystone: Authenticate incoming requests.
 +
* Neutron: Provide networking for containers.
 +
* Glance: An option to store container images (another option is DockerHub).
 +
* Kuryr: A Docker network plugin for connecting containers to neutron networks.
 +
 +
[[File:Zun_Architecture.jpg|frame|none]]
  
 
= Frequently Asked Questions =
 
= Frequently Asked Questions =
 
'''1) What is the relationship between Zun and Magnum?'''  
 
'''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.
+
Zun and Magnum are two independent projects. Zun aims to provide API service for managing containerized applications, 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?'''
 
'''2) Who is Zun for? In comparison, who is Magnum for?'''
Line 90: Line 87:
 
'''4) Does Zun compete with Kubernetes (or other COEs)?'''
 
'''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.
+
No. Zun and Kubernetes are complementary. In fact, Zun team is actively working on a Kubernetes integration feature. See [https://blueprints.launchpad.net/zun/+spec/zun-connector-for-k8s this blueprint] for details.

Latest revision as of 06:05, 1 July 2021

Zun (ex. Higgins) is the OpenStack Containers service. It aims to provide an API service for running application containers without the need to manage servers or clusters.

OpenStack-zun-image.jpeg

News

  • 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"

Resources

Mailing List

Mailing list discussion for this team is on the OpenStack Developers Mailing List. Prepend the topic tag [Zun] to your subject line depending on the category of your inquiry.

IRC

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

Office Hours

The Zun team (office hours) holds public meetings. We meet in #openstack-zun on Tuesday on UTC 03:00 every Tuesday.

Agenda

Backlog

Previous Meetings

Architecture

  • Zun API: Process REST requests and validate inputted parameters.
  • Zun Compute: Launch containers and manage compute resources in localhost.
  • Keystone: Authenticate incoming requests.
  • Neutron: Provide networking for containers.
  • Glance: An option to store container images (another option is DockerHub).
  • Kuryr: A Docker network plugin for connecting containers to neutron networks.
Zun Architecture.jpg

Frequently Asked Questions

1) What is the relationship between Zun and Magnum?

Zun and Magnum are two independent projects. Zun aims to provide API service for managing containerized applications, 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)?

No. Zun and Kubernetes are complementary. In fact, Zun team is actively working on a Kubernetes integration feature. See this blueprint for details.