Re: [openstack-dev] [tripleo][release] Plans re newton-3 release and feature freeze exceptions

2016-08-29 Thread Steven Hardy
On Mon, Aug 29, 2016 at 12:18:17PM +0300, Juan Antonio Osorio wrote:
>On Fri, Aug 26, 2016 at 7:14 PM, Steven Hardy  wrote:
> 
>  Hi all,
> 
>  There have been some discussions on $subject recently, so I wanted to
>  give
>  a status update.
> 
>  Next week we will tag our newton-3 release, and we're currently working
>  to
>  either land or defer the remaining features tracked here:
> 
>  https://launchpad.net/tripleo/+milestone/newton-3
> 
>  We need to land as many of the "Needs Code Review" features as we can
>  before cutting the release next week, so please help by prioritizing
>  your
>  reviews.
> 
>  --
>  Feature Freeze
>  --
> 
>  After newton-3 is released, we'll have reached Feature Freeze for
>  Newton,
>  and any features landed after this point must be agreed as feature
>  freeze
>  exceptions (everything else will be deferred to Ocata) - the process is
>  to
>  mail this list with a justification, and details of which patches need
>  to
>  land, then we'll reach consensus over if it will be accepted or not
>  based
>  on the level of risk, and the status of the patches.
> 
>  Currently there are three potential FFEs which I'm aware of:
> 
>  1. Mistral API
> 
>  We've made good progress on this over recent weeks, but several patches
>  remain - this is the umbrella BP, and it links several dependent BPs
>  which
>  are mostly posted but need code reviews, please help by testing and
>  reviewing these:
> 
>  https://blueprints.launchpad.net/tripleo/+spec/mistral-deployment-library
> 
>  2. Composable Roles
> 
>  There are two parts to this, some remaining cleanups related to
>  per-service
>  configuration (such as bind_ip's) which need to land, and the related
>  custom-roles feature:
> 
>  https://bugs.launchpad.net/tripleo/+bug/1604414
> 
>  https://blueprints.launchpad.net/tripleo/+spec/custom-roles
> 
>  Some patches still need to be fixed or written to enable custom-roles -
>  it's a stretch but I'd say a FFE may be reasonable provided we can get
>  the
>  remaining patches functional in the next few days (I'm planning to do
>  this)
> 
>  3. Contrail integration
> 
>  There are patches posted for this, but they need work - Carlos is
>  helping
>  so I'd suggest it should be possible to land these as a FFE (should be
>  low
>  risk as it's all disabled by default)
> 
>  https://blueprints.launchpad.net/tripleo/+spec/contrail-services
> 
>  These are the main features I'm aware of that are targetted to newton-3
>  but will probably slip, are there others folks want to raise?
> 
>Well, https://review.openstack.org/#/c/282307/ is still in progress and
>will need an FFE. What's the official process to apply for the exception?

Just mail this list, either on this thread or an new one, provide details
of the justification, risk/benefit, and a detailed list of the outstanding
patches, if folks agree a FFE is reasonable (they can reply to the ML
and/or we'll discuss in IRC), I'll move the BP to our RC1 milestone in
launchpad.

I've not yet done that for custom-roles so here's my FFE request for
consideration, you can reply here in a similar format for tls-via-certmonger

FFE request for custom-roles:

Blueprint link: https://blueprints.launchpad.net/tripleo/+spec/custom-roles

Status:

It's about 90% complete, a few of the patches posted need some work, and
the final jina2 refactor of overcloud.yaml isn't finished, I expect all
remaining patches can be posted by the end of this week.

This has been blocked firstly on the composable services refactoring, and
more recently on the Mistral API work, both landed much later than
anticipated, and like everyone I've been struggling with pretty slow review
progress vs a long series of patches.

Justification/Benefit:

A lot of folks have been asking for this, and without the ability to spin
up arbitrary role types, a lot of the value of the effort we put into
composable services is diminished (because you still can't independently
scale anything).

Risk:

This is moderately risky, because some significant refactoring to
allNodesConfig and VipConfig have not yet landed.  I feel OK about this
other than the risk around anything we're not currently testing in CI, e.g
we disabled IPv6 testing so that will definitely need to be carefully
verified (and/or a CI test reinstated) prior to the final Newton release.

Detailed patch status:

Waiting on CI but ready for review:
https://review.openstack.org/#/c/361108/
https://review.openstack.org/#/c/355067
https://review.openstack.org/#/c/355068/
https://review.openstack.org/#/c/361731
https://review.openstack.org/#/c/361730/

WIP (I'm planning to update these later as there's some remaining issues):
https://review.openstack.org/#/c/361777/
https://review.opens

Re: [openstack-dev] [tripleo][release] Plans re newton-3 release and feature freeze exceptions

2016-08-29 Thread Juan Antonio Osorio
On Fri, Aug 26, 2016 at 7:14 PM, Steven Hardy  wrote:

> Hi all,
>
> There have been some discussions on $subject recently, so I wanted to give
> a status update.
>
> Next week we will tag our newton-3 release, and we're currently working to
> either land or defer the remaining features tracked here:
>
> https://launchpad.net/tripleo/+milestone/newton-3
>
> We need to land as many of the "Needs Code Review" features as we can
> before cutting the release next week, so please help by prioritizing your
> reviews.
>
> --
> Feature Freeze
> --
>
> After newton-3 is released, we'll have reached Feature Freeze for Newton,
> and any features landed after this point must be agreed as feature freeze
> exceptions (everything else will be deferred to Ocata) - the process is to
> mail this list with a justification, and details of which patches need to
> land, then we'll reach consensus over if it will be accepted or not based
> on the level of risk, and the status of the patches.
>
> Currently there are three potential FFEs which I'm aware of:
>
> 1. Mistral API
>
> We've made good progress on this over recent weeks, but several patches
> remain - this is the umbrella BP, and it links several dependent BPs which
> are mostly posted but need code reviews, please help by testing and
> reviewing these:
>
> https://blueprints.launchpad.net/tripleo/+spec/mistral-deployment-library
>
> 2. Composable Roles
>
> There are two parts to this, some remaining cleanups related to per-service
> configuration (such as bind_ip's) which need to land, and the related
> custom-roles feature:
>
> https://bugs.launchpad.net/tripleo/+bug/1604414
>
> https://blueprints.launchpad.net/tripleo/+spec/custom-roles
>
> Some patches still need to be fixed or written to enable custom-roles -
> it's a stretch but I'd say a FFE may be reasonable provided we can get the
> remaining patches functional in the next few days (I'm planning to do this)
>
> 3. Contrail integration
>
> There are patches posted for this, but they need work - Carlos is helping
> so I'd suggest it should be possible to land these as a FFE (should be low
> risk as it's all disabled by default)
>
> https://blueprints.launchpad.net/tripleo/+spec/contrail-services
>
> These are the main features I'm aware of that are targetted to newton-3
> but will probably slip, are there others folks want to raise?
>
Well, https://review.openstack.org/#/c/282307/ is still in progress and
will need an FFE. What's the official process to apply for the exception?

>
> 
> Bugs
> 
>
> Any bugs not fixed by newton-3 will be deferred to an RC1 milestone I
> created, so that we can track remaining release-blocker bugs in the weeks
> leading to the final release.  Please ensure all bugs are targetted to this
> milestone so we don't miss them.
>
> https://launchpad.net/tripleo/+milestone/newton-rc1
>
> Please let me know if there are any questions or concerns, and thanks to
> everyone for all the help getting to this point, it's been a tough but
> productive cycle, and I'm looking forward to reaching our final newton
> release! :)
>
> Thanks,
>
> Steve
>
> __
> 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
>



-- 
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
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] [tripleo][release] Plans re newton-3 release and feature freeze exceptions

2016-08-29 Thread Julie Pichon
On 26 August 2016 at 19:04, James Slagle  wrote:
> On Fri, Aug 26, 2016 at 12:14 PM, Steven Hardy  wrote:
>>
>> 1. Mistral API
>>
>> We've made good progress on this over recent weeks, but several patches
>> remain - this is the umbrella BP, and it links several dependent BPs which
>> are mostly posted but need code reviews, please help by testing and
>> reviewing these:
>>
>> https://blueprints.launchpad.net/tripleo/+spec/mistral-deployment-library
>
> Based on what's linked off of that blueprint, here's what's left:
>
> https://blueprints.launchpad.net/tripleo/+spec/cli-deployment-via-workflow
> topic branch: 
> https://review.openstack.org/#/q/status:open+project:openstack/python-tripleoclient+branch:master+topic:deploy
> 5 patches, 2 are marked WIP, all need reviews
>
> https://blueprints.launchpad.net/tripleo-ui/+spec/tripleo-ui-mistral-refactoring
> topic branch: 
> https://review.openstack.org/#/q/topic:bp/tripleo-ui-mistral-refactoring
> 1 tripleo-ui patch
> 1 tripleo-common patch that is Workflow -1
> 1 tripleoclient patch that I just approved

Thank you for moving the tripleoclient patch forward. The Workflow-1'd
patch can be ignored, I updated the topic name to avoid confusion.
(The approach was initially rejected but there's been small voices of
"maybe it would be handy after all" coming up afterwards; I'm keeping
it around to do some rework and perhaps re-discuss it at a later
point.)

Thanks,

Julie

__
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] [tripleo][release] Plans re newton-3 release and feature freeze exceptions

2016-08-26 Thread Ben Swartzlander

On 08/26/2016 02:04 PM, James Slagle wrote:

On Fri, Aug 26, 2016 at 12:14 PM, Steven Hardy  wrote:


1. Mistral API

We've made good progress on this over recent weeks, but several patches
remain - this is the umbrella BP, and it links several dependent BPs which
are mostly posted but need code reviews, please help by testing and
reviewing these:

https://blueprints.launchpad.net/tripleo/+spec/mistral-deployment-library


Based on what's linked off of that blueprint, here's what's left:

https://blueprints.launchpad.net/tripleo/+spec/cli-deployment-via-workflow
topic branch: 
https://review.openstack.org/#/q/status:open+project:openstack/python-tripleoclient+branch:master+topic:deploy
5 patches, 2 are marked WIP, all need reviews

https://blueprints.launchpad.net/tripleo-ui/+spec/tripleo-ui-mistral-refactoring
topic branch: 
https://review.openstack.org/#/q/topic:bp/tripleo-ui-mistral-refactoring
1 tripleo-ui patch
1 tripleo-common patch that is Workflow -1
1 tripleoclient patch that I just approved

https://blueprints.launchpad.net/tripleo/+spec/roles-list-action
single patch: https://review.openstack.org/#/c/330283/, needs review

From: https://etherpad.openstack.org/p/tripleo-mistral-api ---
https://review.openstack.org/#/c/355598/ (merge conflict, needs review)
https://review.openstack.org/#/c/348875/ (just approved, should merge)
https://review.openstack.org/#/c/341572/ (just approved, should merge)

Additionally, there are the validations patches:
https://review.openstack.org/#/q/topic:mistral-validations

If I missed anything, please point it out.


There's 3 small patches that need to be included in Newton. The author, 
marios, didn't tag them with a blueprint or bug so they don't show up on 
the LP milestone page, however there's a joint NetApp/Redhat 
presentation in Barcelona which assumes we have NetApp driver support 
for Manila in TripleO.


https://review.openstack.org/#/c/354019
https://review.openstack.org/#/c/354014
https://review.openstack.org/#/c/355394

I'm hoping these can go in today, but if not I'll file an FFE for them. 
AFAIK there's no problems with these.


-Ben Swartzlander






__
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] [tripleo][release] Plans re newton-3 release and feature freeze exceptions

