[openstack-dev] [TripleO] add support for NFV virtual switch in os_net_config

Hi, all This is Xin from Big Switch. I'm proposing to make os_net_config to support DPDK virtual switch for NFV workloads. Current os_net_config supports ovs_bridge, linux_bridge, ivs_bridge and different types of interfaces. Current os_net_config's abstraction is perfect to support DPDK

Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration

hi Vikas, thanks for you clarify, relied in lines. On 2016年06月22日 14:36, Vikas Choudhary wrote: Magnum: 1. Support to pass neutron network names at container creation apis such as pod-create in k8s case. Hmm. Magnum has deleted all wrapper API for container creation and pod-create 1.

[openstack-dev] [all] Status of the OpenStack port to Python 3

Hi, Current status: only 3 projects are not ported yet to Python 3: * nova (76% done) * trove (42%) * swift (0%) https://wiki.openstack.org/wiki/Python3 Number of projects already ported: * 19 Oslo Libraries * 4 Development Tools * 22 OpenStack Clients * 6 OpenStack Libraries (os-brick, ta

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

On 21.06.2016 18:24, Adam Young wrote: > On 06/21/2016 08:43 AM, Markus Zoeller wrote: >> A reminder that this will happen in ~2 weeks. >> >> Please note that you can spare bug reports if you leave a comment there >> which says one of these (case-sensitive flags): >> * CONFIRMED FOR: NEWTON >> * CO

[openstack-dev] [nova][cinder] How to delete a volume which is attached to a server who was deleted

Hi all, I'd like to delete a volume which is attached to a server who was deleted. It failed. How can I delete the volume? Thanks. [root@b-node3 ~]# openstack volume delete aff1c13f-3c08-4230-9c1f-7d48e342054a Invalid volume: Volume status must be available or error or error_restoring or error_ex

Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration

Hi Eli Qiao, Please find my responses inline. On Wed, Jun 22, 2016 at 12:47 PM, taget wrote: > hi Vikas, > thanks for you clarify, relied in lines. > > On 2016年06月22日 14:36, Vikas Choudhary wrote: > > > Magnum: > >1. Support to pass neutron network names at container creation apis >such

Re: [openstack-dev] [nova] libvirt driver: who should create the libvirt.xml file?

On Mon, Jun 20, 2016 at 4:47 PM, Markus Zoeller wrote: > White working on the change series to implement the virtlogd feature I > got feedback [1] to move code which creates parts of the libvirt.xml > file from the "driver" module into the "guest" module. I'm a bit > hesitant to do so as the resp

Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration

Minor correction regarding kuryr-agent role. On Wed, Jun 22, 2016 at 1:27 PM, Vikas Choudhary wrote: > Hi Eli Qiao, > > Please find my responses inline. > > On Wed, Jun 22, 2016 at 12:47 PM, taget wrote: > >> hi Vikas, >> thanks for you clarify, relied in lines. >> >> On 2016年06月22日 14:36, Vika

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On 06/22/2016 09:18 AM, Victor Stinner wrote: > Hi, > > Current status: only 3 projects are not ported yet to Python 3: > > * nova (76% done) > * trove (42%) > * swift (0%) > >https://wiki.openstack.org/wiki/Python3 > > Number of projects already ported: > > * 19 Oslo Libraries > * 4 Devel

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Doug Wiegley wrote: So I'd argue that you need both. You need the TC whenever a hard call has to be made, but in order to minimize the number of those hard calls (and favor consensus building) you also need working groups to build a bottom-up reasonable way forward. This reads very strange t

[openstack-dev] [packaging-deb] Status of the project

I've been asked to tell everyone the status of the project. So here is a report. What's been already done: - Debian Jessie image is up and running on all Infra nodes. - openstack-pkg-tools package can be built on each request, and is gating on the fact that it builds or not. This includes install

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On 22/06/16 10:52 +0200, Thierry Carrez wrote: Doug Wiegley wrote: So I'd argue that you need both. You need the TC whenever a hard call has to be made, but in order to minimize the number of those hard calls (and favor consensus building) you also need working groups to build a bottom-up rea

