Re: [openstack-dev] [Zun] Announce change of Zun core reviewer team

2018-05-07 Thread Shu M.
+1. Welcome!! Cheers, Shu 2018-05-03 12:20 GMT+09:00 Shuai Zhao : > +1 for Ji Wei :-) > > On Thu, May 3, 2018 at 4:40 AM, Hongbin Lu wrote: > >> Hi all, >> >> I would like to announce the following change on the Zun core reviewers >> team: >> >> + Ji Wei >> >> Ji Wei has been working on Zun for

Re: [openstack-dev] [tap-as-a-service] publish on pypi

2018-05-07 Thread Takashi Yamamoto
thank you. done. https://pypi.org/project/tap-as-a-service/ On Fri, Mar 30, 2018 at 8:27 AM, Clark Boylan wrote: > On Wed, Mar 28, 2018, at 7:59 AM, Takashi Yamamoto wrote: >> hi, >> >> i'm thinking about publishing the latest release of tap-as-a-service on pypi. >> background: https://review.ope

[openstack-dev] [nova] Extra feature of vCPU allocation on demands

2018-05-07 Thread 倪蔚辰
Hi, all I would like to propose a blueprint (not proposed yet), which is related to openstack nova. I hope to have some comments by explaining my idea through this e-mail. Please contact me if anyone has any comment. Background Under current OpenStack, vCPUs assigned to each VM can be config

Re: [openstack-dev] [Openstack-operators][heat][all] Heat now migrated to StoryBoard!!

2018-05-07 Thread Rico Lin
Hi all, I updated more information to this guideline in [1]. Please must take a view on [1] to see what's been updated. will likely to keep update on that etherpad if new Q&A or issue found. Will keep trying to make this process as painless for you as possible, so please endure with us for now, a

Re: [openstack-dev] [tempest] Proposing Felipe Monteiro for Tempest core

2018-05-07 Thread Andrea Frittoli
+1!! On Sat, 28 Apr 2018, 11:29 am Ghanshyam Mann, wrote: > Hi Tempest Team, > > I would like to propose Felipe Monteiro (irc: felipemonteiro) to Tempest > core. > > Felipe has been an active contributor to the Tempest since the Pike > cycle. He has been doing lot of review and commits since

Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling

2018-05-07 Thread Jean-Philippe Evrard
I think Jesse sumarized things elegantly. Here is an analogy for you, to complement the answer with more background. Let me compare our state with a new company, as this is a a notion people many people can relate to. Initially we were a startup. Only a few people were working on OSA on its creat

Re: [openstack-dev] [all][tc][ptls] final stages of python 3 transition

2018-05-07 Thread Jean-Philippe Evrard
We've been juggling with python3, ansible and multiple distros for a while now. That dance hasn't been fruitful: many hidden issues, either due to ansible modules, or our own modules, or upgrade issues. I've recently decided to simplify the python2/3 story. Queens and all the stable branches will

Re: [openstack-dev] [all][tc][ptls] final stages of python 3 transition

2018-05-07 Thread Doug Hellmann
Excerpts from Jean-Philippe Evrard's message of 2018-05-07 13:36:34 +0200: > We've been juggling with python3, ansible and multiple distros for a while > now. > That dance hasn't been fruitful: many hidden issues, either due to > ansible modules, or our own modules, or upgrade issues. > > I've re

[openstack-dev] [tc][goals] tracking status of old goals for new projects

2018-05-07 Thread Doug Hellmann
There is a patch to update the Python 3.5 goal for Kolla [1]. While I'm glad to see the work happening, the change adds a new deliverable to an old goal, and it isn’t clear whether we want to use that approach for tracking goal work indefinitely. I see a few options. 1. We could update the existin

Re: [openstack-dev] [tc][goals] tracking status of old goals for new projects

2018-05-07 Thread Jeremy Stanley
On 2018-05-07 09:52:16 -0400 (-0400), Doug Hellmann wrote: [...] > 3. We could do nothing to record the work related to the goal. [...] For situations like 557863 I think I'd prefer either the status quo (the kolla deliverable _was_ already listed so it could make sense to update it in that docume