2016-08-26 Thread James Slagle
On Fri, Aug 26, 2016 at 12:14 PM, Steven Hardy  wrote:
>
> 1. Mistral API
>
> We've made good progress on this over recent weeks, but several patches
> remain - this is the umbrella BP, and it links several dependent BPs which
> are mostly posted but need code reviews, please help by testing and
> reviewing these:
>
> https://blueprints.launchpad.net/tripleo/+spec/mistral-deployment-library

Based on what's linked off of that blueprint, here's what's left:

https://blueprints.launchpad.net/tripleo/+spec/cli-deployment-via-workflow
topic branch: 
https://review.openstack.org/#/q/status:open+project:openstack/python-tripleoclient+branch:master+topic:deploy
5 patches, 2 are marked WIP, all need reviews

https://blueprints.launchpad.net/tripleo-ui/+spec/tripleo-ui-mistral-refactoring
topic branch: 
https://review.openstack.org/#/q/topic:bp/tripleo-ui-mistral-refactoring
1 tripleo-ui patch
1 tripleo-common patch that is Workflow -1
1 tripleoclient patch that I just approved

https://blueprints.launchpad.net/tripleo/+spec/roles-list-action
single patch: https://review.openstack.org/#/c/330283/, needs review

From: https://etherpad.openstack.org/p/tripleo-mistral-api ---
https://review.openstack.org/#/c/355598/ (merge conflict, needs review)
https://review.openstack.org/#/c/348875/ (just approved, should merge)
https://review.openstack.org/#/c/341572/ (just approved, should merge)

