Re: [openstack-dev] [stable] Preping for the stable/newton EOL

2017-10-25 Thread Tony Breeds 
On Wed, Oct 25, 2017 at 10:24:59AM -0500, Matt Riedemann wrote:
> On 10/24/2017 9:57 PM, Tony Breeds wrote:
> > The timing of the next phase is uncertain right now but I'd like to take
> > care of:
> > 
> > - openstack/nova
> 
> Just a status update, but the final nova newton release is waiting on two
> changes:
> 
> 1. https://review.openstack.org/#/c/514685/ - in the gate, should be merged
> today.

Okay.
 
> 2. https://review.openstack.org/#/c/514339/ - we need a fix for that in
> master and then to get backported through to stable/newton. This is a fix
> for a regression introduced in pike which was unfortunately backported to
> newton, so I think we need to fix the regression we introduced into
> stable/newton before EOL.

Okay.  This is a good outcome to a bad situation.

Yours Tony.


signature.asc
Description: PGP signature
__
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] [stable] Preping for the stable/newton EOL

2017-10-25 Thread Tony Breeds 
On Wed, Oct 25, 2017 at 01:11:53PM +0200, Dmitry Tantsur wrote:

> The last ironic newton release was done, we're ready for EOL.

Thanks that must've happened overnight.

Yours Tony.


signature.asc
Description: PGP signature
__
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] [stable] Preping for the stable/newton EOL

2017-10-25 Thread Tony Breeds 
On Wed, Oct 25, 2017 at 10:11:01AM +0100, Jean-Philippe Evrard wrote:
> On 25 October 2017 at 03:57, Tony Breeds  wrote:
> > On Tue, Oct 24, 2017 at 05:11:15PM +1100, Tony Breeds wrote:
> >> On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrote:
> >> > On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote:
> >> > > I'll prep the list of repos that will be tagged EOL real soon now for
> >> > > review.
> >> >
> >> > As promised here's the list.  The fomat is new, It's grouped by project
> >> > team so it should be easy for teams to find repos they care about.
> >> >
> >> > The only wart may be repos I couldn't find an owning team for, so check
> >> > the '-' as the owning team.
> >> >
> >> > I'm proposing to EOL all projects that meet one or more of the following
> >> > criteria:
> >> >
> >> > - The project is openstack-dev/devstack, openstack-dev/grenade or
> >> >   openstack/requirements (although these wil be done last)
> >> > - The project has the 'check-requirements' job listed as a template in
> >> >   project-config:zuul/layout.yaml
> >> > - The project gates with either devstack or grenade jobs
> >> > - The project is listed in governance:reference/projects.yaml and is 
> >> > tagged
> >> >   with 'stable:follows-policy'.
> >> >
> >> >
> >> > Based on previous cycles I have opted out:
> >> > - 'openstack/group-based-policy'
> >> > - 'openstack/openstack-ansible' # So they can add EOL tags
> >> >
> >> > Also based on recent email's with tripleo I have opted out:
> >> > - 'openstack/instack'
> >> > - 'openstack/instack-undercloud'
> >> > - 'openstack/os-apply-config'
> >> > - 'openstack/os-collect-config'
> >> > - 'openstack/os-net-config'
> >> > - 'openstack/os-refresh-config'
> >> > - 'openstack/puppet-tripleo'
> >> > - 'openstack/python-tripleoclient'
> >> > - 'openstack/tripleo-common'
> >> > - 'openstack/tripleo-heat-templates'
> >> > - 'openstack/tripleo-puppet-elements'
> >> > - 'openstack/tripleo-validations'
> >> > - 'openstack/tripleo-image-elements'
> >> > - 'openstack/tripleo-ui'
> >>
> >> I've also removed the following repos as the have open release requests
> >> for stable/newton
> >>  - openstack/nova
> >>  - openstack/ironic
> >>  - openstack/openstack-ansible*
> >>
> >> And at the request of the docs team I've omitted:
> >>  - openstack/openstack-manuals
> >>
> >> to facilitate 'badging' of the newton docs.
> >
> > The repos listed in 
> > http://lists.openstack.org/pipermail/openstack-dev/2017-October/123910.html
> > have been retired.
> >
> > There were a couple of issues
> > - openstack/deb-python-os-cloud-config
> > - openstack/bareon
> > My clones of both had stale gerrit remotes that has been corrected
> > manually.
> >
> > The timing of the next phase is uncertain right now but I'd like to take
> > care of:
> >
> > - openstack/nova
> > - openstack/ironic
> > - openstack/openstack-ansible*
> > - openstack/openstack-manuals
> >
> > before the summit if possible.
> >
> > Thanks to the infra team for enabling this to happen today.
> >
> > Tony.
> >
> > __
> > 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
> >
> 
> Hello Tony,
> 
> We'd like to continue doing as before: updating all our upstream
> projects to their EOL tag, then creating an EOL release based on our
> roles that would successfully deploy those EOL upstream projects.
> If any role need a change, due to latest upstream changes, we need to be 
> ready.
> 
> TL:DR; I'll submit a patch soon to bump our upstream roles to EOL,
> when nova/ironic will have their EOL tag :p

