Re: [openstack-dev] [tempest] Discussion on to enable "Citrix XenServer CI" to vote openstack/tempest

Added project prefix in the subject and loop in Masayuki and Ghanshyam who know the background as well. Thanks. Jianghua From: Jianghua Wang Sent: Tuesday, June 14, 2016 12:46 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Jianghua Wang Subject: Discussion on to enable

Re: [openstack-dev] [nova] Initial oslo.privsep conversion?

One of the challenges with nova (and I'm working from some earlier conversations, not a first-hand reading of the code) is that we can't restrict file operations to any particular corner of the filesystem, because the location of the libvirt data is stored (only) in the database, and the database

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John, OK, I also find the column "port_pairs" and "flow_classifiers" can not be wrote by idl APIs, I will try to fix it. If any update, i will send you email. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road,

[openstack-dev] Discussion on to enable "Citrix XenServer CI" to vote openstack/tempest

Hi all, Recently the "Citrix XenServer CI" was broken due to a bad commit[1] to openstack/tempest. As the commit was merged on Friday which is vacation at here, it had been in failure for more than three days before we noticed and fixed[2] this problem. As this CI votes for openstack/nova,

Re: [openstack-dev] [Aodh] Ordering Alarm severity on context

From: Sanjana Pai Nagarmat Sent: Tuesday, June 14, 2016 9:46 AM To: openstack-dev@lists.openstack.org Subject: [Aodh] Hi All, This is with respect to the bug https://launchpad.net/bugs/1452254 , which orders the severity of alarms based on context rather than sorting it alphabetically. My

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Juno, Added you to my private repos Regards John Sent from my iPhone On Jun 13, 2016, at 7:39 PM, Na Zhu > wrote: Hi John, My github account is JunoZhu, pls add me as member of your private repo. If you submit WIP patch today, then i can update

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Juno, Trying to implement this today showed that this will not work for OVN. I am going back to RussellB 's original model with port-chain as a child of lswitch. I can make this work and then we can evolve from there. It will require some re-write of the idl code - hopefully I will get it done

[openstack-dev] [Aodh]

Hi All, This is with respect to the bug https://launchpad.net/bugs/1452254 , which orders the severity of alarms based on context rather than sorting it alphabetically. My code is out for review at https://review.openstack.org/#/c/328230 . I would like to know your opinion, on the approach I

Re: [openstack-dev] [Higgins] Call for contribution for Higgins API design

Hi, Hongbin, Yes, those urls are just information for our work. We will create a etherpad page to collaborate. 2016年6月11日(土) 7:38 Hongbin Lu : > Yuanying, > > > > The etherpads you pointed to were a few years ago and the information > looks a bit outdated. I think we

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

That is already supported in stable/mitaka – please see https://review.openstack.org/#/c/260700/ I agree with Kevin From: Kevin Benton Reply-To: OpenStack List Date: Monday, June 13, 2016 at 11:59 PM To: OpenStack List

[openstack-dev] [daisycloud-core] IRC weekly meeting logistics

Hi Team, Here is the IRC weekly meeting logistics: Weekly on Friday at 1200 UTC, You can check out your local time here: http://www.timeanddate.com/worldclock/fixedtime.html?hour=12=0=0 IRC channel: #daisycloud at freenode So our first meeting will be on this friday (Jun 17). The Agenda

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John, I see you add column "port_pairs" and "flow_classifiers" to table Logical_Switch, I am not clear about it, the port-pair ingress port and egress port can be the same, they also can be different and in same/different network, and the flow classifier is not per network neither, can you

[openstack-dev] "OpenStack-dev" mailing list

Email : sanj...@hitachi.co.in Thanks and Regards, Sanjana -Original Message- From: openstack-dev-requ...@lists.openstack.org [mailto:openstack-dev-requ...@lists.openstack.org] Sent: Tuesday, June 14, 2016 8:52 AM To: Sanjana Pai Nagarmat Subject: Welcome to the "OpenStack-dev" mailing

Re: [openstack-dev] [puppet] vision on new modules

On Wed, Jun 8, 2016 at 2:42 PM, Emilien Macchi wrote: > Hi folks, > > Over the last months we've been creating more and more modules [1] [2] > and I would like to take the opportunity to continue some discussion > we had during the last Summits about the quality of our

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John, My github account is JunoZhu, pls add me as member of your private repo. If you submit WIP patch today, then i can update your WIP patch, no need to update your private repo. If not, i will update your private repo. Thanks. Regards, Juno Zhu IBM China Development Labs (CDL) Cloud

Re: [openstack-dev] [magnum] Notes for Magnum design summit

Hi Hongbin, Thank you for your guidance. I’ll take a look at the related existing blueprints and patches to see whether there are any duplicated jobs first. Regards, Gary From: Hongbin Lu [mailto:hongbin...@huawei.com] Sent: Monday, June 13, 2016 10:58 PM To: OpenStack Development Mailing List

Re: [openstack-dev] [magnum] Notes for Magnum design summit

Hi Sypros, Thank you for pointing out the blueprint and the patch. What we have done is modifying the existing kubecluster-ironic, kubemaster –ironic and kubeminion-ironic yaml files. I take a look at the blueprint and the patch you pointed out. Regards, Gary From: Spyros Trigazis

Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice

+1 Thanks -yuanying 2016年6月14日(火) 10:55 Kai Qiang Wu : > +1 Welcome to new one :) > > > > Thanks > > Best Wishes, > > > Kai Qiang Wu (吴开强 Kennan） > IBM China System and Technology Lab, Beijing > >

Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice

+1 Welcome to new one :) Thanks Best Wishes, Kai Qiang Wu (吴开强 Kennan） IBM China System and Technology Lab, Beijing E-mail: wk...@cn.ibm.com Tel: 86-10-82451647 Address: Building 28(Ring Building), ZhongGuanCun

Re: [openstack-dev] [magnum] Need helps to implement the full baremetals support

Hi, Spyros I updated ironic heat template, and succeeded booting k8s bay with Ironic. Could you test it? Unfortunately there are some problem and requirement to test. I describe below. * subnet which belongs to private network should be set up with dns_nameservers like following. $ neutron

Re: [openstack-dev] [nova] Let me know if you have an approved spec but unapproved blueprint

Hi, Matt, Thank you for the clarification. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] Sent: Monday, June 13, 2016 9:07 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova] Let me know if

