[openstack-dev] [watcher] Pike-1 release

Hello Watcher contributors, We have just tagged our Pike-1 milestone. All the unfinished BPs and bug fixes have been moved to Pike-2. You can see our progress for Pike-1 at https://launchpad.net/watcher/+milestone/pike-1 Congratulations to all who have contributed to Watcher! If you have any

[openstack-dev] [glance] virtual midcycle April 20

As discussed at today's Glance weekly meeting, we'll hold the virtual midcycle next week on Thursday, April 20. We'll keep it short, just 3 hours from 14:00-17:00 UTC. Please plan ahead and have breakfast/lunch/snacks/dinner ready at your workstation so we can work straight through. Agenda and

[openstack-dev] [all][elections] Voting for the TC Election is now open

Hello All! Voting for the TC Election is now open and will remain open until 23:45 April 20th, 2017 UTC. We are selecting 7 TC members, please rank all candidates in your order of preference. You are eligible to vote if you are a Foundation individual member[1] that also has committed to one of

[openstack-dev] [api-wg] Question about 'OpenStack-API-Version' header

According to the microversion specification [1], the 'OpenStack-API-Version' header is optional. When it is omitted, the server should act as if the minimum supported version was specified. Recently, we have received some complaints from users that for new APIs added, we should state that the

Re: [openstack-dev] [nova] Why don't we unbind ports or terminate volume connections on shelve offload?

On 4/13/2017 6:53 PM, Andrew Laski wrote: On Thu, Apr 13, 2017, at 12:45 PM, Matt Riedemann wrote: This came up in the nova/cinder meeting today, but I can't for the life of me think of why we don't unbind ports or terminate the connection volumes when we shelve offload an instance from a

[openstack-dev] [all] blog post about being PTL in OpenStack

Exceptionally, I'll self-promote a blog post that I wrote about my personal experience of being PTL in OpenStack. http://my1.fr/blog/my-journey-as-an-openstack-ptl/ My hope is to engage some discussion about what our community thinks about this role and how we could bring more leaders in

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Thu, Apr 13, 2017 at 04:48:34PM -0700, Sumit Naiksatam wrote: > Hi Tony, Kindly do not EOL openstack/group-based-policy, we are > maintaining this branch. Done. Tony. signature.asc Description: PGP signature __

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

