[openstack-dev] [oslo] priorities for the current week (05/02-05/05)

Oslo folks, Oslo team maintain 35 libraries, each core reviewer focuses on part of them. In last several weeks, We did some work , try to make Oslo review productive and efficiently . Summarize them as follow: 1. Collect core reviwers' focuses The Oslo program brings together generalist

[openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

In Cinder, there are many features/APIs which are backend specific and will return 405 or 501 if same is not implemented on any backend [1]. If such tests are implemented in Tempest, then it will break some gate where that backend job is voting. like ceph job in glance_store gate. There been many

Re: [openstack-dev] [Zun] Proposal a change of Zun core team

+1 Regards Shubham On Tue, May 2, 2017 at 6:33 AM, Qiming Teng wrote: > +1 > > Qiming > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe:

[Openstack] [all][OSC] OpenStack Interpreter: A useful tool python interpreter tool for the OpenStack client libraries.

Hello OpenStack folks, As part of my dev work I recently put together a cool little tool which lets me have much easier access to the various OpenStack python clients in the scope of a python interpreter session. The first version was a little rough and without os-client-config support. The

Re: [openstack-dev] [qa][heat][murano][daisycloud] Removing Heat support from Tempest

On Fri, Apr 28, 2017 at 2:17 PM, Andrea Frittoli wrote: > > > On Fri, Apr 28, 2017 at 10:29 AM Rabi Mishra wrote: > >> On Thu, Apr 27, 2017 at 3:55 PM, Andrea Frittoli < >> andrea.fritt...@gmail.com> wrote: >> >>> Dear stackers, >>> >>> starting

[openstack-dev] [all][OSC] OpenStack Interpreter: A useful tool python interpreter tool for the OpenStack client libraries.

Hello OpenStack folks, As part of my dev work I recently put together a cool little tool which lets me have much easier access to the various OpenStack python clients in the scope of a python interpreter session. The first version was a little rough and without os-client-config support. The

Re: [openstack-dev] [ironic] Goodbye ironic o/

Hi Mario, Sorry to hear that you won’t be working on Ironic anymore! Best of luck on whatever you are doing next! Shobha From: John Villalovos [mailto:openstack@sodarock.com] Sent: Monday, May 1, 2017 9:14 AM To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Zun] Proposal a change of Zun core team

+1 :) On 29/04/17 16:05, Hongbin Lu wrote: > > Hi all, > > > > I proposes a change of Zun’s core team memberships as below: > > > > + Feng Shengqin (feng-shengqin) > > - Wang Feilong (flwang) > > > > Feng Shengqin has contributed a lot to the Zun projects. Her > contribution includes BPs,

Re: [openstack-dev] [os-upstream-institute] Order of Slides

Hey Amy, IMHO this is not an issue and IIRC we have followed that flow because we start by showing an overview (the big picture) of how you can contribute to OpenStack (without any exercise), then we move on on creating the accounts for contributing (with exercise) and after that we move on with

Re: [openstack-dev] [Zun] Proposal a change of Zun core team

+1 for both. Well deserved Feng! Thanks, Madhuri From: Hongbin Lu [mailto:hongbin...@huawei.com] Sent: Saturday, April 29, 2017 9:35 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Zun] Proposal a change of Zun

[openstack-dev] [os-upstream-institute] Order of Slides

I was going over the 2 sections I'm presenting this weekend and noticed that in https://docs.openstack.org/upstream-training/workflow-training-contribution-process.html We talk about submitting and taking bugs, doing reviews and pushing up code sets as it's the overview. But the next section

Re: [openstack-dev] [Zun] Proposal a change of Zun core team

+1 for me, Thanks On 29 April 2017 at 12:05, Hongbin Lu wrote: > Hi all, > > > > I proposes a change of Zun’s core team memberships as below: > > > > + Feng Shengqin (feng-shengqin) > > - Wang Feilong (flwang) > > > > Feng Shengqin has contributed a lot to the Zun

[openstack-dev] Boston Summit Forum and working session Log messages (please comment and participate)

Hey folks! I just wanted to raise your awareness of a forum session and a working session on Log Messages that is happening during the Boston Summit. Here is the link to the etherpad for these sessions: https://etherpad.openstack.org/p/BOS-forum-log-messages We’ve been going around in circles

