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

+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 has been contributing to Tacker from the Liberty cycle, and he has grown into a key

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

+1. Thanks for your awesome contributions Bharath ! From: Sripriya Seetharam [mailto:ssee...@brocade.com] Sent: Friday, June 03, 2016 6:39 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tacker] Proposing

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

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 detect neutron tag, so kuryr will not detect it. After I manually restart kuryr process,

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

+1. Welcome onboard Bharath! -Sripriya From: Sridhar Ramaswamy [mailto:sric...@gmail.com] Sent: Friday, June 03, 2016 6:21 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [tacker] Proposing Bharath Thiruveedula to

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

Tackers, I'm happy to propose Bharath Thiruveedula (IRC: tbh) to join the tacker core team. Bharath has been contributing to Tacker from the Liberty cycle, and he has grown into a key member of this project. His contribution has steadily increased as he picked up bigger pieces to deliver [1].

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

Both proposals allow you to provide a path as the project name in auth (so you can still use domain name + project path name). The difference between the two is whether you formally represent the path in the name attribute of a project, i.e. when it is returned by GET /project. The relax name

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

On Jun 3, 2016 12:42, "Lance Bragstad" wrote: > > > > On Fri, Jun 3, 2016 at 11:20 AM, Henry Nash wrote: >> >> >>> On 3 Jun 2016, at 16:38, Lance Bragstad wrote: >>> >>> >>> >>> On Fri, Jun 3, 2016 at 3:20 AM, Henry Nash

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

On Jun 3, 2016 13:16, "Brant Knudson" wrote: > > > > 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, keystone

Re: [openstack-dev] [release] newton 1 milestone closed

On 06/03/2016 05:32 PM, Doug Hellmann wrote: > The Newton 1 milestone deadline is past, and the release team has > processed all but a few of the tag requests. We had some technical > issues with a few requests that we expect to have resolved early > next week. > > A few projects missed the

[openstack-dev] [release] newton 1 milestone closed

The Newton 1 milestone deadline is past, and the release team has processed all but a few of the tag requests. We had some technical issues with a few requests that we expect to have resolved early next week. A few projects missed the deadline. Please review the schedule [1] and add the date for

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

Excerpts from Joshua Harlow's message of 2016-06-03 09:14:05 -0700: > Deja, Dawid wrote: > > On Thu, 2016-05-05 at 11:08 +0700, Renat Akhmerov wrote: > >> > >>> On 05 May 2016, at 01:49, Mehdi Abaakouk >>> > wrote: > >>> > >>> > >>> Le 2016-05-04

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

Carl Baldwin wrote: > On Fri, Jun 3, 2016 at 2:26 PM, Henry Gessau wrote: >> Darek Smigiel wrote: >>> strange, that owner is not able to just get rid of *his* network and >>> subnets. >> >> But not all the subnets are his, and

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

On 3 June 2016 at 13:31, Carl Baldwin wrote: > On Fri, Jun 3, 2016 at 2:26 PM, Henry Gessau wrote: > > Darek Smigiel wrote: > >> strange, that owner is not able to just get rid of *his* network and > subnets. > > > > But not all

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

Dedicated and isolated infrastructure is a must if we want consistent performance numbers. If we can come up with a reasonable plan, I'd be happy to ask for resources. Even with dedicated infrastructure we would still have to keep in mind that it's a data point from a single provider that

[openstack-dev] Announcing Higgins -- Container management service for OpenStack

Hi all, We would like to introduce you a new container project for OpenStack called Higgins (might be renamed later [1]). Higgins is a Container Management service for OpenStack. The key objective of the Higgins project is to enable tight integration between OpenStack and container

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

To me, it seems more appropriate to delete all the subnets no matter who they're owned by if the owner of the network decided they wanted to delete it.  If there is a subnet associated with their network that they do not see, then the delete network call would have to fail.  That's going to be

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

On Fri, Jun 3, 2016 at 2:26 PM, Henry Gessau wrote: > Darek Smigiel wrote: >> strange, that owner is not able to just get rid of *his* network and subnets. > > But not all the subnets are his, and consequently the network is partially not > his. To

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

Darek Smigiel wrote: > strange, that owner is not able to just get rid of *his* network and subnets. But not all the subnets are his, and consequently the network is partially not his. Why did the admin create a subnet on the user's network in [1]? IMO the admin

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

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, keystone used to have a > performance job that would run against proposed patches

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

On Fri, Jun 03, 2016 at 01:53:16PM -0600, Matt Fischer wrote: > On Fri, Jun 3, 2016 at 1: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, keystone

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