Re: [openstack-dev] [octavia] enabling new topologies

Hey Sergey, In-line comments below: On Sun, Jun 5, 2016 at 8:07 AM, Sergey Guenender wrote: > > Hi Stephen, please find my reply next to your points below. > > Thank you, > -Sergey. > > > On 01/06/2016 20:23, Stephen Balukoff wrote: > > Hey Sergey-- > > > > Apologies for the

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Monday, June 13, 2016 6:28 AM, Daniel P. Berrange wrote: > > On Mon, Jun 13, 2016 at 07:39:29AM -0400, Assaf Muller wrote: > > On Mon, Jun 13, 2016 at 4:35 AM, Daniel P. Berrange > wrote: > > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > > >> Hi, > >

[openstack-dev] [neutron] Neutron Common Flow Classifier meeting 6/14 UTC 1700

Hi everyone, We will have the second meeting discussion on Common Flow classifier at 1700 UTC on openstack-meeting channel 6/14/2016. Please refer to the wiki page for more meeting information. https://wiki.openstack.org/wiki/Neutron/CommonFlowClassifier Thanks, Cathy

Re: [openstack-dev] [TripleO] Proposal for a new tool: dlrn-repo

On 13 June 2016 at 21:29, Ben Nemec wrote: > So our documented repo setup steps are three curls, a sed, and a > multi-line bash command. And the best part? That's not even what we > test. The commands we actually use in tripleo.sh --repo-setup consist > of the

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

