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

[Álvaro López García]

On 22 Dec 2016 (21:30), Matt Riedemann wrote:
>
> (...)
> 
> I know people are running it and hacking on it outside of the community
> repo, which is fine, and if someone doing that wanted to stand up and say
> they wanted to own the repo and be the core team I'd be fine with that too,
> but so far no one has done that in the last few years. If you're already
> maintaining it outside of the community I don't know why you wouldn't just
> do that development in the open, and maybe get a free bug fix at times from
> another contributor, but I suppose people have their reasons (secret sauce
> and all that). So meh.

We are using nova-docker and we have contributed back several changes,
(some improvements and some bugfixes) to the community. We cannot aford
the burden of being the core team for nova-docker though, but we would
be happy to see nova-docker maintained at least until Zun is not in beta
status.

Cheers,
-- 
Álvaro López García  al...@ifca.unican.es
Instituto de Física de Cantabria http://alvarolopez.github.io
Ed. Juan Jordá, Campus UC  tel: (+34) 942 200 969
Avda. de los Castros s/nskype: aloga.csic
39005 Santander (SPAIN)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Esra Celik]

Maxim, Matt, 

Thanks a lot we will try Virtuozzo soon, I will share the results, 

Best regards, 
ecelik 

- Orijinal Mesaj -

> Kimden: "Matt Riedemann" <mrie...@linux.vnet.ibm.com>
> Kime: openstack-dev@lists.openstack.org
> Gönderilenler: 29 Aralık Perşembe 2016 17:37:33
> Konu: Re: [openstack-dev] [nova][nova-docker] Time to retire nova-docker?

> On 12/29/2016 8:25 AM, Maxim Nestratov wrote:
> > Hi Esra,
> >
> > Take a look at Virtuozzo, which is supported in Nova via libvirt
> > virt_type=parallels. It provides both VMs and OS Containers similar to
> > lxc except our containers have beed in production for more than 10 years
> > already. Though
> > http://docs.openstack.org/developer/nova/support-matrix.html looks a bit
> > outdated, you still can use Libvirt Virtuozzo CT column to understand
> > what features are supported.
> >
> > Best,
> >
> > Maxim
> >

> I was going to say, of the in-tree container support in Nova, the
> Virtuozzo container driver (part of the libvirt driver) is the most well
> maintained and actually has CI testing. We don't have regular CI testing
> for the LXC driver, we have an experimental queue job for it but it has
> rolling failures that no one has been able to figure out so it's never
> been made voting.

> --

> Thanks,

> Matt Riedemann

> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Matt Riedemann]

On 12/29/2016 8:25 AM, Maxim Nestratov wrote:

Hi Esra,

Take a look at Virtuozzo, which is supported in Nova via libvirt
virt_type=parallels. It provides both VMs and OS Containers similar to
lxc except our containers have beed in production for more than 10 years
already. Though
http://docs.openstack.org/developer/nova/support-matrix.html looks a bit
outdated, you still can use Libvirt Virtuozzo CT column to understand
what features are supported.

Best,

Maxim



I was going to say, of the in-tree container support in Nova, the 
Virtuozzo container driver (part of the libvirt driver) is the most well 
maintained and actually has CI testing. We don't have regular CI testing 
for the LXC driver, we have an experimental queue job for it but it has 
rolling failures that no one has been able to figure out so it's never 
been made voting.


--

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Maxim Nestratov]

Hi Esra,

Take a look at Virtuozzo, which is supported in Nova via libvirt virt_type=parallels. It provides both VMs and OS 
Containers similar to lxc except our containers have beed in production for more than 10 years already. Though 
http://docs.openstack.org/developer/nova/support-matrix.html looks a bit outdated, you still can use Libvirt Virtuozzo 
CT column to understand what features are supported.


Best,

Maxim


29-Dec-16 12:01, Esra Celik пишет:


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" <sammiest...@gmail.com>
*Kime: *"OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@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.e...@tubitak.gov.tr 
<mailto:celik.e...@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" <hongbin...@gmail.com 
<mailto:hongbin...@gmail.com>>
*Kime: *"OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org
<mailto:openstack-dev@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 <jaypi...@gmail.com 
<mailto:jaypi...@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.
   

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

[Michael Still]

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.e...@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" <sammiest...@gmail.com>
> *Kime: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@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.e...@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" <hongbin...@gmail.com>
>> *Kime: *"OpenStack Development Mailing List (not for usage questions)" <
>> openstack-dev@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 <jaypi...@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
>>> contribu

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

[Esra Celik]

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 

- Orijinal Mesaj -

> Kimden: "Sam Stoelinga" <sammiest...@gmail.com>
> Kime: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev@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.e...@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" < hongbin...@gmail.com >
> > 
> 
> > > Kime: "OpenStack Development Mailing List (not for usage questions)" <
> > > openstack-dev@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 < jaypi...@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

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

[Sam Stoelinga]

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.e...@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" <hongbin...@gmail.com>
> *Kime: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@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 <jaypi...@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-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Esra Celik]

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? 



- Orijinal Mesaj -


Kimden: "Hongbin Lu" <hongbin...@gmail.com> 
Kime: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@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 < jaypi...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Hongbin Lu]

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  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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Jay Pipes]

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Esra Celik]

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. 

Any o pinions? 

ecelik 

- Orijinal Mesaj -

> Kimden: "Matt Riedemann" <mrie...@linux.vnet.ibm.com>
> Kime: openstack-dev@lists.openstack.org
> Gönderilenler: 23 Aralık Cuma 2016 6:30:53
> Konu: Re: [openstack-dev] [nova][nova-docker] Time to retire nova-docker?