Hi Tony, I’m not the PTL, but I asked in our channel. You can EOL Chef OpenStack as well. Thanks! -- Best, Samuel Cassiba signature.asc Description: Message signed with OpenPGP __ OpenStack Development Mailing List (not

Re: [openstack-dev] [nova] Why don't we unbind ports or terminate volume connections on shelve offload?

On Thu, Apr 13, 2017, at 12:45 PM, Matt Riedemann wrote: > This came up in the nova/cinder meeting today, but I can't for the life > of me think of why we don't unbind ports or terminate the connection > volumes when we shelve offload an instance from a compute host. > > When you unshelve, if

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

Hi Tony, Kindly do not EOL openstack/group-based-policy, we are maintaining this branch. Thanks, ~Sumit. On Thu, Apr 13, 2017 at 4:40 PM, Tony Breeds wrote: > On Thu, Apr 13, 2017 at 08:20:50AM -0600, Alex Schultz wrote: > >> I would not include puppet-midonet without

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Thu, Apr 13, 2017 at 03:55:56PM +0100, Andy McCrae wrote: > Can the openstack-ansible repository be skipped until other repo's are > EOL'd, please? The reason is that we'd like the mitaka-eol tag for OSA to > point to the mitaka-eol tag of the appropriate upstream projects, in order > for that

[openstack-dev] [keystone][horizon] weekly meeting

Happy Thursday folks, Rob and I have noticed that the weekly attendance for the Keystone/Horizon [0] meeting has dropped significantly in the last month or two. We contemplated changing the frequency of this meeting to be monthly instead of weekly. We still think it is important to have a sync

[openstack-dev] [glance] spec freeze extension

It has come to my attention that the deadline to have Glance-related specs merged for Pike is in the middle of religious holidays/institutional holidays in the EU. Hence, the spec freeze is extended to 23:59 UTC on Wednesday 19 April 2017. Here's a link to the spec tracking etherpad:

Re: [openstack-dev] [tc][elections]questions about one platform vision

> +1 for us to publish sets of projects that work together for specific > scenarios. I heard this idea first from Allison Randall and it > immediately struck a chord. To be fair folks like Jay Pipes have > always said (paraphrasing) "OpenStack is a toolbox". So it's the next > step i guess.

[openstack-dev] [openstack] [summit] Speed Mentoring at Boston summit, updated time!

Hello, We are so pleased to again offer Speed Mentoring on the first day of the Boston summit. The time has recently moved from Monday morning (too early!) to Monday lunch. We have 20 fabulous mentors signed up and 5 great volunteers. We have space for lots more mentees! So if you know of

Re: [openstack-dev] [tc][elections]questions about one platform vision

> […] > What's the one platform will be in your own words? What's your proposal and > your focus to help one platform vision being achieved? In my view it means that OpenStack contains the blocks to build platforms that can serve as a base for different use cases and workloads. We need to keep

[openstack-dev] [horizon] Pike-1 Tagged

Hey everyone, So we've just tagged our first milestone for Pike. I've checked launchpad and bumped anything unfinished to pike-2. You can see our progress for pike-1 at https://launchpad.net/horizon/+milestone/pike-1 5 blueprints implemented and 73 bugs closed, as well as many minor bugs that

Re: [openstack-dev] [tc][elections]questions about one platform vision

On Apr 11, 2017, at 9:54 PM, joehuang wrote: > Can all these efforts lead us to one platform vision? We have to think over > the question. > > What's the one platform will be in your own words? What's your proposal and > your focus to help one platform vision being

Re: [openstack-dev] [nova] Why don't we unbind ports or terminate volume connections on shelve offload?

On 04/13/2017 10:45 AM, Matt Riedemann wrote: This came up in the nova/cinder meeting today, but I can't for the life of me think of why we don't unbind ports or terminate the connection volumes when we shelve offload an instance from a compute host. When you unshelve, if the instance was

Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

I like the idea and would love to help with mentoring. I’ve learned a lot being a Kolla core. I think every contributor is the same – core or not ☺. At the end of the mentorship, I think we need to make sure that non-cores feel no different than cores, and that every contributor is the same,

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, This week's meeting was lightly attended but provided a useful discussion about the future of the working group and how we will continue to improve the API experience for all OpenStack users. The group is considering its role with respect to the guidelines that

[openstack-dev] [nova] Why don't we unbind ports or terminate volume connections on shelve offload?

This came up in the nova/cinder meeting today, but I can't for the life of me think of why we don't unbind ports or terminate the connection volumes when we shelve offload an instance from a compute host. When you unshelve, if the instance was shelved offloaded, the conductor asks the

Re: [openstack-dev] [tc] version document for project navigator

Excerpts from Thierry Carrez's message of 2017-04-13 18:03:41 +0200: > Monty Taylor wrote: > > On 04/13/2017 08:28 AM, Jimmy McArthur wrote: > >> Just checking on the progress of this. :) > > > > Unfortunately a good portion of the TC was away this week at the > > leadership training so getting a

Re: [openstack-dev] [kubernetes][kolla][openstack-helm][magnum] Kubernetes Day at OpenStack Summit NA 2017 announced!

Hello everyone, I'm pleased to announce that the event schedule is published - you may find it at the event page [1]. Please, join us on May 9 at OpenStack Summit venue in Boston! Ihor 1. https://www.cncf.io/event/openstack-north-america-2017 On Tue, Feb 28, 2017 at 12:44 AM, Ihor Dvoretskyi

Re: [openstack-dev] [tc] version document for project navigator

Monty Taylor wrote: > On 04/13/2017 08:28 AM, Jimmy McArthur wrote: >> Just checking on the progress of this. :) > > Unfortunately a good portion of the TC was away this week at the > leadership training so getting a final ok on it was a bit stalled. It's > seeming like the multi-file version is

Re: [openstack-dev] [ironic] 3rdparty CI status and how we can help to make it green

Dell - Internal Use - Confidential Thanks for starting the discussion. Will attend -Original Message- From: Dmitry Tantsur [mailto:dtant...@redhat.com] Sent: Thursday, April 13, 2017 10:33 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev]

Re: [openstack-dev] [tc][election] Questions for Candidates

> You all have proven yourselves to be crucial parts of the community and I > just wanted to say good luck to each one of you in the upcoming election! Thank you. :) > -What is one trait you have that makes it difficult to work in groups like > the TC and how do you counteract it? I can be

[openstack-dev] [ironic] 3rdparty CI status and how we can help to make it green

Hi all, especially maintainers of 3rdparty CI for Ironic :) I've been watching our 3rdparty CI results recently. While things have improved compared to e.g. a month ago, most of jobs still finish with failures. I've written a simple script [1] to fetch CI runs information from my local Gertty

Re: [openstack-dev] [tc] version document for project navigator

On 04/13/2017 08:28 AM, Jimmy McArthur wrote: Just checking on the progress of this. :) Unfortunately a good portion of the TC was away this week at the leadership training so getting a final ok on it was a bit stalled. It's seeming like the multi-file version is the one most people like

