[openstack-dev] [nova][neutron] Is it still valid/supported to create a network with a br- id?

The nova create-server API allows passing a network id that's prefixed with br- [1]. That was added due to this bug from Folsom [2]. I'm wondering if that's still valid? Looking at the network.id data model in Neutron it doesn't look like it would be [3]. I'm trying to sort this out for the

[openstack-dev] [tc] [all] [glance] On operating a high throughput or otherwise team

Hi all, Lately I have been involved in discussions that have resulted in giving a wrong idea to the approach I take in operating the (Glance) team(s). While my approach is consistency, coherency and agility in getting things done (especially including the short, mid as well as long term plans),

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

On 5/14/16 2:35 PM, Mike Perez wrote: > On 18:46 May 12, Nikhil Komawar wrote: >> I realized that I missed one of your questions earlier. Response for >> that inline. >> >> >> On 5/12/16 4:58 PM, Nikhil Komawar wrote: >>> >>> On 5/12/16 4:33 PM, Doug Hellmann wrote: Excerpts from Nikhil

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

On 18:46 May 12, Nikhil Komawar wrote: > I realized that I missed one of your questions earlier. Response for > that inline. > > > On 5/12/16 4:58 PM, Nikhil Komawar wrote: > > > > > > On 5/12/16 4:33 PM, Doug Hellmann wrote: > >> Excerpts from Nikhil Komawar's message of 2016-05-12 15:40:05

Re: [openstack-dev] [tc] supporting Go

Excerpts from Dieterly, Deklan's message of 2016-05-14 01:18:20 +: > Python 2.x will not be supported for much longer, and let¹s face it, > Python is easy, but it just does not scale. Nor does Python have the > performance characteristics that large, distributed systems require. Maybe > Java

Re: [openstack-dev] [tc] supporting Go

Why is that? Thank you, Mark On 5/13/2016 7:21 PM, Dieterly, Deklan wrote: If we allow Go, then we should also consider allowing JVM based languages. -- Deklan Dieterly Senior Systems Software Engineer HPE On 5/13/16, 2:10 PM, "Adam Young" wrote: >Can we just up and

[openstack-dev] [Higgins] weekly team meeting time

Hi all, As discussed, we are going to hold weekly team meetings. I would like to invite you to the Doodle poll "Higgins team weekly meeting", in which you can choose your preferred meeting time. Please follow the link in order to participate in the poll: http://doodle.com/poll/36mrihhkpxhnf6rf

Re: [openstack-dev] [tacker]ad-hoc meeting of May 16

Hi, I was thinking that autoscaling is the topic very relevant to senlin. Regards, Qiming On Fri, May 13, 2016 at 12:31:42PM +, Bruce Thompson (brucet) wrote: > Qiming, > > I don¹t think we will be discussing Senlin as part of the agenda in this > meeting. Is there a Senlin topic that you

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

On Fri, 13 May 2016 17:13:59 -0700 "Armando M." wrote: > On 13 May 2016 at 16:10, Elzur, Uri wrote: > > > Hi Cathy > > > > > > > > Thank you for the quick response. This is the essence of my > > question – does Neutron keep OvS as a gold standard and why

Re: [openstack-dev] [Neutron][QA] Call to action - Neutron/Tempest API tests dedup

On Sat, May 14, 2016 at 8:03 AM, zhi wrote: > hi, Muller. > > As you mentioned, is there will have a individual Tempest plugin named > "Neutron Tempest plugin" in future? It already exists :)

Re: [openstack-dev] [Docs] Enhance Docs Landing Page Descriptive Text

Hi. Short answer: Very good idea, I'd like to see the spec. Slightly longer: Moving this information to the docs landing page, it will increase the visibility of Big Tent projects and it's a way for operators to know what's available. It partially addresses our concern about treating Big Tent

Re: [openstack-dev] [Neutron][QA] Call to action - Neutron/Tempest API tests dedup

hi, Muller. As you mentioned, is there will have a individual Tempest plugin named "Neutron Tempest plugin" in future? Thanks Zhi Chang 2016-05-14 6:53 GMT+08:00 Assaf Muller : > TL;DR: I'm looking for volunteers for tasks 1, 2 and 3 listed below. > Help would be hugely

[openstack-dev] [group-based-policy] Can PTs move to other PTGs?

Hi GBP, While I was working on the QoS PoC for GBP I observed that policy targets require to be associated to a PTG. They also don't seem to be updatable with a different PTG, at least not with the CLI. However, looking at the API I see, for policy targets: 'policy_target_group_id':

Re: [openstack-dev] [tricircle] [Blueprint] Stateless design definition

Hi Team, Sorry for this spam -; Please ignore previous message. I will file that as a doc bug. Cheers, S On Sat, May 14, 2016 at 3:36 PM, Shinobu Kinjo wrote: > Hi Team, > > In page1, we define "stateless design" as follows: > > Note: Stateless proposal is working on

[openstack-dev] [tricircle] [Blueprint] Stateless design definition

Hi Team, In page1, we define "stateless design" as follows: Note: Stateless proposal is working on the “experiment” branch: https://github.com/openstack/tricircle/tree/experiment But, in section 7, we define this design as follows: A PoC was done to verify the feasibility of stateless