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

Hi John, I do not know any better approach, I think it is good to write all the parameters in the creation of a port chain, this can avoid saving many data in northbound db which are not used. We can do it in that way currently, if the community has opposite ideas, we can change, what do you

Re: [openstack-dev] StackViz is now enabled for all devstack-gate jobs

Congrats! I'm looking forward to seeing an integration/collaboration with openstack-heath :) On Tue, Jun 7, 2016 at 8:32 AM, Buckley, Tim Jason wrote: > Hello all, > > I'd like to announce that StackViz will now be running at the end all > tempest-dsvm jobs and

Re: [openstack-dev] StackViz is now enabled for all devstack-gate jobs

Congratulations! Happy to see this important milestone. Awesome job! On 6 Jun 2016 18:32, "Buckley, Tim Jason" wrote: > Hello all, > > I'd like to announce that StackViz will now be running at the end all > tempest-dsvm jobs and saving visualization output to the log

[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [Neutron][Kolla][ovs-discuss] error whenstarting neutron-openvswitch-agent service

Hi Liyong, I think may be that is a consequent. At least it is not the reason for the following error, 2016-06-06 09:19:45.236 1 ERROR neutron.agent.ovsdb.impl_vsctl [req-5b36-4eae-45d0-8240-ed9e76b04a73 - - - - -] Unable to execute ['ovs-vsctl', '--timeout=10', '--oneline',

Re: [openstack-dev] New core reviewers nomination for TOSCA-Parser and or Heat-Translator project [tosca-parser][heat-translator][heat]

Thanks core team for your +1 vote. Welcome new core - Bob, Miguel, Bharath and Mathiue. Thanks again for your great contribution!! Regards, Sahdev Zala From: Sahdev P Zala/Durham/IBM@IBMUS To: "OpenStack Development Mailing List \(not for usage questions\)"

[openstack-dev] [zaqar][zaqar-ui][i18n] Translation enabled

Hi everyone, Now, we can translate Zaqar-UI on Zanata, please translate Zaqar-UI into your native language!! Translation is another good review for Zaqar-UI, so I hope your help. See also https://wiki.openstack.org/wiki/I18nTeam Best regards, Shu Muto

Re: [openstack-dev] StackViz is now enabled for all devstack-gate jobs

Awesome work to all involved. This is really neat! :-) On Tue, Jun 7, 2016 at 9:32 AM, Buckley, Tim Jason < timothy.jas.buck...@hpe.com> wrote: > Hello all, > > I'd like to announce that StackViz will now be running at the end all > tempest-dsvm jobs and saving visualization output to the log

[openstack-dev] [TripleO] Revert "Migrate tripleo to centos-7"

Sending it again to [TripleO]. On Mon, 2016-06-06 at 20:06 -0400, Dan Prince wrote: > Hi all, > > Having a bit of a CI outage today due to (I think) the switch to > Centos > Jenkins slaves. I'd like to suggest that we revert that quickly to > keep > things moving in TripleO: > >

[openstack-dev] Revert "Migrate tripleo to centos-7"

Hi all, Having a bit of a CI outage today due to (I think) the switch to Centos Jenkins slaves. I'd like to suggest that we revert that quickly to keep things moving in TripleO: https://review.openstack.org/326182 Revert "Migrate tripleo to centos- 7" And then perhaps we can follow up with a

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

On 06/06/2016 01:44 PM, Kris G. Lindgren wrote: > Hi ironic folks, > As I'm trying to explore how GoDaddy can use ironic I've created the following > in an attempt to document some of my concerns, and I'm wondering if you folks > could help myself identity ongoing work to solve these (or

Re: [openstack-dev] [neutron][SFC]

Hi Alioune, Which OVS version are you using? Try openvswitch version 2.4.0 and restart the openvswitch-server before installing the devstack. Cathy From: Alioune [mailto:baliou...@gmail.com] Sent: Friday, June 03, 2016 9:07 AM To: openstack-dev@lists.openstack.org Cc: Cathy Zhang Subject:

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

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday June 7th, 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

[openstack-dev] StackViz is now enabled for all devstack-gate jobs

Hello all, I'd like to announce that StackViz will now be running at the end all tempest-dsvm jobs and saving visualization output to the log server. StackViz is a visualization utility for generating interactive visualizations of jobs in the OpenStack QA pipeline and aims to ease debugging and

Re: [openstack-dev] [kolla] stepping down from core

Damn, bad news:( All the best Jeff! On 6 June 2016 at 17:57, Vikram Hosakote (vhosakot) wrote: > Thanks for all the contributions to kolla and good luck Jeff! > > Regards, > Vikram Hosakote > IRC: vhosakot > > From: "Steven Dake (stdake)" > Reply-To:

Re: [openstack-dev] [kolla] stepping down from core

Thanks for all the contributions to kolla and good luck Jeff! Regards, Vikram Hosakote IRC: vhosakot From: "Steven Dake (stdake)" > Reply-To: OpenStack Development Mailing List

Re: [openstack-dev] [nova] Using image metadata to sanity check supplied authentication data at nova 'create' or 'recreate' time?

On Mon, Jun 6, 2016, at 05:44 PM, Gregory Haynes wrote: > > On Mon, Jun 6, 2016, at 05:31 PM, Michael Still wrote: >> On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote: >>> Hello all, >>> >>> At Rackspace we're running into an interesting problem: Consider >>> a user >>> who

Re: [openstack-dev] [nova] Using image metadata to sanity check supplied authentication data at nova 'create' or 'recreate' time?

On Mon, Jun 6, 2016, at 05:31 PM, Michael Still wrote: > On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote: >> Hello all, >> >> At Rackspace we're running into an interesting problem: Consider >> a user >> who boots an instance in Nova with an image which only supports SSH

Re: [openstack-dev] [nova] Using image metadata to sanity check supplied authentication data at nova 'create' or 'recreate' time?

On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote: > Hello all, > > At Rackspace we're running into an interesting problem: Consider a user > who boots an instance in Nova with an image which only supports SSH > public-key authentication, but the user doesn't provide a public

Re: [openstack-dev] [kolla] stepping down from core

Jeff, Thanks for the notification. Likewise it has been a pleasure working with you over the last 3 years on Kolla. I've removed you from gerrit. You have made a big impact on Kolla. For folks that don't know, at one point Kolla was nearly dead, and Jeff was one of our team of 3 that stuck to

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

Excerpts from Kris G. Lindgren's message of 2016-06-06 20:44:26 +: > Hi ironic folks, > As I'm trying to explore how GoDaddy can use ironic I've created the > following in an attempt to document some of my concerns, and I'm wondering if > you folks could help myself identity ongoing work to

[openstack-dev] [nova] Using image metadata to sanity check supplied authentication data at nova 'create' or 'recreate' time?

Hello all, At Rackspace we're running into an interesting problem: Consider a user who boots an instance in Nova with an image which only supports SSH public-key authentication, but the user doesn't provide a public key in the boot request. As far as I understand it, today Nova will happily boot

Re: [openstack-dev] Openstack support for bump-in-the-wire functions

Hi Sean, networking-sfc does not support bump-in-the-wire functions currently as I mentioned.The service functions are essentially L3 (ie. the MAC destination address is changed to the SF and the service function then sources the packet with its MAC address). What I am looking for is

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

Hi John, To get started with adding test scripts, I was trying to workout one end to end flow with the latest code from your private repos and found the following. create_port_chain is calling _create_ovn_vnf. This is calling self.*_ovn.create_lservice*( lservice_name = 'sfi-%s' %

Re: [openstack-dev] [TripleO] Undercloud Configuration Wizard

On 05/12/2016 03:36 AM, Dmitry Tantsur wrote: > On 05/11/2016 06:19 PM, Ben Nemec wrote: >> Hi all, >> >> Just wanted to let everyone know that I've ported the undercloud >> configuration wizard to be a web app so it can be used by people without >> PyQt on their desktop. I've written a blog post

Re: [openstack-dev] [nova][libvirt] Deprecating the live_migration_flag and block_migration_flag config options

On Mon, Jun 6, 2016 at 11:26 PM, Matt Riedemann wrote: > On 6/6/2016 12:15 PM, Matt Riedemann wrote: > >> On 1/8/2016 12:28 PM, Mark McLoughlin wrote: >> >>> On Fri, 2016-01-08 at 14:11 +, Daniel P. Berrange wrote: >>> On Thu, Jan 07, 2016 at 09:07:00PM

Re: [openstack-dev] Openstack support for bump-in-the-wire functions

Take a look at the networking-sfc project. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

Hi ironic folks, As I'm trying to explore how GoDaddy can use ironic I've created the following in an attempt to document some of my concerns, and I'm wondering if you folks could help myself identity ongoing work to solve these (or alternatives?) List of concerns with ironic: 1.)Nova <->

Re: [openstack-dev] [nova][libvirt] Deprecating the live_migration_flag and block_migration_flag config options

On 6/6/2016 12:15 PM, Matt Riedemann wrote: On 1/8/2016 12:28 PM, Mark McLoughlin wrote: On Fri, 2016-01-08 at 14:11 +, Daniel P. Berrange wrote: On Thu, Jan 07, 2016 at 09:07:00PM +, Mark McLoughlin wrote: On Thu, 2016-01-07 at 12:23 +0100, Sahid Orentino Ferdjaoui wrote: On Mon,

[openstack-dev] [swift][keystone] Using JSON as future ACL format

Hello all, Hope everyone had a good weekend, and hope this email does not ruin your next. We had a small internal discussion at IBM and here are some of the findings that I will present to the wider community. 1. The ":" separator that swift currently uses is not entirely safe since LDAP can

Re: [openstack-dev] [neutron][devstack] Does the openvswitch-agent need to be run along side the neutron-l3-agent?

The L3 agent will plug ports into things, but it doesn't know anything about wiring them up for the appropriate VXLAN/VLAN/whatever. That's all very l2 specific logic and dependent on if using linuxbridge/ovs/etc. Think of the l3 agent just like it is Nova wiring up VMs. It plugs them in and then

[openstack-dev] [kolla] stepping down from core

Hi all, This is my official announcement to leave core on Kolla / Kolla-Kubernetes. I've enjoyed working with all of you and hopefully we'll cross paths again! Jeff __ OpenStack Development Mailing List (not for usage

[openstack-dev] Openstack support for bump-in-the-wire functions

Hi, I am working with a vendor who has virtualized his appliance.The vendor's appliance is essentially a bump-in-the-wire appliance. Consider the diagram below.The vendor's appliance is B connected to ports 2 and 3.Whatever comes into B from port 2 is acted upon and then the samepacket is sent

[openstack-dev] [UX] [TripleO] TripleO UI Initial Wireframes

Hi All, I wanted to share some brainstorming we've done on the TripleO UI. I put together wireframes[1] to reflect some ideas we have on moving forward with features in the UI and would love to get any feedback you all have. Feel free to comment via this email or comment within InVision. Best,

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

Hi Matt, We are aware of the issue and have cherry picked patches pending review by the neutron stable team: https://review.openstack.org/#/q/openstack/octavia+status:open+branch:stable/mitaka https://review.openstack.org/#/q/openstack/octavia+status:open+branch:stable/liberty Michael On Mon,

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

Hi Matt, Thanks for the heads up, we are looking into it. And adding some sort of monitor. doug > On Jun 6, 2016, at 11:27 AM, Matt Riedemann > wrote: > > Can someone from the Octavia team check on the stable/liberty failures for > the unit test runs? Those

[openstack-dev] [Smaug]- IRC Meeting tomorrow (07/06) - 1500 UTC SM,

Hi All, We will hold our weekly IRC meeting today (Tuesday, 07/06) at 1500 UTC in #openstack-meeting Please review the proposed meeting agenda here: https://wiki.openstack.org/wiki/Meetings/smaug Please feel free to add to the agenda any subject you would like to discuss. This is the first

Re: [openstack-dev] [Neutron] Getting project version from API

Ihar Hrachyshka wrote: > > > On 06 Jun 2016, at 16:44, Sean M. Collins wrote: > > > > I agree, it would be convenient to have something similar to what Nova > > has: > > > > https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/versions.py#L59-L60 > > >

Re: [openstack-dev] [neutron][devstack] Does the openvswitch-agent need to be run along side the neutron-l3-agent?

Armando M. wrote: > The short answer to your question in the question is yes. For OVS, wherever > you run network services (l3 or dhcp), you need an l2 agent that in charge > of port wiring. OK - I'm going senile then. For some reason I thought the L3 agent called the same code paths for doing

Re: [openstack-dev] [tacker] Proposing Bharath Thiruveedula to Tacker core team

+1 On Fri, Jun 3, 2016 at 9:23 PM, Haddleton, Bob (Nokia - US) < bob.haddle...@nokia.com> wrote: > +1 > > Bob > > On Jun 3, 2016, at 8:24 PM, Sridhar Ramaswamy wrote: > > Tackers, > > I'm happy to propose Bharath Thiruveedula (IRC: tbh) to join the tacker > core team. Bharath

[openstack-dev] [javascript] Meeting time doodle

Between fuel, ironic, horizon, storyboard, the app ecosystem group, the partridges, the pear trees, and the kitchen sinks, there's an awful lot of JavaScript work happening in OpenStack. Enough so that it's a good idea to actually start having regular about it. I've tried to identify dates/times

Re: [openstack-dev] [Neutron][Networking-SFC] Stable/mitaka version

Gary, Yes, it will be. -Louis From: Gary Kotton [mailto:gkot...@vmware.com] Sent: Monday, June 06, 2016 2:39 AM To: OpenStack List Subject: [openstack-dev] [Neutron][Networking-SFC] Stable/mitaka version Hi, In git the project has a stable/liberty and trunk version. Will this be

Re: [openstack-dev] [neutron][devstack] Does the openvswitch-agent need to be run along side the neutron-l3-agent?

On 6 June 2016 at 19:59, Sean M. Collins wrote: > While reviewing https://review.openstack.org/#/c/292778/5 I think I > might have found a bit of coupling between the neutron l2 agent and the > l3 agent when it comes to DevStack. > > In the DevStack neutron guide - the

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

Can someone from the Octavia team check on the stable/liberty failures for the unit test runs? Those have been failing for several weeks, if not months, now, which makes having a job run Octavia unit tests on the periodic-stable queue pointless since they never pass. Keep in mind the octavia

[openstack-dev] [Nova] Live migration meeting tomorrow

The agenda is here: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration With the non-priority spec freeze having passed there is not much on the agenda at the moment. If you have anything to add please feel free. Regards, Paul

Re: [openstack-dev] [Neutron] Getting project version from API

On 6 June 2016 at 17:05, Andreas Scheuring wrote: > Is there a chance to get rid of this vif-plugged event at all? E.g. by > transitioning it to an ReST API interface? As far as I know this is the > only RPC interface between neutron and nova. > This handshake

Re: [openstack-dev] [neutron][devstack] Does the openvswitch-agent need to be run along side the neutron-l3-agent?

On Mon, Jun 6, 2016 at 1:59 PM, Sean M. Collins wrote: > While reviewing https://review.openstack.org/#/c/292778/5 I think I > might have found a bit of coupling between the neutron l2 agent and the > l3 agent when it comes to DevStack. > > In the DevStack neutron guide - the

[openstack-dev] [Fuel] Pinning upstream puppet modules

Dear colleagues, We are approaching 9.0.1 release and for higher level of stability we are going to pin [1] upstream puppet modules temporarily. Once 9.0.1 tag is created we will unpin upstream to make it possible to get upstream fixes. [1] https://review.openstack.org/#/c/325807/ Vladimir

[openstack-dev] [neutron][devstack] Does the openvswitch-agent need to be run along side the neutron-l3-agent?

While reviewing https://review.openstack.org/#/c/292778/5 I think I might have found a bit of coupling between the neutron l2 agent and the l3 agent when it comes to DevStack. In the DevStack neutron guide - the "control node" currently does double duty as both an API server and also as a

[openstack-dev] [ironic] weekly subteam status report

Hi, We are stoked 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 23 May 2016) - Ironic: 204 bugs (+12) + 178 wishlist items. 8 new (+8), 138 in progress, 0

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

Excerpts from Brant Knudson's message of 2016-06-03 15:16:20 -0500: > On Fri, Jun 3, 2016 at 2:35 PM, Lance Bragstad wrote: > > > Hey all, > > > > I have been curious about impact of providing performance feedback as part > > of the review process. From what I understand,

Re: [openstack-dev] [nova][libvirt] Deprecating the live_migration_flag and block_migration_flag config options

On 1/8/2016 12:28 PM, Mark McLoughlin wrote: On Fri, 2016-01-08 at 14:11 +, Daniel P. Berrange wrote: On Thu, Jan 07, 2016 at 09:07:00PM +, Mark McLoughlin wrote: On Thu, 2016-01-07 at 12:23 +0100, Sahid Orentino Ferdjaoui wrote: On Mon, Jan 04, 2016 at 09:12:06PM +, Mark

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

Regarding openstack/murano-apps, in this repo we use stable/kilo branch not as a version of the apps, but rather than compatibility version of the app. Applications which are published in this branch are compatible with Murano from stable/kilo, given than we have a lag between upstream release and

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

From: Lance Bragstad [lbrags...@gmail.com] Sent: Friday, June 03, 2016 1:57 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process Here is a list

[openstack-dev] [mistral] Team meeting minutes - 06/06/2016

Thanks all for joining today’s meeting and having a productive discussion! Meeting minutes and log: http://eavesdrop.openstack.org/meetings/mistral/2016/mistral.2016-06-06-16.00.html

[openstack-dev] [oslo] [keystone] dogpile.cache 0.6.0 released

Hey all - I've released dogpile.cache 0.6.0. As discussed earlier in this thread, the big change in this is that we've retired the dogpile.core package; while that package will stay out on pypi as it is, the actual implementation has been rolled into dogpile.cache itself and the namespace

Re: [openstack-dev] [Neutron][vpnaas]Question about MPLS VPN

On 05/26/2016 02:50 AM, zhangyali (D) wrote: > Hi all, > > I am interested in the VPNaaS project in Neutron. Now I notice that only > IPsec tunnel has completed, but other types of VPN, such as, MPLS/BGP, have > not completed. I'd like to know how's going about MPLS/BGP vpn? What's the >

[openstack-dev] [Nova] Virtual GPU provisioning

How should we expose Virtual GPUs to Nova? Various discussions have happened on the original spec submission for Mitaka[1] and the recent submission for Newton[2], however there are a few questions which need further discussion. But before those question (at the end), some thinking behind the

Re: [openstack-dev] [Neutron] Getting project version from API

> On 06 Jun 2016, at 16:44, Sean M. Collins wrote: > > I agree, it would be convenient to have something similar to what Nova > has: > > https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/versions.py#L59-L60 > > We should put some resources behind

Re: [openstack-dev] [Neutron][vpnaas]Question about MPLS VPN

Hi, sorry for the late reply, but if you want to attach a neutron network or a neutron router to an existing MPLS based BGP L3 VPN, you can use the BGPVPN project [1], with its API and one of it's backend, bagpipe [2] being its opensource and reference implementation. Those projects have

[openstack-dev] [new][senlin] python-senlinclient 0.5.0 release (newton)

We are tickled pink to announce the release of: python-senlinclient 0.5.0: OpenStack Clustering API Client Library This release is part of the newton release series. For more details, please see below. 0.5.0 ^ New Features * Added command for node-check and node-recover.

Re: [openstack-dev] [nova] [placement] conducting, ovo and the placement api

On 06/04/2016 10:37 AM, Dan Smith wrote: There was a conversation earlier this week in which, if I understood things correctly, one of the possible outcomes was that it might make sense for the new placement service (which will perform the function currently provided by the scheduler in Nova) to

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

Juno, I was going to take a pass at 3 today to see if I can get a working use case before I submit the patches. On 1 I will reach out to the networking-sfc team to get the design spec started. I will start looking at how to get the patches submitted too. So with your and Srilatha’s help I think

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

Juno, Let me check – my intention was that the networking-sfc OVNB driver would configure all aspects of the port-chain and add the parameters to the networking-sfc db. Once all the parameters were in the creation of a port-chain would call networking-ovn (passing a deep copy of the port-chain

Re: [openstack-dev] [nova] [placement] conducting, ovo and the placement api

> I believe the only difference between your thoughts on this and my > own are the implementation details of how those placement HTTP API > calls would be made. I believe you want to see those calls done in > the nova.objects.Inventory[List] object whereas I was hoping to have > the resource

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

I’ve submitted a request to release all the unreleased code we still have for murano repositories https://review.openstack.org/#/c/325359/ ; It would be really great if we could get one final release before EOL’ing kilo in murano, murano-dashboard, murano-agent and python-muranoclient, if that is

[openstack-dev] [ironic] moving ansible-deploy driver patches to ironic-staging-drivers

HI All, As you might have noticed, lately we (mostly myself and Yuri) were working on an experimental deployment driver that utilizes Ansible to provision the node (spec proposed at [0]). We started the work in common Ironic’s Gerrit project and lately realized that those patches put a lot of

Re: [openstack-dev] [Neutron] Getting project version from API

The ovs agent reports if it uses hybrid plug or not since [1]. At least the hybrid plug is part of the agent state - haven't tested if it's visible via the API. Might that be helpful? [1]https://review.openstack.org/#/c/311814/ -- - Andreas IRC: andreas_s (formerly scheuran) On Mo,

Re: [openstack-dev] [ironic] Virtual midcycle date poll

By the way, I created an etherpad for the midcycle to start bringing in ideas. You know what to do. :) https://etherpad.openstack.org/p/ironic-newton-midcycle // jim On Wed, Jun 01, 2016 at 02:45:33PM -0400, Jim Rollenhagen wrote: > On Thu, May 19, 2016 at 09:25:18AM -0400, Jim Rollenhagen

Re: [openstack-dev] [Neutron] Getting project version from API

Is there a chance to get rid of this vif-plugged event at all? E.g. by transitioning it to an ReST API interface? As far as I know this is the only RPC interface between neutron and nova. -- - Andreas IRC: andreas_s (formerly scheuran) On Mo, 2016-06-06 at 20:25 +0900, Akihiro Motoki

Re: [openstack-dev] [Neutron][Kolla][ovs-discuss] error when starting neutron-openvswitch-agent service

6: ovs-system: mtu 1500 qdisc noop state DOWN link/ether 3e:c8:1d:8e:b5:5b brd ff:ff:ff:ff:ff:ff 7: br-ex: mtu 1500 qdisc noop state DOWN link/ether 1c:6f:65:05:37:11 brd ff:ff:ff:ff:ff:ff 8: br-int: mtu 1500 qdisc noop

Re: [openstack-dev] [Neutron] Getting project version from API

I agree, it would be convenient to have something similar to what Nova has: https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/versions.py#L59-L60 We should put some resources behind implementing micro versioning and we could end up with something similar. It would also be

[openstack-dev] [new][congress] python-congressclient 1.3.0 release (newton)

We are thrilled to announce the release of: python-congressclient 1.3.0: Client for Congress This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/python-congressclient Please report issues through launchpad:

Re: [openstack-dev] [Kuryr] Kuryr did not detect neutron tag plugin in devstack

On Sat, Jun 4, 2016 at 5:17 AM, Liping Mao (limao) wrote: > Hi Kuryr team, > > I notice kuryr did not detect neutron tag plugin in devstack[1]. > This is because when kuryr process start up in devstack, > neutron-server did not finish load tag plugin. > Kuryr use api call to

Re: [openstack-dev] [neutron] [linuxbridge] Multiple VXLAN multicast groups

Kevin Benton wrote: > Just to be clear, it's not random. It follows a masking pattern so it is > possible to know which address a given VNI will use. And if you use a /8 > prefix the VNIs will have a straightforward 1:1 mapping to multicast > addresses. So, it sounds like we need better

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

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

Re: [openstack-dev] [ironic] looking for documentation liaison

Hi, Thank you Vlad and Jay for volunteering! Neither of you love documentation, but Jay is “very willing”, so Jay wins :D --ruby On 2016-05-31, 1:23 PM, "Loo, Ruby" wrote: >Hi, > >We¹re looking for a documentation liaison [1]. If you love (Œlike¹ is also >acceptable)

Re: [openstack-dev] [nova] [placement] conducting, ovo and the placement api

Le 04/06/2016 16:37, Dan Smith a écrit : There was a conversation earlier this week in which, if I understood things correctly, one of the possible outcomes was that it might make sense for the new placement service (which will perform the function currently provided by the scheduler in Nova)

[openstack-dev] [trove] Trove Newton spec proposal deadline

This week, June 6-10 is R-17 for Newton and marks the deadline for the proposal of any specs for features to be considered for the Newton cycle. Please get all specs into the trove-specs repository as soon as possible. The following specs [1] are currently proposed and in need of review.

[openstack-dev] [puppet] weekly meeting #84

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-20160607 Feel free to add more topics, and any outstanding bug and patch. See you tomorrow! Thanks, -- Emilien

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

Hi John, One question need confirm with you, I think the ovn flow classifier driver and ovn port chain driver should call the APIs which you add to networking-ovn to configure the northbound db sfc tables, right? I see your networking-sfc ovn drivers, they does not call the APIs you add to

[openstack-dev] [nova] Update on resource providers work

Hi Stackers, tl;dr - 0) We moved the resource-providers database tables to the API DB in Nova instead of the child cell DB 1) We are reverting the patches to Nova that queried the old and new inventory/allocation fields and attempted online data migrations for inventory information.

[openstack-dev] [mistral] Team meeting reminder - 06/06/2016

Hi, We’re have a team meeting today as usually at #openstack-meeting at 16.00 UTC. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Custom Actions API spec Open discussion Renat Akhmerov @Nokia

Re: [openstack-dev] [neutron] [linuxbridge] Multiple VXLAN multicast groups

Hi, unfortunately straightforward mapping is not usable for us, we need own distribution of addresses according to vni. For example - 2 data centers connected with VLANs, both with Cisco ASR-9K on L3. Routers have its own vni-multicast group mappings. Router(config-if)# member vni 6010-6030

Re: [openstack-dev] [Neutron] Getting project version from API

Hi, If I understand correctly, what you need is to expose the neutron behavior through API or something. In this particular case, neutron need to send a vif-plugged event when neutron detects some event in the data plane (VIF plugging in OVS or some virtual switch). Thus I think the question can

Re: [openstack-dev] [Neutron] Getting project version from API

On 6 June 2016 at 10:06, Oleg Bondarev wrote: > Hi, > > There are cases where it would be useful to know the version of Neutron > (or any other project) from API, like during upgrades or in cross-project > communication cases. > For example in

[openstack-dev] [Neutron][Kolla][ovs-discuss] error when starting neutron-openvswitch-agent service

Hi Guys, I am new to Neutron Kolla and OVS, I was trying to deploy Mitaka on CeontOS in a all-in-one environment using Kolla. After a successful deploying I realized that I should disable NetworkManager service roughly according to:

Re: [openstack-dev] [Neutron][Networking-SFC] Stable/mitaka version

> On 06 Jun 2016, at 11:39, Gary Kotton wrote: > > Hi, > In git the project has a stable/liberty and trunk version. Will this be > supported in stable/mitaka? > Thanks > Gary For this to happen, the team should propose a release-subproject tagged bug in LP. I don’t see

Re: [openstack-dev] [Kuryr] roles of kuryr server in server/agent mode

Hi Vikas, This is something we discussed over the summit. The kuryr (referred to as server, more like a master instance) is in fact running on the master node (Swarm, k8s, Mesos etc) in the VM. I will push a patch to clarify in the spec. And agree that the instance running inside the VMs will be

[openstack-dev] [Neutron][Networking-SFC] Stable/mitaka version

Hi, In git the project has a stable/liberty and trunk version. Will this be supported in stable/mitaka? Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [nova] [placement] conducting, ovo and the placement api

Thanks for the response, it's very useful to (to me at least) to hash this stuff out in writing. More hashing and crazy talk below. On Sat, 4 Jun 2016, Dan Smith wrote: There was a conversation earlier this week in which, if I understood things correctly, one of the possible outcomes was that

Re: [openstack-dev] [neutron] [linuxbridge] Multiple VXLAN multicast groups

Just to be clear, it's not random. It follows a masking pattern so it is possible to know which address a given VNI will use. And if you use a /8 prefix the VNIs will have a straightforward 1:1 mapping to multicast addresses. On Jun 6, 2016 01:35, "Jiří Kotlín" wrote: >

Re: [openstack-dev] [magnum][kuryr] Nested containers networking

On Tue, May 24, 2016 at 1:23 PM, Gal Sagie wrote: > Hi Hongbin, > > Thank you for starting this thread. > The person that is going to work on this integration is Fawad (CC'ed) and > hopefully others will help > him (We have another person from Huawei that showed intrest in

Re: [openstack-dev] [neutron] [linuxbridge] Multiple VXLAN multicast groups

Hi, yes sorry - I was not concrete enough and the RFE should really be reworded. Our goal is to have the ability to control vni-multicast address distribution somehow, not randomly. Considering multiple addresses support is already implemented in linux bridge agent, I suppose implementing this

Re: [openstack-dev] [Fuel] [Plugins] Netconfig tasks changes

Hi, a bit different patch is on review now [0]. Instead of silently replacing default gateway on the fly in netconfig.pp task it's putting new default gateway into Hiera. Thus we'll have idempotency for subsequent netconfig.pp runs even on Mongo roles. Also we'll have consistent network

[openstack-dev] [Neutron] Getting project version from API

Hi, There are cases where it would be useful to know the version of Neutron (or any other project) from API, like during upgrades or in cross-project communication cases. For example in https://review.openstack.org/#/c/246910/ Nova needs to know if Neutron sends vif-plugged event during live

Re: [openstack-dev] [neutron] [linuxbridge] Multiple VXLAN multicast groups

The linux bridge agent does support using multiple VXLAN groups. You can specify a prefix for 'vxlan_group' and the VNIs will be spread across the multicast addresses in that prefix.[1] The only difference between that and what your RFE proposes is specific control over which multicast address is

[openstack-dev] [nova][notification] transformation TODO list

Hi, If you want to help nova to transform its notification interface to an API then you can find your new TODO list on the wiki [1]. You can find the basic how-to information and the list of work items there. If you have any questions just ping me (gibi) on IRC or join the weekly notification

[openstack-dev] [neutron] [linuxbridge] Multiple VXLAN multicast groups

Hi linuxbridge experts, the ability to define multiple VXLAN groups can be very useful in practice. Is there any design rationale why the vxlan_group was considered a single attribute? More info is in this RFE: https://bugs.launchpad.net/bugs/1579068 Thank you in advance for any help you can

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

+1 Kevin “heterogeneous cluster is more advanced and harder to control” So, I believe that Magnum should control and overcome this problem. Magnum is a container infrastructure as a service. Managing heterogeneous environment seems scope of Magnum’s mission. 2016年6月3日(金) 8:55 Fox, Kevin M

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

John, Thanks your working overtime in last weekend, now we have the following works to do: 1, submit design spec to networking-sfc 2, submit the RFC to ovs community 3, debug end-to-end about your code changes. 4, submit the initial patch to networking-sfc 5, submit the initial patch to ovs

  1   2   >