So, I think it depends what level of compatibility we are aiming at. Let me articulate them, and we can agree which we want: C1) In all version of the our APIs today (v2 and v3.0 to v3.6), you have been able to issue an auth request which used project/tenant name as the scoping directive (with

[openstack-dev] The oslo-incubator and you

Hi all, I just wanted to let everyone know that the oslo-incubator[1, 2] repository is now officially closed for business (it has been deprecated for a long time now) and that it would be much appreciated that any projects with code (or open reviews to remove that code) to merge those sooner

[openstack-dev] [kolla] reclaimed the kolla namespace on docker

Hey folks, Kuan Yi Ming @ Docker helped us reclaim the kolla namespace for our images. If you are a core reviewer and would like access to push to the docker hub in the kolla namespace, please send me your email address offline with your interest. Thanks -steve

[openstack-dev] [ceilometer] [stable] Re: [Openstack-stable-maint] Stable check of openstack/ceilometer failed

-Original Message- From: A mailing list for the OpenStack Stable Branch test reports. Reply: openstack-dev@lists.openstack.org Date: June 13, 2016 at 01:13:54 To: openstack-stable-ma...@lists.openstack.org

[openstack-dev] [stable] Re: [Openstack-stable-maint] Stable check of openstack/nova failed

-Original Message- From: A mailing list for the OpenStack Stable Branch test reports. Reply: openstack-dev@lists.openstack.org Date: June 13, 2016 at 01:14:18 To: openstack-stable-ma...@lists.openstack.org

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/neutron failed

-Original Message- From: A mailing list for the OpenStack Stable Branch test reports. Reply: openstack-dev@lists.openstack.org Date: June 9, 2016 at 01:26:01 To: openstack-stable-ma...@lists.openstack.org

Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port isActive

As for the notifier proposed above it is correct that neutron needs to be changed. This should not be a massive amount of work. Today it works with nova only pretty much because nova it's the only compute service it interacts with. The question brought aboud ping vs operational status is a very

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

+1. Neutron should already be able to tell Nova which bridge to use for an OVS port.[1] For the Linux bridge implementation it's a matter of creating vlan interfaces and plugging them into bridges like regular VM ports, which is all the responsibility of the L2 agent. We shouldn't need any changes

[openstack-dev] [TripleO] Proposal for a new tool: dlrn-repo

So our documented repo setup steps are three curls, a sed, and a multi-line bash command. And the best part? That's not even what we test. The commands we actually use in tripleo.sh --repo-setup consist of the following: three curls, four seds, and (maybe) the same multi-line bash command.

Re: [openstack-dev] [openstack-ansible] Mid-cycle date selection (need input!)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/09/2016 01:51 PM, Major Hayden wrote: > Once we get that sorted out, we can fire up an etherpad for everyone to sign > up for a spot. As promised, here's a link to the etherpad: https://etherpad.openstack.org/p/osa-midcycle-newton Please

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

Excerpts from Dolph Mathews's message of 2016-06-13 20:11:57 +: > On Fri, Jun 10, 2016 at 12:20 PM Clint Byrum wrote: > > > Excerpts from Henry Nash's message of 2016-06-10 14:37:37 +0100: > > > On further reflection, it seems to me that we can never simply enable > >

Re: [openstack-dev] [neutron][ovs] The way we deal with MTU

> So basically, as long as we try to plug ports with different MTUs into the > same bridge, we are utilizing a bug in Open vSwitch, that may break us any > time. > > I guess our alternatives are: > - either redesign bridge setup for openvswitch to e.g. maintain a bridge per > network; > - or

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

Hmm... I tried Friday and again today, and I'm not seeing the VMs being evenly created on the NUMA nodes. Every Cirros VM is created on nodeid 0. I have the m1/small flavor (@GB) selected and am using hw:numa_nodes=1 and hw:mem_page_size=2048 flavor-key settings. Each VM is consuming 1024 huge

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

On Fri, Jun 10, 2016 at 12:20 PM Clint Byrum wrote: > Excerpts from Henry Nash's message of 2016-06-10 14:37:37 +0100: > > On further reflection, it seems to me that we can never simply enable > either of these approaches in a single release. Even a v4.0 version of the > API

[openstack-dev] [Infra] Meeting Tuesday June 14th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday June 14th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agenda

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Hi Doug I've written a few Ansible OpenStack modules, for example: https://github.com/ansible/ansible-modules-extras/pull/2240 Some pending merge, some others already merged. Regards 2016-06-13 21:41 GMT+02:00 Doug Hellmann : > Thanks! > > > On Jun 13, 2016, at 3:23

Re: [openstack-dev] [neutron][networking-sfc] Proposing Mohan Kumar for networking-sfc core

+1. Great addition to the team! On Mon, Jun 13, 2016 at 11:48 AM, Henry Fourie wrote: > +1 > > > > *From:* Cathy Zhang > *Sent:* Monday, June 13, 2016 11:36 AM > *To:* openstack-dev@lists.openstack.org; Cathy Zhang > *Subject:* [openstack-dev] [neutron][networking-sfc]

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Thanks! > On Jun 13, 2016, at 3:23 PM, Anita Kuno wrote: > > On 06/13/2016 03:11 PM, Doug Hellmann wrote: >> I'm trying to pull together some information about contributions >> that OpenStack community members have made *upstream* of OpenStack, >> via code, docs, bug

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Excerpts from Joshua Harlow's message of 2016-06-13 12:28:41 -0700: > Just to clarify, upstream of openstack would be say in a library that > interacts with openstack (jclouds for example); or docs that jclouds has > about openstack or something like that? > > Or do u mean upstream of openstack

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Just to clarify, upstream of openstack would be say in a library that interacts with openstack (jclouds for example); or docs that jclouds has about openstack or something like that? Or do u mean upstream of openstack to mean anything not openstack but openstack related (for example there are

[openstack-dev] [release] new mailing list for tracking release job failures

The kind folks on the infra team are helping to set things up so that we have notifications for release failures, so we don't have to manually check or wait to see if a package we think was released doesn't get uploaded to PyPI. Members of the release team should subscribe to the

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

On 06/13/2016 03:11 PM, Doug Hellmann wrote: > I'm trying to pull together some information about contributions > that OpenStack community members have made *upstream* of OpenStack, > via code, docs, bug reports, or anything else to dependencies that > we have. > > If you've made a contribution

Re: [openstack-dev] [TripleO] Nodes Registration workflow improvements

On 06/13/2016 12:10 PM, Dmitry Tantsur wrote: > On 06/13/2016 06:28 PM, Ben Nemec wrote: >> On 06/13/2016 09:41 AM, Jiri Tomasek wrote: >>> Hi all, >>> >>> As we are close to merging the initial Nodes Registration workflows and >>> action [1, 2] using Mistral which successfully provides the

[openstack-dev] [all] what do you work on upstream of OpenStack?

I'm trying to pull together some information about contributions that OpenStack community members have made *upstream* of OpenStack, via code, docs, bug reports, or anything else to dependencies that we have. If you've made a contribution of that sort, I would appreciate a quick note. Please

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

On Mon, Jun 13, 2016 at 08:06:50AM +, Wang, Shane wrote: > Hi, OpenStackers, > > As you know, Huawei, Intel and CESI are hosting the 4th China OpenStack Bug > Smash at Hangzhou, China. > The 1st China Bug Smash was at Shanghai, the 2nd was at Xi'an, and the 3rd > was at Chengdu. > > We are

Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port isActive

On 06/10/2016 03:13 PM, Kevin Benton wrote: Polling should be fine. get_port operations a relatively cheap operation for Neutron. Just in principle, I would suggest this polling have a back-off built into it. Poll once, see the port is not yet "up" - wait a semi-random short length of time,

Re: [openstack-dev] [neutron][networking-sfc] Proposing Mohan Kumar for networking-sfc core

+1 From: Cathy Zhang Sent: Monday, June 13, 2016 11:36 AM To: openstack-dev@lists.openstack.org; Cathy Zhang Subject: [openstack-dev] [neutron][networking-sfc] Proposing Mohan Kumar for networking-sfc core Mohan has been working on networking-sfc project for over one year. He is a key

Re: [openstack-dev] [Higgins][Zun] Project roadmap

> -Original Message- > From: Sudipto Biswas [mailto:sbisw...@linux.vnet.ibm.com] > Sent: June-13-16 1:43 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Higgins][Zun] Project roadmap > > > > On Monday 13 June 2016 06:57 PM, Flavio Percoco wrote: > > On

[openstack-dev] [neutron][networking-sfc] Proposing Mohan Kumar for networking-sfc core

Mohan has been working on networking-sfc project for over one year. He is a key contributor to the design/coding/testing of SFC CLI, SFC Horizon, as well as ONOS controller support for SFC functionality. He has been great at helping out with bug fixes, testing, and reviews of all components of

[openstack-dev] [nfv][tacker] Tacker sessions @ OPNFV Summit, Berlin

For the folks going to OPNFV Summit @ Berlin next week, and interested in NFV Orchestration + OpenStack, please consider stopping by at the following OpenStack Tacker related sessions, 1) OPNFV Design Summit - Day 1/June 20th, https://wiki.opnfv.org/display/EVNT/Berlin+Design+Summit+Planning

