Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

On 1/30/2016 3:44 PM, Davanum Srinivas wrote: Sylvain, Let's agree to disagree. This works for Oslo, so lets leave it at that. Also, *please* switch Subject as this is not fair to Alexis's nomination if you wish to continue. I agree, and apologize both to Alexis and the broader team for

Re: [openstack-dev] Any chances to backport port_security_enabled support into Heat for Kilo 2015.1.3?

On 29/01/16 09:45, Martinx - ジェームズ wrote: Guys, This is important and Kilo is missing it: https://review.openstack.org/#/c/179989/ Is it possible to backport it to Kilo 2015.1.3? Currently, I am manually patching Kilo / Heat by using the following diff:

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

On 1/31/2016 4:24 PM, Matt Riedemann wrote: On 1/30/2016 3:44 PM, Davanum Srinivas wrote: Sylvain, Let's agree to disagree. This works for Oslo, so lets leave it at that. Also, *please* switch Subject as this is not fair to Alexis's nomination if you wish to continue. I agree, and

Re: [openstack-dev] [Nova][Neutron] Scheduling with routed networks

On 29 January 2016 at 16:09, Armando M. wrote > On 29 January 2016 at 12:16, Jay Pipes wrote: >> On 01/28/2016 09:15 PM, Carl Baldwin wrote: >>> >>> Hi Nova and Neutron, >>> It was a pleasure to attend the Nova mid-cycle in Bristol this week. >> Indeed, I

[openstack-dev] [senlin] translatin setup

I noticed that senlin and python-senline havepot file in the tree but is not using our usual translation setup - and have no translations. Do you want to enable translations using our translation server? Since senlin is an official team under governance, you can make use of that instead of

Re: [openstack-dev] [nova] do not account compute resource of instances in state SHELVED_OFFLOADED

On 27 January 2016 at 16:59, Sascha Vogt wrote: > Hi Andrew, > > Am 27.01.2016 um 10:38 schrieb Andrew Laski: >> 1. This allows for a poor experience where a user would not be able to >> turn on and use an instance that they already have due to overquota. >> This is a

[openstack-dev] [neutron][i18n] networking-powervm: Manual Translations?

I noticed that networking-powervm has translations in the tree but is not using our usual translation setup. Do you want to enable translations using our translation server? Since networking-powervm is part of neutron, you can make use of that instead of having to do manually import

[openstack-dev] [ceilometer] ceilometer-powervm translations

I noticed that ceilometer-powervm has translations in the tree but is not using our usual translation setup. Do you want to enable translations using our translation server? Since ceilometer-powervm is part of ceilometer, you can make use of our infrastructure instead of having to do manually

Re: [openstack-dev] [stable][ceilometer][all] stable/kilo 2015.1.3 delayed

On 30/01/2016 7:54 AM, Dave Walker wrote: > On 29 January 2016 at 20:36, Jeremy Stanley wrote: >> On 2016-01-29 19:34:01 + (+), gordon chung wrote: >>> hmm.. that's unfortunate... anything we need to update so this doesn't >>> happen again? or just a matter of lesson

Re: [openstack-dev] [Cinder] Nominating Patrick East to Cinder Core

On Sat, Jan 30, 2016 at 12:58 PM, Jay Bryant wrote: > +1. Patrick's contributions to Cinder have been notable since he joined us > and he is a pleasure to work with! Welcome to the core team Patrick! > > Jay > > > On Fri, Jan 29, 2016, 19:05 Sean McGinnis

[openstack-dev] Call for papers already closed?

Hello. I am a little bit confused, according to openstack.org: FEBRUARY 1 IS THE DEADLINE TO SUBMIT A TALK (11:59PM PST) I tried to edit a submitted talk and got the following message: Call for speaker closed! Also I have the following note in my interface: Warning! You reached

[openstack-dev] [mistral] Team meeting - 02/01/2016

Hi, This is a reminder about a team meeting that we’ll have today at 16.00 UTC. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Review M-3 BPs and bugs Open discussion Renat Akhmerov @ Mirantis Inc.

Re: [openstack-dev] [mistral] Promoting Anastasia Kuznetsova to core reviewers

Hi, great work, Anastasia! +1 for you! On Fri, Jan 29, 2016 at 11:27 AM, Lingxian Kong wrote: > +1 from me, welcome Anastasia! > > On Fri, Jan 29, 2016 at 9:00 PM, Igor Marnat wrote: > >> Folks, >> I'm not a core reviewer, but if I was, I'd

Re: [openstack-dev] Call for papers already closed?

On 02/01/2016 08:46 AM, Wang, Shane wrote: Yes, I was confused too. The time is yet up. It should not be closed, but it is at the moment :/ I forwarded my previous mail to sum...@openstack.org and hope that somebody can take care of this issue. Christian. -- Christian Berendt Cloud

[openstack-dev] [Cinder] the spec of Add-ServiceGroup-using-Tooz

Hi all, I proposed the spec of Add-ServiceGroup-using-Tooz in Ciner[1]. Project doctor[2] in OPNFV community is its upstream. The goal of this project is to build fault management and maintenance framework for high availability of Network Services on top of virtualized

Re: [openstack-dev] [Cinder] the spec of Add-ServiceGroup-using-Tooz

Hi, dong.wenjuan Sounds very interesting about "doctor" project. What's timezone about the weekly meeting? I want to join it if I have time by then. Thanks Wang Hao 2016-02-01 14:43 GMT+08:00 : > > Hi all, > > I proposed the spec of Add-ServiceGroup-using-Tooz in