[openstack-dev] OpenStack Summit Boston Prices Increase Tomorrow!

Hi everyone, It’s your last chance to save on your OpenStack Summit Boston tickets before prices increase tomorrow Friday, April 14 at 11:59pm PDT (April 15 at 6:59 UTC). Haven’t booked your hotel yet? You can purchase a Full Access Summit

Re: [openstack-dev] [tc] [elections] Available time and top priority

On Wed, Apr 12 2017, Thierry Carrez wrote: > One idea I've been considering is eliminating the one and only sacred > one-hour weekly TC meeting, and encouraging ad-hoc discussions (on > #openstack-dev for example) between change proposers and smaller groups > of TC members present in the same

Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

Thanks sdake! I added this topic to next meeting agenda. Way I see it it might not be any more load on core reviewer as answering questions and reviewing is part of our job already. However having some "trusted" person to ask can mean a lot to new reviewer as it will lower this fear of being

Re: [openstack-dev] [kolla][all][tc] Starting a core reviewer mentorship program for Kolla deliverables

On 12 Apr 2017, at 18:54, Michał Jastrzębski wrote: > I was also thinking of having "cores just for single thing" in Kolla, > but I think that won't really work as most of our code is variation of > other parts with very little unique things to this, it's tuning up > details that takes most of

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

Hi Tony, > Please look over both lists by 2017-04-17 00:00 UTC and let me know if: > - A project is in list 1 and *really* *really* wants to opt *OUT* of > EOLing and > why. Note doing this will amost certainly reduce the testing coverage > you > have in the gate. > - A project is in list 2

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Wed, Apr 12, 2017 at 6:21 PM, Tony Breeds wrote: > On Wed, Apr 12, 2017 at 07:53:17AM -0600, Alex Schultz wrote: > >> Please EOL the Puppet OpenStack projects that have the stable/mitaka branch. > > Thanks Alex! I've added: > openstack/puppet-aodh >

Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

On Wed, Apr 12 2017, Monty Taylor wrote: > Recently Stephen Finucane (sfinucan) has stepped up to the plate to help sort > out issues we've been having. He's shown a lack of fear of the codebase and an > understanding of what's going on. He's also following through on patches to > projects

Re: [openstack-dev] [tc] version document for project navigator

Just checking on the progress of this. :) Monty Taylor April 7, 2017 at 7:05 AM There is a new repo now: http://git.openstack.org/cgit/openstack/project-navigator-data I have pushed up two different patches with two different approaches:

Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

Ok sounds fair. I guess I had misunderstood what nova had done, and thought it was a path to success. I’m happy we can have the conversation about a mentorship program now at least in the Kolla project. I’m not sure how to evaluate the cost of the mentorship program in terms of core reviewer

Re: [openstack-dev] [libvirt] Whether kvm supports NVIDIA VGPU

- Original Message - > From: "文峰sx-9149" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Wednesday, April 12, 2017 10:53:41 PM > Subject: [openstack-dev] [libvirt] Whether kvm supports NVIDIA VGPU >

Re: [openstack-dev] [tc][elections]questions about one platform vision

Excerpts from joehuang's message of 2017-04-13 00:47:53 +: > Interesting to know the idea considering OpenStack as group of > constellations. Does it mean even > Nova/Cinder/Neutron are not necessary to be tied together in some user cases? To me, the important aspect of calling OpenStack

Re: [openstack-dev] [tc][elections]questions about one platform vision

On 12/04/17 02:54 +, joehuang wrote: Hello, I heard the one platform vision in OpenStack now and then: One platform for virtual machines, containers and bare metal. I also learned that there are some groups working on making Kubernets being able to manage virtual machines. Except running

Re: [openstack-dev] [Release-job-failures][telemetry][gnocchi] Release of openstack/python-gnocchiclient failed

Excerpts from Mehdi Abaakouk's message of 2017-04-13 07:51:36 +0200: > Thanks for the investigation. > > I see two things: > > * I have forgotten than pushing tag will build the tarball > automatically. > * I have thought I should do the tagging manually because of [1] > > For the second

Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

The idea is great, no doubt here, meaning mentoring and everything, but it should not come with price of reducing quality control. 2 x +2 +w should still be required from “regular” cores for PS to merge. Serguei From: Richard Wellum [mailto:richwel...@gmail.com] Sent: Thursday, April 13, 2017

Re: [openstack-dev] [tc][election] Questions for Candidates

On 12/04/17 16:19 +, Kendall Nelson wrote: Hello Candidates! -What is one trait you have that makes it difficult to work in groups like the TC and how do you counteract it? I love agreement, I'd rather have everyone agree everytime. This makes it hard for me to drive some conversations.

[openstack-dev] [ heat ]