[openstack-dev] [ironic] weekly sub team status report

Hi, We are thrilled to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 6 June 2016) - Ironic: 213 bugs (+9) + 182 wishlist items (+4). 15 new (+7), 147 in progress

Re: [openstack-dev] [Higgins][Zun] Project roadmap

From: Antoni Segura Puimedon [mailto:toni+openstac...@midokura.com] Sent: June-13-16 3:22 AM To: OpenStack Development Mailing List (not for usage questions) Cc: yanya...@cn.ibm.com; Qi Ming Teng; adit...@nectechnologies.in; sitlani.namr...@yahoo.in; flw...@catalyst.net.nz; Chandan Kumar; Sheel

Re: [openstack-dev] [Group-based-policy] what does policy rule action redirect do

On Mon, Jun 13, 2016 at 3:17 AM, yong sheng gong <18618199...@163.com> wrote: > hi, > > I have followed the steps at > https://github.com/openstack/group-based-policy/blob/master/gbpservice/tests/contrib/devstack/exercises/gbp_servicechain.sh > > and I can see the firewall and lb are created

Re: [openstack-dev] [neutron][ovs] The way we deal with MTU

That's interesting. In our deployments we do something like br-ex (linux bridge, mtu 9000) - OVSIntPort (mtu 65000) - br-floating (ovs bridge, mtu 1500) - br-int (ovs bridge, mtu 1500). qgs then are getting created in br-int, traffic goes all the way and that altogether allows jumbo frames over