Re: [openstack-dev] Call for papers already closed?

Yes, I was confused too. The time is yet up. -- Shane -Original Message- From: Christian Berendt [mailto:christ...@berendt.io] Sent: Sunday, January 31, 2016 11:43 PM To: OpenStack Development Mailing List Subject: [openstack-dev] Call for papers already closed? Hello. I am a little

[openstack-dev] [Magnum]Remove node object from Magnum

Hi all, I want to remove node object from Magnum. The node object represents either a bare metal or virtual machine node that is provisioned with an OS to run the containers, or alternatively, run kubernetes. Magnum use Heat to deploy the nodes, so it is unnecessary to maintain node object in

Re: [openstack-dev] [Cinder] the spec of Add-ServiceGroup-using-Tooz

Hi Whang Hao, OPNFV Doctor meeting details can be found here: https://wiki.opnfv.org/meetings/doctor Br, Tomi From: EXT hao wang [mailto:sxmatch1...@gmail.com] Sent: Monday, February 01, 2016 9:00 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

Re: [openstack-dev] [keystone][cross-project] Standardized role names and policy

On 01/30/2016 08:24 PM, Henry Nash wrote: On 30 Jan 2016, at 21:55, Adam Young > wrote: On 01/30/2016 04:14 PM, Henry Nash wrote: Hi Adam, Fully support this kind of approach. I am still concerned over the scope check, since we do have examples

[openstack-dev] [nova-scheduler] Scheduler sub-group meeting - Agenda 2/1

Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT) 1) Mid-cycle meetup report back. 2) Spec & BPs & Patches - https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking 3) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler 4) Opens -- Don Dugger "Censeo Toto nos in

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-28 5:37 GMT+09:00 Ryan Brown : >> >> I think we would be better served in selecting these things thinking >> about the API consumers first. We already have enough for them to wade >> through, the API-WG is making great gains in herding those particular >> cats, I

Re: [openstack-dev] [nova][API] Question about HTTPNotImplementError

Hi Chen, The API guideline came from this Nova's implementation. 501 case is not exception of microversion bumping[1] on Nova's rule now, so I feeling we need a new microversion if changing the 501 response to the other on *current rule*. However, such microversion seems a little overkill for me.

Re: [openstack-dev] [keystone] changes to keystone-core!

++ I'm happy to see this go through! Samuel and Dave have been helping me out a lot lately. Both make great additions to the team! On Thu, Jan 28, 2016 at 9:12 AM, Brad Topol wrote: > CONGRATULATIONS Dave and Samuel. Very well deserved!!! > > --Brad > > > Brad Topol, Ph.D. >

Re: [openstack-dev] Any chances to backport port_security_enabled support into Heat for Kilo 2015.1.3?

On 31 January 2016 at 18:23, Steve Baker wrote: > On 29/01/16 09:45, Martinx - ジェームズ wrote: >> >> Guys, >> >> This is important and Kilo is missing it: >> >> https://review.openstack.org/#/c/179989/ >> >> Is it possible to backport it to Kilo 2015.1.3? >> >> Currently,

[openstack-dev] [stable][trove] Need help with replication API test failures on stable/liberty

I opened this bug awhile back: https://bugs.launchpad.net/trove/+bug/1538506 The periodic stable jobs have been failing for trove on stable/liberty. It looks like this could be a related change on master that we might want to get into stable/liberty, basically to disable these tests:

[openstack-dev] [Kuryr] IRC Meeting - Monday (2/1) 1500 UTC (#openstack-meeting-4)

Hello All, We are going to have an IRC Meeting tomorrow (2/1) at 1500 UTC in #openstack-meeting-4 The meeting agenda can be seen here [1]. We are going to focus most of the meeting on the Kubernetes-Kuryr integration. You can view the logs from our specific Kuryr-Kubernetes integration IRC

Re: [openstack-dev] [Kuryr] IRC Meeting - Monday (2/1) 1500 UTC (#openstack-meeting-4)

On Sun, Jan 31, 2016 at 12:57 PM, Gal Sagie wrote: > > Hello All, > > We are going to have an IRC Meeting tomorrow (2/1) at 1500 UTC > in #openstack-meeting-4 > > The meeting agenda can be seen here [1]. > We are going to focus most of the meeting on the Kubernetes-Kuryr >

Re: [openstack-dev] [Horizon] It's already too late for ... Updating XStatic packages

On 01/06/2016 06:18 PM, Rob Cresswell (rcresswe) wrote: > Hi all, > > While the automated system is broken, I’d like to work on manually > releasing a few of the XStatic packages. This will *only* be the release > stage; we will still use gerrit to review the package content as usual. > > List

Re: [openstack-dev] Upstream University: Signup for Mentors and Mentees

Hi there! This is awesome! I participated in previous Upstream Training events and it's a very exciting and enriching experience. I'm looking forward to join this time again and I hope to see many people joining this initiative. Count on me for organization or anything else beyond mentoring.

Re: [openstack-dev] [puppet] Stepping down from Puppet Core

Mathieu, Thank you for everything you've done during the past years, your excellent work makes puppet community more better. And personally, you give me lots of guidance when I get started. Wish you all the best in the new journey. 2016-01-28 4:13 GMT+08:00 Mathieu Gagné :

[openstack-dev] [nova] Non-priority Feature Freeze update (including deadlines)

Hi, We have recently past the deadline for the non-priority Feature Freeze: http://docs.openstack.org/releases/schedules/mitaka.html#m-nova-npff We do this to make sure we prioritise review and developer bandwidth for Bug Fixes and our agreed release priorities: