[openstack-dev] [vitrage] Vitrage IRC meetings - notice the change of time

Hi, Reminder: Vitrage weekly meeting time and channel were be changed to: Wednesday at 8:00 UTC, #openstack-meeting-4 See you on Wednesday, Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

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

On 05/16/2016 04:35 PM, Adam Young wrote: On 05/16/2016 05:23 AM, Dmitry Tantsur wrote: On 05/14/2016 03:00 AM, Adam Young wrote: On 05/13/2016 08:21 PM, Dieterly, Deklan wrote: If we allow Go, then we should also consider allowing JVM based languages. Nope. Don't get me wrong, I've written

Re: [openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

Hi, Actually the breakage is not sue to Q_L3_ENABLED. It is due to https://review.openstack.org/#q,d894221457efa3a2a0bf3db76a4c5e8ffba36e29,n, z The Q_L3_ENABLED is something that each CI can configure depending on what their supported mode is. Until now this mean that L3 was supported by the

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

On 05/16/2016 05:09 PM, Ian Cordasco wrote: -Original Message- From: Dmitry Tantsur Reply: OpenStack Development Mailing List (not for usage questions) Date: May 16, 2016 at 09:55:27 To: openstack-dev@lists.openstack.org

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

On 05/12/2016 08:26 PM, Ilya Chukhnakov wrote: > Hi everyone. > > I’ve recently found that straightforward use of NeutronDbObject is prone to > concurrency-related problems. > > I’ve submitted a patch set [3] with some tests to show that without special > treatment using NeutronDbObject could lead

Re: [openstack-dev] [vitrage] Normalized Resource State

> -Original Message- > From: EXT Malin, Eylon (Nokia - IL) [mailto:eylon.ma...@nokia.com] > Sent: Monday, May 16, 2016 6:09 PM > > Hi all, > > Aggregated_state can has only values from NormalizedResourceState which > is constant enum. > Currently the NormalizedResourceState has these

Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

Le 16/05/2016 16:12, Peter Stachowski a écrit : We're aware that there are ways to mock (and un-mock) correctly. We're trying to make sure that all our new test code follows those patterns. We also decided that it wouldn't make sense to change all the working tests to use the 'right' methods as

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

On 16/05/16 00:23 -0700, Clint Byrum wrote: Excerpts from Nikhil Komawar's message of 2016-05-14 17:42:16 -0400: Hi all, Lately I have been involved in discussions that have resulted in giving a wrong idea to the approach I take in operating the (Glance) team(s). While my approach is

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

On 5/15/2016 7:42 PM, Jason Kölker wrote: On Sun, May 15, 2016 at 3:56 PM, Sean M. Collins wrote: Matt Riedemann wrote: The nova create-server API allows passing a network id that's prefixed with br- [1]. That was added due to this bug from Folsom [2]. I'm wondering if

Re: [openstack-dev] [openstack-ansible] LBaaSv2 / Octavia support

On 05/15/2016 04:53 AM, Xav Paice wrote: > Great stuff! - that's covered everything I've been looking at so far, except > that we're not wanting to run neutron-server (and therefore the octavia api) > on the same boxes as the Neutron L3 agent (where I understand we need to run > the worker).

[openstack-dev] [mistral] Team meeting minutes - 05/16/2016

Thanks for joining our team meeting today! In case you want to see what we discussed, Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2016/mistral.2016-05-16-16.01.html Meeting log:

[openstack-dev] [craton] meeting notes

first team meeting notes here https://etherpad.openstack.org/p/craton-meeting-2016-05-16 We have two weeks until M1, which is a good date to finalize what features we will have in the newton release. We proposed the project name Craton to stick. Let's propose an alternative here quickly if

Re: [openstack-dev] [TripleO] Aodh upgrades - Request backport exception for stable/liberty

>From what I've seen of the IRC discussion it sounds like we're doing this, but can we at least agree that it is a bad way to handle service replacement? First, we are completely replacing a service on a minor upgrade, which even if it is a 100% compatible drop-in replacement may have

Re: [openstack-dev] [kolla] Vagrant environment for kolla-kubernetes

(continuing to top post) I wasn't arguing otherwise for the record. My comment was merely to remind that coupling between the two repos should be kept at a minimum. But I'm fully in favor of any coupling that eliminates code duplication. On Fri, May 13, 2016 at 2:51 PM, Steven Dake (stdake)

[openstack-dev] [kolla] Prepare for Ansible 2.0

Hey folks, As distros move to Ansible 2.0 and Ansible 1.9 is unsupported by upstream and essentially unmaintained, I suggest we move Kolla to Ansible 2.y series. The blueprint is here: https://blueprints.launchpad.net/kolla/+spec/ansible2 I'm not sure if Jeffrey is actively working on this,

Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

Victor, You're right, all the tests are currently passing the detector. There is still legacy code that does unmocking the 'old' way and there is a fair bit of it. Our concern if you remove the detector is that objects that have been mocked might not be unmocked correctly (due to copy/paste)

Re: [openstack-dev] [Openstack-operators] [glance] glance-registry deprecation: Request for feedback

On 13/05/16 17:10 -0400, Nikhil Komawar wrote: On 5/13/16 4:29 PM, Flavio Percoco wrote: On 13/05/16 15:52 -0400, Nikhil Komawar wrote: On 5/13/16 3:36 PM, Flavio Percoco wrote: On 12/05/16 21:41 -0400, Nikhil Komawar wrote: I have been of the same opinion as far as upgrades go. I think

Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

Victor, To correct the math, Python3 runs 686 tests in 15.971s or 42.95 tests per second. Python2 runs 1495 tests in 22.595s or 66.16 tests per second. Python2 is 54% faster (but even that's just an estimate, since it assumes all tests run at the same speed, which isn't true - plus it runs

[openstack-dev] [kolla] Newton Milestone #1 and #2 obectives

Hey OpenStackers, I'd like to point out a few commitments made at OpenStack summit during various discussions among the community. Our direction (if your looking for work to do ;) should be the following: * Ansible 2.0 implementation. * Making the dashboard load automated. *

[openstack-dev] [tripleo] Reason for installing devstack in CI pipeline

Greetings, Over the last few weeks I've been head deep into understanding the TripleO CI pipeline. For the most part, I am happy that we have merged centos-7 DIB support and I'm working to migrate the jobs to it. Something I have been trying to figure out, is why does the pipeline install

Re: [openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

Hi, This is even more motivation for us to revert the patch. Please consider this. Thanks Gary On 5/16/16, 6:23 PM, "Sean M. Collins" wrote: >Gary Kotton wrote: >> Hi, >> Actually the breakage is not sue to Q_L3_ENABLED. It is due to >>

Re: [openstack-dev] [craton] meeting notes

Thanks for the notes. Is the agreement to work using Craton as a base for the fleet management ? Tim From: sean roberts Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Monday 16 May 2016 at 17:51 To:

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

On 05/16/2016 05:49 PM, Ilya Chukhnakov wrote: > On 16 May 2016, at 18:18, Michał Dulko > wrote: >> In Cinder we're handling similar problems related to race conditions >> between status check and status change with conditional updates. >>

Re: [openstack-dev] [ironic] usage of ironic-lib

> -Original Message- > From: Lucas Alvares Gomes [mailto:lucasago...@gmail.com] > What I don't think we should do is say that the library's _right now_ > ready for it, the interfaces we have at the moment should not be > considered stable, Ironic is very opinionated in many aspects >

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

On 16 May 2016, at 18:18, Michał Dulko wrote: > In Cinder we're handling similar problems related to race conditions > between status check and status change with conditional updates. > Basically we're doing "UPDATE table SET status='abc' WHERE id=1 AND >

Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

> -Original Message- > From: Victor Stinner [mailto:vstin...@redhat.com] > Sent: Monday, May 16, 2016 12:10 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [trove] timeouts in

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

Hi Tim, Sounds good. I’ll take a look at the links you sent below and will let you know if I have any questions. Thanks, Alexey From: Tim Hinrichs [mailto:t...@styra.com] Sent: Thursday, May 12, 2016 9:53 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

Re: [openstack-dev] [ironic] usage of ironic-lib

I personally disagree with saying that if we wanted it make it usable by projects other than ones in the Ironic umbrella it should go into oslo. I think that non-ironic projects directly related to Ironic such as out of tree drivers etc, should be able to utilise the code placed into ironic-lib.

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

On 16 May 2016, at 8:14, Dmitry Tantsur wrote: > On 05/16/2016 05:09 PM, Ian Cordasco wrote: >> >> >> -Original Message- >> From: Dmitry Tantsur >> Reply: OpenStack Development Mailing List (not for usage questions) >> >> Date:

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

hi, On Mon, May 16, 2016 at 9:00 PM, Ihar Hrachyshka wrote: > +1 for earlier time. But also, have we booked any channel for the meeting? > Hijacking #openstack-neutron may not work fine during such a busy (US) time. > I suggest we propose a patch for >

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

On Mon, May 16, 2016 at 10:25 PM, Takashi Yamamoto wrote: > hi, > > On Mon, May 16, 2016 at 9:00 PM, Ihar Hrachyshka wrote: >> +1 for earlier time. But also, have we booked any channel for the meeting? >> Hijacking #openstack-neutron may not work fine

Re: [openstack-dev] [sahara] Nominating new members to Sahara Core

1. Lu Huichun +2 2. Nikita Konovalov +2 3. Chad Roberts +2 -- Sergey R. 2016-05-13 18:33 GMT+03:00 Vitaly Gridnev : > Hello Sahara core folks! > > I'd like to bring the following folks to Sahara Core: > > 1. Lu Huichun > 2. Nikita Konovalov > 3. Chad Roberts > > Let's

Re: [openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

Gary Kotton wrote: > Hi, > Actually the breakage is not sue to Q_L3_ENABLED. It is due to > https://review.openstack.org/#q,d894221457efa3a2a0bf3db76a4c5e8ffba36e29,n, > z > The Q_L3_ENABLED is something that each CI can configure depending on what > their supported mode is. > Until now this mean

Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

Le 16/05/2016 16:12, Peter Stachowski a écrit : Amrith is right though - python34 is *much* slower running this check (and somewhat in general) than python27. Maybe that doesn't translate into real-world performance data, but it has made me a bit nervous nonetheless. IMHO we should look more

Re: [openstack-dev] [api] [senlin] [keystone] [ceilometer] [telemetry] Questions about api-ref launchpad bugs

On Mon, May 16, 2016 at 8:04 AM, Atsushi SAKAI wrote: > Anne > > I move and clean up api-site issues as far as I can do. > But it still remain 36 open bugs. > mainly WADL, INCOMPLETE status, FIX COMMITED status, > and too many project issue (like 1390528, 1390523

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

On 05/16/2016 05:21 PM, John Dickinson wrote: On 16 May 2016, at 8:14, Dmitry Tantsur wrote: On 05/16/2016 05:09 PM, Ian Cordasco wrote: -Original Message- From: Dmitry Tantsur Reply: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] OpenStack Developer Mailing List Digest May 7-13

HTML render: http://www.openstack.org/blog/2016/05/openstack-developer-mailing-list-digest-20160513/ SuccessBot Says === * Pabelanger: bare-precise has been replaced by ubuntu-precise. Long live DIB * bknudson: The Keystone CLI is finally gone. Long live openstack CLI. * Jrichli:

Re: [openstack-dev] [all][release] change in release announcement emails

Excerpts from Dmitry Tantsur's message of 2016-05-16 11:26:16 +0200: > On 05/13/2016 07:40 PM, Doug Hellmann wrote: > > The release team has recently landed a change to the script that > > generates the automated release announcement emails send to > > openstack-dev and openstack-announce when a

Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

Le 16/05/2016 13:52, Amrith Kumar a écrit : IMHO the strange mock detector code must be removed. It is very slow and I don't understand its purpose. [amrith] It serves and has served a very useful purpose and that is to detect bad tests where code has (and we've had lots of trouble with this)

Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

Le 09/05/2016 16:16, Peter Stachowski a écrit : Hi Amrith, We’ve had a lot of ‘new’ tests enabled for py34 in the last week – from your results you can see it’s running 6x the number of tests (although it’s taking 8.5x as long). It looks like python3 isn’t as fast as python2.7? If so, we may

[openstack-dev] [TripleO] Aodh upgrades - Request backport exception for stable/liberty

Hi Everyone: I wanted to start a discussion around considering backporting Aodh to stable/liberty for upgrades. We have been discussing quite a bit on whats the best way for our users to upgrade ceilometer alarms to Aodh when moving from liberty to mitaka. A quick refresh on what changed, In

Re: [openstack-dev] [python3][performance][python] [trove] timeouts in gate-trove-python34-db

Thanks Victor, I see your question on Infra. I'm going to restate it here just in case someone who reads the ML notices it. hi. i'm investigating "Random timeout on gate-trove-python34-db" https://bugs.launchpad.net/trove/+bug/1582257 : i noticed that python 2 has many precompiled wheel

Re: [openstack-dev] [ironic][openstackclient] deprecation process

Thanks Steve, that’s exactly what I wanted to know! —ruby From: Steve Martinelli > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date:

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

  -Original Message- From: Dmitry Tantsur Reply: OpenStack Development Mailing List (not for usage questions) Date: May 16, 2016 at 09:55:27 To: openstack-dev@lists.openstack.org Subject:  Re:

Re: [openstack-dev] [ironic] usage of ironic-lib

Hi, On Mon, May 16, 2016 at 3:56 PM, Sam Betts (sambetts) wrote: > I personally disagree with saying that if we wanted it make it usable by > projects other than ones in the Ironic umbrella it should go into oslo. I > think that non-ironic projects directly related to Ironic

Re: [openstack-dev] [ironic] usage of ironic-lib

Hi, I'd like to point that ironic-lib is already used outside of Ironic tree - for the third-party deployment drivers, e.g this fuel-agent based one [0]. [0] https://github.com/openstack/fuel-agent/blob/master/contrib/ironic/ironic-fa-deploy/ironic_fa_deploy/modules/fuel_agent.py#L30 Best

Re: [openstack-dev] [vitrage] Normalized Resource State

Sounds good Ifat and Eylon. Maybe we only need to think of a more general name for TERMINATING state (something that will include all end transient states). > -Original Message- > From: Afek, Ifat (Nokia - IL) [mailto:ifat.a...@nokia.com] > Sent: Monday, May 16, 2016 6:29 PM > To:

Re: [openstack-dev] [javascript] [infra] NPM Mirrors (IMPORTANT)

Hey there, Vitaly- I suspect that the issue you're encountering is actually a cross-atlantic lag, combined with the Mirror's AFS cache warming up. As of this morning, fuel-ui seems to be installing fine from dfw.rax, though you may run into similar issues with other mirrors until those caches

[openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

Hi, During the neutron refactor of DevStack, I made a conscious decision to take the Q_L3_ENABLED variable and change the default from False to True. Most DevStack installations will want to have L3 services enabled, so my thinking was, let's make it the default. That broke some people last

Re: [openstack-dev] [sahara] Nominating new members to Sahara Core

+2 for all On Fri, 2016-05-13 at 18:33 +0300, Vitaly Gridnev wrote: > Hello Sahara core folks! > > > I'd like to bring the following folks to Sahara Core: > > > 1. Lu Huichun > 2. Nikita Konovalov > 3. Chad Roberts > > > Let's vote with +2/-2 for additions above. > > > [0]

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

Tom, Devil's advocate here.. :) Can you offer examples of other OpenStack API services which behave in this way with a API? I'm struggling to think of any off the top of my head, but admittedly don't know all the ins and outs of OpenStack ;) Thanks -steve On 5/16/16, 2:28 AM, "Cammann,

[openstack-dev] [ironic] usage of ironic-lib

Hi, A patch to ironic-lib made me wonder about what is our supported usage of ironic-lib. Or even the intent/scope of it. This patch changes a method, ‘bootable’ parameter is removed and ‘boot_flag’ parameter is added [1]. If this library/method is used by some out-of-tree thing (or even some

Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

Victor, We're aware that there are ways to mock (and un-mock) correctly. We're trying to make sure that all our new test code follows those patterns. We also decided that it wouldn't make sense to change all the working tests to use the 'right' methods as that could have the short-term

Re: [openstack-dev] [ironic] usage of ironic-lib

Hi, Thanks for starting this discussion Ruby. On Mon, May 16, 2016 at 2:57 PM, Loo, Ruby wrote: > Hi, > > A patch to ironic-lib made me wonder about what is our supported usage of > ironic-lib. Or even the intent/scope of it. This patch changes a method, > ‘bootable’

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

On 05/16/2016 05:23 AM, Dmitry Tantsur wrote: On 05/14/2016 03:00 AM, Adam Young wrote: On 05/13/2016 08:21 PM, Dieterly, Deklan wrote: If we allow Go, then we should also consider allowing JVM based languages. Nope. Don't get me wrong, I've written more than my fair share of Java in my

Re: [openstack-dev] [neutron]Get one network's usage

On Mon, May 16, 2016 at 4:38 AM, zhi wrote: > hi, all > > Many times we want to get one network's usage. Like this command: > "neutron get-network-usage". We can get how many ports were used in this > network. Besides, we can get floatingips usage from external

[openstack-dev] [vitrage] Normalized Resource State

Hi all, Aggregated_state can has only values from NormalizedResourceState which is constant enum. Currently the NormalizedResourceState has these values : TERMINATED,  ERROR, UNRECOGNIZED ,  SUSPENDED ,   RESCUED ,  RESIZED ,  TRANSIENT ,  SUBOPTIMAL,   RUNNING ,  UNDEFINED. I think that 2

Re: [openstack-dev] [sahara] Nominating new members to Sahara Core

On 05/13/2016 11:33 AM, Vitaly Gridnev wrote: I'd like to bring the following folks to Sahara Core: 1. Lu Huichun +2 2. Nikita Konovalov +2 3. Chad Roberts +2 regards, mike __ OpenStack Development Mailing List

Re: [openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

I disagree. Sadly I approved the patch and it breaks all of the plugins that have L3 support but do not require an agent. Would it be possible that we unblock all of the plugins and try and work towards a better solution. The OVN example is good but that have a very small subset of tests. Thanks

Re: [openstack-dev] [ironic] usage of ironic-lib

I tend to agree with Lucas. I think ironic-lib was designed to have common code to be used primarily into ironic and IPA. It was not intended to be used in other projects. We tend to add methods in the ironic-lib with Ironic and IPA in mind and never thought of it could be used by out of tree

Re: [openstack-dev] [Rally] Could you share reference for Mitaka Upadates

Yuki, Sorry for long reply. Here are the slides: https://docs.google.com/presentation/d/1g5fd2BJXc40yienjCB0Fuc8NaB0e5pQO0XbUHQ1CY0s Best regards, Boris Pavlovic On Tue, May 10, 2016 at 12:16 AM, Yuki Nisiwaki wrote: > To: Mr. Boris > cc: OpenStacker who is interested in

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

Hi All, We will have the Cinder-Nova interaction changes meetings in a new slot starting from this week. The new slot is __Tuesday, 1700UTC__. We will also move it to another channel, which is the __#openstack-meeting-alt__. Related etherpad:

[openstack-dev] [tosca-parser] [heat-translator] [heat] [tacker] [opnfv] TOSCA-Parser and Heat-Translator 0.5.0 release

Hello Everyone, On behalf of the TOSCA-Parser and Heat-Translator team, I am pleased to announce the 0.5.0 PyPI release of tosca-parser and heat-translator which can be downloaded from https://pypi.python.org/pypi/tosca-parser and https://pypi.python.org/pypi/heat-translator respectively.

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

Sounds ok, but there needs to be a careful upgrade/migration path, where both are supported until after all pods are migrated out of nodes that are in the resourcegroup. Thanks, Kevin From: Hongbin Lu Sent: Sunday, May 15, 2016 3:49:39 PM To: OpenStack

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

I think I remember something about resourcegroups having a way to delete one of them too. Might double check. Thanks, Kevin From: Cammann, Tom Sent: Monday, May 16, 2016 2:28:24 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

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

> On May 16, 2016, at 7:59 AM, Steven Dake (stdake) wrote: > > Tom, > > Devil's advocate here.. :) > > Can you offer examples of other OpenStack API services which behave in > this way with a API? The more common pattern is actually: or: Examples: # trove

Re: [openstack-dev] [nova] api-ref sprint Monday update

On 05/09/2016 08:23 AM, Sean Dague wrote: > There is a lot of work to be done to get the api-ref into a final state. > > Review / fix existing patches - > https://review.openstack.org/#/q/project:openstack/nova+file:api-ref+status:open > shows patches not yet merged. Please review them, and if

Re: [openstack-dev] [TripleO] Aodh upgrades - Request backport exception for stable/liberty

On Mon, May 16, 2016 at 12:25 PM, Ben Nemec wrote: > From what I've seen of the IRC discussion it sounds like we're doing > this, but can we at least agree that it is a bad way to handle service > replacement? > > First, we are completely replacing a service on a minor

[openstack-dev] [Infra] Meeting Tuesday May 17th at 19:00 UTC

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

Re: [openstack-dev] [Neutron][L2GW] Mitaka release of L2 Gateway now available

On 16 May 2016 at 05:15, Ihar Hrachyshka wrote: > > > On 11 May 2016, at 22:05, Sukhdev Kapur wrote: > > > > > > Folks, > > > > I am happy to announce that Mitaka release for L2 Gateway is released > and now available at

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

Hi, We are quick 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 9 May 2016): - Ironic: 190 bugs (0) + 177 wishlist items (+4). 0 new (-17), 134 in progress (+1),

Re: [openstack-dev] [TripleO] Aodh upgrades - Request backport exception for stable/liberty

On Mon, May 16, 2016 at 10:34 AM, Pradeep Kilambi wrote: > Hi Everyone: > > I wanted to start a discussion around considering backporting Aodh to > stable/liberty for upgrades. We have been discussing quite a bit on whats > the best way for our users to upgrade ceilometer alarms

Re: [openstack-dev] [TripleO] Austin summit - session recap/summary

On Mon, May 09, 2016 at 04:50:19PM -0400, Paul Belanger wrote: > On Fri, May 06, 2016 at 09:18:03AM -0400, Paul Belanger wrote: > > On Tue, May 03, 2016 at 05:34:55PM +0100, Steven Hardy wrote: > > > Hi all, > > > > > > Some folks have requested a summary of our summit sessions, as has been > > >

Re: [openstack-dev] [nova] api-ref sprint Monday update

On 05/16/2016 03:18 PM, Sean Dague wrote: > On 05/09/2016 08:23 AM, Sean Dague wrote: >> There is a lot of work to be done to get the api-ref into a final state. >> >> Review / fix existing patches - >> https://review.openstack.org/#/q/project:openstack/nova+file:api-ref+status:open >> shows

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

Hi Uri, I hope all the replies have helped answer your question. To echo what Paul said, the networking-sfc approach is to separate the API from the backend drivers. The actual data plane forwarder is not part of networking-sfc. We aren't going to maintain the out-of-tree OVS NSH code. When

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

On Mon, May 16, 2016 at 10:10 AM, Flavio Percoco wrote: > On 16/05/16 00:23 -0700, Clint Byrum wrote: > >> Excerpts from Nikhil Komawar's message of 2016-05-14 17:42:16 -0400: >> >>> Hi all, >>> >>> >>> Lately I have been involved in discussions that have resulted in giving

[openstack-dev] [oslo][all] oslo.log `verbose` and $your project

Hi all, I just wanted to ensure folks are aware that the oslo group has removed the 'verbose' option and the hence-forth the 'debug' option should just be used (having to options that did very similar things was very confusing to folks). This deprecation for this was merged on aug 1, 2015

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

On 17:59 May 16, Ildikó Váncsa wrote: > Hi All, > > We will have the Cinder-Nova interaction changes meetings in a new slot > starting from this week. The new slot is __Tuesday, 1700UTC__. We will also > move it to another channel, which is the __#openstack-meeting-alt__. > > Related etherpad:

[openstack-dev] [tacker] Agenda for weekly IRC meeting

Tackers, This week's meeting will be wholly focused on alarm based monitoring and auto-scaling work. https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_May_17.2C_2016 1600 UTC Tuesday - Announcements - Alarm based VDU Monitoring & Scaling - User Scenarios - Scope - what

Re: [openstack-dev] [TripleO] Aodh upgrades - Request backport exception for stable/liberty

On Mon, May 16, 2016 at 3:33 PM, James Slagle wrote: > On Mon, May 16, 2016 at 10:34 AM, Pradeep Kilambi wrote: > > Hi Everyone: > > > > I wanted to start a discussion around considering backporting Aodh to > > stable/liberty for upgrades. We have been

[openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension

Hi everyone, We will have the first meeting discussion on Common Flow classifier at 1700 UTC on openstack-neutron channel 5/17/2016. Based on our etherpad action item in the Austin Summit meeting, Louis and I have created a wiki page for this work, describing the work overview and API design

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

I would vote for the OSC pattern to make it easier for the users, since we already expect that migration path. Also agree with Tom that this is a significant change so we should write a spec to think through carefully. Ton, From: Adrian Otto To: "OpenStack

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

> On 16 May 2016, at 20:01, Michał Dulko wrote: > > It's not directly related, but this reminds me of tests done by geguileo > [1] some time ago that were comparing different methods of preventing DB > race conditions in concurrent environment. Maybe you'll also find

Re: [openstack-dev] [neutron]Get one network's usage

How is that different than "neutron port-list --network-id=" ? On Mon, May 16, 2016 at 1:38 AM, zhi wrote: > hi, all > > Many times we want to get one network's usage. Like this command: > "neutron get-network-usage". We can get how many ports were used in this >

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

Thanks for your reply. No offense intended (on the earlier one). I really want us to make sure all of us are on the same page on this thread. On 5/16/16 11:32 PM, John Griffith wrote: > > > On Mon, May 16, 2016 at 7:43 PM, Nikhil Komawar >

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

On Mon, May 16, 2016 at 7:43 PM, Nikhil Komawar wrote: > > First of all, are you serious? This is not the right email thread for > such issue complaints. This thread is about communication and not just > for Glance but for [tc] and [all]! > > Secondly, you have not

[openstack-dev] [kolla] How to get prebuilt all images from dockerhub for a specific tag

Hi, Kolla fellows, The latest quickstart.rst says: "the `dockerhub image registry https://hub.docker.com/u/kollaglue/`__ contains all images from each of Kolla’s major releases. " So I decided to get images from above URL to save time for building them. But when I trying to get the all

Re: [openstack-dev] [Neutron][L2GW] Mitaka release of L2 Gateway now available

On 11 May 2016 at 16:05, Sukhdev Kapur wrote: > > Folks, > > I am happy to announce that Mitaka release for L2 Gateway is released and > now available at https://pypi.python.org/pypi/networking-l2gw. > > You can install it by using "pip install networking-l2gw" > > This

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

> -Original Message- > From: Mike Perez [mailto:thin...@gmail.com] > Sent: May 17, 2016 02:23 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly > IRC meetings > > On 17:59 May 16, Ildikó

Re: [openstack-dev] [telemetry] Gate broken by openstack/requirements

>From IRC discussion I got that Telemetry team opted out of using global-requirements and upper-constraints altogether a while ago, so I understand why my proposal is not an option. On Mon, May 16, 2016 at 3:33 PM Yuriy Taraday wrote: > Isn't it just a matter of updating

Re: [openstack-dev] [api] [senlin] [keystone] [ceilometer] [telemetry] Questions about api-ref launchpad bugs

Anne 　 　I move and clean up api-site issues as far as I can do. But it still remain 36 open bugs. mainly WADL, INCOMPLETE status, FIX COMMITED status, and too many project issue (like 1390528, 1390523 etc) Would you check it? Thanks Atsushi SAKAI On Wed, 11 May 2016 10:04:06 -0500 Anne

[openstack-dev] [nova] upgrade connection_info when Ceph mon IP changed

Hi all： I got a problem described in https://bugs.launchpad.net/cinder/+bug/1452641, and my colleague got another similar problem described in https://bugs.launchpad.net/nova/+bug/1581367. It's all about the storage backend ip change. With the storage backend, not only Ceph but also

[openstack-dev] A Summary of Design Summit Summaries (!)

Hiya, A couple of folk were kind enough to point out that the list I'd collated each week in Lwood [1] of Design Summit Project summaries was of use to them. Thus inspired I've just done a blog post (which will appear on planet.openstack.org too) which brings them all into a single article;

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

I have an opposing point of view. In summary of below, there are actually three kinds of style. 1. The “python-*client” style. For example: $ magnum node-add [--flavor ] 2. The OSC style. For example: $ openstack bay node add [--flavor ] 3. The proposed style (which is a mix of #1 and #2).

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

First of all, are you serious? This is not the right email thread for such issue complaints. This thread is about communication and not just for Glance but for [tc] and [all]! Secondly, you have not mentioned _anything_ about the upgrade numbers/releases. You may want to notice the *major* API

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

On 5/16/16 4:26 AM, Julien Danjou wrote: > On Sat, May 14 2016, Nikhil Komawar wrote: > >> I think people prefer to use ML a lot and I am not a great fan of the >> same. It is a multi-cast way of communication and it has assumptions >> around time, space, intent of the audience & intent to

Re: [openstack-dev] [Storlets] Swift copy middlleware

wrote on 16/05/2016 04:32:58 AM: > From: > To: > Date: 16/05/2016 04:36 AM > Subject: Re: [openstack-dev] [Storlets] Swift copy middlleware > > > I agree with Kota, and I think this is the easiest way to fix

[openstack-dev] Nova API is run on controller node instead of Compute node

Hi All, I have setup the Openstack controller and compue node on 2 VMs in my windows 8 Laptop. It is running. I am starting development for the NOVA compute APIs. To kick-off, i am trying to call compute API, for example: $nova hypervisor-list Response is OK. It should call the 'show'

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

Hi, tl;dr We need everyone agreeing and understanding the "why" behind what we are doing. A shared language/understanding of the context is an important part of that. Writing things down, and giving people links to that, really helps. On 15 May 2016 at 13:07, Chris Dent

Re: [openstack-dev] Nova API is run on controller node instead of Compute node

On 16 May 2016 at 09:58, Tarun wrote: > Hi All, > > I have setup the Openstack controller and compue node on 2 VMs in my windows > 8 Laptop. > > It is running. > > I am starting development for the NOVA compute APIs. > > To kick-off, i am trying to call compute API, for

  1   2   >