Yup that was my assumption, sorry it wasn't clear from my
talking-to-myself email thread ;p

So I see it working more or less like:

1. ironic and releases happen and repos tagged
2. The existing OSA review is merged
3. A new review is created for OSA using the tags for $all_projects
that's merged and released
4. a review in openstack-ansible pins the OSA roles to that from 3. (I'm
making that bit up is it right?)
5. openstack-ansible* repos tagged EOL

Where'd I get it wrong?

Yours Tony.


signature.asc
Description: PGP signature
__
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] [stable] Preping for the stable/newton EOL

2017-10-25 Thread Matt Riedemann 

On 10/24/2017 9:57 PM, Tony Breeds wrote:

The timing of the next phase is uncertain right now but I'd like to take
care of:

- openstack/nova


Just a status update, but the final nova newton release is waiting on 
two changes:


1. https://review.openstack.org/#/c/514685/ - in the gate, should be 
merged today.


2. https://review.openstack.org/#/c/514339/ - we need a fix for that in 
master and then to get backported through to stable/newton. This is a 
fix for a regression introduced in pike which was unfortunately 
backported to newton, so I think we need to fix the regression we 
introduced into stable/newton before EOL.


--

Thanks,

Matt

__
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] [stable] Preping for the stable/newton EOL

2017-10-25 Thread Dmitry Tantsur 

On 10/25/2017 04:57 AM, Tony Breeds wrote:

On Tue, Oct 24, 2017 at 05:11:15PM +1100, Tony Breeds wrote:

On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrote:

On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote:

I'll prep the list of repos that will be tagged EOL real soon now for
review.


As promised here's the list.  The fomat is new, It's grouped by project
team so it should be easy for teams to find repos they care about.

The only wart may be repos I couldn't find an owning team for, so check
the '-' as the owning team.

I'm proposing to EOL all projects that meet one or more of the following
criteria:

- The project is openstack-dev/devstack, openstack-dev/grenade or
   openstack/requirements (although these wil be done last)
- The project has the 'check-requirements' job listed as a template in
   project-config:zuul/layout.yaml
- The project gates with either devstack or grenade jobs
- The project is listed in governance:reference/projects.yaml and is tagged
   with 'stable:follows-policy'.


Based on previous cycles I have opted out:
- 'openstack/group-based-policy'
- 'openstack/openstack-ansible' # So they can add EOL tags

Also based on recent email's with tripleo I have opted out:
- 'openstack/instack'
- 'openstack/instack-undercloud'
- 'openstack/os-apply-config'
- 'openstack/os-collect-config'
- 'openstack/os-net-config'
- 'openstack/os-refresh-config'
- 'openstack/puppet-tripleo'
- 'openstack/python-tripleoclient'
- 'openstack/tripleo-common'
- 'openstack/tripleo-heat-templates'
- 'openstack/tripleo-puppet-elements'
- 'openstack/tripleo-validations'
- 'openstack/tripleo-image-elements'
- 'openstack/tripleo-ui'


I've also removed the following repos as the have open release requests
for stable/newton
  - openstack/nova
  - openstack/ironic
  - openstack/openstack-ansible*