> On 12/22/2016 8:26 PM, Tony Breeds wrote:
> > Hi All,
> > I know this comes up from time to time, but as the subject says, is it time
> > to retire nova-docker.
> >
> > The nova-docker has lagged behind the last 6 months of nova development and
> > no
> > longer passes simple CI unit tests. There are open patches to at least get
> > the
> > unit tests to pass[1] but if the current core team no longer has time (no
> > offence intended) then perhaps we should just archive it.
> >
> > Thoughts?
> >
> > Yours Tony.
> > [1]
> > https://review.openstack.org/#/q/status:open+project:openstack/nova-docker+branch:master+topic:fixes_for_master
> >
> >
> >
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >

> +1 for what it's worth.

> People show up in the nova channel in IRC from time to time (maybe once
> or twice per year) asking about the state of the driver and I send them
> to the nova-docker IRC channel, but also explain it's not really maintained.

> I know people are running it and hacking on it outside of the community
> repo, which is fine, and if someone doing that wanted to stand up and
> say they wanted to own the repo and be the core team I'd be fine with
> that too, but so far no one has done that in the last few years. If
> you're already maintaining it outside of the community I don't know why
> you wouldn't just do that development in the open, and maybe get a free
> bug fix at times from another contributor, but I suppose people have
> their reasons (secret sauce and all that). So meh.

> --

> Thanks,

> Matt Riedemann

> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Matt Riedemann]

On 12/22/2016 8:26 PM, Tony Breeds wrote:

Hi All,
I know this comes up from time to time, but as the subject says, is it time
to retire nova-docker.

The nova-docker has lagged behind the last 6 months of nova development and no
longer passes simple CI unit tests.  There are open patches to at least get the
unit tests to pass[1] but if the current core team no longer has time (no
offence intended) then perhaps we should just archive it.

Thoughts?

Yours Tony.
[1] 
https://review.openstack.org/#/q/status:open+project:openstack/nova-docker+branch:master+topic:fixes_for_master



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



+1 for what it's worth.

People show up in the nova channel in IRC from time to time (maybe once 
or twice per year) asking about the state of the driver and I send them 
to the nova-docker IRC channel, but also explain it's not really maintained.


I know people are running it and hacking on it outside of the community 
repo, which is fine, and if someone doing that wanted to stand up and 
say they wanted to own the repo and be the core team I'd be fine with 
that too, but so far no one has done that in the last few years. If 
you're already maintaining it outside of the community I don't know why 
you wouldn't just do that development in the open, and maybe get a free 
bug fix at times from another contributor, but I suppose people have 
their reasons (secret sauce and all that). So meh.


--

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Tony Breeds]

On Thu, Dec 22, 2016 at 09:43:34PM -0500, Davanum Srinivas wrote:
> yep, it's time to pull the plug Tony
> 
> fyi, http://lists.openstack.org/pipermail/openstack-dev/2016-July/098940.html

Okay I knew it'd come up before.  If noone objects befoerm Monday Dec 26th,
I'll send the announcement to openstack-annouce, openstack-dev and
openstck-operators setting the EOL date for March 1.  I feel like that is
oodles[1] of warning. and it wont detract from any of the ocata development or
release work.

Yours Tony.

[1] Yes that's a technical term[2]
[2] http://www.dictionary.com/browse/oodles


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[ChangBo Guo]

+1

2016-12-23 10:43 GMT+08:00 Davanum Srinivas :

> yep, it's time to pull the plug Tony
>
> fyi, http://lists.openstack.org/pipermail/openstack-dev/2016-
> July/098940.html
>
> -- Dims
>
> On Thu, Dec 22, 2016 at 9:26 PM, Tony Breeds 
> wrote:
> > Hi All,
> > I know this comes up from time to time, but as the subject says, is
> it time
> > to retire nova-docker.
> >
> > The nova-docker has lagged behind the last 6 months of nova development
> and no
> > longer passes simple CI unit tests.  There are open patches to at least
> get the
> > unit tests to pass[1] but if the current core team no longer has time (no
> > offence intended) then perhaps we should just archive it.
> >
> > Thoughts?
> >
> > Yours Tony.
> > [1] https://review.openstack.org/#/q/status:open+project:
> openstack/nova-docker+branch:master+topic:fixes_for_master
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
ChangBo Guo(gcb)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Davanum Srinivas]

yep, it's time to pull the plug Tony

fyi, http://lists.openstack.org/pipermail/openstack-dev/2016-July/098940.html

-- Dims

On Thu, Dec 22, 2016 at 9:26 PM, Tony Breeds  wrote:
> Hi All,
> I know this comes up from time to time, but as the subject says, is it 
> time
> to retire nova-docker.
>
> The nova-docker has lagged behind the last 6 months of nova development and no
> longer passes simple CI unit tests.  There are open patches to at least get 
> the
> unit tests to pass[1] but if the current core team no longer has time (no
> offence intended) then perhaps we should just archive it.
>
> Thoughts?
>
> Yours Tony.
> [1] 
> https://review.openstack.org/#/q/status:open+project:openstack/nova-docker+branch:master+topic:fixes_for_master
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Davanum Srinivas :: https://twitter.com/dims

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Tony Breeds]

Hi All,
I know this comes up from time to time, but as the subject says, is it time
to retire nova-docker.

The nova-docker has lagged behind the last 6 months of nova development and no
longer passes simple CI unit tests.  There are open patches to at least get the
unit tests to pass[1] but if the current core team no longer has time (no
offence intended) then perhaps we should just archive it.

Thoughts?

Yours Tony.
[1] 
https://review.openstack.org/#/q/status:open+project:openstack/nova-docker+branch:master+topic:fixes_for_master


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev