[openstack-dev] Time to retire nova-docker?

Csatari, Gergely (Nokia - HU/Budapest) gergely.csatari at nokia.com
Tue Dec 27 11:27:35 UTC 2016


Zun provides a lifecycle management interface for the containers started in the COE deployed with Magnum. In other words a COE is still needed for Zun. For more information look the Zun wiki.
Internally, to separate the started containers into different sandboxes Zun uses a fork of nova-docker driver which was developed further to fulfill the specific needs of Zun.
To have support for containers without an additional COE to Nova  Zun provides no solution.
I’ve added Hongbin to the mail to correct me if I’m wrong about Zun.


From: Esra Celik [mailto:celik.esra at tubitak.gov.tr]
Sent: Monday, December 26, 2016 7:38 PM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [nova][nova-docker] Time to retire nova-docker?

Hi Jay, I was asking because our discussions to contribute to nova-docker project ran across the discussions here to retire the project :)

Hongbin, that is exactly what I meant. Using nova-docker it deploys containers to physical machines, not virtual machines.
Using Ironic driver with Magnum is a solution, but I guess every time creating a cluster with Magnum it will redeploy the operating system for the selected physical machine, which is not necessary.
I will investigate Zun project more, thank you very much. What would you say for its current maturity level?

Kimden: "Hongbin Lu" <hongbin034 at gmail.com<mailto:hongbin034 at gmail.com>>
Kime: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Gönderilenler: 26 Aralık Pazartesi 2016 17:53:00
Konu: Re: [openstack-dev] [nova][nova-docker] Time to retire nova-docker?

I guess "extra virtualization layer" means Magnum provisions a Container Orchestration Engines (COE) on top of nova instances. If the nova instances are virtual machines, there is a "extra virtualization layer".

I think you could consider using Magnum with Ironic driver. If the driver is Ironic, COEs are deployed to nova instances that are physical machines provided by Ironic. Zun project [1] could be another option for your use case. Zun is similar to nova-docker, which enables running containers on compute hosts. You could find a thoughtful introduction here [2].

[1] https://wiki.openstack.org/wiki/Zun
[2] http://www.slideshare.net/hongbin034/zun-presentation-openstack-barcelona-summit

Best regards,

On Mon, Dec 26, 2016 at 8:23 AM, Jay Pipes <jaypipes at gmail.com<mailto:jaypipes at gmail.com>> wrote:

On 12/26/2016 08:23 AM, Esra Celik wrote:

Hi All,

It is very sad to hear nova-docker's retirement. Me and my team (3) are
working for a cloud computing laboratory and we were very keen on
working with nova-docker.
After some research about its current state I saw these mails. Will you
actually propose another equivalent to nova-docker or is it just the
lack of contributors to this project?
Some of the contributors previously advised us the magnum project
instead of nova-docker, however it does not satisfy our needs because of
the additional virtualization layer it needs.
If the main problem is the lack of contributors we may participate in
this project.
There's never any need to ask permission to contribute to a project :) If nova-docker driver is something you cannot do without, feel free to contribute to it.

That said, Magnum does seem to be where most of the docker-related contributions to the compute landscape have moved. So, it's more likely you will find company in that project and perhaps be able to make more effective contributions there. Can I ask what is the "extra virtualization layer" that you are referring to in Magnum?


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<mailto:OpenStack-dev-request at lists.openstack.org?subject:unsubscribe>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161227/9d43b700/attachment.html>

More information about the OpenStack-dev mailing list