Re: [openstack-dev] [Zun] Proposal a change of Zun core team

+1 Qiming __ 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] [nova] Something seems to have regressed the live migration job

I don't have the time to dig into this tonight and nothing is jumping out at me for obvious regressions in nova, tempest or devstack, but it seems something has regressed the live migration job in the last 12 hours: https://bugs.launchpad.net/nova/+bug/1687511 -- Thanks, Matt

Re: [openstack-dev] [qa][heat][murano][daisycloud] Removing Heat support from Tempest

On Tue, May 2, 2017 at 5:27 AM, MONTEIRO, FELIPE C wrote: > Murano currently uses the Tempest orchestration client for its scenario > Tempest tests [0], which are not turned on by default in the Murano Tempest > gate due to resource constraints. > > However, I'm hesitant to

Re: [openstack-dev] [nova][blazar][scientific] advanced instance scheduling: reservations and preeemption - Forum session

You can also count on me for discussing about what was Blazar previously and how Nova could help it ;-) -Sylvain Le 1 mai 2017 21:53, "Jay Pipes" a écrit : > On 05/01/2017 03:39 PM, Blair Bethwaite wrote: > >> Hi all, >> >> Following up to the recent thread

Re: [openstack-dev] [Forum] Moderators needed!

If no body has claimed it yet, I will be happy to moderate Making Neutron easy session - https://www.openstack.org/summit/boston-2017/summit-schedule/events/18800/making-neutron-easy-for-people-who-want-basic-networking I am already presenter into two sessions. Let me know if you want me to do

[Openstack-operators] Defining the agenda for Kubernetes Ops on OpenStack forum session @ OpenStack Summit Boston

Hi all, There will be a forum session at OpenStack Summit Boston next week on the topic of Kubernetes Ops on OpenStack on OpenStack. This session will be occurring on the Wednesday, May 10, at 1:50pm-2:30pm [1]. If you are an operator, developer, or other contributor attending OpenStack Summit

[openstack-dev] Defining the agenda for Kubernetes Ops on OpenStack forum session @ OpenStack Summit Boston

Hi all, There will be a forum session at OpenStack Summit Boston next week on the topic of Kubernetes Ops on OpenStack on OpenStack. This session will be occurring on the Wednesday, May 10, at 1:50pm-2:30pm [1]. If you are an operator, developer, or other contributor attending OpenStack Summit

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are glad to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. Pike priorities

Re: [Openstack-operators] [nova][blazar][scientific] advanced instance scheduling: reservations and preeemption - Forum session

On 05/01/2017 03:39 PM, Blair Bethwaite wrote: Hi all, Following up to the recent thread "[Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session" and adding openstack-dev. This is now a confirmed forum session

Re: [openstack-dev] [nova][blazar][scientific] advanced instance scheduling: reservations and preeemption - Forum session

On 05/01/2017 03:39 PM, Blair Bethwaite wrote: Hi all, Following up to the recent thread "[Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session" and adding openstack-dev. This is now a confirmed forum session

Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

Sam- Under the current design, you can provide a specific endpoint (singular) via the `endpoint_override` conf option. Based on feedback on this thread, we will also be keeping support for `[glance]api_servers` for consumers who actually need to be able to specify multiple endpoints.

[Openstack-operators] [nova][blazar][scientific] advanced instance scheduling: reservations and preeemption - Forum session

Hi all, Following up to the recent thread "[Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session" and adding openstack-dev. This is now a confirmed forum session

[openstack-dev] [nova][blazar][scientific] advanced instance scheduling: reservations and preeemption - Forum session

Hi all, Following up to the recent thread "[Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session" and adding openstack-dev. This is now a confirmed forum session

Re: [openstack-dev] [Openstack-operators] [nova][glance] Who needs multiple api_servers?

Sam- Under the current design, you can provide a specific endpoint (singular) via the `endpoint_override` conf option. Based on feedback on this thread, we will also be keeping support for `[glance]api_servers` for consumers who actually need to be able to specify multiple endpoints.

Re: [Openstack-operators] [openstack-dev] [scientific][nova][cyborg] Special Hardware Forum session