[openstack-dev] [ironic] [ironic-python-agent] Broken functional tests

This patch https://review.openstack.org/#/c/324909/ merged last night and has broken the IPA functional tests. To verify pull master and run "tox -r -e func" and it¹ll fail to run. If you git checkout the commit before that one merged the same thing passes successfully. Seeing this error has mad

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for the fuel-web-core team

Thank you! I appreciate that and hope that i'll help to reduce time of the review stage) On Mon, Jun 20, 2016 at 12:01 PM, Bulat Gaifullin wrote: > Well, the agreement is reached. I added Ilya to fuel-web-core group. > > Ilya, congratulations! Will be happy to see even more thorough reviews from

[openstack-dev] [fuel] [plugins] Requesting voting permissions

The ACL at https://git.openstack.org/cgit/openstack-infra/project-config/tree/gerrit/acls/openstack/fuel-plugin-xenserver.config shows that, in order for our CI to vote on the fuel-plugins-xenserver project, we need to be in the fuel-plugins-ci group. As such, could I request that the "Citrix X

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Le 22/06/2016 à 10:49, Thomas Goirand a écrit : Do you think it looks like possible to have Nova ported to Py3 during the Newton cycle? It doesn't depend on me: I'm sending patches, and then I have to wait for reviews. The question is more how to accelerate reviews. Right now, I'm splitting

[openstack-dev] [Fuel] Nominating Dmitry Burmistrov for core reviewers of fuel-mirror

Hi All, I'd like to nominate Dmitry Burmistrov for core reviewers of fuel-mirror. Dmitry is one of the top contributors to the project [1, 2]. One of his latest activity was related to perestroika builder (add Xenial build target), build target separation for CentOS, etc. Fuel Cores, please supp

Re: [openstack-dev] [Fuel] Nominating Dmitry Burmistrov for core reviewers of fuel-mirror

+1 Regards, Bulat Gaifullin Mirantis Inc. > On 22 Jun 2016, at 13:18, Sergey Kulanov wrote: > > Hi All, > > I'd like to nominate Dmitry Burmistrov for core reviewers of fuel-mirror. > Dmitry is one of the top > contributors to the project [1, 2]. One of his latest activity was related > t

Re: [openstack-dev] [Fuel] Nominating Dmitry Burmistrov for core reviewers of fuel-mirror

+1 On Wed, Jun 22, 2016 at 1:20 PM, Bulat Gaifullin wrote: > +1 > > Regards, > Bulat Gaifullin > Mirantis Inc. > > > > On 22 Jun 2016, at 13:18, Sergey Kulanov wrote: > > Hi All, > > I'd like to nominate Dmitry Burmistrov for core reviewers of fuel-mirror. > Dmitry is one of the top > contribut

Re: [openstack-dev] [packaging-deb] Status of the project

