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...") |
(No difference)
|
Revision as of 20:38, 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.
Contents
News
- 2016-03-04 The Fuxi project was found
- 2016-08-02 Fuxi joined OpenStack as a Kuryr sub-project
Resources
- Launchpad Project Pages
- Mailing List
- OpenStack Mailing List for project related discussion
- Add [Zun] to the subject line of new posts about this project.
- OpenStack Mailing List Archives for current discussion.
- OpenStack Mailing List for project related discussion
- Code Repository
- Design Spec
- https://review.openstack.org/#/c/365754/ The sandbox approach
- Etherpads
IRC
Our developers use IRC in #openstack-zun
on freenode for development discussion.
Meetings
The Zun team holds public meetings. We meet in #openstack-meeting
on Tuesday on the following schedule:
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)
- 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
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.