Jump to: navigation, search

Difference between revisions of "Fuxi"

(Created page with "Fuxi focuses on enabling Docker container to use Cinder volume and Manila share, thus Docker volume can reuse the advance features and numerous vendor drivers in Cinder and Ma...")
 
(Meetings)
 
(One intermediate revision by the same user not shown)
Line 10: Line 10:
 
= Resources =
 
= Resources =
 
* Launchpad Project Pages
 
* Launchpad Project Pages
** [http://launchpad.net/zun Zun Launchpad Project]
+
** [https://launchpad.net/fuxi Fuxi Launchpad Project]
** [https://bugs.launchpad.net/zun Bug Tracker]
+
** [https://bugs.launchpad.net/fuxi Bug Tracker]
 
* Mailing List
 
* Mailing List
 
** [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack Mailing List] for project related discussion
 
** [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.
+
*** Add [Fuxi][Kuryr] to the subject line of new posts about this project.
 
** [http://lists.openstack.org/pipermail/openstack-dev/ OpenStack Mailing List Archives] for current discussion.
 
** [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
+
** http://git.openstack.org/cgit/openstack/fuxi
* Design Spec
 
** https://review.openstack.org/#/c/365754/ The sandbox approach
 
* Etherpads
 
**  https://etherpad.openstack.org/p/container-management-service
 
** https://etherpad.openstack.org/p/zun-architecture-decisions
 
** https://etherpad.openstack.org/p/zun-container-state-management
 
** https://etherpad.openstack.org/p/zun-container-image
 
** https://etherpad.openstack.org/p/zun-ocata-planning
 
  
 
= IRC =
 
= IRC =
Our developers use IRC in <code>#openstack-zun</code> on freenode for development discussion.
+
Our developers use IRC in <code>#openstack-kuryr</code> on freenode for development discussion.
  
 
= Meetings =
 
= Meetings =
The Zun team holds public meetings. We meet in <code>#openstack-meeting</code> on Tuesday on the following schedule:
+
Our developers are expected to join Kuryr weekly team meeting holding at IRC public channel. Check [https://wiki.openstack.org/wiki/Meetings/Kuryr here] for meeting schedule.
 
 
{| class="wikitable"
 
|-
 
| 2016-11-15 || UTC 0300 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Zun+Team+Meeting&iso=20161115T03
 
|-
 
| 2016-11-22 || UTC 0300 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Zun+Team+Meeting&iso=20161122T03
 
|-
 
| 2016-11-29 || UTC 0300 Tuesday || http://www.timeanddate.com/worldclock/fixedtime.html?msg=Zun+Team+Meeting&iso=20161129T03
 
|}
 
 
 
== Agenda for 2016-11-22 0300 UTC ==
 
* Roll Call
 
* Announcements
 
* Review Action Items
 
** hongbin add k8s bp to weekly meeting agenda (DONE)
 
* Container image store (mkrai)
 
** #link https://blueprints.launchpad.net/zun/+spec/glance-integration The BP
 
** #link https://review.openstack.org/#/c/383678/ Madhuri's patch
 
** #link https://review.openstack.org/#/c/380298/ Shubham's patch
 
* Container sandbox (hongbin)
 
** #link https://blueprints.launchpad.net/zun/+spec/neutron-integration The BP
 
** #link https://review.openstack.org/#/c/365754/ The proposed spec (merged)
 
** #link https://review.openstack.org/#/c/380646/ The patch
 
* Open Discussion
 
 
 
== Backlog ==
 
* Kubernetes integration (shubhams)
 
** #link https://blueprints.launchpad.net/zun/+spec/k8s-integration
 
* Support interactive mode (kevinz)
 
** #link https://blueprints.launchpad.net/zun/+spec/support-interactive-mode The BP
 
** #link https://review.openstack.org/#/c/396841/ The design spec
 
 
 
== Previous Meetings ==
 
* [http://eavesdrop.openstack.org/meetings/zun/2016/ 2016 Zun Team Meeting Archive]
 
* [http://eavesdrop.openstack.org/meetings/higgins/2016/ 2016 Higgins Team Meeting Archive]
 
  
 
= Frequently Asked Questions =
 
= Frequently Asked Questions =
'''1) What is the relationship between Zun and Magnum?'''
+
TBD
 
 
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.
 

Latest revision as of 20:44, 23 November 2016

Fuxi focuses on enabling Docker container to use Cinder volume and Manila share, thus Docker volume can reuse the advance features and numerous vendor drivers in Cinder and Manila. With Fuxi, Cinder and Manila can be used as the unified persistence storage provider for virtual machine, baremetal and Docker container.

News

Resources

IRC

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

Meetings

Our developers are expected to join Kuryr weekly team meeting holding at IRC public channel. Check here for meeting schedule.

Frequently Asked Questions

TBD