Re: [openstack-dev] [Higgins][Zun] Project roadmap

On Monday 13 June 2016 06:57 PM, Flavio Percoco wrote: On 12/06/16 22:10 +, Hongbin Lu wrote: Hi team, During the team meetings these weeks, we collaborated the initial project roadmap. I summarized it as below. Please review. * Implement a common container abstraction for different

Re: [openstack-dev] [neutron][ovs] The way we deal with MTU

Hi Ihar, This reminds me of a mailing list thread from a while back about moving OVS ports between namespaces being considered harmful [1]. Do you know if that was ever resolved by the OVS folks? Or, is this MTU bug just further indication of this action being harmful? Another comment inline.

Re: [openstack-dev] [javascript] Meeting time doodle

Productive meeting this morning, everyone. As agreed, we'll be meeting weekly at 1400UTC. I had to change the meeting time from Monday to Wednesday though, because twice-a-month there were not meeting channels available. Since Wednesday at 1400UTC was also available in the former doodle poll, I

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

So is this horse dead now, 'cuz I wanna turn hitting it... First of all, this thread brings up two separate messaging concepts: 1) at-least-once delivery 2) message acknowledgement For #1 - oslo.messaging cannot guarantee that messages will not be duplicated. Specifically in the case of

Re: [openstack-dev] [TripleO] Nodes Registration workflow improvements

