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

Reply via email to