Additionally, there are the validations patches:
https://review.openstack.org/#/q/topic:mistral-validations

If I missed anything, please point it out.

-- 
-- James Slagle
--

__
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] [tripleo][release] Plans re newton-3 release and feature freeze exceptions

2016-08-26 Thread Steven Hardy
Hi all,

There have been some discussions on $subject recently, so I wanted to give
a status update.

Next week we will tag our newton-3 release, and we're currently working to
either land or defer the remaining features tracked here:

https://launchpad.net/tripleo/+milestone/newton-3

We need to land as many of the "Needs Code Review" features as we can
before cutting the release next week, so please help by prioritizing your
reviews.

--
Feature Freeze
--

After newton-3 is released, we'll have reached Feature Freeze for Newton,
and any features landed after this point must be agreed as feature freeze
exceptions (everything else will be deferred to Ocata) - the process is to
mail this list with a justification, and details of which patches need to
land, then we'll reach consensus over if it will be accepted or not based
on the level of risk, and the status of the patches.

Currently there are three potential FFEs which I'm aware of:

1. Mistral API

We've made good progress on this over recent weeks, but several patches
remain - this is the umbrella BP, and it links several dependent BPs which
are mostly posted but need code reviews, please help by testing and
reviewing these:

https://blueprints.launchpad.net/tripleo/+spec/mistral-deployment-library