On 06/13/2016 06:28 PM, Ben Nemec wrote: On 06/13/2016 09:41 AM, Jiri Tomasek wrote: Hi all, As we are close to merging the initial Nodes Registration workflows and action [1, 2] using Mistral which successfully provides the current registration logic via common API, I'd like to start

Re: [openstack-dev] [release][infra] os-brick 1.4.0 not on our pypi mirrors

Thanks a ton Jeremy! On Mon, Jun 13, 2016 at 9:46 AM, Jeremy Stanley wrote: > On 2016-06-11 21:08:14 -0400 (-0400), Davanum Srinivas wrote: >> Can someone nudge the banderstanch thingy please? >> >> Release in pypi: >> https://pypi.python.org/pypi/os-brick/1.4.0 >> >> Error in

[openstack-dev] [neutron][ovs] The way we deal with MTU

Hi all, in Mitaka, we introduced a bunch of changes to the way we handle MTU in Neutron/Nova, making sure that the whole instance data path, starting from instance internal interface, thru hybrid bridge, into the br-int; as well as router data path (qr) have proper MTU value set on all

Re: [openstack-dev] [new][cinder] os-brick 1.4.0 release (newton)

This release broke gate and will be blocked in g-r: https://bugs.launchpad.net/os-brick/+bug/1592043 > On 13 Jun 2016, at 18:42, no-re...@openstack.org wrote: > > We are content to announce the release of: > > os-brick 1.4.0: OpenStack Cinder brick library for managing local > volume attaches

[openstack-dev] [new][cinder] os-brick 1.4.0 release (newton)

We are content to announce the release of: os-brick 1.4.0: OpenStack Cinder brick library for managing local volume attaches This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/os-brick With package available at:

Re: [openstack-dev] [release][infra] os-brick 1.4.0 not on our pypi mirrors

On 2016-06-11 21:08:14 -0400 (-0400), Davanum Srinivas wrote: > Can someone nudge the banderstanch thingy please? > > Release in pypi: > https://pypi.python.org/pypi/os-brick/1.4.0 > > Error in Nova: >

Re: [openstack-dev] [TripleO] Nodes Registration workflow improvements

On 06/13/2016 09:41 AM, Jiri Tomasek wrote: > Hi all, > > As we are close to merging the initial Nodes Registration workflows and > action [1, 2] using Mistral which successfully provides the current > registration logic via common API, I'd like to start discussion on how > to improve it so it

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Juno, What ever is easiest for you – I can submit WIP patches today for networking-ovn and networking-ovs. If you send me your github login I will add you as a collaborator to my private repo. I am currently working on getting the changes into ovs/ovn ovn-northd.c to support the new schema –

Re: [openstack-dev] [TripleO] Nodes Registration workflow improvements

On 06/13/2016 04:41 PM, Jiri Tomasek wrote: Hi all, As we are close to merging the initial Nodes Registration workflows and action [1, 2] using Mistral which successfully provides the current registration logic via common API, I'd like to start discussion on how to improve it so it satisfies

Re: [openstack-dev] [rally] "Failed to create the requested number of tenants" error

hi Nate, It looks like I know the core of your issue. We will try to fix it as soon as possible. On Fri, Jun 10, 2016 at 6:05 PM, Nate Johnston wrote: > Running 'rally deployment check' appears to come up with good results: > > > keystone endpoints are valid and

Re: [openstack-dev] [magnum] Notes for Magnum design summit

Gary, It is hard to tell if your change fits into Magnum upstream or not, unless there are further details. I encourage you to upload your changes to gerrit, so that we can review and discuss it inline. Also, keep in mind that the change might be rejected if it doesn’t fit into upstream