Hi team, I am creating a stack which is having nested templates. So while issuing the heat stack-create command I got error " Failed to fetch the remote template < template name >". My heat version is 0.2.8 . Can you please help how to overcome the issue? Regards, VenkataMahesh

[openstack-dev] [devstack] uwsgi for API services

One of the many reasons for getting all our API services running wsgi under a real webserver is to get out of the custom ports for all services game. However, because of some of the limits of apache mod_wsgi, we really haven't been able to do that in our development enviroment. Plus, the moment we

Re: [openstack-dev] [tripleo][manila] Ganesha deployment

On Tue, Apr 11, 2017 at 9:45 PM, Ben Nemec wrote: > > > On 04/11/2017 02:00 PM, Giulio Fidente wrote: >> >> On Tue, 2017-04-11 at 16:50 +0200, Jan Provaznik wrote: >>> >>> On Mon, Apr 10, 2017 at 6:55 PM, Ben Nemec >>> wrote: On

Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

As a relatively new member of the openstack community I think the idea of a mentorship program is a good one; I'd like to throw my hat in the ring if the kolla community needs a guinea-pig to try this on. :) Rich On Wed, Apr 12, 2017 at 7:53 PM Matt Riedemann wrote: > On

Re: [openstack-dev] [tc][election] Questions for Candidates

On 12 April 2017 at 17:19, Kendall Nelson wrote: > -What is one trait you have that makes it difficult to work in groups like > the TC and how do you counteract it? My inability to say no to more work (and being too interested in everything). I think I am slowly getting

[openstack-dev] [openstack][keystonemiddleware][oslo_context]

Hi, I am now trying to refactor the mistral context by using oslo_context. However, it turns out the error in testing of keystone (this test belongs to mistral unittest). What i saw in the error that, the below statement does not return value: auth_url = CONF.keystone_authtoken.auth_uri (

Re: [openstack-dev] [tc][election] Questions for Candidates

Kendall Nelson wrote: > -What is one trait you have that makes it difficult to work in groups > like the TC and how do you counteract it? I dislike conflict, and would always like everyone to win. I consider most people in this community as good friends and I like when they are all happy. This

Re: [openstack-dev] [heat] change in behavior from Mitaka to Newton, is this a bug ?

Hello, I confirm that setting: [oslo_middleware] enable_proxy_headers_parsing = true Fixes the problem, and the 'links' property when I create new stacks gets again the https:// URL. THANK YOU !!! :) Anyway we should document this change in the Release notes for people upgrading to Newton. I

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

On 13.04.2017 0:59, Michał Jastrzębski wrote: > My dear Kollegues, > > Today we had discussion about how to properly name/tag images being > pushed to dockerhub. That moved towards general discussion on revision > mgmt. > > Problem we're trying to solve is this: > If you build/push images today,

Re: [openstack-dev] [nova] What is the difference between default_schedule_zone and default_availability_zone?

Le 12/04/2017 18:24, Matt Riedemann a écrit : > I'm hoping someone more learned can teach me. These two options sound > very similar, and are thus very confusing. They are also both in the > [DEFAULT] config option group, but defined in different places [1][2]. > > The help text for one says: >

Re: [openstack-dev] [Tacker][OSC] Command naming specs

Thanks Akihiro for suggestions and comments. Thanks, Trinath Somanchi. Digital Networking | NXP – Hyderabad – INDIA. Email: trinath.soman...@nxp.com Mobile: +91 9866235130 | Off: +91 4033504051 From: Akihiro Motoki [mailto:amot...@gmail.com] Sent: Thursday,

Re: [openstack-dev] [heat] change in behavior from Mitaka to Newton, is this a bug ?

On Thu, Apr 13, 2017 at 1:04 PM, Saverio Proto wrote: > Hello, > > I am looking at a strange change in default behavior in heat, after the > upgrade from Mitaka to Newton. > > when you do > > openstack stack show uuid > > you get a table, and there is a property called

[openstack-dev] [heat] change in behavior from Mitaka to Newton, is this a bug ?

Hello, I am looking at a strange change in default behavior in heat, after the upgrade from Mitaka to Newton. when you do openstack stack show uuid you get a table, and there is a property called 'links' In Mitaka the value was something like - href: https://URL rel: self After I upgraded

Re: [openstack-dev] [TripleO][Heat] Conditionally passing properties in Heat

On Thu, Apr 13, 2017 at 2:14 AM, Dan Sneddon wrote: > On 04/12/2017 01:22 PM, Thomas Herve wrote: > > On Wed, Apr 12, 2017 at 9:00 PM, Dan Sneddon > wrote: > >> I'm implementing predictable control plane IPs for spine/leaf, and I'm > >> running into a