Re: [openstack-dev] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL
On 2017-09-24 12:48:41 -0400 (-0400), Paul Belanger wrote: [...] > I just noticed our DIB image git cache is still referencing old > branches we have EOL'd. This is because we haven't deleted the > cache in some time. The fact that the cache needs manual cleaning is a bug, in my opinion. It would be good to figure out whether it can be pruned at every update, and whether there's maybe just a feature of DIB's source repositories functionality we're missing turning on to make that happen. Otherwise maybe we can prune unreachable refs and nonexistent remote heads periodically via cron? > I think we could update the EOL docs to have an infra-root make > sure we do this, after all branches have been EOL'd in gerrit. > Unless there is a better way to do this using git over manually > deleting the cache on our nodepool-builder servers. Yeah, while it'll do in the short term it strikes me as more of a workaround than a proper solution. -- Jeremy Stanley signature.asc Description: Digital 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] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL
On Wed, Sep 20, 2017 at 11:26:46AM -0400, Tony Breeds wrote: > On Wed, Sep 20, 2017 at 12:56:07PM +0200, Andreas Jaeger wrote: > > > So, for fuel we have stable/7.0 etc - what are the plans for these? Can > > we retire them as well? > > > > Those are even older AFAIK, > > As discussed on IRC, when I started this I needed to start with > something small and simple, so I picked the series based branches. > > I do intend to get look at the older numeric stable branches but I doubt > there is enough time for real community consultation befoer the zuulv3 > migration. > > Yours Tony. Hijacking thread for branch EOL things. I just noticed our DIB image git cache is still referencing old branches we have EOL'd. This is because we haven't deleted the cache in some time. I think we could update the EOL docs to have an infra-root make sure we do this, after all branches have been EOL'd in gerrit. Unless there is a better way to do this using git over manually deleting the cache on our nodepool-builder servers. -Paul __ 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] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL
On Wed, Sep 20, 2017 at 12:56:07PM +0200, Andreas Jaeger wrote: > So, for fuel we have stable/7.0 etc - what are the plans for these? Can > we retire them as well? > > Those are even older AFAIK, As discussed on IRC, when I started this I needed to start with something small and simple, so I picked the series based branches. I do intend to get look at the older numeric stable branches but I doubt there is enough time for real community consultation befoer the zuulv3 migration. 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] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL
On 2017-08-24 05:14, Tony Breeds wrote:
> Hello all,
> We have a number of old stable/* branches hanging around and I'd
> like to mark anything <= stable/mitaka as EOL. I've highlighted a few
> projects on the subject line:
>
> QA: Are the older branches of grenade safe to go? IIUC we don't use
> them as we don't do grenade testing on $oldest stable branch
> group-based-policy: In the past you've requested your old branches stay
> around Do you still need this? Is there value in
> the *all* staying active?
> zaqar: I see that liberty was EOL and then reactivated do you still need
>liberty2?
> packaging_deb: As these repos have the $project origin using the
>standard series-eol tag doesn't make sense for exaxple
>deb-nova gets a mitaka-eol from the nova repo. So I've
>picked mitaka-eol-dpkg.
> fuel, networking-*: There are several entries for these projects groups
> so I'm calling them out here for attention.
>
> I'm proposing we do this removal during the PTG. Once we've done the
> series based branches we can look at old versioned releases like
> stable/16.04 etc.
So, for fuel we have stable/7.0 etc - what are the plans for these? Can
we retire them as well?
Those are even older AFAIK,
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 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] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL
Hello Tony,Thanks for the heads-up!Responding for the 'networking-bigswitch' plugin - could we retain mitaka and upwards for this project please? We have a controller release which supports mitaka - so we would like to keep it for any patch fixes in the near future.We're good to remove anything <= liberty :)Also, let me know if this requires any action from my end.Thanks again!Adityavia telegram On Aug 29 2017, at 2:33 pm, Sumit Naiksatam wrote: Hi Tony, Thanks for reaching out. With regards to “group-based-policy”, branches < mitaka (meaning Liberty or older) can be EOL’ed. We would still like to have the stable/mitaka branches for a little more time if that’s possible. This applies to the repos: group-based-policy group-based-policy-automation group-based-policy-ui python-group-based-policy-client Thanks, ~Sumit. On Wed, Aug 23, 2017 at 8:14 PM, Tony Breeds wrote: > Hello all, > We have a number of old stable/* branches hanging around and I'd > like to mark anything <= stable/mitaka as EOL. I've highlighted a few > projects on the subject line: > > QA: Are the older branches of grenade safe to go? IIUC we don't use > them as we don't do grenade testing on $oldest stable branch > group-based-policy: In the past you've requested your old branches stay > around Do you still need this? Is there value in > the *all* staying active? > zaqar: I see that liberty was EOL and then reactivated do you still need >liberty2? > packaging_deb: As these repos have the $project origin using the >standard series-eol tag doesn't make sense for exaxple >deb-nova gets a mitaka-eol from the nova repo. So I've >picked mitaka-eol-dpkg. > fuel, networking-*: There are several entries for these projects groups > so I'm calling them out here for attention. > > I'm proposing we do this removal during the PTG. Once we've done the > series based branches we can look at old versioned releases like > stable/16.04 etc. > > It's hard to present the data in a clear way so given infra will be the > ultimate actioners of this list I present this as a shell script: > > --- > eol-branch.sh -- stable/essex essex-eol openstack/anvil > eol-branch.sh -- stable/folsom folsom-eol openstack/anvil > eol-branch.sh -- stable/grizzly grizzly-eol openstack/anvil > eol-branch.sh -- stable/havana havana-eol openstack/openstack > eol-branch.sh -- stable/icehouse icehouse-eol \ > openstack/astara openstack/networking-brocade \ > openstack/networking-cisco openstack/networking-mlnx \ > openstack/networking-odl openstack/networking-plumgrid \ > openstack/nova-solver-scheduler \ > openstack/sahara-image-elements openstack/tricircle \ > openstack/trio2o openstack/vmware-nsx > eol-branch.sh -- stable/icehouse icehouse-eol-dpkg \ > openstack/deb-networking-cisco \ > openstack/deb-networking-mlnx openstack/deb-networking-odl > eol-branch.sh -- stable/juno juno-eol \ > openstack/astara openstack/astara-appliance \ > openstack/astara-horizon openstack/astara-neutron \ > openstack/group-based-policy \ > openstack/group-based-policy-automation \ > openstack/group-based-policy-ui openstack/mistral \ > openstack/mistral-dashboard openstack/mistral-extra \ > openstack/networking-bigswitch \ > openstack/networking-brocade openstack/networking-cisco \ > openstack/networking-mlnx openstack/networking-odl \ > openstack/networking-plumgrid \ > openstack/nova-solver-scheduler \ > openstack/openstack-resource-agents \ > openstack/powervc-driver openstack/proliantutils \ > openstack/puppet-n1k-vsm openstack/puppet-vswitch \ > openstack/python-group-based-policy-client \ > openstack/python-mistralclient \ > openstack/python-muranoclient openstack/vmware-nsx > eol-branch.sh -- stable/juno juno-eol-dpkg \ > openstack/deb-mistral openstack/deb-networking-cisco \ > openstack/deb-networking-mlnx openstack/deb-networking-odl \ > openstack/deb-python-mistralclient \ > openstack/deb-python-muranoclient \ > openstack/deb-python-proliantutils > eol-branch.sh -- stable/kilo kilo-eol \ > openstack-dev/grenade openstack/murano-apps \ > openstack/networking-h3c openstack/requirements > eol-branch.sh -- stable/kilo kilo-eol1 \ > openstack/group-based-policy \ > openstack/group-based-policy-automation \ >
Re: [openstack-dev] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL
Hi Tony, Thanks for reaching out. With regards to “group-based-policy”, branches < mitaka (meaning Liberty or older) can be EOL’ed. We would still like to have the stable/mitaka branches for a little more time if that’s possible. This applies to the repos: group-based-policy group-based-policy-automation group-based-policy-ui python-group-based-policy-client Thanks, ~Sumit. On Wed, Aug 23, 2017 at 8:14 PM, Tony Breeds wrote: > Hello all, > We have a number of old stable/* branches hanging around and I'd > like to mark anything <= stable/mitaka as EOL. I've highlighted a few > projects on the subject line: > > QA: Are the older branches of grenade safe to go? IIUC we don't use > them as we don't do grenade testing on $oldest stable branch > group-based-policy: In the past you've requested your old branches stay > around Do you still need this? Is there value in > the *all* staying active? > zaqar: I see that liberty was EOL and then reactivated do you still need >liberty2? > packaging_deb: As these repos have the $project origin using the >standard series-eol tag doesn't make sense for exaxple >deb-nova gets a mitaka-eol from the nova repo. So I've >picked mitaka-eol-dpkg. > fuel, networking-*: There are several entries for these projects groups > so I'm calling them out here for attention. > > I'm proposing we do this removal during the PTG. Once we've done the > series based branches we can look at old versioned releases like > stable/16.04 etc. > > It's hard to present the data in a clear way so given infra will be the > ultimate actioners of this list I present this as a shell script: > > --- > eol-branch.sh -- stable/essex essex-eol openstack/anvil > eol-branch.sh -- stable/folsom folsom-eol openstack/anvil > eol-branch.sh -- stable/grizzly grizzly-eol openstack/anvil > eol-branch.sh -- stable/havana havana-eol openstack/openstack > eol-branch.sh -- stable/icehouse icehouse-eol \ > openstack/astara openstack/networking-brocade \ > openstack/networking-cisco openstack/networking-mlnx \ > openstack/networking-odl openstack/networking-plumgrid \ > openstack/nova-solver-scheduler \ > openstack/sahara-image-elements openstack/tricircle \ > openstack/trio2o openstack/vmware-nsx > eol-branch.sh -- stable/icehouse icehouse-eol-dpkg \ > openstack/deb-networking-cisco \ > openstack/deb-networking-mlnx openstack/deb-networking-odl > eol-branch.sh -- stable/juno juno-eol \ > openstack/astara openstack/astara-appliance \ > openstack/astara-horizon openstack/astara-neutron \ > openstack/group-based-policy \ > openstack/group-based-policy-automation \ > openstack/group-based-policy-ui openstack/mistral \ > openstack/mistral-dashboard openstack/mistral-extra \ > openstack/networking-bigswitch \ > openstack/networking-brocade openstack/networking-cisco \ > openstack/networking-mlnx openstack/networking-odl \ > openstack/networking-plumgrid \ > openstack/nova-solver-scheduler \ > openstack/openstack-resource-agents \ > openstack/powervc-driver openstack/proliantutils \ > openstack/puppet-n1k-vsm openstack/puppet-vswitch \ > openstack/python-group-based-policy-client \ > openstack/python-mistralclient \ > openstack/python-muranoclient openstack/vmware-nsx > eol-branch.sh -- stable/juno juno-eol-dpkg \ > openstack/deb-mistral openstack/deb-networking-cisco \ > openstack/deb-networking-mlnx openstack/deb-networking-odl \ > openstack/deb-python-mistralclient \ > openstack/deb-python-muranoclient \ > openstack/deb-python-proliantutils > eol-branch.sh -- stable/kilo kilo-eol \ > openstack-dev/grenade openstack/murano-apps \ > openstack/networking-h3c openstack/requirements > eol-branch.sh -- stable/kilo kilo-eol1 \ > openstack/group-based-policy \ > openstack/group-based-policy-automation \ > openstack/group-based-policy-ui \ > openstack/python-group-based-policy-client > eol-branch.sh -- stable/kilo_v2 kilo_v2-eol openstack/networking-bigswitch > eol-branch.sh -- stable/liberty liberty-eol \ > openstack-dev/grenade openstack/ceilometer-powervm \ > openstack/ceilometer-zvm openstack/ceilometermiddleware \ > openstack/fuel-plugin-calico openstack/group-based-policy \ > openstack/group-based-policy-automation \ >
Re: [openstack-dev] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL
Hi Tony, TBH, I have no idea what happened for Zaqar's Liberty. So I don't think we need a liberty2. Thanks. On 24/08/17 15:14, Tony Breeds wrote: > Hello all, > We have a number of old stable/* branches hanging around and I'd > like to mark anything <= stable/mitaka as EOL. I've highlighted a few > projects on the subject line: > > QA: Are the older branches of grenade safe to go? IIUC we don't use > them as we don't do grenade testing on $oldest stable branch > group-based-policy: In the past you've requested your old branches stay > around Do you still need this? Is there value in > the *all* staying active? > zaqar: I see that liberty was EOL and then reactivated do you still need >liberty2? > packaging_deb: As these repos have the $project origin using the >standard series-eol tag doesn't make sense for exaxple >deb-nova gets a mitaka-eol from the nova repo. So I've >picked mitaka-eol-dpkg. > fuel, networking-*: There are several entries for these projects groups > so I'm calling them out here for attention. > > I'm proposing we do this removal during the PTG. Once we've done the > series based branches we can look at old versioned releases like > stable/16.04 etc. > > It's hard to present the data in a clear way so given infra will be the > ultimate actioners of this list I present this as a shell script: > > --- > eol-branch.sh -- stable/essex essex-eol openstack/anvil > eol-branch.sh -- stable/folsom folsom-eol openstack/anvil > eol-branch.sh -- stable/grizzly grizzly-eol openstack/anvil > eol-branch.sh -- stable/havana havana-eol openstack/openstack > eol-branch.sh -- stable/icehouse icehouse-eol \ > openstack/astara openstack/networking-brocade \ > openstack/networking-cisco openstack/networking-mlnx \ > openstack/networking-odl openstack/networking-plumgrid \ > openstack/nova-solver-scheduler \ > openstack/sahara-image-elements openstack/tricircle \ > openstack/trio2o openstack/vmware-nsx > eol-branch.sh -- stable/icehouse icehouse-eol-dpkg \ > openstack/deb-networking-cisco \ > openstack/deb-networking-mlnx openstack/deb-networking-odl > eol-branch.sh -- stable/juno juno-eol \ > openstack/astara openstack/astara-appliance \ > openstack/astara-horizon openstack/astara-neutron \ > openstack/group-based-policy \ > openstack/group-based-policy-automation \ > openstack/group-based-policy-ui openstack/mistral \ > openstack/mistral-dashboard openstack/mistral-extra \ > openstack/networking-bigswitch \ > openstack/networking-brocade openstack/networking-cisco \ > openstack/networking-mlnx openstack/networking-odl \ > openstack/networking-plumgrid \ > openstack/nova-solver-scheduler \ > openstack/openstack-resource-agents \ > openstack/powervc-driver openstack/proliantutils \ > openstack/puppet-n1k-vsm openstack/puppet-vswitch \ > openstack/python-group-based-policy-client \ > openstack/python-mistralclient \ > openstack/python-muranoclient openstack/vmware-nsx > eol-branch.sh -- stable/juno juno-eol-dpkg \ > openstack/deb-mistral openstack/deb-networking-cisco \ > openstack/deb-networking-mlnx openstack/deb-networking-odl \ > openstack/deb-python-mistralclient \ > openstack/deb-python-muranoclient \ > openstack/deb-python-proliantutils > eol-branch.sh -- stable/kilo kilo-eol \ > openstack-dev/grenade openstack/murano-apps \ > openstack/networking-h3c openstack/requirements > eol-branch.sh -- stable/kilo kilo-eol1 \ > openstack/group-based-policy \ > openstack/group-based-policy-automation \ > openstack/group-based-policy-ui \ > openstack/python-group-based-policy-client > eol-branch.sh -- stable/kilo_v2 kilo_v2-eol openstack/networking-bigswitch > eol-branch.sh -- stable/liberty liberty-eol \ > openstack-dev/grenade openstack/ceilometer-powervm \ > openstack/ceilometer-zvm openstack/ceilometermiddleware \ > openstack/fuel-plugin-calico openstack/group-based-policy \ > openstack/group-based-policy-automation \ > openstack/group-based-policy-ui openstack/mistral-extra \ > openstack/networking-infoblox openstack/networking-powervm \ > openstack/networking-zvm openstack/nova-powervm \ > openstack/nova-zvm-virt-driver \ > ope
[openstack-dev] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL
Hello all, We have a number of old stable/* branches hanging around and I'd like to mark anything <= stable/mitaka as EOL. I've highlighted a few projects on the subject line: QA: Are the older branches of grenade safe to go? IIUC we don't use them as we don't do grenade testing on $oldest stable branch group-based-policy: In the past you've requested your old branches stay around Do you still need this? Is there value in the *all* staying active? zaqar: I see that liberty was EOL and then reactivated do you still need liberty2? packaging_deb: As these repos have the $project origin using the standard series-eol tag doesn't make sense for exaxple deb-nova gets a mitaka-eol from the nova repo. So I've picked mitaka-eol-dpkg. fuel, networking-*: There are several entries for these projects groups so I'm calling them out here for attention. I'm proposing we do this removal during the PTG. Once we've done the series based branches we can look at old versioned releases like stable/16.04 etc. It's hard to present the data in a clear way so given infra will be the ultimate actioners of this list I present this as a shell script: --- eol-branch.sh -- stable/essex essex-eol openstack/anvil eol-branch.sh -- stable/folsom folsom-eol openstack/anvil eol-branch.sh -- stable/grizzly grizzly-eol openstack/anvil eol-branch.sh -- stable/havana havana-eol openstack/openstack eol-branch.sh -- stable/icehouse icehouse-eol \ openstack/astara openstack/networking-brocade \ openstack/networking-cisco openstack/networking-mlnx \ openstack/networking-odl openstack/networking-plumgrid \ openstack/nova-solver-scheduler \ openstack/sahara-image-elements openstack/tricircle \ openstack/trio2o openstack/vmware-nsx eol-branch.sh -- stable/icehouse icehouse-eol-dpkg \ openstack/deb-networking-cisco \ openstack/deb-networking-mlnx openstack/deb-networking-odl eol-branch.sh -- stable/juno juno-eol \ openstack/astara openstack/astara-appliance \ openstack/astara-horizon openstack/astara-neutron \ openstack/group-based-policy \ openstack/group-based-policy-automation \ openstack/group-based-policy-ui openstack/mistral \ openstack/mistral-dashboard openstack/mistral-extra \ openstack/networking-bigswitch \ openstack/networking-brocade openstack/networking-cisco \ openstack/networking-mlnx openstack/networking-odl \ openstack/networking-plumgrid \ openstack/nova-solver-scheduler \ openstack/openstack-resource-agents \ openstack/powervc-driver openstack/proliantutils \ openstack/puppet-n1k-vsm openstack/puppet-vswitch \ openstack/python-group-based-policy-client \ openstack/python-mistralclient \ openstack/python-muranoclient openstack/vmware-nsx eol-branch.sh -- stable/juno juno-eol-dpkg \ openstack/deb-mistral openstack/deb-networking-cisco \ openstack/deb-networking-mlnx openstack/deb-networking-odl \ openstack/deb-python-mistralclient \ openstack/deb-python-muranoclient \ openstack/deb-python-proliantutils eol-branch.sh -- stable/kilo kilo-eol \ openstack-dev/grenade openstack/murano-apps \ openstack/networking-h3c openstack/requirements eol-branch.sh -- stable/kilo kilo-eol1 \ openstack/group-based-policy \ openstack/group-based-policy-automation \ openstack/group-based-policy-ui \ openstack/python-group-based-policy-client eol-branch.sh -- stable/kilo_v2 kilo_v2-eol openstack/networking-bigswitch eol-branch.sh -- stable/liberty liberty-eol \ openstack-dev/grenade openstack/ceilometer-powervm \ openstack/ceilometer-zvm openstack/ceilometermiddleware \ openstack/fuel-plugin-calico openstack/group-based-policy \ openstack/group-based-policy-automation \ openstack/group-based-policy-ui openstack/mistral-extra \ openstack/networking-infoblox openstack/networking-powervm \ openstack/networking-zvm openstack/nova-powervm \ openstack/nova-zvm-virt-driver \ openstack/python-group-based-policy-client \ openstack/requirements openstack/swiftonhpss eol-branch.sh -- stable/liberty liberty-eol-dpkg \ openstack/deb-aodh openstack/deb-barbican \ openstack/deb-ceilometer \ openstack/deb-ceilometermiddleware op