[openstack-dev] [TripleO] Nodes Registration workflow improvements

Hi all, As we are close to merging the initial Nodes Registration workflows and action [1, 2] using Mistral which successfully provides the current registration logic via common API, I'd like to start discussion on how to improve it so it satisfies GUI and CLI requirements. I'd like to try

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

Hi All, A friendly reminder that we will have the next Cinder-Nova API changes meeting in a few hours at 1700UTC on #openstack-meeting-cp. For the ongoing work items and agenda details please see the following etherpad: https://etherpad.openstack.org/p/cinder-nova-api-changes Thanks and Best

Re: [openstack-dev] [heat][TripleO] Adding interfaces to environment files?

On 06/08/2016 07:00 AM, Jiri Tomasek wrote: > > On Wed, Jun 8, 2016 at 11:23 AM, Steven Hardy > wrote: > > On Tue, Jun 07, 2016 at 04:53:12PM -0400, Zane Bitter wrote: > > On 07/06/16 15:57, Jay Dobies wrote: > > > > > > > > 1. Now

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.06.14 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160614T17 __ OpenStack

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John, I know you are busy recently, sorry to disturb you. I want to ask you whether I can submit patch to your private repo, I test your code changes and find some minor errors, I think we can work together to make the debug work done faster, then you can submit the WIP patch. What do you

Re: [openstack-dev] [Higgins][Zun] Project roadmap

On 12/06/16 22:10 +, Hongbin Lu wrote: Hi team, During the team meetings these weeks, we collaborated the initial project roadmap. I summarized it as below. Please review. * Implement a common container abstraction for different container runtimes. The initial implementation will focus

[openstack-dev] weekly meeting #85

Hi Puppeteers! We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting-4. Here's a first agenda: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160614 Feel free to add more topics, and any outstanding bug and patch. See you tomorrow! Thanks, -- Emilien

[openstack-dev] [Openstack] OpenStack Newton B1 for Ubuntu 16.04 LTS and Ubuntu 16.10

Hi All, The Ubuntu OpenStack team is pleased to announce the general availability of the OpenStack Newton B1 milestone in Ubuntu 16.10 and for Ubuntu 16.04 LTS via the Ubuntu Cloud Archive. Ubuntu 16.04 LTS You can enable the Ubuntu Cloud Archive pocket for OpenStack

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

> -Original Message- > From: Daniel P. Berrange [mailto:berra...@redhat.com] > Sent: Monday, June 13, 2016 1:12 PM > To: Armando M. > Cc: Carl Baldwin ; OpenStack Development Mailing > List ; Jay Pipes >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Mon, Jun 13, 2016 at 07:39:29AM -0400, Assaf Muller wrote: > On Mon, Jun 13, 2016 at 4:35 AM, Daniel P. Berrange > wrote: > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > >> Hi, > >> > >> You may or may not be aware of the vlan-aware-vms effort [1] in >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 13 June 2016 at 14:11, Daniel P. Berrange wrote: > On Mon, Jun 13, 2016 at 02:08:30PM +0200, Armando M. wrote: > > On 13 June 2016 at 10:35, Daniel P. Berrange > wrote: > > > > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > > > >

Re: [openstack-dev] [Neutron] Random IP address allocations

I think for a major change like this we should have at least had a mail list discussion. On 6/10/16, 7:24 PM, "Carl Baldwin" wrote: >On Fri, Jun 10, 2016 at 2:40 AM, Gary Kotton wrote: >> Hi, >> The patch https://review.openstack.org/#/c/292207/ has

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Mon, Jun 13, 2016 at 02:08:30PM +0200, Armando M. wrote: > On 13 June 2016 at 10:35, Daniel P. Berrange wrote: > > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > > > Hi, > > > > > > You may or may not be aware of the vlan-aware-vms effort [1] in > > >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 13 June 2016 at 10:35, Daniel P. Berrange wrote: > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > > Hi, > > > > You may or may not be aware of the vlan-aware-vms effort [1] in > > Neutron. If not, there is a spec and a fair number of patches in > >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Mon, Jun 13, 2016 at 4:35 AM, Daniel P. Berrange wrote: > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: >> Hi, >> >> You may or may not be aware of the vlan-aware-vms effort [1] in >> Neutron. If not, there is a spec and a fair number of patches in >>

