Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Dmitry Tantsur wrote: On 05/09/2017 07:59 PM, Joshua Harlow wrote: Matt Riedemann wrote: On 5/8/2017 1:10 PM, Octave J. Orgeron wrote: I do agree that scalability and high-availability are definitely issues for OpenStack when you dig deeper into the sub-components. There is a lot of

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/09/2017 07:59 PM, Joshua Harlow wrote: Matt Riedemann wrote: On 5/8/2017 1:10 PM, Octave J. Orgeron wrote: I do agree that scalability and high-availability are definitely issues for OpenStack when you dig deeper into the sub-components. There is a lot of re-inventing of the wheel when

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Matt Riedemann wrote: On 5/8/2017 1:10 PM, Octave J. Orgeron wrote: I do agree that scalability and high-availability are definitely issues for OpenStack when you dig deeper into the sub-components. There is a lot of re-inventing of the wheel when you look at how distributed services are

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 5 May 2017 at 23:45, Chris Friesen wrote: > On 05/05/2017 02:04 PM, John Griffith wrote: >> I'd love some detail on this. What falls over? > It's been a while since I looked at it, but the main issue was that with LIO > as the iSCSI server there is no automatic

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 5/8/2017 1:24 PM, Octave J. Orgeron wrote: Now for Oracle, we definitely need more 3rd party CI to make it easier to test our drivers, components, and patches against so that it's easier for the community to validate things. However, it takes time, resources, and money to make that happen.

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 5/8/2017 1:10 PM, Octave J. Orgeron wrote: I do agree that scalability and high-availability are definitely issues for OpenStack when you dig deeper into the sub-components. There is a lot of re-inventing of the wheel when you look at how distributed services are implemented inside of

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Excerpts from Jeremy Stanley's message of 2017-05-08 20:18:35 +: > On 2017-05-08 11:24:00 -0600 (-0600), Octave J. Orgeron wrote: > [...] > > none of those products that those drivers are written for are open > > sourced and they meet less resistance to committing code upstream. > > So I have

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 2017-05-08 11:24:00 -0600 (-0600), Octave J. Orgeron wrote: [...] > none of those products that those drivers are written for are open > sourced and they meet less resistance to committing code upstream. > So I have to call BS on your comment that the community can't work > with us because

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Hi Jeremy, I'm sure everyone would love to see Solaris open sourced again. I know I do! But unfortunately, it's not something within my power or control. However, there is the reality that OpenStack wouldn't be as successful without commercial companies contributing to it. A good example is

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

om: Michał Jastrzębski [inc...@gmail.com] Sent: Friday, May 05, 2017 3:20 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time You are talking about OpenStack being hard because it

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 08.05.2017 16:06, Doug Hellmann wrote: >>> >>> option #3: Do not support or nurse gates for stable branches upstream. >>> Instead, only create and close them and attach 3rd party gating, if >>> asked by contributors willing to support LTS and nurse their gates. >>> Note, closing a branch should

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Excerpts from Davanum Srinivas (dims)'s message of 2017-05-08 06:12:51 -0400: > On Mon, May 8, 2017 at 3:52 AM, Bogdan Dobrelya wrote: > > On 06.05.2017 23:06, Doug Hellmann wrote: > >> Excerpts from Thierry Carrez's message of 2017-05-04 16:14:07 +0200: > >>> Chris Dent

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Mon, May 8, 2017 at 3:52 AM, Bogdan Dobrelya wrote: > On 06.05.2017 23:06, Doug Hellmann wrote: >> Excerpts from Thierry Carrez's message of 2017-05-04 16:14:07 +0200: >>> Chris Dent wrote: On Wed, 3 May 2017, Drew Fisher wrote: > "Most large customers move slowly

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 06.05.2017 23:06, Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2017-05-04 16:14:07 +0200: >> Chris Dent wrote: >>> On Wed, 3 May 2017, Drew Fisher wrote: "Most large customers move slowly and thus are running older versions, which are EOL upstream sometimes before

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 5/5/2017 6:44 PM, Fox, Kevin M wrote: Note, when I say OpenStack below, I'm talking about nova/glance/cinder/neutron/horizon/heat/octavia/designate. No offence to the other projects intended. just trying to constrain the conversation a bit... Those parts are fairly comparable to what k8s

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Excerpts from Thierry Carrez's message of 2017-05-04 16:14:07 +0200: > Chris Dent wrote: > > On Wed, 3 May 2017, Drew Fisher wrote: > >> "Most large customers move slowly and thus are running older versions, > >> which are EOL upstream sometimes before they even deploy them." > > > > Can someone

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Excerpts from Octave J. Orgeron's message of 2017-05-05 15:35:16 -0600: > Hi Matt, > > And this is actually part of the problem for vendors. Many Oracle > engineers, including myself, have tried to get features and fixes pushed > upstream. While that may sound easy, the reality is that it

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 2017-05-05 15:35:16 -0600 (-0600), Octave J. Orgeron wrote: [...] > If it's in support of Oracle specific technologies such as Solaris, [...] > we are often shunned away because it's not Linux or "mainstream" > enough. A great example is how our Nova drivers for Solaris Zones, > Kernel Zones,

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