[openstack-dev] [TripleO] TripleO deployment on OVB on public cloud

2018-05-07 Thread Ben Nemec
Hi, I wanted to make everyone aware that I recorded a demo of running an OVB deployment on a public cloud. As I say in the video, this is significant because in the past OVB has largely been limited to running in our special-purpose CI clouds, which have distinctly finite capacity and are ge

[openstack-dev] [nova] review runway status

2018-05-07 Thread melanie witt
Howdy everyone, This is just a brief status about the blueprints currently occupying review runways [0] and an ask for the nova-core team to give these reviews priority for their code review focus. * XenAPI: Support a new image handler for non-FS based SRs https://blueprints.launchpad.net/nova/+

[openstack-dev] [horizon] No meeting this week

2018-05-07 Thread Ivan Kolodyazhny
Hi team, Due to the Victory Day, I won't be able to chair the meeting this week. After a short conversation in the IRC, we decided to skip this meeting. Feel free to add your topic to https://wiki.openstack.org/wiki/Meetings/Horizon and see you next week! Regards, Ivan Kolodyazhny, http://blog.e0

Re: [openstack-dev] [nova] Extra feature of vCPU allocation on demands

2018-05-07 Thread Eric Fried
I will be interested to watch this develop. In PowerVM we already have shared vs. dedicated processors [1] along with concepts like capped vs. uncapped, min/max proc units, weights, etc. But obviously it's all heavily customized to be PowerVM-specific. If these concepts made their way into mains

Re: [openstack-dev] [nova] Extra feature of vCPU allocation on demands

2018-05-07 Thread Jay Pipes
On 05/07/2018 05:55 AM, 倪蔚辰 wrote: Hi, all I would like to propose a blueprint (not proposed yet), which is related to openstack nova. I hope to have some comments by explaining my idea through this e-mail. Please contact me if anyone has any comment. Background Under current OpenStack, vCP

[openstack-dev] [tc] Technical Committee Status update, 7 May

2018-05-07 Thread Doug Hellmann
This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at: https://storyboard.openstack.org/#!/pro

Re: [openstack-dev] [all][requirements] uncapping eventlet

2018-05-07 Thread Michel Peterson
On Fri, Apr 20, 2018 at 11:06 PM, Doug Hellmann wrote: > > We have made great progress on this but we do still have quite a > few of these patches that have not been approved. Many are failing > test jobs and will need a little attention ( the failing requirements > jobs are real problems and re

[openstack-dev] [neutron] Bug deputy report

2018-05-07 Thread Hongbin Lu
Hi all, Below is the bug deputy report for last week (Apr 30 - May 6). * https://bugs.launchpad.net/neutron/+bug/1767811 Confirmed. In DVR scenario, VM capture unexpected packet that should not be sent to the VM. The bug reporter self-assigned this bug. * https://bugs.launchpad.net/neutron/+bug

[openstack-dev] [tripleo] CI & Tempest squad planning summary: Sprint 13

2018-05-07 Thread Matt Young
Greetings, The TripleO CI & Tempest squads have begun work on Sprint 13. Like most of our sprints these are three weeks long and are planned on a Thursday or Friday (depending on squad) and have a retrospective on Wednesday. Sprint 13 runs from 2018-05-03 thru 2018-05-23. More information regar

[openstack-dev] Ironic Status Updates

2018-05-07 Thread Julia Kreger
Greetings everyone, For some time, Rama Yeleswarapu (rama_y) has been graciously sending out a weekly update for Ironic to the mailing list. We found out late last week that this contributor would be unable to continue to do so. While discussing this and searching for a volunteer, we came up with

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

2018-05-07 Thread Ildiko Vancsa
Hi Training Team, It’s a friendly reminder that our next meeting is in an hour, 2000 UTC, on #openstack-meeting-3. Agenda is here: https://etherpad.openstack.org/p/openstack-upstream-institute-meetings See you in a bit! Thanks, Ildikó (IRC: ildikov)

Re: [openstack-dev] [tc][goals] tracking status of old goals for new projects

2018-05-07 Thread Mohammed Naser
On Mon, May 7, 2018 at 9:52 AM, Doug Hellmann wrote: > There is a patch to update the Python 3.5 goal for Kolla [1]. While > I'm glad to see the work happening, the change adds a new deliverable > to an old goal, and it isn’t clear whether we want to use that > approach for tracking goal work inde

[openstack-dev] [sdk] identity proxy: users, groups, projects, membership, roles

2018-05-07 Thread gerard.d...@wipro.com
Hi, I'm wondering if there are (or should be) operations in the Connection.identity proxy to manage user and group membership to projects, and to manage user and group role assignments (there are role management methods in the Project class, but I couldn't find them in the identity proxy): The

