Re: [openstack-dev] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked

2018-09-09 Thread Tony Breeds
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

2018-09-09 Thread Julien Danjou
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


[openstack-dev] [Kuryr] Meeting cancelled

2018-09-09 Thread Daniel Mellado Area
Due to folks being at the Denver PTG (including myself virtually at  odd
hours x) we'll be cancelling today's weekly meeting.

Best!

Daniel
__
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] [k8s] SIG-K8s PTG Meetings, Monday September 10, 2018

2018-09-09 Thread Chris Hoge
SIG-K8s has space reserved in Ballroom A for all of Monday, September 10
at the PTG. We will begin at 9:00 with a planning session, similar to that
in Dublin, where we will organize topics and times for the remainder of
the day.

The planning etherpad can be found here: 
https://etherpad.openstack.org/p/sig-k8s-2018-denver-ptg
The link to the Dublin planning etherpad: 
https://etherpad.openstack.org/p/sig-k8s-2018-dublin-ptg

Thanks,
Chris


__
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] [Release-job-failures] Tag of openstack/python-neutronclient failed

2018-09-09 Thread Tony Breeds
On Mon, Sep 10, 2018 at 05:13:35AM +, z...@openstack.org wrote:
> Build failed.
> 
> - publish-openstack-releasenotes 
> http://logs.openstack.org/c8/c89ca61fdcaf603a10750b289228b7f9a3597290/tag/publish-openstack-releasenotes/fbbd0fa/
>  : FAILURE in 4m 03s

I'm not sure what caused this to fail and my attempts to reproduce it
haven't been fruitful :(

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

2018-09-09 Thread Tony Breeds
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

2018-09-09 Thread Ian Wienand

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] [election] [tc] TC Candidacy

2018-09-09 Thread Kristi Nikolla
Thanks for the question Matt,

I have to agree that that is not a good use of time, which is why I’m really 
interested in the Constellations initiative. There doesn’t have to be a very 
specifically defined “what OpenStack is” answer, but instead we can focus on 
multiple answers based on the features we offer and the multitude of problems 
that we solve. Furthermore, I think that constellations will help weaken the 
silos between teams by increasing cross-project collaboration and integration 
towards a common goal. Ultimately, to me, what OpenStack is, first and 
foremost, is a community.

Additionally, I would like to be much more involved with the process of 
welcoming and mentoring new contributors, and the various groups formed around 
that. Working in academia, gives me access to a large pool of students, 
especially during the cloud computing course that we offer in two universities 
of the Boston area. Many of our previous alums (me included) end up becoming 
regular contributors and continuing their work in OpenStack and other open 
source communities.

Ultimately, this list isn’t exclusive and I’d love to hear your and other 
people's opinions about what you think the I should focus on.

Kristi Nikolla

> On Sep 7, 2018, at 7:26 AM, Matt Riedemann  wrote:
> 
> On 9/5/2018 1:20 PM, Kristi Nikolla wrote:
>> I’m really excited to have the opportunity to take part in the discussion 
>> with
>> regards to the technical vision for OpenStack. Regardless of election 
>> outcome,
>> this is the first step towards a larger involvement from me in the important
>> discussions (no more shying away from the important mailing list threads.)
> 
> I'm not trying to pick on you Kristi, but personally I'm tired of the TC 
> vision question that's been going on for years now and would like the people 
> I vote for to spend less time talking about OpenStack and what it is or what 
> it isn't (because that changes based on the person you talk to and on what 
> day you ask them), and spend more time figuring out how to move cross-project 
> initiatives forward. So whether or not OpenStack is a toolkit for 
> private/public/edge clouds, or a product, or something else, there are likely 
> common themes within OpenStack that we can generally agree on across projects 
> and need people to work on them, rather than just talk about doing them. Are 
> there specific cross-project initiatives you are interested in working on?
> 
> -- 
> 
> 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


__
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

2018-09-09 Thread Tony Breeds
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] [os-upstream-institute] Team lunch at the PTG next week - ACTION NEEDED

2018-09-09 Thread Ghanshyam Mann
I am in for Wed lunch meeting. 

-gmann

  On Sat, 08 Sep 2018 07:30:53 +0900 Ildiko Vancsa 
 wrote  
 > Hi Training Team,
 > 
 > As a couple of us will be at the PTG next week it would be great to get 
 > together one of the days maybe for lunch.
 > 
 > Wednesday would work the best for Kendall and me, but we can look into other 
 > days as well if it would not work for the majority of people around.
 > 
 > So my questions would be:
 > 
 > * Are you interested in getting together one of the lunch slots during next 
 > week?
 > 
 > * Would Wednesday work for you or do you have another preference?
 > 
 > Please drop a response to this thread and we will figure it out by Monday or 
 > early next week based on the responses.
 > 
 > Thanks,
 > Ildikó
 > (IRC: ildikov)
 > 
 > 
 > 
 > __
 > 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] [tempest][CI][nova compute] Skipping non-compute-driver tests

2018-09-09 Thread Ghanshyam Mann



  On Sat, 08 Sep 2018 08:28:06 +0900 Matt Riedemann  
wrote  
 > On 9/7/2018 10:25 AM, William M Edmonds wrote:
 > > The concern that I have with whitelisting in a given CI is that it has 
 > > to be done independently in every compute driver CI. So while I agree 
 > > that it won't be easy to maintain tagging for compute driver on the 
 > > tempest side, at least that's one place / easier than doing it in every 
 > > driver CI. When anyone figures out that an change is needed, all of the 
 > > CIs would benefit together if there is a shared solution.
 > 
 > How about storing the compute-driver specific whitelist in a common 
 > location? I'm not sure if that would be tempest, nova or somewhere else.