Is there a higher-level overview somewhere of what packaging-deb does? Should it be useful to me as the packager of a Neutron driver project (networking-calico)? (Currently I've rolled my own processes for generating Debian packages for Ubuntu Trusty and Xenial.) Thanks, Neil On Wed, Jun 22

Re: [openstack-dev] [Fuel] Nominating Dmitry Burmistrov for core reviewers of fuel-mirror

+1 On Wed, Jun 22, 2016 at 1:18 PM, Sergey Kulanov wrote: > Hi All, > > I'd like to nominate Dmitry Burmistrov for core reviewers of fuel-mirror. > Dmitry is one of the top > contributors to the project [1, 2]. One of his latest activity was related > to perestroika builder (add Xenial build tar

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

On 06/22/2016 01:36 AM, Haïkel wrote: > 2016-06-22 7:23 GMT+02:00 Tony Breeds : >> >> I'm fine with doign something like this. I wrote [1] some time ago but >> didn't >> push on it as I needed to verify that this wouldn't create a "storm" of >> pointless updates that just reorder things in every

Re: [openstack-dev] [oslo][monasca][requirements] Kafka 1.x for Oslo.Messaging and Monasca

Thanks for the update Joe. Let's start the discussion on the mailing list please. -- Dims On Wed, Jun 22, 2016 at 1:34 AM, Keen, Joe wrote: > Davanum, > We started work on getting Monasca into the global requirements with two > reviews [1] [2] that add gate jobs and check requirements jobs for

Re: [openstack-dev] [ironic] [ironic-python-agent] Broken functional tests

Hi, On Wed, Jun 22, 2016 at 10:53 AM, Sam Betts (sambetts) wrote: > This patch https://review.openstack.org/#/c/324909/ merged last night and > has broken the IPA functional tests. > > To verify pull master and run "tox -r -e func" and it¹ll fail to run. If > you git checkout the commit before th

[openstack-dev] [monasca] step-by-step installation guide

Hi, does there exist a step-by-step manual installation guide for Monasca? Something that is independent of DevStack. I have manually installed it recently for testing purposes and I could not find an up-to-date description. In case there is a need for it, I can prepare a guide to share on the

Re: [openstack-dev] [ironic] [ironic-python-agent] Broken functional tests

On 06/22/2016 12:55 PM, Lucas Alvares Gomes wrote: Hi, On Wed, Jun 22, 2016 at 10:53 AM, Sam Betts (sambetts) wrote: This patch https://review.openstack.org/#/c/324909/ merged last night and has broken the IPA functional tests. To verify pull master and run "tox -r -e func" and it¹ll fail to

Re: [openstack-dev] [ironic] [ironic-python-agent] Broken functional tests

Hi, >> I would say we should add a job to the IPA gate to verify the >> functional tests, just like swift does [0]. >> >> We may also need to revert/fix that patch that broke those tests. > > > I'm -1 to reverting anything until we have the test in the gate. > Fair enough. I've opened two bugs:

Re: [openstack-dev] RHEL free for developer use

On 22/06/16 03:33, Jeremy Stanley wrote: On 2016-06-21 14:48:58 +0200 (+0200), Zane Bitter wrote: That isn't my understanding, but it's hard to give a definitive answer without knowing what kinds of non-free software you're referring to (since I know there have been fierce disagreements even e.g

[openstack-dev] [neutron][general] Multiple implementation of /usr/bin/foo stored at the same location, leading to conflicts

tl;dr: Please don't reuse multiple times /usr/bin/neutron-l3-agent, instead call it /usr/bin/neutron-fwaas-l3-agent, as otherwise it makes it impossible for dpkg to install neutron-fwaas, and downstream distros must patch & hack. Hi, I've seen more than once the same file on /usr/bin/foo in diffe

Re: [openstack-dev] [nova][cinder] How to delete a volume which is attached to a server who was deleted

Please note that this Mailing List is not for usage questions. It is for development issues. You can reset the state of the volume and then delete it (admin only): cinder reset-state #sets to available From: Will Zhou Sent: Wednesday, June 22, 2016 1:22:31 AM

Re: [openstack-dev] [neutron][general] Multiple implementation of /usr/bin/foo stored at the same location, leading to conflicts

Yes, RDO faced the very same issue: https://github.com/rdo-packages/neutron-fwaas-distgit/blob/rpm-master/openstack-neutron-fwaas.spec#L115 My understanding was that neutron folks were looking for a solution, but we ship this workaround for now a month. Regards, H ___

Re: [openstack-dev] [packaging-deb] Status of the project

On 06/22/2016 12:34 PM, Neil Jerram wrote: > Is there a higher-level overview somewhere of what packaging-deb does? The goal is to do all of the OpenStack packaging directly within the OpenStack infra, with enough gating so that gerrit starts to make sense. > Should it be useful to me as the pac

Re: [openstack-dev] [packaging-deb] Status of the project

On 2016-06-22 14:42:21 +0200 (+0200), Thomas Goirand wrote: [...] > Currently, we're all in irc.debian.org, aka OFTC, in > #debian-openstack, before we move to a channel in Freenode, on > #openstack-pkg. BTW, why aren't the robots joining? [...] It looks like "openstackgerrit" (gerrit change repor

Re: [openstack-dev] [nova] Vendordata improvements

On 6/21/2016 12:53 AM, Michael Still wrote: So, https://review.openstack.org/#/c/317739 is basically done I think. I'm after people's thoughts on: - I need to do some more things, as described in the commit message. Are we ok with them being in later patches to get reviews moving on this? I'd

Re: [openstack-dev] RHEL free for developer use

On 2016-06-22 13:42:06 +0200 (+0200), Zane Bitter wrote: [...] > I'm not familiar with the ancient history, but the SRPMs dating back to the > first RHEL release in 2002 are publicly available for downloaded from: > > http://ftp.redhat.com/redhat/linux/enterprise/ [...] I don't think it has alway

Re: [openstack-dev] [nova] Vendordata improvements

On 06/22/2016 09:03 AM, Matt Riedemann wrote: > On 6/21/2016 12:53 AM, Michael Still wrote: >> So, https://review.openstack.org/#/c/317739 is basically done I think. >> I'm after people's thoughts on: >> >> - I need to do some more things, as described in the commit message. >> Are we ok with them

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Clint, In your original email, you proposed "So, with that, I'd like to propose the creation of an Architecture Working Group. This group's charge would not be design by committee, but a place for architects to share their designs and gain support across projects to move forward with and ratify

[openstack-dev] [openstack-ansible] L3HA problem

Hi, we deployed our openstack infrastructure with your « exciting » project openstack-ansible (mitaka 13.1.2) but we have some problems with L3HA after create router. Our infra (closer to the doc): 3 controllers nodes (with bond0 (br-mgmt, br-storage), bond1 (br-vxlan, br-vlan)) 2 compute node

[openstack-dev] [announce] Debian Jessie arm 64bits backports for Mitaka and Newton available

Hi everyone, I am pleased to announce that, as of today, there are arm64 backports to Jessie available in non-official backports repositories for Debian Jessie. Here are the URLs (repository definitions are available at the below addresses): http://newton-jessie-arm64.linaro.org/ http://mitaka-je

Re: [openstack-dev] [openstack-ansible] L3HA problem

Hi! What Keepalived version is used? On Wed, Jun 22, 2016 at 4:24 PM, fabrice grelaud < [email protected]> wrote: > Hi, > > we deployed our openstack infrastructure with your « exciting » project > openstack-ansible (mitaka 13.1.2) but we have some problems with L3HA after > create r

[openstack-dev] [new][ironic] ironic-python-agent 1.2.3 release (mitaka)

We are amped to announce the release of: ironic-python-agent 1.2.3: Ironic Python Agent Ramdisk This release is part of the mitaka stable release series. For more details, please see below. Changes in ironic-python-agent 1.2.2..1.2.3 --- d19558e Fix unwa

Re: [openstack-dev] [openstack-ansible] L3HA problem

On Wed, Jun 22, 2016 at 9:24 AM, fabrice grelaud wrote: > Hi, > > we deployed our openstack infrastructure with your « exciting » project > openstack-ansible (mitaka 13.1.2) but we have some problems with L3HA after > create router. > > Our infra (closer to the doc): > 3 controllers nodes (with bo

[openstack-dev] [new][ironic] ironic-python-agent 1.0.4 release (liberty)

We are jubilant to announce the release of: ironic-python-agent 1.0.4: Ironic Python Agent Ramdisk This release is part of the liberty stable release series. For more details, please see below. Changes in ironic-python-agent 1.0.3..1.0.4 --- b1471ea Fix

[openstack-dev] OpenStack Trove Ocata Midcycle, NYC, August 25 and 26.

The Trove midcycle will be held in midtown NYC, thanks to IBM for hosting the event, on August 25th and 26th. If you are interested in attending, please join the Trove meeting today, 2pm Eastern Time (#openstack-meeting-alt) and register at http://www.eventbrite.com/e/openstack-trove-ocata-midc

Re: [openstack-dev] [openstack-ansible] L3HA problem

Hi, keepalived 1:1.2.7-1ubuntu > Le 22 juin 2016 à 15:41, Anna Kamyshnikova a > écrit : > > Hi! > > What Keepalived version is used? > > On Wed, Jun 22, 2016 at 4:24 PM, fabrice grelaud > mailto:[email protected]>> wrote: > Hi, > > we deployed our openstack infrastructure with

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On Tue, 21 Jun 2016, Sylvain Bauza wrote: To be honest, Chris and you were saying that you don't like Flask, and I'm a bit agreeing with you. Why now it's a good possibility ? As I said when I started the other version of this same thread: What is most important to me is generating a consensus

Re: [openstack-dev] OpenStack Trove Ocata Midcycle, NYC, August 25 and 26.

[echoing what I just said on the openstack-operators ML since they just announced an Ops Midcycle in NYC also on the 25th and 26th] Hi Folks, FYI for those that may not be aware, that’s also the week of OpenStack East. OpenStack East runs August 23-24 also in New York City at the Playstation

Re: [openstack-dev] [openstack-ansible] L3HA problem

Keepalived 1.2.7 is bad version. Please, see comments in this bug https://bugs.launchpad.net/neutron/+bug/1497272. I suggest you to try one of the latest version of Keepalived. On Wed, Jun 22, 2016 at 5:03 PM, fabrice grelaud < [email protected]> wrote: > Hi, > > keepalived 1:1.2.7-1u

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On 21/06/16 12:12 -0600, Doug Wiegley wrote: On Jun 21, 2016, at 11:29 AM, Jay Pipes wrote: [snip] Perhaps you weren't around for the endless (and pointless) discussions around what is "the core of OpenStack"? Or you weren't around for the endless (and conflicting, contradictory, and religi

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On 20/06/16 11:31 -0700, Clint Byrum wrote: Excerpts from Joshua Harlow's message of 2016-06-17 15:33:25 -0700: Thanks for getting this started Clint, I'm happy and excited to be involved in helping try to guide the whole ecosystem together (it's also why I like being in oslo) to a architecture

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On 6/21/2016 10:12 PM, Angus Lees wrote: On Wed, 22 Jun 2016 at 05:59 Matt Riedemann mailto:[email protected]>> wrote: Angus, what should we be looking at from the privsep side for debugging this? The line above the screen-n-cpu.txt.gz failure you linked to is: 2016-06-21 16:2

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On Tue, 21 Jun 2016, Sean Dague wrote: I honestly don't think raw WSGI is a bad choice here. People are going to be pretty familiar with it in related projects at this level. Yeah, WSGI itself is a framework, one that is clearly defined and works well for the types of things we are currently t

Re: [openstack-dev] [tc][pbr][packaging][all] Definition of Data Files (config) in setup.cfg

On 06/12/2016 10:45 PM, Monty Taylor wrote: > On 06/11/2016 10:13 PM, Robert Collins wrote: >> On 12 June 2016 at 11:31, Thomas Goirand wrote: >>> On 06/11/2016 05:02 AM, Robert Collins wrote: >> ... >>> Then keystone.conf ends up installed in /usr/etc/keystone when setup.py >>> install is used. W

Re: [openstack-dev] [openstack-ansible] L3HA problem

> Le 22 juin 2016 à 15:45, Assaf Muller a écrit : > > On Wed, Jun 22, 2016 at 9:24 AM, fabrice grelaud > mailto:[email protected]>> wrote: >> Hi, >> >> we deployed our openstack infrastructure with your « exciting » project >> openstack-ansible (mitaka 13.1.2) but we have some probl

Re: [openstack-dev] [packaging-deb] Status of the project

On 06/22/2016 02:54 PM, Jeremy Stanley wrote: > It looks like "openstackgerrit" (gerrit change reports) is already > there, but "openstack" (channel logging) and "openstackstatus" > (infra status notifications, success submissions) are not yet > because the channel is not in the "meetbot_channels"

[openstack-dev] [designate] IRC Meeting today

Hi, Myself, Kiall and Federico are going to be caught up in some meetings today during the IRC meeting. Can someone chair the meeting? Thanks! - Graham __ OpenStack Development Mailing List (not for usage questions) Uns

[openstack-dev] [craton] patch submitted to OpenStack project-config

It will transfer both repos -- ~sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listin

Re: [openstack-dev] [craton] patch submitted to OpenStack project-config

Once the patch is merged and repos transferred, I will create the gerrit bits and jenkins job config. On Wednesday, June 22, 2016, sean roberts wrote: > It will transfer both repos > > -- > ~sean > -- ~sean __ OpenStack D

Re: [openstack-dev] [tc][pbr][packaging][all] Definition of Data Files (config) in setup.cfg

On Tue, Jun 14, 2016, at 05:36 AM, Julien Danjou wrote: > On Sun, Jun 12 2016, Monty Taylor wrote: > > > I will call hogwash on that. That we install files such as that which > > are actually code has been a deployer nightmare since day one, and the > > solution is not to make pip smarter, it's

Re: [openstack-dev] [neutron][general] Multiple implementation of /usr/bin/foo stored at the same location, leading to conflicts

On 06/22/2016 02:33 PM, Haïkel wrote: > Yes, RDO faced the very same issue: > https://github.com/rdo-packages/neutron-fwaas-distgit/blob/rpm-master/openstack-neutron-fwaas.spec#L115 > > My understanding was that neutron folks were looking for a solution, > but we ship this workaround for now a mon

Re: [openstack-dev] [openstack-ansible] L3HA problem

Thanks. I will test… Do you think trusty-backport is enough (1:1.2.13-1~ubuntu14.04.1) ? > Le 22 juin 2016 à 16:21, Anna Kamyshnikova a > écrit : > > Keepalived 1.2.7 is bad version. Please, see comments in this bug > https://bugs.launchpad.net/neutron/+bug/1497272 >

Re: [openstack-dev] [openstack-ansible] L3HA problem

> Le 22 juin 2016 à 17:35, fabrice grelaud a > écrit : > >> >> Le 22 juin 2016 à 15:45, Assaf Muller > > a écrit : >> >> On Wed, Jun 22, 2016 at 9:24 AM, fabrice grelaud >> mailto:[email protected]>> wrote: >>> Hi, >>> >>> we deployed our openstack infras

Re: [openstack-dev] [neutron][general] Multiple implementation of /usr/bin/foo stored at the same location, leading to conflicts

On Wed, Jun 22, 2016 at 05:55:48PM +0200, Thomas Goirand wrote: > Does neutron-fwaas also use "neutron" as launchpad package for bug report? Yes we do, just add the 'fwaas' tag to the bug. Thanks! --N. __ OpenStack Devel

[openstack-dev] [tripleo] [bigswitch] question about neutron bigswitch agent

Hey, I have a quick question for Bigswitch folks. I'm currently working on TripleO composable service and refactoring a bit of Neutron puppet code in TripleO Heat Templates. I need to know if when you deploy a compute node, if you actually need neutron plugins parameter (restproxy bits [1]). Look

Re: [openstack-dev] [openstack-ansible] L3HA problem

On Wed, Jun 22, 2016 at 12:02 PM, fabrice grelaud wrote: > > Le 22 juin 2016 à 17:35, fabrice grelaud a > écrit : > > > Le 22 juin 2016 à 15:45, Assaf Muller a écrit : > > On Wed, Jun 22, 2016 at 9:24 AM, fabrice grelaud > wrote: > > Hi, > > we deployed our openstack infrastructure with your «

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

I did have a question about the current implementation as described by 292499, 324379, and 292500. Looking at the code, when a NUMAPagesTopology object is create, a new parameter is passed for the "reserved" pages. This reservation comes from a dictionary, which is populated at LIbvirtDriver init

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

> On Jun 20, 2016, at 5:10 AM, Sean Dague wrote: > > On 06/14/2016 07:19 PM, Chris Hoge wrote: >> >>> On Jun 14, 2016, at 3:59 PM, Edward Leafe wrote: >>> >>> On Jun 14, 2016, at 5:50 PM, Matthew Treinish wrote: >>> But, if we add another possible state on the defcore side like conditi

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Amrith Kumar's message of 2016-06-22 13:15:03 +: > Clint, > > In your original email, you proposed "So, with that, I'd like to propose the > creation of an Architecture Working Group. This group's charge would not be > design by committee, but a place for architects to share th

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On 06/22/2016 01:59 PM, Chris Hoge wrote: > >> On Jun 20, 2016, at 5:10 AM, Sean Dague > > wrote: >> >> On 06/14/2016 07:19 PM, Chris Hoge wrote: >>> On Jun 14, 2016, at 3:59 PM, Edward Leafe >>> > wrote: On Jun 14, 2016, at 5:50 PM, Mat

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

> On Jun 22, 2016, at 11:24 AM, Sean Dague wrote: > > On 06/22/2016 01:59 PM, Chris Hoge wrote: >> >>> On Jun 20, 2016, at 5:10 AM, Sean Dague >> > wrote: >>> >>> On 06/14/2016 07:19 PM, Chris Hoge wrote: > On Jun 14, 2016, at 3:59 PM, Edward Leafe

Re: [openstack-dev] [all] Proposal: Architecture Working Group

> -Original Message- > From: Clint Byrum [mailto:[email protected]] > Sent: Wednesday, June 22, 2016 2:25 PM > To: openstack-dev > Subject: Re: [openstack-dev] [all] Proposal: Architecture Working Group > > Excerpts from Amrith Kumar's message of 2016-06-22 13:15:03 +: > > Clint, > > >

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On 06/22/2016 02:37 PM, Chris Hoge wrote: > >> On Jun 22, 2016, at 11:24 AM, Sean Dague wrote: >> >> On 06/22/2016 01:59 PM, Chris Hoge wrote: >>> On Jun 20, 2016, at 5:10 AM, Sean Dague >>> > wrote: On 06/14/2016 07:19 PM, Chris Hoge wrote: > >> On J

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On 6/22/16 12:01 PM, Sean Dague wrote: > On 06/22/2016 02:37 PM, Chris Hoge wrote: >>> On Jun 22, 2016, at 11:24 AM, Sean Dague wrote: >>> >>> On 06/22/2016 01:59 PM, Chris Hoge wrote: > On Jun 20, 2016, at 5:10 AM, Sean Dague > wrote: > > On 06/14/2016 07

[openstack-dev] [lbaas]HA for lbaas v2 agent

Hi, I have a multinode openstack installation (3 controller, 3 network nodes, and some compute nodes). Like l3 agent, is high availability feature available for the lbaas v2 agent? Thanks Akshay __ OpenStack Development Mailin

[openstack-dev] Notes from Trove weekly meeting

Notes from the Trove weekly meeting are at: http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-06-22-18.00.html A significant amount of the discussion related to https://review.openstack.org/#/c/332933/ [Document house rules for approving changes] The summary of the change pro

Re: [openstack-dev] [lbaas]HA for lbaas v2 agent

On Wed, Jun 22, 2016 at 3:17 PM, Akshay Kumar Sanghai wrote: > Hi, > I have a multinode openstack installation (3 controller, 3 network nodes, > and some compute nodes). > Like l3 agent, is high availability feature available for the lbaas v2 > agent? It is not. Nir Magnezi is working on a couple

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On 06/22/2016 03:13 PM, Jay Faulkner wrote: > > > On 6/22/16 12:01 PM, Sean Dague wrote: >> On 06/22/2016 02:37 PM, Chris Hoge wrote: On Jun 22, 2016, at 11:24 AM, Sean Dague wrote: On 06/22/2016 01:59 PM, Chris Hoge wrote: >> On Jun 20, 2016, at 5:10 AM, Sean Dague >

[openstack-dev] [ironic] Gate troubleshooting howto

There was a request at the mid-cycle for a presentation on troubleshooting Ironic gate failures. I'd be willing to share some of my knowledge about this to interested folks. I've created a doodle with a few possible times; note that one option is this Friday, but the others are in mid-July, as I'l

Re: [openstack-dev] [monasca] step-by-step installation guide

Hi Laszlo, There isn't an official install guide for Monasca. This is one of the missing pieces in the Monasca project and I would love to see it added. There were some blog's written by Victor Munteanu over a year ago that might be good referring too. http://blog.zhaw.ch/icclab/how-to-install-

Re: [openstack-dev] [nova] Vendordata improvements

On Wed, Jun 22, 2016 at 11:13 PM, Sean Dague wrote: > On 06/22/2016 09:03 AM, Matt Riedemann wrote: > > On 6/21/2016 12:53 AM, Michael Still wrote: > >> So, https://review.openstack.org/#/c/317739 is basically done I think. > >> I'm after people's thoughts on: > >> > >> - I need to do some more

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On 10:27 Jun 20, Clint Byrum wrote: > Excerpts from Doug Wiegley's message of 2016-06-20 10:40:56 -0600: > > So, it sounds like you’ve just described the job of the TC. And they have > > so far refused to define OpenStack, leading to a series of derivative > > decisions that seem … inconsistent o

[openstack-dev] Openstack Neutron lbaas question

Dear Openstack Team: I have some questions regarding to openstack Mitaka Neutron lbaas For Neutron-lbaas installation, should I just follow this LINKhttps://wiki.openstack.org/wiki/Neutron/LBaaS/HowToRunbut my openstack has controller and compute nodes. is not installed by Devstack, it is manual

[openstack-dev] [grenade] upgrades vs rootwrap

So how does rootwrap fit into the "theory of upgrade"? The doc talks about deprecating config, but is silent on when new required config (rootwrap filters) should be installed. By virtue of the way the grenade code works (install N from scratch, attempt to run code from N+1), we effectively have

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote: > Le 22/06/2016 à 10:49, Thomas Goirand a écrit : > > Do you think it looks like possible to have Nova ported to Py3 during > > the Newton cycle? > > It doesn't depend on me: I'm sending patches, and then I have to wait for > reviews.

[openstack-dev] [midonet] NetlinkInterfaceSensor timeout causes failure of networking

Hi Midoers, I'm running a small production system for a long time, which deploys v2014.11 version because the Openstack cluster is Icehouse and the end-user doesn't want to upgrade it. Currently, this exception occurs periodically which causes network connection failure for virtual machines. WAR

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

2016-06-22 22:52 GMT+08:00 Chris Dent : > On Tue, 21 Jun 2016, Sean Dague wrote: > > I honestly don't think raw WSGI is a bad choice here. People are going >> to be pretty familiar with it in related projects at this level. >> > > Yeah, WSGI itself is a framework, one that is clearly defined and w

Re: [openstack-dev] [kolla] better solution for the non-ini format configure file

Link: https://openstack.nimeyo.com/83165/?show=88496#a88496 From: AndrewLiu Recently, we find this feature of ansible:http://docs.ansible.com/ansible/playbooks_loops.html#finding-first-matched-files A specific path of template file can be add in the ansible task. If a user want to customize an

Re: [openstack-dev] [tripleo] [bigswitch] question about neutron bigswitch agent

Ok I found what I wanted, for the record, only python-networking-bigswitch is required on the compute node, and not the restproxy options in neutron. On Wed, Jun 22, 2016 at 1:04 PM, Emilien Macchi wrote: > Hey, > > I have a quick question for Bigswitch folks. > I'm currently working on TripleO c

[openstack-dev] [daisycloud-core] OPNFV Summit update

Hi Team, You can find new presentation about daisycloud at https://wiki.opnfv.org/display/PROJ/Daisy4NFV from the OPNFV Summit. You can also find another presentation about daisy highlights compared with other installers. -- Yours, Jason ___