And at the request of the docs team I've omitted:
  - openstack/openstack-manuals

to facilitate 'badging' of the newton docs.


The repos listed in 
http://lists.openstack.org/pipermail/openstack-dev/2017-October/123910.html
have been retired.

There were a couple of issues
- openstack/deb-python-os-cloud-config
- openstack/bareon
My clones of both had stale gerrit remotes that has been corrected
manually.

The timing of the next phase is uncertain right now but I'd like to take
care of:

- openstack/nova
- openstack/ironic


The last ironic newton release was done, we're ready for EOL.


- openstack/openstack-ansible*
- openstack/openstack-manuals

before the summit if possible.

Thanks to the infra team for enabling this to happen today.

Tony.



__
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] [stable] Preping for the stable/newton EOL

2017-10-25 Thread Jean-Philippe Evrard 
On 25 October 2017 at 03:57, Tony Breeds  wrote:
> On Tue, Oct 24, 2017 at 05:11:15PM +1100, Tony Breeds wrote:
>> On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrote:
>> > On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote:
>> > > I'll prep the list of repos that will be tagged EOL real soon now for
>> > > review.
>> >
>> > As promised here's the list.  The fomat is new, It's grouped by project
>> > team so it should be easy for teams to find repos they care about.
>> >
>> > The only wart may be repos I couldn't find an owning team for, so check
>> > the '-' as the owning team.
>> >
>> > I'm proposing to EOL all projects that meet one or more of the following
>> > criteria:
>> >
>> > - The project is openstack-dev/devstack, openstack-dev/grenade or
>> >   openstack/requirements (although these wil be done last)
>> > - The project has the 'check-requirements' job listed as a template in
>> >   project-config:zuul/layout.yaml
>> > - The project gates with either devstack or grenade jobs
>> > - The project is listed in governance:reference/projects.yaml and is tagged
>> >   with 'stable:follows-policy'.
>> >
>> >
>> > Based on previous cycles I have opted out:
>> > - 'openstack/group-based-policy'
>> > - 'openstack/openstack-ansible' # So they can add EOL tags
>> >
>> > Also based on recent email's with tripleo I have opted out:
>> > - 'openstack/instack'
>> > - 'openstack/instack-undercloud'
>> > - 'openstack/os-apply-config'
>> > - 'openstack/os-collect-config'
>> > - 'openstack/os-net-config'
>> > - 'openstack/os-refresh-config'
>> > - 'openstack/puppet-tripleo'
>> > - 'openstack/python-tripleoclient'
>> > - 'openstack/tripleo-common'
>> > - 'openstack/tripleo-heat-templates'
>> > - 'openstack/tripleo-puppet-elements'
>> > - 'openstack/tripleo-validations'
>> > - 'openstack/tripleo-image-elements'
>> > - 'openstack/tripleo-ui'
>>
>> I've also removed the following repos as the have open release requests
>> for stable/newton
>>  - openstack/nova
>>  - openstack/ironic
>>  - openstack/openstack-ansible*
>>
>> And at the request of the docs team I've omitted:
>>  - openstack/openstack-manuals
>>
>> to facilitate 'badging' of the newton docs.
>
> The repos listed in 
> http://lists.openstack.org/pipermail/openstack-dev/2017-October/123910.html
> have been retired.
>
> There were a couple of issues
> - openstack/deb-python-os-cloud-config
> - openstack/bareon
> My clones of both had stale gerrit remotes that has been corrected
> manually.
>
> The timing of the next phase is uncertain right now but I'd like to take
> care of:
>
> - openstack/nova
> - openstack/ironic
> - openstack/openstack-ansible*
> - openstack/openstack-manuals
>
> before the summit if possible.
>
> Thanks to the infra team for enabling this to happen today.
>
> Tony.
>
> __
> 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
>

Hello Tony,

We'd like to continue doing as before: updating all our upstream
projects to their EOL tag, then creating an EOL release based on our
roles that would successfully deploy those EOL upstream projects.
If any role need a change, due to latest upstream changes, we need to be ready.

TL:DR; I'll submit a patch soon to bump our upstream roles to EOL,
when nova/ironic will have their EOL tag :p