Yeah, Tempest would not fit as best location for such tagging or whitelist. I 
think nova may be better choice if nothing else.

 > 
 > -- 
 > 
 > 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
 > 



__
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] [manila] initial schedule for PTG

2018-09-09 Thread Tom Barron
Manila meets Monday and Tuesday this week in Steamboat [1] from 9am to 
5pm UTC-0600.


The team came up with a rich set of discussion topics and I've 
arranged the manila PTG etherpad [2] so that they are all included in 
a schedule for the two days.  We'll need to make adjustments if some 
topics go fast and others need more time, but please take a 
preliminary look now and let me know if you see anything that you 
think will need more time or that is scheduled for a bad time.


I tried to start with stuff like backlog, cross-project goals, etc. 
and Stein deadlines so that we have a framework for decisions about 
what work we can fit into the Stein cycle.


Also, we have remote attendees participating, I think all to the east 
of Denver, so I tried to shift topics known to be of interest to those 
folks earlier in the day.


-- Tom Barron (tbarron)

[1] https://www.openstack.org/assets/ptg/Denver-map.pdf

[2] https://etherpad.openstack.org/p/manila-ptg-planning-denver-2018


__
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] [goals][python3][cinder] starting zuul migration

2018-09-09 Thread Doug Hellmann
I apparently missed the email Sean sent a while back saying it was OK to
start the migration, but we talked today and so I've submitted the
patches to move cinder's zuul settings. Here's the list.

Doug

+--+-+---+
| Subject  | Repo   
 | Branch|
+--+-+---+
| remove job settings for cinder repositories  | openstack-infra/project-config 
 | master|
| import zuul job settings from project-config | openstack/cinder   
 | master|
| switch documentation job to new PTI  | openstack/cinder   
 | master|
| add python 3.6 unit test job | openstack/cinder   
 | master|
| import zuul job settings from project-config | openstack/cinder   
 | stable/ocata  |
| import zuul job settings from project-config | openstack/cinder   
 | stable/pike   |
| import zuul job settings from project-config | openstack/cinder   
 | stable/queens |
| import zuul job settings from project-config | openstack/cinder   
 | stable/rocky  |
| import zuul job settings from project-config | openstack/cinder-specs 
 | master|
| import zuul job settings from project-config | 
openstack/cinder-tempest-plugin | master|
| import zuul job settings from project-config | openstack/os-brick 
 | master|
| switch documentation job to new PTI  | openstack/os-brick 
 | master|
| add python 3.6 unit test job | openstack/os-brick 
 | master|
| add lib-forward-testing-python3 test job | openstack/os-brick 
 | master|
| import zuul job settings from project-config | openstack/os-brick 
 | stable/ocata  |
| import zuul job settings from project-config | openstack/os-brick 
 | stable/pike   |
| import zuul job settings from project-config | openstack/os-brick 
 | stable/queens |
| import zuul job settings from project-config | openstack/os-brick 
 | stable/rocky  |
| import zuul job settings from project-config | 
openstack/python-brick-cinderclient-ext | master|
| switch documentation job to new PTI  | 
openstack/python-brick-cinderclient-ext | master|
| add python 3.6 unit test job | 
openstack/python-brick-cinderclient-ext | master|
| import zuul job settings from project-config | 
openstack/python-brick-cinderclient-ext | stable/ocata  |
| import zuul job settings from project-config | 
openstack/python-brick-cinderclient-ext | stable/pike   |
| import zuul job settings from project-config | 
openstack/python-brick-cinderclient-ext | stable/queens |
| import zuul job settings from project-config | 
openstack/python-brick-cinderclient-ext | stable/rocky  |
| import zuul job settings from project-config | openstack/python-cinderclient  
 | master|
| switch documentation job to new PTI  | openstack/python-cinderclient  
 | master|
| add python 3.6 unit test job | openstack/python-cinderclient  
 | master|
| add lib-forward-testing-python3 test job | openstack/python-cinderclient  
 | master|
| import zuul job settings from project-config | openstack/python-cinderclient  
 | stable/ocata  |
| import zuul job settings from project-config | openstack/python-cinderclient  
 | stable/pike   |
| import zuul job settings from project-config | openstack/python-cinderclient  
 | stable/queens |
| import zuul job settings from project-config | openstack/python-cinderclient  
 | stable/rocky  |
+--+-+---+

__
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] [openstack-ansible] ptg schedule

2018-09-09 Thread Mohammed Naser
Hi team:

I've come up with a schedule which includes the general events
happening at the PTG which would be interesting for the OSA team and
contributors.

https://calendar.google.com/calendar?cid=dmV4eGhvc3QuY29tXzgwNmJyb2hpZnNoaGdmY2kzcWdqdDk3aTJzQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20

Please let me know if you have any difficulty accessing that link.
Also, it seems like a very loaded schedule however we're likely going
to have extra time here and there so it's very tentative :)

Thanks and look forward to seeing everyone!

Regards,
Mohammed

-- 
Mohammed Naser — vexxhost
-
D. 514-316-8872
D. 800-910-1726 ext. 200
E. mna...@vexxhost.com
W. http://vexxhost.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


[openstack-dev] [openstack-ansible] no meeting this week

2018-09-09 Thread Mohammed Naser
Hi team:

We won't be conducting a meeting this week because of the PTG,
however, we'll be making an effort to try and allow/bring remote
access to those not at the PTG over this week.

Thanks everyone.

Regards,
Mohammed

__
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