[openstack-dev] [Group-based-policy] what does policy rule action redirect do

hi, I have followed the steps at https://github.com/openstack/group-based-policy/blob/master/gbpservice/tests/contrib/devstack/exercises/gbp_servicechain.sh and I can see the firewall and lb are created right. But I thought the vm client-1's traffic will be redirected to firewall, lb and

Re: [openstack-dev] [qa] Tempest unstable interfaces in plugins

On Sun, Jun 12, 2016 at 2:25 PM Assaf Muller wrote: > On Sat, Jun 11, 2016 at 4:04 PM, Ken'ichi Ohmichi > wrote: > > 2016-06-10 17:01 GMT-07:00 Assaf Muller : > >> On Fri, Jun 10, 2016 at 12:02 PM, Andrea Frittoli > >>

[openstack-dev] [Group-based-policy] what does policy rule action redirect do

hi, I have followed the steps athttps://github.com/openstack/group-based-policy/blob/master/gbpservice/tests/contrib/devstack/exercises/gbp_servicechain.sh and I can see the firewall and lb are created right. But I thought the vm client-1's traffic will be redirected to firewall, lb and last to

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

On Mon, Jun 13, 2016 at 08:06:50AM +, Wang, Shane wrote: > Hi, OpenStackers, > > As you know, Huawei, Intel and CESI are hosting the 4th China OpenStack Bug > Smash at Hangzhou, China. > The 1st China Bug Smash was at Shanghai, the 2nd was at Xi'an, and the 3rd > was at Chengdu. > > We are

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

Hi, Are there plans to follow the OpenStack events policy this time? eg Commercial participants should have equal opportunity to sponsor and support the activity. When the number of sponsorships is limited, a best practice is to publish a sponsorship prospectus online on a date known in

Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice

+1 On Fri, Jun 10, 2016 at 5:32 PM, Shuu Mutou wrote: > Hi team, > > I propose the following changes to the magnum-ui core group. > > + Thai Tran > http://stackalytics.com/report/contribution/magnum-ui/90 > I'm so happy to propose Thai as a core reviewer. > His

Re: [openstack-dev] [TripleO] Proposed TripleO core changes

On 09/06/16 17:03, Steven Hardy wrote: > Hi all, > > I've been in discussion with Martin André and Tomas Sedovic, who are > involved with the creation of the new tripleo-validations repo[1] > > We've agreed that rather than create another gerrit group, they can be > added to tripleo-core and

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > Hi, > > You may or may not be aware of the vlan-aware-vms effort [1] in > Neutron. If not, there is a spec and a fair number of patches in > progress for this. Essentially, the goal is to allow a VM to connect > to multiple Neutron

[openstack-dev] [Dragonflow] - No IRC meeting today (06/13)

Hello all, Sorry for the late notice but we will not have an IRC meeting today. We will continue the IRC meetings next week. Thanks Gal. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Neutron] [sr-iov] rename *device* config options to *interface*

While reviewing [1] I got hung up on the terms "device" and "interface". It seems like in sr-iov agent they are used in a different manner than in the linuxbridge agent. For Example the lb agent uses a config option "physical_interface_mappings" (mapping between uplink interface for bridge and

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

Hi I would, once again, love to attend. If you find that other cores apply and you'd rather have a new face, I would be very understanding of the situation. Regards -- Duncan Thomas On 13 June 2016 at 11:06, Wang, Shane wrote: > Hi, OpenStackers, > > As you know,

  1   2   >