Thanks Rochelle. I encourage everyone to dump thoughts into the etherpad (https://etherpad.openstack.org/p/BOS-forum-special-hardware - feel free to garden it as you go!) so we can have some chance of organising a coherent session. In particular it would be useful to know what is going to be most

Re: [openstack-dev] [scientific][nova][cyborg] Special Hardware Forum session

Thanks Rochelle. I encourage everyone to dump thoughts into the etherpad (https://etherpad.openstack.org/p/BOS-forum-special-hardware - feel free to garden it as you go!) so we can have some chance of organising a coherent session. In particular it would be useful to know what is going to be most

[openstack-dev] [os-upstream-institute] Meeting reminder

Hi Training Team, Friendly reminder that we will have our next (and last before the Boston training) meeting in less than an hour at 2000 UTC on #openstack-meeting-3. You can find the agenda for the meeting here: https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

On 29 April 2017 at 01:46, Mike Dorman wrote: > I don’t disagree with you that the client side choose-a-server-at-random is > not a great load balancer. (But isn’t this roughly the same thing that > oslo-messaging does when we give it a list of RMQ servers?) For us it’s

[openstack-dev] [neutron] neutron-lib impact: Port security extension moved

The neutron portsecurity extension has been rehomed into neutron-lib and we are now in the process of consuming it. Suggested actions: - If your project consumes neutron.extensions.portsecurity [2] and there's not an existing patch for your project in [1], please move your imports over to

Re: [openstack-dev] [Openstack-operators] [nova][glance] Who needs multiple api_servers?

On 29 April 2017 at 01:46, Mike Dorman wrote: > I don’t disagree with you that the client side choose-a-server-at-random is > not a great load balancer. (But isn’t this roughly the same thing that > oslo-messaging does when we give it a list of RMQ servers?) For us it’s

Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

I agree. I think the solution proposed earlier in this thread about making default to service catalog and optionally allow ops to choose 'the list of glance-apis to send data to', would make everyone's life easier. On Mon, May 1, 2017 at 2:16 PM, Blair Bethwaite

Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

On 28 April 2017 at 21:17, Sean Dague wrote: > On 04/28/2017 12:50 AM, Blair Bethwaite wrote: >> We at Nectar are in the same boat as Mike. Our use-case is a little >> bit more about geo-distributed operations though - our Cells are in >> different States around the country, so

[Openstack-operators] [newton] [keystone] [nova] [novaclient] [shibboleth] [v3token] [ecp] nova boot fails for federated users

Trying to figure out if this is a bug in ECP support within novaclient, or if I am misconfiguring something. Any feedback helps! We have keystone configured to use a separate Shibboleth server for auth (with an ECP endpoint). Federated users with the _member_ role on a project can boot VMs using

Re: [openstack-dev] [horizon] Adding Ying Zuo to core team

Welcome Ying Zuo! On Mon, May 1, 2017 at 5:19 AM, Rob Cresswell (rcresswe) wrote: > Hey everyone, > > I’m adding Ying Zuo to the Horizon Core team. She’s been contributing many > great patches to the code base driven by operator experience, as well as > providing solid

Re: [openstack-dev] [qa][heat][murano][daisycloud] Removing Heat support from Tempest

Murano currently uses the Tempest orchestration client for its scenario Tempest tests [0], which are not turned on by default in the Murano Tempest gate due to resource constraints. However, I'm hesitant to switch to Heat's testing client, because it is not a Tempest client, but rather the

Re: [openstack-dev] [all] Removal of puppet and ruby from nodepool images

On Mon, May 01, 2017 at 12:11:14PM -0400, Paul Belanger wrote: > On Mon, May 01, 2017 at 09:59:01AM -0400, Paul Belanger wrote: > > On Thu, Apr 27, 2017 at 07:39:00PM -0400, Paul Belanger wrote: > > > On Wed, Apr 26, 2017 at 12:17:03PM -0400, Paul Belanger wrote: > > > > Greetings, > > > > > > >

Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

> On 1 May 2017, at 4:24 pm, Sean McGinnis wrote: > > On Mon, May 01, 2017 at 10:17:43AM -0400, Matthew Treinish wrote: >>> >> >> I thought it was just nova too, but it turns out cinder has the same exact >> option as nova: (I hit this in my devstack patch trying to

Re: [openstack-dev] [Openstack-operators] [nova][glance] Who needs multiple api_servers?

> On 1 May 2017, at 4:24 pm, Sean McGinnis wrote: > > On Mon, May 01, 2017 at 10:17:43AM -0400, Matthew Treinish wrote: >>> >> >> I thought it was just nova too, but it turns out cinder has the same exact >> option as nova: (I hit this in my devstack patch trying to

Re: [openstack-dev] [ironic] Goodbye ironic o/

Mario, So sorry you won't be working with us on Ironic anymore :( You have been an great part of Ironic and I'm glad I got to know you. Hopefully I will get to work with you again. Best of luck for the future! John On Fri, Apr 28, 2017 at 9:12 AM, Mario Villaplana < mario.villapl...@gmail.com>

Re: [openstack-dev] [all] Removal of puppet and ruby from nodepool images

On Mon, May 01, 2017 at 09:59:01AM -0400, Paul Belanger wrote: > On Thu, Apr 27, 2017 at 07:39:00PM -0400, Paul Belanger wrote: > > On Wed, Apr 26, 2017 at 12:17:03PM -0400, Paul Belanger wrote: > > > Greetings, > > > > > > We, openstack-infra, are on our final steps of removing puppet (and ruby)

Re: [OpenStack-Infra] Ask.o.o Email not getting through?

On 01/05/17 23:36, James E. Blair wrote: Tom Fifield writes: Hello infra, Exploratory question here, no idea what's actually going on. We have a prospective new user on Ask OpenStack, who despite trying multiple auth methods (Launchpad & Google) multiple times did not

Re: [OpenStack-Infra] Ask.o.o Email not getting through?

Tom Fifield writes: > Hello infra, > > Exploratory question here, no idea what's actually going on. > > We have a prospective new user on Ask OpenStack, who despite trying > multiple auth methods (Launchpad & Google) multiple times did not > receive a confirmation email. > >

[Openstack-operators] User Committee IRC Meeting - Monday May 1st

Dear UC Community, This is a kind reminder that we are having our UC IRC meeting today at 1900 UTC in (freenode) #openstack-meeting Agenda: https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee Thanks, Edgar Magana ___

Re: [openstack-dev] [all][tc][cinder][mistral][manila] A path forward to shiny consistent service types

On 04/28/2017 06:26 PM, Monty Taylor wrote: Hey everybody! Yay! (I'm sure you're all saying this, given the topic. I'll let you collect yourself from your exuberant celebration) == Background == As I'm sure you all know, we've been trying to make some hearway for a while on getting

Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

Matt- Yeah, clearly other projects have the same issuethis blueprint is trying to solve in nova. I think the idea is that, once the infrastructure is in place and nova has demonstrated the concept, other projects can climbaboard. It's conceivable that the new get_service_url() method

Re: [openstack-dev] [Openstack-operators] [nova][glance] Who needs multiple api_servers?

Matt- Yeah, clearly other projects have the same issuethis blueprint is trying to solve in nova. I think the idea is that, once the infrastructure is in place and nova has demonstrated the concept, other projects can climbaboard. It's conceivable that the new get_service_url() method

Re: [openstack-dev] [Openstack-operators] [nova][glance] Who needs multiple api_servers?

On Mon, May 01, 2017 at 10:17:43AM -0400, Matthew Treinish wrote: > > > > I thought it was just nova too, but it turns out cinder has the same exact > option as nova: (I hit this in my devstack patch trying to get glance deployed > as a wsgi app) > >

Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

On Mon, May 01, 2017 at 05:00:17AM -0700, Flavio Percoco wrote: > On 28/04/17 11:19 -0500, Eric Fried wrote: > > If it's *just* glance we're making an exception for, I prefer #1 (don't > > deprecate/remove [glance]api_servers). It's way less code & > > infrastructure, and it discourages others

Re: [openstack-dev] [Openstack-operators] [nova][glance] Who needs multiple api_servers?

On Mon, May 01, 2017 at 05:00:17AM -0700, Flavio Percoco wrote: > On 28/04/17 11:19 -0500, Eric Fried wrote: > > If it's *just* glance we're making an exception for, I prefer #1 (don't > > deprecate/remove [glance]api_servers). It's way less code & > > infrastructure, and it discourages others

[OpenStack-Infra] Ask.o.o Email not getting through?

Hello infra, Exploratory question here, no idea what's actually going on. We have a prospective new user on Ask OpenStack, who despite trying multiple auth methods (Launchpad & Google) multiple times did not receive a confirmation email. I checked and there have been several new users

Re: [openstack-dev] [all] Removal of puppet and ruby from nodepool images

On Thu, Apr 27, 2017 at 07:39:00PM -0400, Paul Belanger wrote: > On Wed, Apr 26, 2017 at 12:17:03PM -0400, Paul Belanger wrote: > > Greetings, > > > > We, openstack-infra, are on our final steps of removing puppet (and ruby) > > from > > our images jobs run in nodepool. At this point, I think

Re: [openstack-dev] [ironic] [stable] ironic-stable-maint update proposal

+1 to all and more sighs. I wish I didn't have to be added. Can't we make people stay? :) --ruby From: Julia Kreger Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, April 27, 2017 at 5:57

Re: [openstack-dev] [ironic] Goodbye ironic o/

Hi Mario, I will miss you; good luck! So long and thanks for all the metrics :) --ruby From: Mario Villaplana Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Friday, April 28, 2017 at 12:12 PM To:

Re: [openstack-dev] [gnocchi] per-sack vs per-metric locking tradeoffs

On 29/04/17 08:14 AM, Julien Danjou wrote: > 1. get 'deleted' metrics > 2. delete all things in storage > -> if it fails, whatever, ignore, maybe a janitor is doing the same > thing? > 3. expunge from indexer possibly? i was thinking it was possible that maybe it would partially delete and

Re: [Openstack] two elastic ips

Hi, Yes, it is possible, but as I know this functionality not able to use via Horizon dashboard. Please use neutron cli client to do this: - neutron floatingip-list - neutron port-list - neutron floatingip-associate On Mon, May 1, 2017 at 4:31 AM, Konstantin Raskoshnyi

[Openstack] Query: User types and authentication

Hi All I am a new to openstack and have a basic question regarding User types and administration I find 3 categories of users 1. Openstack cloud administrators/users who create tenants (or projects) and administer the cloud 2. Tenant/Project adminstrators/ops users who belong to the organizations

Re: [openstack-dev] [Openstack-operators] [nova][glance] Who needs multiple api_servers?

On 28/04/17 11:19 -0500, Eric Fried wrote: If it's *just* glance we're making an exception for, I prefer #1 (don't deprecate/remove [glance]api_servers). It's way less code & infrastructure, and it discourages others from jumping on the multiple-endpoints bandwagon. If we provide

Re: [openstack-dev] [all][tc][cinder][mistral][manila] A path forward to shiny consistent service types

On 29/04/17 22:40 -0500, Sean McGinnis wrote: On Fri, Apr 28, 2017 at 05:26:16PM -0500, Monty Taylor wrote: Hey everybody! ... == Proposed Solution == ... Clean things up ... Make things simple ... Don't break everybody +1 from me. I think this is a good direction to go. /me likes! /me

[openstack-dev] [horizon] Adding Ying Zuo to core team

Hey everyone, I’m adding Ying Zuo to the Horizon Core team. She’s been contributing many great patches to the code base driven by operator experience, as well as providing solid reviews. Welcome to the team! Rob __

[openstack-dev] [neutron][osc] Openstack client, unit tests & creating default empty values

Hello, The unit test for the network/v2/fakes.py for the port creates empty dictionaries e.g. for allowed_address_pairs: port_attrs = { 'admin_state_up': True, 'allowed_address_pairs': [{}], 'binding:host_id': 'binding-host-id-' + uuid.uuid4().hex,

Re: [openstack-dev] [tricircle]poll for new weekly meeting time slot

Hello, According to the poll, most of contributors prefer the option "Wed UTC 01:00, Beijing 9:00 AM, PDT(-1 day) 6:00 PM". I'll submit a patch to update the weekly meeting time slot. Best Regards Chaoyi Huang (joehuang) From: joehuang Sent: 24 April 2017

[openstack-dev] [vitrage] The next two IRC meetings are SKIPPED

Hi, Due to the Boston summit and the fact that most of Vitrage contributors are now busy preparing to it, we will skip the IRC meetings this week and next week. We will meet again on Wednesday, May 17 at 8:00 UTC. Thanks, Ifat.