Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker project
On 07/07/2016 01:12 PM, Davanum Srinivas wrote: Folks, The nova-docker project[1] is barely alive[2]. So i'll kick off the process of retiring the project [3] Thanks, Dims [1] http://git.openstack.org/cgit/openstack/nova-docker/ [2] http://stackalytics.com/report/contribution/nova-docker/30 [3] http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project It seems prudent. Thanks Dims for keeping this effort alive so long. It's unfortunate that no one else was up for maintaining this driver. -Sean -- Sean Dague http://dague.net __ 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] Retiring nova-docker project
Álvaro, There is no plan for any other Nova driver that will drive a Docker Daemon that i know. Thanks, Dims On Mon, Jul 11, 2016 at 8:10 AM, Álvaro López García wrote: > On 08 Jul 2016 (10:07), Davanum Srinivas wrote: >> Tim, > > Hi Davanum, > >> I've initiated conversation a couple of times more than a year ago. >> >> http://lists.openstack.org/pipermail/openstack-operators/2015-May/thread.html#7129 >> http://lists.openstack.org/pipermail/openstack-operators/2015-May/thread.html#7006 > > To be honest I overlooked and missed these emails in the operators > mailing list. I am aware of several sites where it is being used so I > would have reacted on these emails, sorry for that. > > What is the status and position of Zun (ex Higgings) with regards > nova-docker? Will it support the same features in the (near) future? > Does it make sense to maintain nova-docker until Zun fills the gap? > > Regards, > -- > Á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 -- 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
Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker project
On 08 Jul 2016 (10:07), Davanum Srinivas wrote: > Tim, Hi Davanum, > I've initiated conversation a couple of times more than a year ago. > > http://lists.openstack.org/pipermail/openstack-operators/2015-May/thread.html#7129 > http://lists.openstack.org/pipermail/openstack-operators/2015-May/thread.html#7006 To be honest I overlooked and missed these emails in the operators mailing list. I am aware of several sites where it is being used so I would have reacted on these emails, sorry for that. What is the status and position of Zun (ex Higgings) with regards nova-docker? Will it support the same features in the (near) future? Does it make sense to maintain nova-docker until Zun fills the gap? Regards, -- Á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] Retiring nova-docker project
Tim, I've initiated conversation a couple of times more than a year ago. http://lists.openstack.org/pipermail/openstack-operators/2015-May/thread.html#7129 http://lists.openstack.org/pipermail/openstack-operators/2015-May/thread.html#7006 Thanks, Dims On Fri, Jul 8, 2016 at 9:10 AM, Tim Bell wrote: > Given the inconsistency between the user survey and the apparent > utilization/maintenance, I’d recommend checking on the openstack-operators > list to see if this would be a major issue. > > Tim > > On 08/07/16 13:54, "Amrith Kumar" wrote: > > Did not realize that; I withdraw my request. You are correct; 12 months+ is > fair warning. > > -amrith > > P.S. I volunteered (in Ann Arbor) to work with you and contribute to > nova-docker but I guess that's now moot; it'd have been fun :) > >> -Original Message- >> From: Davanum Srinivas [mailto:dava...@gmail.com] >> Sent: Friday, July 08, 2016 7:32 AM >> To: OpenStack Development Mailing List (not for usage questions) >> >> Subject: Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker >> project >> >> Amrith, >> >> A year and few months is sufficient notice: >> http://markmail.org/message/geijiljch4yxfcvq >> >> I really really want this to go away. Every time this comes up, >> example it came up in Austin too, a few people raise their hands and >> then do not show up. (Not saying you will do the same!). >> >> -- Dims >> >> On Fri, Jul 8, 2016 at 7:10 AM, Amrith Kumar wrote: >> > Does it make sense that this conversation about the merits of nova- >> docker be had before the retirement is actually initiated. It seems odd >> that in the face of empirical evidence of actual use (user survey) we >> merely hypothesize that people are likely using their own forks and >> therefore it is fine to retire this project. >> > >> > As ttx indicates there is nothing wrong with a project with low >> activity. That said, if the issue is that nova-docker is not actively >> maintained and broken, then what it needs is contributors not retirement. >> > >> > -amrith >> > >> >> -Original Message- >> >> From: Daniel P. Berrange [mailto:berra...@redhat.com] >> >> Sent: Friday, July 08, 2016 5:03 AM >> >> To: OpenStack Development Mailing List (not for usage questions) >> >> >> >> Subject: Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker >> >> project >> >> >> >> On Fri, Jul 08, 2016 at 10:11:59AM +0200, Thierry Carrez wrote: >> >> > Matt Riedemann wrote: >> >> > > [...] >> >> > > Expand the numbers to 6 months and you'll see only 13 commits. >> >> > > >> >> > > It's surprisingly high in the user survey (page 39): >> >> > > >> >> > > https://www.openstack.org/assets/survey/April-2016-User-Survey- >> >> Report.pdf >> >> > > >> >> > > So I suspect most users/deployments are just running their own >> forks. >> >> > >> >> > Why ? Is it completely unusable as it stands ? 13 commits in 6 months >> >> sounds >> >> > like enough activity to keep something usable (if it was usable in >> the >> >> first >> >> > place). We have a lot of (official) projects and libraries with less >> >> > activity than that :) >> >> > >> >> > I'm not sure we should be retiring an unofficial project if it's >> usable, >> >> > doesn't have critical security issues and is used by a number of >> >> people... >> >> > Now, if it's unusable and abandoned, that's another story. >> >> >> >> Nova explicitly provides *zero* stable APIs for out of tree drivers to >> >> use. Changes to Nova internals will reliably break out of tree drivers >> >> at least once during a development cycle, often more. So you really do >> >> need someone committed to updating out of tree drivers to cope with the >> >> fact that they're using an explicitly unstable API. We actively intend >> >> to keep breaking out of tree drivers as often as suits Nova's best >> >> interests. >> >> >> >> Regards, >> >> Daniel >> >> -- >> >> |: http://berrange.com -o- >> http://www.flickr.com/photos/dberrange/ >>
Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker project
Given the inconsistency between the user survey and the apparent utilization/maintenance, I’d recommend checking on the openstack-operators list to see if this would be a major issue. Tim On 08/07/16 13:54, "Amrith Kumar" wrote: Did not realize that; I withdraw my request. You are correct; 12 months+ is fair warning. -amrith P.S. I volunteered (in Ann Arbor) to work with you and contribute to nova-docker but I guess that's now moot; it'd have been fun :) > -Original Message- > From: Davanum Srinivas [mailto:dava...@gmail.com] > Sent: Friday, July 08, 2016 7:32 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker > project > > Amrith, > > A year and few months is sufficient notice: > http://markmail.org/message/geijiljch4yxfcvq > > I really really want this to go away. Every time this comes up, > example it came up in Austin too, a few people raise their hands and > then do not show up. (Not saying you will do the same!). > > -- Dims > > On Fri, Jul 8, 2016 at 7:10 AM, Amrith Kumar wrote: > > Does it make sense that this conversation about the merits of nova- > docker be had before the retirement is actually initiated. It seems odd > that in the face of empirical evidence of actual use (user survey) we > merely hypothesize that people are likely using their own forks and > therefore it is fine to retire this project. > > > > As ttx indicates there is nothing wrong with a project with low > activity. That said, if the issue is that nova-docker is not actively > maintained and broken, then what it needs is contributors not retirement. > > > > -amrith > > > >> -Original Message- > >> From: Daniel P. Berrange [mailto:berra...@redhat.com] > >> Sent: Friday, July 08, 2016 5:03 AM > >> To: OpenStack Development Mailing List (not for usage questions) > >> > >> Subject: Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker > >> project > >> > >> On Fri, Jul 08, 2016 at 10:11:59AM +0200, Thierry Carrez wrote: > >> > Matt Riedemann wrote: > >> > > [...] > >> > > Expand the numbers to 6 months and you'll see only 13 commits. > >> > > > >> > > It's surprisingly high in the user survey (page 39): > >> > > > >> > > https://www.openstack.org/assets/survey/April-2016-User-Survey- > >> Report.pdf > >> > > > >> > > So I suspect most users/deployments are just running their own > forks. > >> > > >> > Why ? Is it completely unusable as it stands ? 13 commits in 6 months > >> sounds > >> > like enough activity to keep something usable (if it was usable in > the > >> first > >> > place). We have a lot of (official) projects and libraries with less > >> > activity than that :) > >> > > >> > I'm not sure we should be retiring an unofficial project if it's > usable, > >> > doesn't have critical security issues and is used by a number of > >> people... > >> > Now, if it's unusable and abandoned, that's another story. > >> > >> Nova explicitly provides *zero* stable APIs for out of tree drivers to > >> use. Changes to Nova internals will reliably break out of tree drivers > >> at least once during a development cycle, often more. So you really do > >> need someone committed to updating out of tree drivers to cope with the > >> fact that they're using an explicitly unstable API. We actively intend > >> to keep breaking out of tree drivers as often as suits Nova's best > >> interests. > >> > >> Regards, > >> Daniel > >> -- > >> |: http://berrange.com -o- > http://www.flickr.com/photos/dberrange/ > >> :| > >> |: http://libvirt.org -o- http://virt- > manager.org > >> :| > >> |: http://autobuild.org -o- > http://search.cpan.org/~danberr/ > >> :| > >> |: http://entangle-photo.org -o- http://live.gnome.org/gtk- > vnc > >> :| > >> > >> > __ > >> 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] Retiring nova-docker project
On Jul 7, 2016, at 11:37 PM, Joshua Harlow wrote: > Then can we get > https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml#n2514finally > adjusted to be what it really is... instead of what it really isn't... I would be in favor of updating that statement. -- Ed Leafe __ 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] Retiring nova-docker project
Did not realize that; I withdraw my request. You are correct; 12 months+ is fair warning. -amrith P.S. I volunteered (in Ann Arbor) to work with you and contribute to nova-docker but I guess that's now moot; it'd have been fun :) > -Original Message- > From: Davanum Srinivas [mailto:dava...@gmail.com] > Sent: Friday, July 08, 2016 7:32 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker > project > > Amrith, > > A year and few months is sufficient notice: > http://markmail.org/message/geijiljch4yxfcvq > > I really really want this to go away. Every time this comes up, > example it came up in Austin too, a few people raise their hands and > then do not show up. (Not saying you will do the same!). > > -- Dims > > On Fri, Jul 8, 2016 at 7:10 AM, Amrith Kumar wrote: > > Does it make sense that this conversation about the merits of nova- > docker be had before the retirement is actually initiated. It seems odd > that in the face of empirical evidence of actual use (user survey) we > merely hypothesize that people are likely using their own forks and > therefore it is fine to retire this project. > > > > As ttx indicates there is nothing wrong with a project with low > activity. That said, if the issue is that nova-docker is not actively > maintained and broken, then what it needs is contributors not retirement. > > > > -amrith > > > >> -Original Message- > >> From: Daniel P. Berrange [mailto:berra...@redhat.com] > >> Sent: Friday, July 08, 2016 5:03 AM > >> To: OpenStack Development Mailing List (not for usage questions) > >> > >> Subject: Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker > >> project > >> > >> On Fri, Jul 08, 2016 at 10:11:59AM +0200, Thierry Carrez wrote: > >> > Matt Riedemann wrote: > >> > > [...] > >> > > Expand the numbers to 6 months and you'll see only 13 commits. > >> > > > >> > > It's surprisingly high in the user survey (page 39): > >> > > > >> > > https://www.openstack.org/assets/survey/April-2016-User-Survey- > >> Report.pdf > >> > > > >> > > So I suspect most users/deployments are just running their own > forks. > >> > > >> > Why ? Is it completely unusable as it stands ? 13 commits in 6 months > >> sounds > >> > like enough activity to keep something usable (if it was usable in > the > >> first > >> > place). We have a lot of (official) projects and libraries with less > >> > activity than that :) > >> > > >> > I'm not sure we should be retiring an unofficial project if it's > usable, > >> > doesn't have critical security issues and is used by a number of > >> people... > >> > Now, if it's unusable and abandoned, that's another story. > >> > >> Nova explicitly provides *zero* stable APIs for out of tree drivers to > >> use. Changes to Nova internals will reliably break out of tree drivers > >> at least once during a development cycle, often more. So you really do > >> need someone committed to updating out of tree drivers to cope with the > >> fact that they're using an explicitly unstable API. We actively intend > >> to keep breaking out of tree drivers as often as suits Nova's best > >> interests. > >> > >> Regards, > >> Daniel > >> -- > >> |: http://berrange.com -o- > http://www.flickr.com/photos/dberrange/ > >> :| > >> |: http://libvirt.org -o- http://virt- > manager.org > >> :| > >> |: http://autobuild.org -o- > http://search.cpan.org/~danberr/ > >> :| > >> |: http://entangle-photo.org -o- http://live.gnome.org/gtk- > vnc > >> :| > >> > >> > __ > >> 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 > > > > -- > 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 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] Retiring nova-docker project
Amrith, A year and few months is sufficient notice: http://markmail.org/message/geijiljch4yxfcvq I really really want this to go away. Every time this comes up, example it came up in Austin too, a few people raise their hands and then do not show up. (Not saying you will do the same!). -- Dims On Fri, Jul 8, 2016 at 7:10 AM, Amrith Kumar wrote: > Does it make sense that this conversation about the merits of nova-docker be > had before the retirement is actually initiated. It seems odd that in the > face of empirical evidence of actual use (user survey) we merely hypothesize > that people are likely using their own forks and therefore it is fine to > retire this project. > > As ttx indicates there is nothing wrong with a project with low activity. > That said, if the issue is that nova-docker is not actively maintained and > broken, then what it needs is contributors not retirement. > > -amrith > >> -Original Message- >> From: Daniel P. Berrange [mailto:berra...@redhat.com] >> Sent: Friday, July 08, 2016 5:03 AM >> To: OpenStack Development Mailing List (not for usage questions) >> >> Subject: Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker >> project >> >> On Fri, Jul 08, 2016 at 10:11:59AM +0200, Thierry Carrez wrote: >> > Matt Riedemann wrote: >> > > [...] >> > > Expand the numbers to 6 months and you'll see only 13 commits. >> > > >> > > It's surprisingly high in the user survey (page 39): >> > > >> > > https://www.openstack.org/assets/survey/April-2016-User-Survey- >> Report.pdf >> > > >> > > So I suspect most users/deployments are just running their own forks. >> > >> > Why ? Is it completely unusable as it stands ? 13 commits in 6 months >> sounds >> > like enough activity to keep something usable (if it was usable in the >> first >> > place). We have a lot of (official) projects and libraries with less >> > activity than that :) >> > >> > I'm not sure we should be retiring an unofficial project if it's usable, >> > doesn't have critical security issues and is used by a number of >> people... >> > Now, if it's unusable and abandoned, that's another story. >> >> Nova explicitly provides *zero* stable APIs for out of tree drivers to >> use. Changes to Nova internals will reliably break out of tree drivers >> at least once during a development cycle, often more. So you really do >> need someone committed to updating out of tree drivers to cope with the >> fact that they're using an explicitly unstable API. We actively intend >> to keep breaking out of tree drivers as often as suits Nova's best >> interests. >> >> Regards, >> Daniel >> -- >> |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ >> :| >> |: http://libvirt.org -o- http://virt-manager.org >> :| >> |: http://autobuild.org -o- http://search.cpan.org/~danberr/ >> :| >> |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc >> :| >> >> __ >> 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 -- 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
Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker project
Does it make sense that this conversation about the merits of nova-docker be had before the retirement is actually initiated. It seems odd that in the face of empirical evidence of actual use (user survey) we merely hypothesize that people are likely using their own forks and therefore it is fine to retire this project. As ttx indicates there is nothing wrong with a project with low activity. That said, if the issue is that nova-docker is not actively maintained and broken, then what it needs is contributors not retirement. -amrith > -Original Message- > From: Daniel P. Berrange [mailto:berra...@redhat.com] > Sent: Friday, July 08, 2016 5:03 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker > project > > On Fri, Jul 08, 2016 at 10:11:59AM +0200, Thierry Carrez wrote: > > Matt Riedemann wrote: > > > [...] > > > Expand the numbers to 6 months and you'll see only 13 commits. > > > > > > It's surprisingly high in the user survey (page 39): > > > > > > https://www.openstack.org/assets/survey/April-2016-User-Survey- > Report.pdf > > > > > > So I suspect most users/deployments are just running their own forks. > > > > Why ? Is it completely unusable as it stands ? 13 commits in 6 months > sounds > > like enough activity to keep something usable (if it was usable in the > first > > place). We have a lot of (official) projects and libraries with less > > activity than that :) > > > > I'm not sure we should be retiring an unofficial project if it's usable, > > doesn't have critical security issues and is used by a number of > people... > > Now, if it's unusable and abandoned, that's another story. > > Nova explicitly provides *zero* stable APIs for out of tree drivers to > use. Changes to Nova internals will reliably break out of tree drivers > at least once during a development cycle, often more. So you really do > need someone committed to updating out of tree drivers to cope with the > fact that they're using an explicitly unstable API. We actively intend > to keep breaking out of tree drivers as often as suits Nova's best > interests. > > Regards, > Daniel > -- > |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ > :| > |: http://libvirt.org -o- http://virt-manager.org > :| > |: http://autobuild.org -o- http://search.cpan.org/~danberr/ > :| > |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc > :| > > __ > 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] Retiring nova-docker project
On Fri, Jul 08, 2016 at 10:11:59AM +0200, Thierry Carrez wrote: > Matt Riedemann wrote: > > [...] > > Expand the numbers to 6 months and you'll see only 13 commits. > > > > It's surprisingly high in the user survey (page 39): > > > > https://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf > > > > So I suspect most users/deployments are just running their own forks. > > Why ? Is it completely unusable as it stands ? 13 commits in 6 months sounds > like enough activity to keep something usable (if it was usable in the first > place). We have a lot of (official) projects and libraries with less > activity than that :) > > I'm not sure we should be retiring an unofficial project if it's usable, > doesn't have critical security issues and is used by a number of people... > Now, if it's unusable and abandoned, that's another story. Nova explicitly provides *zero* stable APIs for out of tree drivers to use. Changes to Nova internals will reliably break out of tree drivers at least once during a development cycle, often more. So you really do need someone committed to updating out of tree drivers to cope with the fact that they're using an explicitly unstable API. We actively intend to keep breaking out of tree drivers as often as suits Nova's best interests. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| __ 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] Retiring nova-docker project
Matt Riedemann wrote: [...] Expand the numbers to 6 months and you'll see only 13 commits. It's surprisingly high in the user survey (page 39): https://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf So I suspect most users/deployments are just running their own forks. Why ? Is it completely unusable as it stands ? 13 commits in 6 months sounds like enough activity to keep something usable (if it was usable in the first place). We have a lot of (official) projects and libraries with less activity than that :) I'm not sure we should be retiring an unofficial project if it's usable, doesn't have critical security issues and is used by a number of people... Now, if it's unusable and abandoned, that's another story. -- Thierry Carrez (ttx) __ 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] Retiring nova-docker project
On Thu, 2016-07-07 at 21:28 -0500, Edward Leafe wrote: > On Jul 7, 2016, at 8:33 PM, Joshua Harlow > wrote: > > > > That's sad, how can we fix the fact that users/deployments have > > gone off into their own silos and may be running their own forks; > > what went wrong (besides some of the obvious stuff that I think I > > know about, that others probably don't) that resulted in this > > happening? > > > > Seems like something we can learn from by reflecting on this and > > trying to find a path forward (or maybe we just accept there isn't > > one, idk). > > I think admitting that it was a conceptual mis-match from the start > would be the first step. Containers are not VMs. That's not a correct statement: they certainly can be orchestrated like VMs if constructed like them: that's actually what operating system containers are. However, container systems are also amenable to being constructed very differently from VMs because of the granular nature of the virtualisations. > Attempts to treat them as such are always going to be poor > compromises. I think this reflects the persistent failure OpenStack has had in trying to encompass the entire container space. The problem is that they're not monolithic, like VMs for which, whether it's ESX, KVM, Xen or HyperV, one VM looks very like another. The homogeneous nature of VMs makes it natural to think containers can be pidgeonholed in the same way ... the problem is that really, they can't. Some container systems absolutely can be orchestrated by nova and some can't. Currently there is no one OpenStack system that can orchestrate the full power of containers as presented by the raw Linux API. I don't think this is a particular problem because there's no industrial consumer begging for that full power. Right at the moment, containers are consumed as a collection of disparate use cases and, reflecting this, OpenStack has a variety of systems corresponding somewhat to the consumption models. However, being use case specific, none of them can orchestrate an arbitrary "container" system, and, of course, any new use case that arises likely doesn't fit with any of the current models. Reality is being messy again, I'm afraid. > Containers have an important place in OpenStack; it's just not in > Nova. Following this theory, the next move would be trying to remove the lxc and vz container drivers from nova? I really don't think that's a good idea because the fit is quite useful for a significant set of use cases. James > > -- Ed Leafe > > > > > > _ > _ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs > cribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev signature.asc Description: This is a digitally signed message part __ 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] Retiring nova-docker project
Edward Leafe wrote: On Jul 7, 2016, at 8:33 PM, Joshua Harlow wrote: That's sad, how can we fix the fact that users/deployments have gone off into their own silos and may be running their own forks; what went wrong (besides some of the obvious stuff that I think I know about, that others probably don't) that resulted in this happening? Seems like something we can learn from by reflecting on this and trying to find a path forward (or maybe we just accept there isn't one, idk). I think admitting that it was a conceptual mis-match from the start would be the first step. Containers are not VMs. Attempts to treat them as such are always going to be poor compromises. Containers have an important place in OpenStack; it's just not in Nova. Then can we get https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml#n2514 finally adjusted to be what it really is... instead of what it really isn't... -- Ed Leafe __ 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] Retiring nova-docker project
On Jul 7, 2016, at 8:33 PM, Joshua Harlow wrote: > > That's sad, how can we fix the fact that users/deployments have gone off into > their own silos and may be running their own forks; what went wrong (besides > some of the obvious stuff that I think I know about, that others probably > don't) that resulted in this happening? > > Seems like something we can learn from by reflecting on this and trying to > find a path forward (or maybe we just accept there isn't one, idk). I think admitting that it was a conceptual mis-match from the start would be the first step. Containers are not VMs. Attempts to treat them as such are always going to be poor compromises. Containers have an important place in OpenStack; it's just not in Nova. -- Ed Leafe signature.asc Description: Message signed with OpenPGP using GPGMail __ 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] Retiring nova-docker project
That's sad, how can we fix the fact that users/deployments have gone off into their own silos and may be running their own forks; what went wrong (besides some of the obvious stuff that I think I know about, that others probably don't) that resulted in this happening? Seems like something we can learn from by reflecting on this and trying to find a path forward (or maybe we just accept there isn't one, idk). Matt Riedemann wrote: On 7/7/2016 3:12 PM, Davanum Srinivas wrote: Folks, The nova-docker project[1] is barely alive[2]. So i'll kick off the process of retiring the project [3] Thanks, Dims [1] http://git.openstack.org/cgit/openstack/nova-docker/ [2] http://stackalytics.com/report/contribution/nova-docker/30 [3] http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project +1 Expand the numbers to 6 months and you'll see only 13 commits. It's surprisingly high in the user survey (page 39): https://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf So I suspect most users/deployments are just running their own forks. __ 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] Retiring nova-docker project
On 7/7/2016 3:12 PM, Davanum Srinivas wrote: Folks, The nova-docker project[1] is barely alive[2]. So i'll kick off the process of retiring the project [3] Thanks, Dims [1] http://git.openstack.org/cgit/openstack/nova-docker/ [2] http://stackalytics.com/report/contribution/nova-docker/30 [3] http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project +1 Expand the numbers to 6 months and you'll see only 13 commits. It's surprisingly high in the user survey (page 39): https://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf So I suspect most users/deployments are just running their own forks. -- 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-dev] [nova][nova-docker] Retiring nova-docker project
Folks, The nova-docker project[1] is barely alive[2]. So i'll kick off the process of retiring the project [3] Thanks, Dims [1] http://git.openstack.org/cgit/openstack/nova-docker/ [2] http://stackalytics.com/report/contribution/nova-docker/30 [3] http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project -- 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