On Fri, Jun 3, 2016 at 11:16 AM, Darek Smigiel wrote: > Hello, > Doing reviews I noticed, that Liu Yong submitted a bug [1] where we have a > problem with removing subnets. This makes me wonder what the use case that gets in to this situation. > In short: if tenant

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

On Fri, Jun 3, 2016 at 1: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, keystone used to have a > performance job that would run against proposed patches

Re: [openstack-dev] [ironic] Trello board

On 06/03/2016 07:08 PM, Jim Rollenhagen wrote: > On Fri, Jun 03, 2016 at 06:29:13PM +0200, Alexis Monville wrote: >> Hi, >> >> On Fri, Jun 3, 2016 at 5:39 PM, Jim Rollenhagen >> wrote: >>> Hey all, >>> >>> Myself and some other cores have had trouble tracking our

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

On Fri, Jun 3, 2016 at 11:20 AM, Henry Nash wrote: > > On 3 Jun 2016, at 16:38, Lance Bragstad wrote: > > > > On Fri, Jun 3, 2016 at 3:20 AM, Henry Nash wrote: > >> >> On 3 Jun 2016, at 01:22, Adam Young wrote: >>

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

Hey all, I have been curious about impact of providing performance feedback as part of the review process. From what I understand, keystone used to have a performance job that would run against proposed patches (I've only heard about it so someone else will have to keep me honest about its

Re: [openstack-dev] [ironic] Trello board

On Fri, Jun 03, 2016 at 06:29:13PM +0200, Alexis Monville wrote: > Hi, > > On Fri, Jun 3, 2016 at 5:39 PM, Jim Rollenhagen > wrote: > > Hey all, > > > > Myself and some other cores have had trouble tracking our priorities > > using Launchpad and friends, so we put

[openstack-dev] [new] nova_powervm 2.0.2 release (mitaka)

We are satisfied to announce the release of: nova_powervm 2.0.2: PowerVM driver for OpenStack Nova. This release is part of the mitaka stable release series. For more details, please see below. Changes in nova_powervm 2.0.1..2.0.2 c9e0ea4 hdisk discovery

[openstack-dev] [nova] Replacing user based policies in Nova

With https://review.openstack.org/324068 (thanks ☺), the key parts of user based policies as currently deployed would be covered in the short term. However, my understanding is that this functionality needs to be replaced with something sustainable in the long term and consistent with the

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

Thanks for the link Tim! Right now, I have two things I'm unsure about... One is that I had 1945 huge pages left (of size 2048k) and tried to create a VM with a small flavor (2GB), which should need 1024 pages, but Nova indicated that it wasn't able to find a host (and QEMU reported an

Re: [openstack-dev] [kolla] OSIC cluster accepteed

Michal, Great news. Just as a followup, the midcycle is scheduled for the 12th and 13th of July. I am working on the eventbrite page today, but the initial information is here: https://wiki.openstack.org/wiki/Sprints#Newton_sprints Unlike last midcycles, there is no vote on the date this time

[openstack-dev] [Neutron] Elevating context to remove subnets created by admin

Hello, Doing reviews I noticed, that Liu Yong submitted a bug [1] where we have a problem with removing subnets. In short: if tenant wants to delete network with subnets, where at least one of subnets is created by admin, he’s not able to do this. Liu also prepared bugfix for it [2], but now

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

The documentation at http://docs.openstack.org/admin-guide/compute-flavors.html is gradually improving. Are there areas which were not covered in your clarifications ? If so, we should fix the documentation too since this is a complex area to configure and good documentation is a great help.

Re: [openstack-dev] [ironic] [oslo] Template to follow for policy support?

On 05/31/2016 04:01 PM, Jay Faulkner wrote: > Hi all, > > > During this cycle, on behalf of OSIC, I'll be working on implementing proper > oslo.policy support for Ironic. The reasons this is needed probably don't need > to be explained here, so I won't :). > > > I have two requests for the

Re: [openstack-dev] [puppet] Discussion of PuppetOpenstack Project abbreviation

On 06/03/2016 01:34 AM, Sergii Golovatiuk wrote: I would vote for POSM - "Puppet OpenStack Modules" +1 - possum, american slang for the animal "opossum" -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Jun 1, 2016 at 7:25 PM, Cody Herriges

Re: [openstack-dev] [release] [infra] Conflict between publishing jobs

On 06/02/2016 03:38 PM, Julien Danjou wrote: > Hi, > > While importing Panko¹ into OpenStack, Andreas informed me that the jobs > "openstack-server-release-jobs" and "publish-to-pypi" were incompatible > and that the release team would know that. We actually want to publish > Panko as an

[openstack-dev] [kolla] OSIC cluster accepteed

Hello Kollagues, Some of you might know that I submitted request for 130 nodes out of osic cluster for testing Kolla. We just got accepted. Time window will be 3 weeks between 7/22 and 8/14, so we need to make most of it. I'd like some volunteers to help me with tests, setup and such. We need to

Re: [openstack-dev] [ironic] Trello board

Hi, On Fri, Jun 3, 2016 at 5:39 PM, Jim Rollenhagen wrote: > Hey all, > > Myself and some other cores have had trouble tracking our priorities > using Launchpad and friends, so we put together a Trello board to help > us track it. This should also help us focus on what

[openstack-dev] [nova] We are now past the non-priority spec approval deadline

Yesterday was the non-priority spec approval deadline per the nova release schedule [1]. We have 80 approved blueprints for Newton so far [2]. In my opinion we're already way over-committed for the release, but we'll get done what we can. The upside to getting your spec approved in Newton is

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

> On 3 Jun 2016, at 16:38, Lance Bragstad wrote: > > > > On Fri, Jun 3, 2016 at 3:20 AM, Henry Nash > wrote: > >> On 3 Jun 2016, at 01:22, Adam Young > > wrote: >> >> On

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

Deja, Dawid wrote: On Thu, 2016-05-05 at 11:08 +0700, Renat Akhmerov wrote: On 05 May 2016, at 01:49, Mehdi Abaakouk > wrote: Le 2016-05-04 10:04, Renat Akhmerov a écrit : No problem. Let’s not call it RPC (btw, I completely agree with that).

[openstack-dev] [neutron][SFC]

Probleme with OpenStack SFC Hi all, I've installed Openstack SFC with devstack and all module are corretly running except the neutron L2-agent After a "screen -rd", it seems that there is a conflict between l2-agent and SFC (see trace bellow). I solved the issue with "sudo ovs-vsctl set bridge br

[openstack-dev] [kolla] Fwd: Re: Kilo version of Kolla

fyi Forwarded Message Subject: Re: Kilo version of Kolla Date: Fri, 3 Jun 2016 16:01:59 + From: Steven Dake (stdake) To: Paul Bourke , POLAKU, CHANDRA CC: VENKATSUBRAMANIAM, SHRINATH ,

Re: [openstack-dev] [kolla] Google Hangouts discussion for dueling specifications for Dockerfile customization

Ihor, I don't plan to have hangouts be a common theme in our community. However, one of our main contributor's to the conversation IT department requires google hangouts or nothing at all. So we were stuck with that, or I'd used webex and recorded it. Regards -steve From: Ihor Dvoretskyi

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

I agree that heterogeneous cluster is more advanced and harder to control, but I don't get why we (as service developers/providers) care about that. If there is a significant portion of users asking for advanced topologies (i.e. heterogeneous cluster) and willing to deal with the complexities,

[openstack-dev] [OpenStack-Ansible] Splitting out generic testing components

TL;DR We're doing a PoC to split out common testing plays/vars into a generic repository, for the purposes of making in-role testing more uniform and generic. Looking for feedback, comments, informal reviews, ideas etc! https://github.com/andymcc/openstack-ansible-testing-core (Includes a simple

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

On Fri, Jun 3, 2016 at 3:20 AM, Henry Nash wrote: > > On 3 Jun 2016, at 01:22, Adam Young wrote: > > On 06/02/2016 07:22 PM, Henry Nash wrote: > > Hi > > As you know, I have been working on specs that change the way we handle > the uniqueness of project

[openstack-dev] [ironic] Trello board

Hey all, Myself and some other cores have had trouble tracking our priorities using Launchpad and friends, so we put together a Trello board to help us track it. This should also help us focus on what to review or work on. https://trello.com/b/ROTxmGIc/ironic-newton-priorities Some notes on

Re: [openstack-dev] [Cinder] Discuss Cinder testing Wednesdays at 1500 UTC

In the interest of yet-another-etherpad I created: https://etherpad.openstack.org/p/Cinder-testing I'll put an agenda, folks can sign up to be pinged, we'll keep the notes and action items here, etc From: D'Angelo, Scott Sent: Friday, June 03, 2016 8:14

[openstack-dev] [Cinder] Discuss Cinder testing Wednesdays at 1500 UTC

For those interested in various aspects of Cinder testing, we're planning on discussing and coordinating efforts. Please join us: #openstack-cinder 1500 UTC Wednesdays (just before the Weekly Cinder meeting) Testing subjects: Multi-node Cinder testing Active-Active HA testing Improved Tempest

Re: [openstack-dev] [freezer] Addition to the core team

Welcome to the core team Deklan ! Don't forget, with great power comes great responsability ;-) - Pierre From: Saad Zaher Sent: Friday, June 3, 2016 11:01:21 AM To: OpenStack Development Mailing List (not for usage questions) Cc: Lopes do Sacramento, Cynthia;

Re: [openstack-dev] [OpenStack-Infra] [Infra][tricircle] patch not able to be merged

On 2016-06-03 03:45:31 + (+), joehuang wrote: > There is one quite strange issue in Tricircle stable/mitaka branch > (https://github.com/openstack/tricircle/tree/stable/mitaka) . Even > the patch ( https://review.openstack.org/#/c/324209/ ) were given > Code-Review +2 and Workflow +1, the

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

See PCM inline... On Fri, Jun 3, 2016 at 8:44 AM Daniel P. Berrange wrote: > On Fri, Jun 03, 2016 at 12:32:17PM +, Paul Michali wrote: > > Hi! > > > > I've been playing with Liberty code a bit and had some questions that I'm > > hoping Nova folks may be able to provide

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

On Thu, Jun 2, 2016 at 7:32 PM, Tony Breeds wrote: > On Thu, Jun 02, 2016 at 07:10:23PM -0400, Emilien Macchi wrote: > >> I think that all openstack/puppet-* projects that have stable/kilo can >> be kilo-EOLed. >> Let me know if it's ok and I'll abandon all open reviews.

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

> openstack/packstack BigTent Just to clarify, Packstack has not formally applied to BigTent yet, it has only been automatically migrated from stackforge to openstack namespace. But yes, please keep its kilo branch for now until we properly wrap it up.

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

On Fri, Jun 03, 2016 at 12:32:17PM +, Paul Michali wrote: > Hi! > > I've been playing with Liberty code a bit and had some questions that I'm > hoping Nova folks may be able to provide guidance on... > > If I set up a flavor with hw:mem_page_size=2048, and I'm creating (Cirros) > VMs with

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

Hi! I've been playing with Liberty code a bit and had some questions that I'm hoping Nova folks may be able to provide guidance on... If I set up a flavor with hw:mem_page_size=2048, and I'm creating (Cirros) VMs with size 1024, will the scheduling use the minimum of the number of huge pages

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

Hi Fawad, While I was going through nested-containers-spec , found it difficult to understand the roles and responsibilities of kuryr-server, which is supposed to be run on controller nodes. To me

Re: [openstack-dev] [tc][security] Item #5 of the VMT

Doug Chivers might have some thoughts on this but I'm happy with your proposal Steve, kind of you to do the leg-work. -rob On Fri, Jun 3, 2016 at 1:29 AM, Steven Dake (stdake) wrote: > Hi folks, > > I think we are nearly done with Item #5 [1] of the VMT. One question >

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

On Thu, 2016-05-05 at 11:08 +0700, Renat Akhmerov wrote: On 05 May 2016, at 01:49, Mehdi Abaakouk > wrote: Le 2016-05-04 10:04, Renat Akhmerov a écrit : No problem. Let’s not call it RPC (btw, I completely agree with that). But it’s one of the

[openstack-dev] [tricircle] reviewed by multiple eyes

Hi Team, There are some patch sets reviewed by only myself. >From my point of view, any patch set needs to be reviewed by multiple eyes. It's because anyone is not perfect. And there should be anything missing. Please take a look, if you get notification to review. Cheers, Shinobu -- Email:

Re: [openstack-dev] [ironic] versioning of IPA, it is time or is it?

I personally think that we need IPA versioning, but not so that we can pin a version. We need versioning so that we can do more intelligent graceful degradation in Ironic without just watching for errors and guessing if a feature isn’t available. If we add a new feature in Ironic that requires

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

> On 03 Jun 2016, at 12:56, Kirill Zaitsev wrote: > > I’d like to ask to keep murano-apps kilo branch alive. It’s indeed not a > deployable project, but a collection of reference apps for murano. While no > active development happens for murano on kilo itself anymore,

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

I’d like to ask to keep murano-apps kilo branch alive. It’s indeed not a deployable project, but a collection of reference apps for murano. While no active development happens for murano on kilo itself anymore, the apps repo is intended to provide reference application for kilo users. Is it

Re: [openstack-dev] [networking-sfc] how to install networking-sfc on compute node

Juno Zhu , Please check this wiki link : https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining#Multi-Host_Installation Thanks., Mohankumar.N On Fri, Jun 3, 2016 at 12:43 PM, Na Zhu wrote: > Yes, but networking-sfc rewrite the q-agt binary file, when i install

[openstack-dev] [trove] trove-image-builder project

We've had some lengthy discussions over the past couple of release cycles, most recently in Austin, and on the ML on the subject of the trove-image-builder project[1]. Subsequently the trove spec [2] has been merged and yesterday the infra and governance changes [3] and [4] have also merged.

Re: [openstack-dev] [freezer] Addition to the core team

+1 On Fri, Jun 3, 2016 at 10:11 AM, Vanni, Fabrizio wrote: > +1 > > -Original Message- > From: Lopes do Sacramento, Cynthia > Sent: 02 June 2016 17:21 > To: Zaher, Saad ; Mathieu, Pierre-Arthur < > pierre-arthur.math...@hpe.com>;

Re: [openstack-dev] [kolla] Google Hangouts discussion for dueling specifications for Dockerfile customization

Steve, If you have any concerns with recording the Hangouts meetings, we may try to run Zoom for that. On Fri, Jun 3, 2016 at 3:50 AM, Steven Dake (stdake) wrote: > Hey folks, > > IRC and mailing list were going far too slow for us to make progress on > the competing

Re: [openstack-dev] [freezer] Addition to the core team

+1 -Original Message- From: Lopes do Sacramento, Cynthia Sent: 02 June 2016 17:21 To: Zaher, Saad ; Mathieu, Pierre-Arthur ; openstack-dev@lists.openstack.org Cc: freezer-eskimos Subject: RE:

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

> On 3 Jun 2016, at 01:22, Adam Young wrote: > > On 06/02/2016 07:22 PM, Henry Nash wrote: >> Hi >> >> As you know, I have been working on specs that change the way we handle the >> uniqueness of project names in Newton. The goal of this is to better support >> project

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

On Fri, Jun 03, 2016 at 09:29:34AM +0200, Matthias Runge wrote: > On 02/06/16 12:31, Tony Breeds wrote: > > The list of 171 projects that match above is at [1]. There are > > another 68 > I just abandoned open reviews for django_openstack_auth in kilo version. Thanks. Yours Tony.

Re: [openstack-dev] [sahara] openstack Unauthorized HTTP 401 'Could not find user' when sahara call heat

oh, so old of Juno, Kilo's reached EOL already. Suggest you to add [sahara] in subject. On 2016年06月03日 09:51, 阮鹏飞 wrote: Hi, Friends, I used Openstack-Juno heat, keystone and Mitaka sahara in CentOS7. Sahara is installed in docker container using host network. When sahara wants to call

Re: [openstack-dev] [puppet] Discussion of PuppetOpenstack Project abbreviation

I would vote for POSM - "Puppet OpenStack Modules" -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Jun 1, 2016 at 7:25 PM, Cody Herriges wrote: > > > On Jun 1, 2016, at 5:56 AM, Dmitry Tantsur wrote: > > > > On 06/01/2016 02:20

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/06/16 12:31, Tony Breeds wrote: > Hi all, In early May we tagged/EOL'd several (13) projects. We'd > like to do a final round for a more complete set. We looked for > projects meet one or more of the following criteria: - The project > is

Re: [openstack-dev] [networking-sfc] how to install networking-sfc on compute node

Yes, but networking-sfc rewrite the q-agt binary file, when i install networking-sfc in allinone mode, the q-aget binary file is: juno@sfc:~/devstack$ cat /usr/local/bin/neutron-openvswitch-agent #!/usr/bin/python # PBR Generated from u'console_scripts' import sys from

Re: [openstack-dev] [networking-sfc] how to install networking-sfc on compute node

On Thu, Jun 2, 2016 at 9:11 PM, Na Zhu wrote: > Hi, > > From this link > https://github.com/openstack/networking-sfc/tree/master/devstack, it is > about installing networking-sfc together with neutron-server, > I want to install networking-sfc on compute node, can anyone tell

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

On Thu, Jun 02, 2016 at 08:31:43PM +1000, Tony Breeds wrote: > Hi all, > In early May we tagged/EOL'd several (13) projects. We'd like to do a > final round for a more complete set. We looked for projects meet one or more > of the following criteria: > - The project is