questions) Subject: Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time You are talking about OpenStack being hard because it's complex and at the same time you're talking about using "non-linux-mainstream" tools around. It's either flex

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

_ From: Michał Jastrzębski [inc...@gmail.com] Sent: Friday, May 05, 2017 3:20 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time You are talking about OpenStack being hard be

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/05/2017 02:34 PM, Matt Riedemann wrote: I don't have a nice way to wrap this up. I'm depressed and just want to go outside. I don't expect pleasant replies to my rant, so I probably won't reply again after this anyway since this is always a never-ending back and forth which just leaves

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/05/2017 02:04 PM, John Griffith wrote: On Fri, May 5, 2017 at 11:24 AM, Chris Friesen > wrote: On 05/05/2017 10:48 AM, Chris Dent wrote: Would it be accurate to say, then, that from your perpsective the

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 5/4/2017 10:08 AM, Alex Schultz wrote: On Thu, May 4, 2017 at 5:32 AM, Chris Dent wrote: I know you're not speaking as the voice of your employer when making this message, so this is not directed at you, but from what I can tell Oracle's presense upstream (both

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

You are talking about OpenStack being hard because it's complex and at the same time you're talking about using "non-linux-mainstream" tools around. It's either flexibility or ease guys... Prescriptive is easy, flexible is hard. When you want to learn about linux you're not starting from compiling

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

+1 On 5/5/2017 3:46 PM, Alex Schultz wrote: Sooo... I always get a little triggered when I hear that OpenStack is hard to deploy. We've spent last few years fixing it and I think it's pretty well fixed now. Even as we speak I'm deploying 500+ vms on OpenStack cluster I deployed last week

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 1:02 PM, Michał Jastrzębski wrote: > On 5 May 2017 at 11:33, Alex Schultz wrote: >> On Fri, May 5, 2017 at 10:48 AM, Chris Dent wrote: >>> On Fri, 5 May 2017, Alex Schultz wrote: >>> You have to

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

+1. From: Octave J. Orgeron [octave.orge...@oracle.com] Sent: Friday, May 05, 2017 1:23 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time Thank you Alex

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 05, 2017 at 04:17:29PM -0400, Jonathan Proulx wrote: > On Fri, May 05, 2017 at 02:04:43PM -0600, John Griffith wrote: > :On Fri, May 5, 2017 at 11:24 AM, Chris Friesen > > :> Cinder theoretically supports LVM/iSCSI, but if you actually try to use it > :>

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Hi Matt, And this is actually part of the problem for vendors. Many Oracle engineers, including myself, have tried to get features and fixes pushed upstream. While that may sound easy, the reality is that it isn't! In many cases, it takes months for us to get something in or we get shot down

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 1:49 PM, Sean Dague wrote: > On 05/05/2017 12:36 PM, Alex Schultz wrote: >> On Fri, May 5, 2017 at 6:16 AM, Sean Dague wrote: >>> On 05/04/2017 11:08 AM, Alex Schultz wrote: >>> >>> The general statement of "people care more about features

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 3:39 PM, Davanum Srinivas wrote: > "If we had an LTS branch and a solid governance model" - The way to > make it happen is for everyone to show up in the Stable team, do the > work that is need to define/setup etc.. > > Who is up for it? Please show up in

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 5/5/2017 3:23 PM, Octave J. Orgeron wrote: From a vendors perspective, it's incredibly difficult to keep up with the releases because once you get your automation tooling and any extra value-added components integrated with a release, it's more than likely already behind or EOL. Plus there

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Octave, Folks, "If we had an LTS branch and a solid governance model" - The way to make it happen is for everyone to show up in the Stable team, do the work that is need to define/setup etc.. Who is up for it? Please show up in the next weekly meeting and get active in the work needed to take

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 5/5/2017 11:36 AM, Alex Schultz wrote: The cell v2 initial implementation was neither usable or stable (for my definition of stable). Yea you could say 'but it's a work and progress' and I would say, why is it required for the end user then? If I wanted to I could probably go back and go

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Thank you Alex for the points you made below. These are some of the big issues that I see all OpenStack customers and operators struggling with. Regardless of the tools that the community or vendors put on the table, OpenStack is still a very complicated piece of technology to deploy and

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 05, 2017 at 02:04:43PM -0600, John Griffith wrote: :On Fri, May 5, 2017 at 11:24 AM, Chris Friesen :> Cinder theoretically supports LVM/iSCSI, but if you actually try to use it :> for anything stressful it falls over. :> : :​Oh really?​ : :​I'd love some

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

> +1. ocata's cell v2 stuff added a lot of extra required complexity > with no perceivable benefit to end users. If there was a long term > stable version, then putting it in the non lts release would have > been ok. In absence of lts, I would have recommended the cell v2 > stuff have been done in

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 11:24 AM, Chris Friesen wrote: > On 05/05/2017 10:48 AM, Chris Dent wrote: > > Would it be accurate to say, then, that from your perpsective the >> tendency of OpenStack to adopt new projects willy nilly contributes >> to the sense of features

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/05/2017 10:09 AM, Chris Friesen wrote: > On 05/05/2017 06:16 AM, Sean Dague wrote: >> On 05/04/2017 11:08 AM, Alex Schultz wrote: > >>> Probably because they are still on Kilo. Not sure how much they could >>> be contributing to the current when their customers are demanding that >>>

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/05/2017 12:36 PM, Alex Schultz wrote: > On Fri, May 5, 2017 at 6:16 AM, Sean Dague wrote: >> On 05/04/2017 11:08 AM, Alex Schultz wrote: >> >> The general statement of "people care more about features than >> usability/stability" gets thrown around a lot. And gets lots of

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 5/5/2017 9:30 AM, Thierry Carrez wrote: Davanum Srinivas wrote: I would encourage folks here to help the stable branches we have right now! Release/Requirements constantly wait on Stable team and Stable team is way short of hands. Please join #openstack-stable, throw your name in wiki etc

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 5 May 2017 at 11:33, Alex Schultz wrote: > On Fri, May 5, 2017 at 10:48 AM, Chris Dent wrote: >> On Fri, 5 May 2017, Alex Schultz wrote: >> >>> You have to understand that as I'm mainly dealing with having to >>> actually deploy/configure the

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 10:48 AM, Chris Dent wrote: > On Fri, 5 May 2017, Alex Schultz wrote: > >> You have to understand that as I'm mainly dealing with having to >> actually deploy/configure the software, when I see 'new project X' >> that does 'cool new things Y, Z' it

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 05, 2017 at 11:24:49AM -0600, Chris Friesen wrote: > [snip] > > Cinder theoretically supports LVM/iSCSI, but if you actually try to use it > for anything stressful it falls over. > A bit of a tangent, but I would love to hear more about this. We have a lot of folks using LVM

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 10:52 AM, Dean Troyer wrote: > On Fri, May 5, 2017 at 11:36 AM, Alex Schultz wrote: >> configuration and usability issues. But those aren't exciting so >> people don't want to work on them... > > [Not picking on Alex here, but I've

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

...@redhat.com] Sent: Friday, May 05, 2017 9:36 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time On Fri, May 5, 2017 at 6:16 AM, Sean Dague <s...@dague.net> wrote: > On 05/04/2017

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/05/2017 11:52 AM, Dean Troyer wrote: On Fri, May 5, 2017 at 11:36 AM, Alex Schultz wrote: configuration and usability issues. But those aren't exciting so people don't want to work on them... [Not picking on Alex here, but I've seen this repeated again in this

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/05/2017 10:48 AM, Chris Dent wrote: Would it be accurate to say, then, that from your perpsective the tendency of OpenStack to adopt new projects willy nilly contributes to the sense of features winning out over deployment, configuration and usability issues? Personally I don't care

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 11:36 AM, Alex Schultz wrote: > configuration and usability issues. But those aren't exciting so > people don't want to work on them... [Not picking on Alex here, but I've seen this repeated again in this thread like every other one]

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, 5 May 2017, Alex Schultz wrote: You have to understand that as I'm mainly dealing with having to actually deploy/configure the software, when I see 'new project X' that does 'cool new things Y, Z' it makes me cringe. Because it's just added complexity for new features that who knows if

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 6:16 AM, Sean Dague wrote: > On 05/04/2017 11:08 AM, Alex Schultz wrote: >> On Thu, May 4, 2017 at 5:32 AM, Chris Dent wrote: >>> On Wed, 3 May 2017, Drew Fisher wrote: >>> This email is meant to be the ML discussion of a

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Davanum Srinivas wrote: > I would encourage folks here to help the stable branches we have right > now! Release/Requirements constantly wait on Stable team and Stable > team is way short of hands. > > Please join #openstack-stable, throw your name in wiki etc >

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 9:34 AM, Bogdan Dobrelya wrote: > On 05.05.2017 14:12, Sean Dague wrote: >> On 05/05/2017 07:16 AM, Bogdan Dobrelya wrote: >>> So perhaps there is a (naive?) option #3: Do not support or nurse gates >>> for stable branches upstream. Instead, only create

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/05/2017 06:16 AM, Sean Dague wrote: On 05/04/2017 11:08 AM, Alex Schultz wrote: Probably because they are still on Kilo. Not sure how much they could be contributing to the current when their customers are demanding that something is rock solid which by now looks nothing like the

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/05/2017 05:16 AM, Bogdan Dobrelya wrote: I may be wrong, but I have a strong perception that even when major upgrades run smooth and flawless, operators tend to operate legacy enterprise software for long, long, long. It would be an utopia to expect any changes here, IMO. One reason for

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05.05.2017 14:12, Sean Dague wrote: > On 05/05/2017 07:16 AM, Bogdan Dobrelya wrote: >> So perhaps there is a (naive?) option #3: Do not support or nurse gates >> for stable branches upstream. Instead, only create and close them and >> attach 3rd party gating, if asked by contributors willing

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Excerpts from Zane Bitter's message of 2017-05-04 20:09:35 -0400: > On 04/05/17 10:14, Thierry Carrez wrote: > > Chris Dent wrote: > >> On Wed, 3 May 2017, Drew Fisher wrote: > >>> "Most large customers move slowly and thus are running older versions, > >>> which are EOL upstream sometimes before

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 2017-05-04 20:09:35 -0400 (-0400), Zane Bitter wrote: > On 04/05/17 10:14, Thierry Carrez wrote: [...] > >Maintaining stable branches has a cost. Keeping the infrastructure that > >ensures that stable branches are actually working is a complex endeavor > >that requires people to constantly pay

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/05/2017 08:50 AM, Dean Troyer wrote: > On Fri, May 5, 2017 at 7:16 AM, Sean Dague wrote: >> The general statement of "people care more about features than >> usability/stability" gets thrown around a lot. And gets lots of head >> nodding. But rarely comes with specifics. >

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 7:16 AM, Sean Dague wrote: > The general statement of "people care more about features than > usability/stability" gets thrown around a lot. And gets lots of head > nodding. But rarely comes with specifics. I think a lot of this general sentiment comes from

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/04/2017 11:08 AM, Alex Schultz wrote: > On Thu, May 4, 2017 at 5:32 AM, Chris Dent wrote: >> On Wed, 3 May 2017, Drew Fisher wrote: >> >>> This email is meant to be the ML discussion of a question I brought up >>> during the TC meeting on April 25th.; [1] >> >> >>

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/05/2017 07:16 AM, Bogdan Dobrelya wrote: > On 05.05.2017 2:09, Zane Bitter wrote: >> On 04/05/17 10:14, Thierry Carrez wrote: >>> We started with no stable branches, we were just producing releases and >>> ensuring that updates vaguely worked from N-1 to N. There were a lot of >>>

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05.05.2017 2:09, Zane Bitter wrote: > On 04/05/17 10:14, Thierry Carrez wrote: >> We started with no stable branches, we were just producing releases and >> ensuring that updates vaguely worked from N-1 to N. There were a lot of >> distributions, and they all maintained their own stable

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 04/05/17 10:14, Thierry Carrez wrote: Chris Dent wrote: On Wed, 3 May 2017, Drew Fisher wrote: "Most large customers move slowly and thus are running older versions, which are EOL upstream sometimes before they even deploy them." Can someone with more of the history give more detail on

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Flavio Percoco wrote: > On 04/05/17 11:18 -0400, Jonathan Proulx wrote: >> On Thu, May 04, 2017 at 04:14:07PM +0200, Thierry Carrez wrote: >> :I agree that our current stable branch model is inappropriate: >> :maintaining stable branches for one year only is a bit useless. But I >> :only see two

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 04/05/17 11:18 -0400, Jonathan Proulx wrote: On Thu, May 04, 2017 at 04:14:07PM +0200, Thierry Carrez wrote: :I agree that our current stable branch model is inappropriate: :maintaining stable branches for one year only is a bit useless. But I :only see two outcomes: : :1/ The OpenStack

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Thu, May 04, 2017 at 04:14:07PM +0200, Thierry Carrez wrote: :Chris Dent wrote: :> On Wed, 3 May 2017, Drew Fisher wrote: :>> "Most large customers move slowly and thus are running older versions, :>> which are EOL upstream sometimes before they even deploy them." :> :> Can someone with more

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Thu, May 4, 2017 at 5:32 AM, Chris Dent wrote: > On Wed, 3 May 2017, Drew Fisher wrote: > >> This email is meant to be the ML discussion of a question I brought up >> during the TC meeting on April 25th.; [1] > > > Thanks for starting this Drew, I hope my mentioning it

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Chris Dent wrote: > On Wed, 3 May 2017, Drew Fisher wrote: >> "Most large customers move slowly and thus are running older versions, >> which are EOL upstream sometimes before they even deploy them." > > Can someone with more of the history give more detail on where the > expectation arose that

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Wed, 3 May 2017, Drew Fisher wrote: This email is meant to be the ML discussion of a question I brought up during the TC meeting on April 25th.; [1] Thanks for starting this Drew, I hope my mentioning it in my tc report email wasn't too much of a nag. I've added [tc] and [all] tags to the