Re: [OpenStack-Infra] Stop supporting bindep-fallback.txt moving forward

[Paul Belanger]

On Fri, Apr 20, 2018 at 05:34:09PM +, Jeremy Stanley wrote:
> On 2018-04-20 12:31:24 -0400 (-0400), Paul Belanger wrote:
> [...]
> > That is fine, if we want to do the mass migration to bionic first,
> > then start looking at which projects are still using
> > bindep-fallback.txt is fine with me.
> > 
> > I just wanted to highlight I think it is time we start pushing a
> > little harder on projects to stop using this logic and start
> > managing bindep.txt themself.
> 
> Yep, this is something I _completely_ agree with. We could even
> start with a deprecation warning in the fallback path so it starts
> showing up more clearly in the job logs too.
> -- 
> Jeremy Stanley

Okay, looking at codesearch.o.o, I've been able to start pushing up changes to
remove bindep-fallback.txt.

https://review.openstack.org/#/q/topic:bindep.txt

This adds bindep.txt to projects that need it, and also removes the legacy
install-distro-packages.sh scripts in favor of our bindep role.

Paul

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] PTG September 10-14 in Denver

[Melvin Hillsman]

Planning on being in attendance (travel approval pending)

On Fri, Apr 20, 2018 at 12:58 PM, Jeremy Stanley  wrote:

> On 2018-04-20 10:42:48 -0700 (-0700), Clark Boylan wrote:
> [...]
> > Let me know (doesn't have to be to the list if you aren't
> > comfortable with that) and thanks!
>
> You can expect me there. Not only was the venue great, the
> restaurants within walking distance were just my speed and, as icing
> on the cake, Denver is one of the few airports to/from which I can
> get direct flights!
> --
> Jeremy Stanley
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] PTG September 10-14 in Denver

[Jeremy Stanley]

On 2018-04-20 10:42:48 -0700 (-0700), Clark Boylan wrote:
[...]
> Let me know (doesn't have to be to the list if you aren't
> comfortable with that) and thanks!

You can expect me there. Not only was the venue great, the
restaurants within walking distance were just my speed and, as icing
on the cake, Denver is one of the few airports to/from which I can
get direct flights!
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] PTG September 10-14 in Denver

[Paul Belanger]