Best regards,
Jean-Philippe Evrard (evrardjp)

PS: The existing newton release to review was the last bump before
EOL, and was submitted during EOL week IIRC. It's good to keep it,
this way we are still following our release train, while some EOL tags
are not yet issued.

__
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] [stable] Preping for the stable/newton EOL

2017-10-24 Thread Tony Breeds 
On Tue, Oct 24, 2017 at 05:11:15PM +1100, Tony Breeds wrote:
> On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrote:
> > On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote:
> > > I'll prep the list of repos that will be tagged EOL real soon now for
> > > review.
> > 
> > As promised here's the list.  The fomat is new, It's grouped by project
> > team so it should be easy for teams to find repos they care about.
> > 
> > The only wart may be repos I couldn't find an owning team for, so check
> > the '-' as the owning team.
> > 
> > I'm proposing to EOL all projects that meet one or more of the following
> > criteria:
> > 
> > - The project is openstack-dev/devstack, openstack-dev/grenade or
> >   openstack/requirements (although these wil be done last)
> > - The project has the 'check-requirements' job listed as a template in
> >   project-config:zuul/layout.yaml
> > - The project gates with either devstack or grenade jobs
> > - The project is listed in governance:reference/projects.yaml and is tagged
> >   with 'stable:follows-policy'.
> > 
> > 
> > Based on previous cycles I have opted out:
> > - 'openstack/group-based-policy'
> > - 'openstack/openstack-ansible' # So they can add EOL tags
> > 
> > Also based on recent email's with tripleo I have opted out:
> > - 'openstack/instack'
> > - 'openstack/instack-undercloud'
> > - 'openstack/os-apply-config'
> > - 'openstack/os-collect-config'
> > - 'openstack/os-net-config'
> > - 'openstack/os-refresh-config'
> > - 'openstack/puppet-tripleo'
> > - 'openstack/python-tripleoclient'
> > - 'openstack/tripleo-common'
> > - 'openstack/tripleo-heat-templates'
> > - 'openstack/tripleo-puppet-elements'
> > - 'openstack/tripleo-validations'
> > - 'openstack/tripleo-image-elements'
> > - 'openstack/tripleo-ui'
> 
> I've also removed the following repos as the have open release requests
> for stable/newton
>  - openstack/nova
>  - openstack/ironic
>  - openstack/openstack-ansible*
> 
> And at the request of the docs team I've omitted:
>  - openstack/openstack-manuals
> 
> to facilitate 'badging' of the newton docs.

The repos listed in 
http://lists.openstack.org/pipermail/openstack-dev/2017-October/123910.html
have been retired.

There were a couple of issues
- openstack/deb-python-os-cloud-config
- openstack/bareon
My clones of both had stale gerrit remotes that has been corrected
manually.

The timing of the next phase is uncertain right now but I'd like to take
care of:

- openstack/nova
- openstack/ironic
- openstack/openstack-ansible*
- openstack/openstack-manuals

before the summit if possible.

Thanks to the infra team for enabling this to happen today.

Tony.


signature.asc
Description: PGP signature
__
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] [stable] Preping for the stable/newton EOL

2017-10-24 Thread Tony Breeds 
On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrote:
> On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote:
> > I'll prep the list of repos that will be tagged EOL real soon now for
> > review.
> 
> As promised here's the list.  The fomat is new, It's grouped by project
> team so it should be easy for teams to find repos they care about.
> 
> The only wart may be repos I couldn't find an owning team for, so check
> the '-' as the owning team.
> 
> I'm proposing to EOL all projects that meet one or more of the following
> criteria:
> 
> - The project is openstack-dev/devstack, openstack-dev/grenade or
>   openstack/requirements (although these wil be done last)
> - The project has the 'check-requirements' job listed as a template in
>   project-config:zuul/layout.yaml
> - The project gates with either devstack or grenade jobs
> - The project is listed in governance:reference/projects.yaml and is tagged
>   with 'stable:follows-policy'.
> 
> 
> Based on previous cycles I have opted out:
> - 'openstack/group-based-policy'
> - 'openstack/openstack-ansible' # So they can add EOL tags
> 
> Also based on recent email's with tripleo I have opted out:
> - 'openstack/instack'
> - 'openstack/instack-undercloud'
> - 'openstack/os-apply-config'
> - 'openstack/os-collect-config'
> - 'openstack/os-net-config'
> - 'openstack/os-refresh-config'
> - 'openstack/puppet-tripleo'
> - 'openstack/python-tripleoclient'
> - 'openstack/tripleo-common'
> - 'openstack/tripleo-heat-templates'
> - 'openstack/tripleo-puppet-elements'
> - 'openstack/tripleo-validations'
> - 'openstack/tripleo-image-elements'
> - 'openstack/tripleo-ui'