2. Composable Roles

There are two parts to this, some remaining cleanups related to per-service
configuration (such as bind_ip's) which need to land, and the related
custom-roles feature:

https://bugs.launchpad.net/tripleo/+bug/1604414

https://blueprints.launchpad.net/tripleo/+spec/custom-roles

Some patches still need to be fixed or written to enable custom-roles -
it's a stretch but I'd say a FFE may be reasonable provided we can get the
remaining patches functional in the next few days (I'm planning to do this)

3. Contrail integration

There are patches posted for this, but they need work - Carlos is helping
so I'd suggest it should be possible to land these as a FFE (should be low
risk as it's all disabled by default)

https://blueprints.launchpad.net/tripleo/+spec/contrail-services

These are the main features I'm aware of that are targetted to newton-3
but will probably slip, are there others folks want to raise?


Bugs


Any bugs not fixed by newton-3 will be deferred to an RC1 milestone I
created, so that we can track remaining release-blocker bugs in the weeks
leading to the final release.  Please ensure all bugs are targetted to this
milestone so we don't miss them.

https://launchpad.net/tripleo/+milestone/newton-rc1

Please let me know if there are any questions or concerns, and thanks to
everyone for all the help getting to this point, it's been a tough but
productive cycle, and I'm looking forward to reaching our final newton
release! :)

Thanks,

Steve

__
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