Re: [openstack-dev] [nova] Hold off on pushing new patches for config option cleanup

2016-08-27 Thread Matt Riedemann 

On 8/22/2016 5:52 PM, Michael Still wrote:

Its a shame so many are -2'ed. There is a lot there I could have merged
yesterday if it wasn't for that.

Michael



When I went through and -2'ed things I left those that had a +2 on them, 
so the -2 was really on the stuff that was not reviewed yet, or had a -1.


--

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] Hold off on pushing new patches for config option cleanup

2016-08-22 Thread Michael Still 
Its a shame so many are -2'ed. There is a lot there I could have merged
yesterday if it wasn't for that.

Michael

On Mon, Aug 22, 2016 at 9:00 PM, Sean Dague  wrote:

> On 08/22/2016 12:10 AM, Michael Still wrote:
>
>> So, if this is about preserving CI time, then its cool for me to merge
>> these on a US Sunday when the gate is otherwise idle, right?
>>
>
> yes.
>
>
>> Michael
>>
>> On Fri, Aug 19, 2016 at 7:02 AM, Sean Dague > > wrote:
>>
>> On 08/18/2016 04:46 PM, Michael Still wrote:
>> > We're still ok with merging existing ones though?
>>
>> Mostly we'd like to conserve the CI time now. It's about 14.5
>> node-hours
>> to run CI on these patches (probably on about 9 node-hours in the
>> gate).
>> With ~800 nodes every patch represents 1.5% of our CI resources (per
>> hour) to pass through. There are a ton of these patches up there, so
>> even just landing gating ones consumes resources that could go towards
>> other more critical fixes / features.
>>
>> I think the theory is these are fine to merge post freeze / milestone
>> 3,
>> when the CI should have cooled down a bit and there is more head room.
>>
>> -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
>> 
>>
>>
>>
>>
>> --
>> Rackspace Australia
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> --
> 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
>



-- 
Rackspace Australia
__
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] Hold off on pushing new patches for config option cleanup

2016-08-22 Thread Sean Dague 

On 08/22/2016 12:10 AM, Michael Still wrote:

So, if this is about preserving CI time, then its cool for me to merge
these on a US Sunday when the gate is otherwise idle, right?


yes.



Michael

On Fri, Aug 19, 2016 at 7:02 AM, Sean Dague > wrote:

On 08/18/2016 04:46 PM, Michael Still wrote:
> We're still ok with merging existing ones though?

Mostly we'd like to conserve the CI time now. It's about 14.5 node-hours
to run CI on these patches (probably on about 9 node-hours in the gate).
With ~800 nodes every patch represents 1.5% of our CI resources (per
hour) to pass through. There are a ton of these patches up there, so
even just landing gating ones consumes resources that could go towards
other more critical fixes / features.

I think the theory is these are fine to merge post freeze / milestone 3,
when the CI should have cooled down a bit and there is more head room.

-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





--
Rackspace Australia


__
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




--
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] Hold off on pushing new patches for config option cleanup

2016-08-21 Thread Michael Still 
So, if this is about preserving CI time, then its cool for me to merge
these on a US Sunday when the gate is otherwise idle, right?

Michael

On Fri, Aug 19, 2016 at 7:02 AM, Sean Dague  wrote:

> On 08/18/2016 04:46 PM, Michael Still wrote:
> > We're still ok with merging existing ones though?
>
> Mostly we'd like to conserve the CI time now. It's about 14.5 node-hours
> to run CI on these patches (probably on about 9 node-hours in the gate).
> With ~800 nodes every patch represents 1.5% of our CI resources (per
> hour) to pass through. There are a ton of these patches up there, so
> even just landing gating ones consumes resources that could go towards
> other more critical fixes / features.
>
> I think the theory is these are fine to merge post freeze / milestone 3,
> when the CI should have cooled down a bit and there is more head room.
>
> -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
>



-- 
Rackspace Australia
__
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] Hold off on pushing new patches for config option cleanup

2016-08-18 Thread Sean Dague 
On 08/18/2016 04:46 PM, Michael Still wrote:
> We're still ok with merging existing ones though?

Mostly we'd like to conserve the CI time now. It's about 14.5 node-hours
to run CI on these patches (probably on about 9 node-hours in the gate).
With ~800 nodes every patch represents 1.5% of our CI resources (per
hour) to pass through. There are a ton of these patches up there, so
even just landing gating ones consumes resources that could go towards
other more critical fixes / features.

I think the theory is these are fine to merge post freeze / milestone 3,
when the CI should have cooled down a bit and there is more head room.

-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] Hold off on pushing new patches for config option cleanup

2016-08-18 Thread Michael Still 
We're still ok with merging existing ones though?

Michael

On Fri, Aug 19, 2016 at 5:18 AM, Jay Pipes  wrote:

> Roger that.
>
> On 08/18/2016 11:48 AM, Matt Riedemann wrote:
>
>> We have a lot of open changes for the centralize / cleanup config option
>> work:
>>
>> https://review.openstack.org/#/q/status:open+project:opensta
>> ck/nova+branch:master+topic:bp/centralize-config-options-newton
>>
>>
>> We said at the midcycle we'd allow those past non-priority feature
>> freeze because they are docs changes, but with the gate being backed up
>> every day let's hold off on pushing new changes for this series, at
>> least until after feature freeze on 9/2. These changes run all of the
>> test jobs so they do take a tool on the CI system, which is hurting
>> other functional things from landing before feature freeze.
>>
>>
> __
> 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
>



-- 
Rackspace Australia
__
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] Hold off on pushing new patches for config option cleanup

2016-08-18 Thread Jay Pipes 

Roger that.

On 08/18/2016 11:48 AM, Matt Riedemann wrote:

We have a lot of open changes for the centralize / cleanup config option
work:

https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/centralize-config-options-newton


We said at the midcycle we'd allow those past non-priority feature
freeze because they are docs changes, but with the gate being backed up
every day let's hold off on pushing new changes for this series, at
least until after feature freeze on 9/2. These changes run all of the
test jobs so they do take a tool on the CI system, which is hurting
other functional things from landing before feature freeze.



__
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] Hold off on pushing new patches for config option cleanup

2016-08-18 Thread Matt Riedemann 
We have a lot of open changes for the centralize / cleanup config option 
work:


https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/centralize-config-options-newton

We said at the midcycle we'd allow those past non-priority feature 
freeze because they are docs changes, but with the gate being backed up 
every day let's hold off on pushing new changes for this series, at 
least until after feature freeze on 9/2. These changes run all of the 
test jobs so they do take a tool on the CI system, which is hurting 
other functional things from landing before feature freeze.


--

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