I've also removed the following repos as the have open release requests
for stable/newton
 - openstack/nova
 - openstack/ironic
 - openstack/openstack-ansible*

And at the request of the docs team I've omitted:
 - openstack/openstack-manuals

to facilitate 'badging' of the newton docs.

---
# EOL repos belonging to barbican
eol-branch.sh -- stable/newton newton-eol openstack/barbican 
openstack/python-barbicanclient
# EOL repos belonging to cinder
eol-branch.sh -- stable/newton newton-eol \
 openstack/cinder openstack/os-brick \
 openstack/python-brick-cinderclient-ext \
 openstack/python-cinderclient
# EOL repos belonging to cloudkitty
eol-branch.sh -- stable/newton newton-eol openstack/cloudkitty
# EOL repos belonging to congress
eol-branch.sh -- stable/newton newton-eol openstack/congress 
openstack/python-congressclient
# EOL repos belonging to designate
eol-branch.sh -- stable/newton newton-eol \
 openstack/designate openstack/designate-dashboard \
 openstack/python-designateclient
# EOL repos belonging to dragonflow
eol-branch.sh -- stable/newton newton-eol openstack/dragonflow
# EOL repos belonging to ec2-api
eol-branch.sh -- stable/newton newton-eol openstack/ec2-api
# EOL repos belonging to freezer
eol-branch.sh -- stable/newton newton-eol \
 openstack/freezer openstack/freezer-api \
 openstack/freezer-dr openstack/freezer-web-ui \
 openstack/python-freezerclient
# EOL repos belonging to glance
eol-branch.sh -- stable/newton newton-eol \
 openstack/glance openstack/glance_store \
 openstack/python-glanceclient
# EOL repos belonging to heat
eol-branch.sh -- stable/newton newton-eol openstack/heat 
openstack/python-heatclient
# EOL repos belonging to horizon
eol-branch.sh -- stable/newton newton-eol openstack/django_openstack_auth 
openstack/horizon
# EOL repos belonging to ironic
eol-branch.sh -- stable/newton newton-eol \
 openstack/bifrost openstack/ironic-inspector \
 openstack/ironic-lib openstack/ironic-python-agent \
 openstack/ironic-ui \
 openstack/python-ironic-inspector-client \
 openstack/python-ironicclient
# EOL repos belonging to karbor
eol-branch.sh -- stable/newton newton-eol \
 openstack/karbor openstack/karbor-dashboard \
 openstack/python-karborclient
# EOL repos belonging to keystone
eol-branch.sh -- stable/newton newton-eol \
 openstack/keystone openstack/keystoneauth \
 openstack/keystonemiddleware openstack/pycadf \
 openstack/python-keystoneclient
# EOL repos belonging to kolla
eol-branch.sh -- stable/newton newton-eol openstack/kolla
# EOL repos belonging to magnum
eol-branch.sh -- stable/newton newton-eol \
 openstack/magnum openstack/magnum-ui \
 openstack/python-magnumclient
# EOL repos belonging to manila
eol-branch.sh -- stable/newton newton-eol \
 openstack/manila openstack/manila-ui \
 openstack/python-manilaclient
# EOL repos belonging to masakari
eol-branch.sh -- stable/newton newton-eol \
 openstack/masakari openstack/masakari-monitors \

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

2017-10-10 Thread Emilien Macchi 
On Thu, Oct 5, 2017 at 4:01 PM, Tony Breeds  wrote:
[...]

> I'm happy to exclude tripleo from the initial EOL cycle (and had added
> tripleo's repos to my list of 'opt-out' repos based on previous emails).
> It'd be good if we could setup a one-off time with tripleo, stable (me)
> and infra to look at what CI you have an which parts are generally
> impacted by repo's EOLing.  For example it's probable that
> openstack/requiremnets (and that implies openstack-dev/devstack) need to
> be the last projects to retire.
>
> That isn't terrible but I'd still like to make sure we're on the same
> page so we can level set everyone's expectations.
>
> So who from tripleo needs to be there and what TZ are they in?

It would be me (PST but flexible enough to work on your morning with you).

These are the jobs we currently have for newton:

puppet-tripleo:
OpenStack Infra:
gate-puppet-tripleo-puppet-lint in 11m 51s
gate-puppet-tripleo-puppet-syntax-3-legacy-centos-7 in 3m 52s
gate-puppet-tripleo-puppet-syntax-4-centos-7 in 3m 11s
gate-tripleo-ci-centos-7-nonha-multinode-oooq in 1h 36m 42s
gate-tripleo-ci-centos-7-undercloud-oooq in 49m 23s
gate-puppet-tripleo-puppet-unit-4.8-centos-7 in 7m 26s

RH1:
gate-tripleo-ci-centos-7-ovb-ha-oooq in 2h 29m 44s
gate-tripleo-ci-centos-7-ovb-1ctlr_1comp_1ceph-featureset024 in 2h 24m 02s


tripleo-heat-templates and others:

OpenStack Infra:
gate-tripleo-ci-centos-7-nonha-multinode-oooq in 1h 45m 38s
gate-tripleo-heat-templates-pep8-ubuntu-xenial in 1m 36s

RH1:
gate-tripleo-ci-centos-7-ovb-ha-oooq in 2h 29m 44s
gate-tripleo-ci-centos-7-ovb-1ctlr_1comp_1ceph-featureset024 in 2h 24m 02s

We don't have upgrade jobs on stable/newton, so the amount of consumed
resources is reasonable I guess.

Ping me anytime for further discussion,
Thanks!
-- 
Emilien Macchi

__
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] [stable] Preping for the stable/newton EOL

2017-10-09 Thread Alex Schultz 
On Thu, Oct 5, 2017 at 5:01 PM, Tony Breeds  wrote:
> On Thu, Oct 05, 2017 at 09:00:00AM -0600, Alex Schultz wrote:
>> On Tue, Oct 3, 2017 at 9:51 PM, Tony Breeds  wrote:
>
>> Would it be possible to delay the Newton EOL for the TripleO projects
>> for ~1month? We still have some patches outstanding and would like to
>> delay the EOL for now.  As previously mentioned elsewhere it would be
>> beneficial for us to wait until the end of Queens but for now I'd like
>> to pencil in ~1month to give us additional time to evaulate if we need
>> more time.  Let me know if this isn't realistic or there are any
>> glaring issues with this.
>
> I'm happy to exclude tripleo from the initial EOL cycle (and had added
> tripleo's repos to my list of 'opt-out' repos based on previous emails).
> It'd be good if we could setup a one-off time with tripleo, stable (me)
> and infra to look at what CI you have an which parts are generally
> impacted by repo's EOLing.  For example it's probable that
> openstack/requiremnets (and that implies openstack-dev/devstack) need to
> be the last projects to retire.
>
> That isn't terrible but I'd still like to make sure we're on the same
> page so we can level set everyone's expectations.
>
> So who from tripleo needs to be there and what TZ are they in?
>

So probably Emilien and/or some folks from the TripleO CI Squad to
review.  I will bring it up tomorrow during the tripleo meeting.

Thanks,
-Alex

> Yours Tony.
>
> __
> 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] [stable] Preping for the stable/newton EOL

2017-10-05 Thread Tony Breeds 
On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote:
> I'll prep the list of repos that will be tagged EOL real soon now for
> review.

As promised here's the list.  The fomat is new, It's grouped by project
team so it should be easy for teams to find repos they care about.

The only wart may be repos I couldn't find an owning team for, so check
the '-' as the owning team.

I'm proposing to EOL all projects that meet one or more of the following
criteria:

- The project is openstack-dev/devstack, openstack-dev/grenade or
  openstack/requirements (although these wil be done last)
- The project has the 'check-requirements' job listed as a template in
  project-config:zuul/layout.yaml
- The project gates with either devstack or grenade jobs
- The project is listed in governance:reference/projects.yaml and is tagged
  with 'stable:follows-policy'.


Based on previous cycles I have opted out:
- 'openstack/group-based-policy'
- 'openstack/openstack-ansible' # So they can add EOL tags

Also based on recent email's with tripleo I have opted out:
- 'openstack/instack'
- 'openstack/instack-undercloud'
- 'openstack/os-apply-config'
- 'openstack/os-collect-config'
- 'openstack/os-net-config'
- 'openstack/os-refresh-config'
- 'openstack/puppet-tripleo'
- 'openstack/python-tripleoclient'
- 'openstack/tripleo-common'
- 'openstack/tripleo-heat-templates'
- 'openstack/tripleo-puppet-elements'
- 'openstack/tripleo-validations'
- 'openstack/tripleo-image-elements'
- 'openstack/tripleo-ui'


---
# EOL repos belonging to barbican
eol-branch.sh -- stable/newton newton-eol openstack/barbican 
openstack/python-barbicanclient
# EOL repos belonging to cinder
eol-branch.sh -- stable/newton newton-eol \
 openstack/cinder openstack/os-brick \
 openstack/python-brick-cinderclient-ext \
 openstack/python-cinderclient
# EOL repos belonging to cloudkitty
eol-branch.sh -- stable/newton newton-eol openstack/cloudkitty
# EOL repos belonging to congress
eol-branch.sh -- stable/newton newton-eol openstack/congress 
openstack/python-congressclient
# EOL repos belonging to designate
eol-branch.sh -- stable/newton newton-eol \
 openstack/designate openstack/designate-dashboard \
 openstack/python-designateclient
# EOL repos belonging to dragonflow
eol-branch.sh -- stable/newton newton-eol openstack/dragonflow
# EOL repos belonging to ec2-api
eol-branch.sh -- stable/newton newton-eol openstack/ec2-api
# EOL repos belonging to freezer
eol-branch.sh -- stable/newton newton-eol \
 openstack/freezer openstack/freezer-api \
 openstack/freezer-dr openstack/freezer-web-ui \
 openstack/python-freezerclient
# EOL repos belonging to glance
eol-branch.sh -- stable/newton newton-eol \
 openstack/glance openstack/glance_store \
 openstack/python-glanceclient
# EOL repos belonging to heat
eol-branch.sh -- stable/newton newton-eol openstack/heat 
openstack/python-heatclient
# EOL repos belonging to horizon
eol-branch.sh -- stable/newton newton-eol openstack/django_openstack_auth 
openstack/horizon
# EOL repos belonging to ironic
eol-branch.sh -- stable/newton newton-eol \
 openstack/bifrost openstack/ironic \
 openstack/ironic-inspector openstack/ironic-lib \
 openstack/ironic-python-agent openstack/ironic-ui \
 openstack/python-ironic-inspector-client \
 openstack/python-ironicclient
# EOL repos belonging to karbor
eol-branch.sh -- stable/newton newton-eol \
 openstack/karbor openstack/karbor-dashboard \
 openstack/python-karborclient
# EOL repos belonging to keystone
eol-branch.sh -- stable/newton newton-eol \
 openstack/keystone openstack/keystoneauth \
 openstack/keystonemiddleware openstack/pycadf \
 openstack/python-keystoneclient
# EOL repos belonging to kolla
eol-branch.sh -- stable/newton newton-eol openstack/kolla
# EOL repos belonging to magnum
eol-branch.sh -- stable/newton newton-eol \
 openstack/magnum openstack/magnum-ui \
 openstack/python-magnumclient
# EOL repos belonging to manila
eol-branch.sh -- stable/newton newton-eol \
 openstack/manila openstack/manila-ui \
 openstack/python-manilaclient
