Open Stack

I'd be remiss if I didn't point out that the nova LXC driver is much better
supported than the nova-docker driver.

Michael

On Thu, Dec 29, 2016 at 8:01 PM, Esra Celik <celik.esra at tubitak.gov.tr>
wrote:

>
> Hi Sam,
>
> nova-lxc is not recommended in production [1]. And LXD is built on top of
> LXC AFAIK. But I will investigate nova-lxd in detail, thank you.
> If nova-docker will be retired at the end of the day, we will need to
> choose a similar service.
>
> [1] http://docs.openstack.org/newton/config-reference/
> compute/hypervisor-lxc.html
>
> ecelik
>
> ------------------------------
>
> *Kimden: *"Sam Stoelinga" <sammiestoel at gmail.com>
> *Kime: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org>
> *Gönderilenler: *29 Aralık Perşembe 2016 0:13:22
>
> *Konu: *Re: [openstack-dev] [nova][nova-docker] Time to retire
> nova-docker?
>
> Esra,
>
> Not sure what's your use case, but I would also take a look at nova LXC
> driver. It looks like you are treating your Containers as VMs and for that
> I would say the nova lxc driver is a better fit. [1] Docker has specific
> requirements on images and networking, which doesn't fit well in the nova
> model imo.
>
> There is also a new hypervisor LXD which aims to treat containers as VMs
> as well. [2]
>
> [1] http://docs.openstack.org/developer/nova/support-matrix.html
> [2] https://linuxcontainers.org/lxd/introduction/
>
> Regards,
> Sam Stoelinga
>
> On Mon, Dec 26, 2016 at 10:38 AM, Esra Celik <celik.esra at tubitak.gov.tr>
> wrote:
>
>>
>> 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>
>> *Kime: *"OpenStack Development Mailing List (not for usage questions)" <
>> 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,
>> Hongbin
>>
>> On Mon, Dec 26, 2016 at 8:23 AM, Jay Pipes <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?
>>>
>>> Best,
>>> -jay
>>>
>>>
>>> ____________________________________________________________
>>> ______________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:
>>> unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:
>> unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:
>> unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Rackspace Australia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161229/48063fd0/attachment.html>