On Fri, Apr 20, 2018 at 10:42:48AM -0700, Clark Boylan wrote:
> Hello everyone,
> 
> I've been asked if the Infra team plans to attend the next PTG in Denver. My 
> current position is that it would be good to attend as a team as I think it 
> will give us a good opportunity to work on modernizing config management 
> efforts. But before I go ahead and commit to that it would be helpful to get 
> a rough headcount of who intends to go (if it will just be me then likely 
> don't need to have team space).
> 
> Don't worry if you don't have approval yet or have to sort out other details. 
> Mostly just interested in a "do we intend on being there or not" type of 
> answer.
> 
> More details on the event can be found at 
> http://lists.openstack.org/pipermail/openstack-dev/2018-April/129564.html. 
> Feel free to ask questions if that will help you too.
> 
> Let me know (doesn't have to be to the list if you aren't comfortable with 
> that) and thanks!
> 
Intend on being there (pending travel approval)

-Paul

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Stop supporting bindep-fallback.txt moving forward

[Jeremy Stanley]

On 2018-04-20 12:31:24 -0400 (-0400), Paul Belanger wrote:
[...]
> That is fine, if we want to do the mass migration to bionic first,
> then start looking at which projects are still using
> bindep-fallback.txt is fine with me.
> 
> I just wanted to highlight I think it is time we start pushing a
> little harder on projects to stop using this logic and start
> managing bindep.txt themself.

Yep, this is something I _completely_ agree with. We could even
start with a deprecation warning in the fallback path so it starts
showing up more clearly in the job logs too.
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Stop supporting bindep-fallback.txt moving forward

[Paul Belanger]

On Fri, Apr 20, 2018 at 09:13:17AM -0700, Clark Boylan wrote:
> On Fri, Apr 20, 2018, at 9:01 AM, Jeremy Stanley wrote:
> > On 2018-04-19 19:15:18 -0400 (-0400), Paul Belanger wrote:
> > [...]
> > > today ubuntu-bionic does seem to pass properly with
> > > bindep-fallback.txt, but perhaps we prime it with a bad package on
> > > purpose to force the issue. As clarkb points out, the downside to
> > > this it does make it harder for projects to be flipped to
> > > ubuntu-bionic.
> > [...]
> > 
> > My main concern is that this seems sort of at odds with how we
> > discussed simply forcing all PTI jobs from ubuntu-xenial to
> > ubuntu-bionic on master branches rather than giving projects the
> > option to transition on their own timelines (which worked out pretty
> > terribly when we tried being flexible with them on the ubuntu-trusty
> > to ubuntu-xenial transition a couple years ago). Adding a forced
> > mass migration to in-repo bindep.txt files at the same moment we
> > also force all the PTI jobs to a new platform will probably result
> > in torches and pitchforks.
> 
> Yup, this was my concern as well. I think the value of not being on older 
> platforms outweighs needing to manage a list of packages for longer. We 
> likely just need to keep pushing on projects to add/update bindep.txt in repo 
> instead. We can run a logstash query against job-output.txt looking for 
> output of using the fallback file and nicely remind projects if they show up 
> on that list.
> 
That is fine, if we want to do the mass migration to bionic first, then start
looking at which projects are still using bindep-fallback.txt is fine with me.

I just wanted to highlight I think it is time we start pushing a little harder
on projects to stop using this logic and start managing bindep.txt themself.

-Paul

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Stop supporting bindep-fallback.txt moving forward

[Clark Boylan]

On Fri, Apr 20, 2018, at 9:01 AM, Jeremy Stanley wrote:
> On 2018-04-19 19:15:18 -0400 (-0400), Paul Belanger wrote:
> [...]
> > today ubuntu-bionic does seem to pass properly with
> > bindep-fallback.txt, but perhaps we prime it with a bad package on
> > purpose to force the issue. As clarkb points out, the downside to
> > this it does make it harder for projects to be flipped to
> > ubuntu-bionic.
> [...]
> 
> My main concern is that this seems sort of at odds with how we
> discussed simply forcing all PTI jobs from ubuntu-xenial to
> ubuntu-bionic on master branches rather than giving projects the
> option to transition on their own timelines (which worked out pretty
> terribly when we tried being flexible with them on the ubuntu-trusty
> to ubuntu-xenial transition a couple years ago). Adding a forced
> mass migration to in-repo bindep.txt files at the same moment we
> also force all the PTI jobs to a new platform will probably result
> in torches and pitchforks.

Yup, this was my concern as well. I think the value of not being on older 
platforms outweighs needing to manage a list of packages for longer. We likely 
just need to keep pushing on projects to add/update bindep.txt in repo instead. 
We can run a logstash query against job-output.txt looking for output of using 
the fallback file and nicely remind projects if they show up on that list.

Clark

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Stop supporting bindep-fallback.txt moving forward

[Jeremy Stanley]

On 2018-04-19 19:15:18 -0400 (-0400), Paul Belanger wrote:
[...]
> today ubuntu-bionic does seem to pass properly with
> bindep-fallback.txt, but perhaps we prime it with a bad package on
> purpose to force the issue. As clarkb points out, the downside to
> this it does make it harder for projects to be flipped to
> ubuntu-bionic.
[...]

My main concern is that this seems sort of at odds with how we
discussed simply forcing all PTI jobs from ubuntu-xenial to
ubuntu-bionic on master branches rather than giving projects the
option to transition on their own timelines (which worked out pretty
terribly when we tried being flexible with them on the ubuntu-trusty
to ubuntu-xenial transition a couple years ago). Adding a forced
mass migration to in-repo bindep.txt files at the same moment we
also force all the PTI jobs to a new platform will probably result
in torches and pitchforks.
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Stop supporting bindep-fallback.txt moving forward

[Andreas Jaeger]

On 2018-04-20 16:05, Paul Belanger wrote:
> On Fri, Apr 20, 2018 at 09:07:25AM +0200, Andreas Jaeger wrote:
>> On 2018-04-20 01:15, Paul Belanger wrote:
>>> Greetings,
>>>
>>> I'd like to propose we hard freeze changes to bindep-fallback.txt[1] and 
>>> push
>>> projects to start using a local bindep.txt file.
>>>
>>> This would mean, moving forward with ubuntu-bionic, if a project was still
>>> depending on bindep-fallback.txt, their jobs may raise a syntax error.
>>>
>>> In fact, today ubuntu-bionic does seem to pass properly with
>>> bindep-fallback.txt, but perhaps we prime it with a bad package on purpose 
>>> to
>>> force the issue. As clarkb points out, the downside to this it does make it
>>> harder for projects to be flipped to ubuntu-bionic.  It is possible we could
>>> also prime gerrit patches for projects that are missing bindep.txt to help 
>>> push
>>> this effort along.
>>>
>>> Thoughts?
>>>
>>> [1] 
>>> http://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/elements/bindep-fallback.txt
>>
>> This might break all stable branches as well. Pushing those changes in
>> is a huge effort ;( Is that worth it?
>>
> I wouldn't expect stable branches to be running bionic, unless I am missing
> something obvious.

How do you want to change the set up tox jobs, especially python27,
sphinx-docs, and python35?

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Stop supporting bindep-fallback.txt moving forward

[Paul Belanger]

On Fri, Apr 20, 2018 at 09:07:25AM +0200, Andreas Jaeger wrote:
> On 2018-04-20 01:15, Paul Belanger wrote:
> > Greetings,
> > 
> > I'd like to propose we hard freeze changes to bindep-fallback.txt[1] and 
> > push
> > projects to start using a local bindep.txt file.
> > 
> > This would mean, moving forward with ubuntu-bionic, if a project was still
> > depending on bindep-fallback.txt, their jobs may raise a syntax error.
> > 
> > In fact, today ubuntu-bionic does seem to pass properly with
> > bindep-fallback.txt, but perhaps we prime it with a bad package on purpose 
> > to
> > force the issue. As clarkb points out, the downside to this it does make it
> > harder for projects to be flipped to ubuntu-bionic.  It is possible we could
> > also prime gerrit patches for projects that are missing bindep.txt to help 
> > push
> > this effort along.
> > 
> > Thoughts?
> > 
> > [1] 
> > http://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/elements/bindep-fallback.txt
> 
> This might break all stable branches as well. Pushing those changes in
> is a huge effort ;( Is that worth it?
> 
I wouldn't expect stable branches to be running bionic, unless I am missing
something obvious.

> 
> Andreas
> -- 
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>HRB 21284 (AG Nürnberg)
> GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Stop supporting bindep-fallback.txt moving forward

[Andreas Jaeger]

On 2018-04-20 01:15, Paul Belanger wrote:
> Greetings,
> 
> I'd like to propose we hard freeze changes to bindep-fallback.txt[1] and push
> projects to start using a local bindep.txt file.
> 
> This would mean, moving forward with ubuntu-bionic, if a project was still
> depending on bindep-fallback.txt, their jobs may raise a syntax error.
> 
> In fact, today ubuntu-bionic does seem to pass properly with
> bindep-fallback.txt, but perhaps we prime it with a bad package on purpose to
> force the issue. As clarkb points out, the downside to this it does make it
> harder for projects to be flipped to ubuntu-bionic.  It is possible we could
> also prime gerrit patches for projects that are missing bindep.txt to help 
> push
> this effort along.
> 
> Thoughts?
> 
> [1] 
> http://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/elements/bindep-fallback.txt

This might break all stable branches as well. Pushing those changes in
is a huge effort ;( Is that worth it?


Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra