Re: [openstack-dev] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked
On Mon, Sep 10, 2018 at 08:40:28AM +0200, Julien Danjou wrote:
> On Mon, Sep 10 2018, Tony Breeds wrote:
>
> > It looks like in August this was already setup
> > https://review.openstack.org/#/c/591682/
> > So releases going forward will be on pypi.
> >
> > Julien, Do you mind me arranging for at least the following versions to
> > be published to pypi?
> >
> > [tony@thor ceilometer]$ for branch in
> > origin/stable/{ocata,pike,queens,rocky} ; do printf "%-25s: %s\n" $branch
> > "$(git describe --abbrev=0 $branch)" ; done
> > origin/stable/ocata : 8.1.5
> > origin/stable/pike : 9.0.6
> > origin/stable/queens : 10.0.1
> > origin/stable/rocky : 11.0.0
>
> Sure, go ahead!
Thanks!
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] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked
On Mon, Sep 10 2018, Tony Breeds wrote:
> It looks like in August this was already setup
> https://review.openstack.org/#/c/591682/
> So releases going forward will be on pypi.
>
> Julien, Do you mind me arranging for at least the following versions to
> be published to pypi?
>
> [tony@thor ceilometer]$ for branch in origin/stable/{ocata,pike,queens,rocky}
> ; do printf "%-25s: %s\n" $branch "$(git describe --abbrev=0 $branch)" ; done
> origin/stable/ocata : 8.1.5
> origin/stable/pike : 9.0.6
> origin/stable/queens : 10.0.1
> origin/stable/rocky : 11.0.0
Sure, go ahead!
--
Julien Danjou
;; Free Software hacker
;; https://julien.danjou.info
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] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked
On Mon, Sep 10, 2018 at 11:02:06AM +1000, Ian Wienand wrote: > On 09/10/2018 09:39 AM, Tony Breeds wrote: > > Julien, Do you mind me arranging for at least the following versions to > > be published to pypi? > > For this particular case, I think our best approach is to have an > admin manually upload the tar & wheels from tarballs.openstack.org to > pypi. All other options seem to be sub-optimal: > > - if we re-ran the release pipeline, I *think* it would all be >idempotent and the publishing would happen, but there would be >confusing duplicate release emails sent. fungi also points[1] out that we'd re-sign/publish those artefacts which isn't desirable. So I think we're limited to publishing the existing artefacts (preferred) or waiting/making releases from the open branches. Yours Tony. [1] http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2018-09-10.log.html#t2018-09-10T04:16:37 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] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked
On 09/10/2018 09:39 AM, Tony Breeds wrote: Julien, Do you mind me arranging for at least the following versions to be published to pypi? For this particular case, I think our best approach is to have an admin manually upload the tar & wheels from tarballs.openstack.org to pypi. All other options seem to be sub-optimal: - if we re-ran the release pipeline, I *think* it would all be idempotent and the publishing would happen, but there would be confusing duplicate release emails sent. - we could make a special "only-publish" template that avoids notification jobs; switch ceilometer to this, re-run the releases, then switch back. urgh, especially if something goes wrong. - ceilometer could make "no-op" releases on each branch to trigger a fresh release & publish; but releases that essentially do nothing are I imagine an annoyance for users and distributors who track stable branches. It would look like https://test.pypi.org/project/ceilometer/ The pypi hashes will all line up with the .asc files we publish, so we know there's no funny business going on. Thanks, -i __ 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] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked
On Sat, Sep 08, 2018 at 03:21:38PM +1000, Tony Breeds wrote:
> On Fri, Sep 07, 2018 at 11:09:15AM +0200, Julien Danjou wrote:
>
> > You can, I've already said +1 on a review a few weeks ago. :)
>
> Oh great. I'll dig that up and push forward with that side of things if
> you don't mind.
It looks like in August this was already setup
https://review.openstack.org/#/c/591682/
So releases going forward will be on pypi.
Julien, Do you mind me arranging for at least the following versions to
be published to pypi?
[tony@thor ceilometer]$ for branch in origin/stable/{ocata,pike,queens,rocky} ;
do printf "%-25s: %s\n" $branch "$(git describe --abbrev=0 $branch)" ; done
origin/stable/ocata : 8.1.5
origin/stable/pike : 9.0.6
origin/stable/queens : 10.0.1
origin/stable/rocky : 11.0.0
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] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked
On Fri, Sep 07, 2018 at 11:09:15AM +0200, Julien Danjou wrote: > You can, I've already said +1 on a review a few weeks ago. :) Oh great. I'll dig that up and push forward with that side of things if you don't mind. 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] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked
On 18-09-07 11:09:15, Julien Danjou wrote: > On Fri, Sep 07 2018, Tony Breeds wrote: > > > On Thu, Sep 06, 2018 at 01:33:12PM +0300, Michel Peterson wrote: > > > >> I remember that before landing the problematic patch [1] there was some > >> discussion around it. Basically the problem was not n-odl but ceilometer > >> not being in pypi, but we never foresaw this problem. > >> > >> Now that the problem is so critical, the question is how can we, from the > >> n-odl team, help in fixing this? I am open to help in any effort that > >> involves n-odl or any other project. > > > > As other have pointed out we can just ask the Telemetry team (PTL on CC) > > why we can't publish ceilometer to pypi? > > You can, I've already said +1 on a review a few weeks ago. :) > Mind linking? I can't find it. > > https://pypi.org/project/ceilometer/ certainly seems to be the right > > project. > > > > The crux of the code issue is: > > from ceilometer.network.statistics import driver > > > > in networking_odl/ceilometer/network/statistics/opendaylight_v2/driver.py > > > > If this is supposed to be used they way you are how are prjects supposed > > to get the ceilometer code? > > -- Matthew Thode 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] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked
On Fri, Sep 07 2018, Tony Breeds wrote: > On Thu, Sep 06, 2018 at 01:33:12PM +0300, Michel Peterson wrote: > >> I remember that before landing the problematic patch [1] there was some >> discussion around it. Basically the problem was not n-odl but ceilometer >> not being in pypi, but we never foresaw this problem. >> >> Now that the problem is so critical, the question is how can we, from the >> n-odl team, help in fixing this? I am open to help in any effort that >> involves n-odl or any other project. > > As other have pointed out we can just ask the Telemetry team (PTL on CC) > why we can't publish ceilometer to pypi? You can, I've already said +1 on a review a few weeks ago. :) > https://pypi.org/project/ceilometer/ certainly seems to be the right > project. > > The crux of the code issue is: > from ceilometer.network.statistics import driver > > in networking_odl/ceilometer/network/statistics/opendaylight_v2/driver.py > > If this is supposed to be used they way you are how are prjects supposed > to get the ceilometer code? > > > > Yours Tony. > -- Julien Danjou // Free Software hacker // https://julien.danjou.info 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] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked
On Thu, Sep 06, 2018 at 01:33:12PM +0300, Michel Peterson wrote: > I remember that before landing the problematic patch [1] there was some > discussion around it. Basically the problem was not n-odl but ceilometer > not being in pypi, but we never foresaw this problem. > > Now that the problem is so critical, the question is how can we, from the > n-odl team, help in fixing this? I am open to help in any effort that > involves n-odl or any other project. As other have pointed out we can just ask the Telemetry team (PTL on CC) why we can't publish ceilometer to pypi? https://pypi.org/project/ceilometer/ certainly seems to be the right project. The crux of the code issue is: from ceilometer.network.statistics import driver in networking_odl/ceilometer/network/statistics/opendaylight_v2/driver.py If this is supposed to be used they way you are how are prjects supposed to get the ceilometer code? 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