[openstack-dev] [barbican] meeting cancelled for 5/7/2018

2018-05-07 Thread Ade Lee
Hi all, I have a conflict for this week's meeting. Therefore we will cancel for this week and reconvene next week. Thanks. Ade __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-req

Re: [openstack-dev] [tc][goals] tracking status of old goals for new projects

2018-05-07 Thread Doug Hellmann
Excerpts from Jeremy Stanley's message of 2018-05-07 14:06:35 +: > On 2018-05-07 09:52:16 -0400 (-0400), Doug Hellmann wrote: > [...] > > 3. We could do nothing to record the work related to the goal. > [...] > > For situations like 557863 I think I'd prefer either the status quo > (the kolla

Re: [openstack-dev] Ironic Status Updates

2018-05-07 Thread Doug Hellmann
Excerpts from Julia Kreger's message of 2018-05-07 13:53:13 -0400: > Greetings everyone, > > For some time, Rama Yeleswarapu (rama_y) has been graciously sending > out a weekly update for Ironic to the mailing list. We found out late > last week that this contributor would be unable to continue to

Re: [openstack-dev] [all][requirements] uncapping eventlet

2018-05-07 Thread Doug Hellmann
Excerpts from Michel Peterson's message of 2018-05-07 17:54:02 +0300: > On Fri, Apr 20, 2018 at 11:06 PM, Doug Hellmann > wrote: > > > > > We have made great progress on this but we do still have quite a > > few of these patches that have not been approved. Many are failing > > test jobs and wil

Re: [openstack-dev] [sdk] issues with using OpenStack SDK Python client

2018-05-07 Thread gerard.d...@wipro.com
more details about router deletion: I tried replacing the "!=None" test with a try statement: try: onap_router = conn.network.find_router(ONAP_ROUTER_NAME) conn.network.delete_router(onap_router.id) (router print-out just before deleting): openstack.network.v2.ro

Re: [openstack-dev] [all][requirements] uncapping eventlet

2018-05-07 Thread John Dickinson
I've discovered that eventlet 0.23.0 (released April 6) does break things for Swift. I'm not sure about other projects yet. https://bugs.launchpad.net/swift/+bug/1769749 --John On 7 May 2018, at 13:50, Doug Hellmann wrote: Excerpts from Michel Peterson's message of 2018-05-07 17:54:02 +03

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

2018-05-07 Thread Yeleswarapu, Ramamani
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) Weekly priorities ---

[openstack-dev] [All] A worked example of adding privsep to an OpenStack project

2018-05-07 Thread Michael Still
Hi, further to last week's example of how to add a new privsep'ed call in Nova, I thought I'd write up how to add privsep to a new OpenStack project. I've used Cinder in this worked example, but it really applies to any project which wants to do things with escalated permissions. The write up is

Re: [openstack-dev] [All] A worked example of adding privsep to an OpenStack project

2018-05-07 Thread ChangBo Guo
Thanks Michael, that's very useful. 2018-05-08 10:05 GMT+08:00 Michael Still : > Hi, > > further to last week's example of how to add a new privsep'ed call in > Nova, I thought I'd write up how to add privsep to a new OpenStack project. > I've used Cinder in this worked example, but it really app