# EOL repos belonging to mistral
eol-branch.sh -- stable/newton newton-eol \
 openstack/mistral openstack/mistral-dashboard \
 openstack/mistral-extra openstack/python-mistralclient
# EOL repos belonging to monasca
eol-branch.sh -- stable/newton newton-eol \
 openstack/monasca-agent openstack/monasca-api \
 openstack/monasca-ceilometer openstack/monasca-common \
 openstack/monasca-log-api openstack/monasca-notification \
 openstack/monasca-persister

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

2017-10-05 Thread Tony Breeds 
On Thu, Oct 05, 2017 at 09:00:00AM -0600, Alex Schultz wrote:
> On Tue, Oct 3, 2017 at 9:51 PM, Tony Breeds  wrote:

> Would it be possible to delay the Newton EOL for the TripleO projects
> for ~1month? We still have some patches outstanding and would like to
> delay the EOL for now.  As previously mentioned elsewhere it would be
> beneficial for us to wait until the end of Queens but for now I'd like
> to pencil in ~1month to give us additional time to evaulate if we need
> more time.  Let me know if this isn't realistic or there are any
> glaring issues with this.

I'm happy to exclude tripleo from the initial EOL cycle (and had added
tripleo's repos to my list of 'opt-out' repos based on previous emails).
It'd be good if we could setup a one-off time with tripleo, stable (me)
and infra to look at what CI you have an which parts are generally
impacted by repo's EOLing.  For example it's probable that
openstack/requiremnets (and that implies openstack-dev/devstack) need to
be the last projects to retire.

That isn't terrible but I'd still like to make sure we're on the same
page so we can level set everyone's expectations.

So who from tripleo needs to be there and what TZ are they in?

Yours Tony.


signature.asc
Description: PGP signature
__
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] [stable] Preping for the stable/newton EOL

2017-10-05 Thread Alex Schultz 
On Tue, Oct 3, 2017 at 9:51 PM, Tony Breeds  wrote:
> Hi All,
> This is a quick update on the process for tagging stable/newton as
> EOL:
>
> The published[1][2] timeline is:
> Sep 29 : Final newton library releases
> Oct 09 : stable/newton branches enter Phase III
> Oct 11 : stable/newton branches get tagged EOL
>
> Given that those key dates were a little disrupted I'm proposing adding
> a week to each so the new timeline looks like:
> Oct 08 : Final newton library releases
> Oct 16 : stable/newton branches enter Phase III
> Oct 18 : stable/newton branches get tagged EOL
>
> The transition to Phase II is important to set expectation about what
> backports are applicable while we process the EOL.
>
> I'll prep the list of repos that will be tagged EOL real soon now for
> review.
>

Would it be possible to delay the Newton EOL for the TripleO projects
for ~1month? We still have some patches outstanding and would like to
delay the EOL for now.  As previously mentioned elsewhere it would be
beneficial for us to wait until the end of Queens but for now I'd like
to pencil in ~1month to give us additional time to evaulate if we need
more time.  Let me know if this isn't realistic or there are any
glaring issues with this.

Thanks,
-Alex

> Yours Tony.
>
> [1] https://releases.openstack.org/index.html
> [2] https://releases.openstack.org/queens/schedule.html
>
> __
> 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

[openstack-dev] [stable] Preping for the stable/newton EOL

2017-10-03 Thread Tony Breeds 
Hi All,
This is a quick update on the process for tagging stable/newton as
EOL:

The published[1][2] timeline is:
Sep 29 : Final newton library releases
Oct 09 : stable/newton branches enter Phase III
Oct 11 : stable/newton branches get tagged EOL

Given that those key dates were a little disrupted I'm proposing adding
a week to each so the new timeline looks like:
Oct 08 : Final newton library releases
Oct 16 : stable/newton branches enter Phase III
Oct 18 : stable/newton branches get tagged EOL

The transition to Phase II is important to set expectation about what
backports are applicable while we process the EOL.

I'll prep the list of repos that will be tagged EOL real soon now for
review.

Yours Tony.

[1] https://releases.openstack.org/index.html 
[2] https://releases.openstack.org/queens/schedule.html


signature.asc
Description: PGP signature
__
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