Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

+1, welcome to the team. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Wed, May 4, 2016 at 4:20 AM, John Griffith wrote: > Definitely a +1 from me > > On Tue, May 3, 2016 at 6:10 PM, Patrick East > wrote: > >> +1, Michal has done some awesome work on Cinder! >> >> -Patrick >> >> On Tue,

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

> On 04 May 2016, at 04:47, Dmitriy Ukhlov wrote: > > Hi Joshua. > > I think than Mistral have already fast solution - they customised > oslo.messaging rpc to achieve ack-after-process in Mistral code base Dmitri, I disagree. This is not any kind of a decent solution, it is a very very very

Re: [openstack-dev] [nova] post-copy live migration

Hi all, Based on Live Migration IRC meeting discussions, I've uploaded an updated patch set for the "add post-copy live migration support to Nova" specs (https://review.openstack.org/#/c/301509/). Based on that discussions, the proposed way of including the post-copy live migration capability

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

> On 04 May 2016, at 13:21, Mehdi Abaakouk wrote: > > >> That said, I agree with Mehdi that *most* RPC calls throughout OpenStack, >> not being idempotent, should not use process-then-ack. > > That why I think we must not call this RPC. And the new API should be clear > the expected idempoten

Re: [openstack-dev] [Nova] Live Migration: Austin summit update

On Tue, May 03, 2016 at 04:16:43PM -0600, Chris Friesen wrote: > On 05/03/2016 03:14 AM, Daniel P. Berrange wrote: > > >There are currently many options for live migration with QEMU that can > >assist in completion > > > > >Given this I've spent the last week creating an automated test harness

Re: [openstack-dev] [keystone] newton release deadlines

Steve Martinelli wrote: A few keystone specific dates and definitions: - May 30-03 -> R-18 -> **Spec proposal freeze** - Specs must be available for review by this week - keystone newton-1 will be released this week - Jul 04-06 -> R-13 -> **Spec freeze** - Specs must be merged by this

Re: [openstack-dev] [tricircle] Requirements for becoming approved official project

Hi Team, There is an additional work to become an official (approval) project. Once we complete PTL election with everyone's consensus, we need to update projects.yaml. [1] I think that the OSPF to become approval project is to elect PTL, then talk to other PTLs of other projects. [1] https://git

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

Hayes, Graham wrote: [...] Designate is looking to move a single component of ours to Go - and we were wondering what was the best way to do it. The current policy does allow for the TC to bless different languages on a case by case basis - do we need to go from just python and JS to allowing al

Re: [openstack-dev] [vitrage] [aodh] Error when creating 2 event alarms with the same name

Great! We are currently starting to work on plans for Newton, and we have this on our list. See here: https://etherpad.openstack.org/p/vitrage-newton-planning We plan to start working on this soon :) Alexey Weyl > -Original Message- > From: EXT Julien Danjou [mailto:jul...@danjou.inf

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

Fox, Kevin M wrote: RadosGW has been excluded from joining the OpenStack community in part due to its use of c++. I'm not sure I'd use the word "excluded" since RadosGW was never actually proposed. Maybe our past Python-centricity discouraged them to apply, but that's conjecture. Now that

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

On 03/05, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > contributions with both code reviews [0] and code contributions [1] have > been significant for some time now. > > His persistence with versioned objects has been instrumen

Re: [openstack-dev] [vitrage] [aodh] Error when creating 2 event alarms with the same name

Hi Fan, The reason we need such a thing is because in Vitrage (which is an Openstack Root Cause Analysis Engine) we may raise a deduced alarms on (for example) each instance in the host, and we would like this name to be a human readable alarm (as you said yourself) without any random strings i

[openstack-dev] [vitrage] Vitrage meeting - Newton design

Hi, We started Vitrage Newton planning on the IRC meeting today. You can find the minutes here: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-05-04-09.00.html Meeting log: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-05-04-09.00.log.html You are mor

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

Could we kindly stop discussing radosgw at this moment? On Wed, May 4, 2016 at 6:47 PM, Thierry Carrez wrote: > Fox, Kevin M wrote: >> >> RadosGW has been excluded from joining the OpenStack community in part due >> to its use of c++. > > > I'm not sure I'd use the word "excluded" since RadosGW w

[openstack-dev] [all][stable] stable/kilo (2015.1.4) Release Freeze

Hi, I have just frozen pending merges for stable/kilo in preparation for the next (and final) point release. It was agreed in Austin that Kilo will be End Of Life'd directly after this release. Therefore, any changes not merged during this freeze will be abandoned. Currently there are 54 change

[openstack-dev] [stable][horizon] Logout user if he has no valid tokens for stable/Kilo

Link to the patch: https://review.openstack.org/#/c/304504/ Pros: Only 13 lines of code (the rest is modifying the tests). Resolves a very nasty end user experience issue which is not documented anywhere. Already merged on master since Liberty. Cons: Seems to me that its a low-risk/hig

Re: [openstack-dev] Timeframe for naming the P release?

On 05/02/2016 08:53 PM, Shamail Tahir wrote: Hi everyone, When will we name the P release of OpenStack? We named two releases simultaneously (Newton and Ocata) during the Mitaka release cycle. This gave us the names for the N (Mitaka), N+1 (Newton), and N+2 (Ocata) releases. If we were to vot

Re: [openstack-dev] [tricircle]weekly meeting of May. 4

One more agenda in the weekly meeting: PTL election. From: joehuang Sent: 04 May 2016 10:44 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev][tricircle]weekly meeting of May. 4 Hi, In last virtual design summit meeting, s

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

- Could we kindly stop discussing radosgw at this moment? + Could we kindly stop discussing any particular application at this moment? On Wed, May 4, 2016 at 7:02 PM, Shinobu Kinjo wrote: > Could we kindly stop discussing radosgw at this moment? > > On Wed, May 4, 2016 at 6:47 PM, Thierry Carrez

Re: [openstack-dev] [stable][horizon] feature freeze exception Logout user if he has no valid tokens for stable/Kilo

This is me asking for a feature freeze exception, sorry if it wasnt clear. Itxaka On 05/04/2016 12:11 PM, Itxaka Serrano Garcia wrote: Link to the patch: https://review.openstack.org/#/c/304504/ Pros: Only 13 lines of code (the rest is modifying the tests). Resolves a very nasty end user exper

Re: [openstack-dev] [nova] Should be instance_dir in all nova compute node same ?

The instance path is assumed to be the same everywhere. When using libvirt to do cold migration/resize the source host creates the instance directory on the target host using ssh and then copies the files to it using scp. So the target host doesn’t even get to determine where its own files are c

Re: [openstack-dev] [stable][horizon] feature freeze exception Logout user if he has no valid tokens for stable/Kilo

On 04/05/16 12:44, Itxaka Serrano Garcia wrote: > This is me asking for a feature freeze exception, sorry if it wasnt clear. > > Itxaka > > On 05/04/2016 12:11 PM, Itxaka Serrano Garcia wrote: >> Link to the patch: https://review.openstack.org/#/c/304504/ >> >> Pros: >> Only 13 lines of code (the

[openstack-dev] [Manila] Any updates on share groups?

Hi all, Back in the office with only minor jetlag... unfortunately I had to skip the discussion last Friday, I was wondering if there was much more discussion about how share groups were going to work, especially from a driver POV? The etherpad notes are mainly recap. I'd like to get ahead of th

Re: [openstack-dev] Timeframe for naming the P release?

Dmitry Tantsur wrote: On 05/02/2016 08:53 PM, Shamail Tahir wrote: When will we name the P release of OpenStack? We named two releases simultaneously (Newton and Ocata) during the Mitaka release cycle. This gave us the names for the N (Mitaka), N+1 (Newton), and N+2 (Ocata) releases. If we we

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

Thanks a ton, Steve! I have to admit, although I was at the summit in person, I can get out of your write-up a lot more than from the sessions itself. (Probably because of a mixture of not being a native speaker and being new to tripleO.) Cheers, Sven _

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

Excerpts from Hayes, Graham's message of 2016-05-03 23:29:11 +: > On 03/05/2016 17:03, John Dickinson wrote: > > TC, > > > > In reference to > > http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html and > > Thierry's reply, I'm currently drafting a TC resolution to update >

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

On Wed, May 4, 2016 at 8:45 AM, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-05-03 23:29:11 +: >> On 03/05/2016 17:03, John Dickinson wrote: >> > TC, >> > >> > In reference to >> > http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html >> > and Thierr

Re: [openstack-dev] Timeframe for naming the P release?

On 05/04/2016 02:44 PM, Thierry Carrez wrote: Dmitry Tantsur wrote: On 05/02/2016 08:53 PM, Shamail Tahir wrote: When will we name the P release of OpenStack? We named two releases simultaneously (Newton and Ocata) during the Mitaka release cycle. This gave us the names for the N (Mitaka), N+

Re: [openstack-dev] [nova] Distributed Database

On Tue, May 3, 2016, at 08:05 PM, Mark Doffman wrote: > This thread has been a depressing read. > > I understand that the content is supposed to be distributed databases > but for me it has become an inquisition of cellsV2. > > Our question has clearly become "Should we continue efforts on >

[openstack-dev] [Security] Austin summit - VMT session recap/summary

Hi all, here is my report of the Austin summit: https://www.rdoproject.org/blog/2016/05/vulnerability-management-newton/ Thank you all for the great OpenStack Newton Design Summit! -Tristan signature.asc Description: OpenPGP digital signature __

Re: [openstack-dev] [glance] [glare] [heat] [tosca] [tacker] [murano] [magnum] [app-catalog] Austin summit summary: Generic cataloging and Glare v1 API

Hi Nikhil: The Tacker project may also be interested in using Glare during this cycle. Is there any API or other documentation/examples that we could use to start? Thanks Bob On 5/3/2016 2:40 PM, EXT Nikhil Komawar wrote: Comment inline. On 5/3/16 3:21 PM, Flavio Percoco wrote: On 02

Re: [openstack-dev] Timeframe for naming the P release?

On 05/04/2016 08:07 AM, Dmitry Tantsur wrote: On 05/04/2016 02:44 PM, Thierry Carrez wrote: Dmitry Tantsur wrote: On 05/02/2016 08:53 PM, Shamail Tahir wrote: When will we name the P release of OpenStack? We named two releases simultaneously (Newton and Ocata) during the Mitaka release cycle.

Re: [openstack-dev] [glance] [glare] [heat] [tosca] [tacker] [murano] [magnum] [app-catalog] Austin summit summary: Generic cataloging and Glare v1 API

Hi Bob, Thanks for reaching out! We're in the process of finalizing the API and the team is working hard on getting the code ready; atm with near to complete functionality WIP patches. Please be mindful of the fact that there is currently an experimental API in glance and code that will change co

Re: [openstack-dev] [oslo] config: deduce related options for config generator?

> From: Doug Hellmann > To: openstack-dev > Date: 05/03/2016 07:04 PM > Subject: Re: [openstack-dev] [oslo] config: deduce related options for > config generator? > > Excerpts from Markus Zoeller's message of 2016-05-03 18:26:50 +0200: > > While working on [1] I came across a config option ("pyb

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

Recently, Jack Ning pushed a PS[0], which export the `WEBROOT` to the globals.yml file. Because there is no chance to change the horizon/apache configure file now. The root cause is that: Kolla do not support non-ini format configure file. for the ini-format file, we use a merge_config module[1] t

[openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

I'm emailing the ML on the subject of a review ongoing in the Trove project regarding image building[1]. TL;DR One of the most frequent questions that new users of Trove ask is how and where to get guest images with which to experiment with Trove, and how to build these images for themselves.

Re: [openstack-dev] [dib][trove][sahara][infra][Octavia][manila] discussion of image building in Trove

Adding [dib] to the subject line. -amrith > -Original Message- > From: Amrith Kumar [mailto:amr...@tesora.com] > Sent: Wednesday, May 04, 2016 11:05 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [trove][sahara][infra][Octavia][manila]

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

I agree with your approach Jeffrey, although this is not ideal, this is an approach already used in kolla. 2016-05-04 12:01 GMT-03:00 Jeffrey Zhang : > Recently, Jack Ning pushed a PS[0], which export the `WEBROOT` to the > globals.yml file. > Because there is no chance to change the horizon/apac

[openstack-dev] [release] summit fishbowl summary

Last week we had a retrospective for the Mitaka release and a planning session for the Newton release. The notes are in the etherpad [1], and this email is a summary based on those notes. As usual, if I've left out something important or mis-remembered something, please post a follow-up. Doug Re

[openstack-dev] [magnum] Add support for using Keystone in k8s bay

Hi team, Based on requests, I propose to add support for Keystone authentication for k8s bay. A blueprint was created for that: https://blueprints.launchpad.net/magnum/+spec/keystone-for-k8s-bay A goal is to enable other OpenStack services to access the APIs of k8s bays. So far, I received a u

Re: [openstack-dev] [infra][neutron][nova] publish and update Gerrit dashboard link automatically

Hi all, in case you are wondering what's the progress of this, I am happy to say that we finally have a link in reviewday [1] that points to the Neutron dashboard that it's constantly updated. It took some effort to get there, thanks to the infra team for the help and especially to AJaeger. Now th

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

+1. Michal will be a great addition to the core team. Thanks, Xing > On May 3, 2016, at 2:19 PM, Sean McGinnis wrote: > > Hey everyone, > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > contributions with both code reviews [0] and code contributions [1] have > been

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On 04/05/16 15:05 +, Amrith Kumar wrote: I'm emailing the ML on the subject of a review ongoing in the Trove project regarding image building[1]. TL;DR One of the most frequent questions that new users of Trove ask is how and where to get guest images with which to experiment with Trove,

[openstack-dev] [designate] Reminder - IRC meeting postponed this week

As discussed in the design summit - we are skipping the IRC meeting today. Talk to you all in a week / #openstack-dns - Graham __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ..

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote: > On 04/05/16 15:05 +, Amrith Kumar wrote: > >I'm emailing the ML on the subject of a review ongoing in the Trove project > >regarding image building[1]. > > > >TL;DR > > > >One of the most frequent questions that new users of Trove ask i

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

Ok. Sure. More generically then. There are OpenStack compatible API implementations existing in the world, deployed by a not insignificant number of production clouds, that are currently outside the big tent that may have not considered proposing joining the community because of the past history

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote: > On 04/05/16 15:05 +, Amrith Kumar wrote: > >I'm emailing the ML on the subject of a review ongoing in the Trove project > >regarding image building[1]. > > > >TL;DR > > > >One of the most frequent questions that new users of Trove ask i

[openstack-dev] [stable] Requesting exception for stable/kilo

Hi Stable Maintainers, We have a critical bug impacting customers production network. This is a minor fix. I would like to request an exception so that the customers do not have to baby sit this patch. https://review.openstack.org/#/c/309653/ Please allow this to be merged. Thanks -Sukhdev

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On 05/04/2016 11:46 AM, Clark Boylan wrote: On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote: On 04/05/16 15:05 +, Amrith Kumar wrote: I'm emailing the ML on the subject of a review ongoing in the Trove project regarding image building[1]. TL;DR One of the most frequent questions t

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On Wed, May 4, 2016 at 11:55 AM, Flavio Percoco wrote: > On 04/05/16 15:05 +, Amrith Kumar wrote: > >> I'm emailing the ML on the subject of a review ongoing in the Trove >> project regarding image building[1]. >> >> TL;DR >> >> One of the most frequent questions that new users of Trove ask i

[openstack-dev] [nova] Austin summit API session recap

On Thursday morning Sean Dague led a double session for work in the Nova API. The full etherpad is here [1]. There were four main focus areas for discussion: 1. Policy defaults in code 2. Policy discoverability 3. api-ref documentation 4. Deprecating/deleting things from the API Policy defaults

Re: [openstack-dev] [nova] Distributed Database

On May 3, 2016, at 7:05 PM, Mark Doffman wrote: > This thread has been a depressing read. > > I understand that the content is supposed to be distributed databases but for > me it has become an inquisition of cellsV2. Thanks for bringing this up, and I feel a lot of the responsibility for this

Re: [openstack-dev] [magnum] Add support for using Keystone in k8s bay

+1. Thanks for starting the discussion. We may need a spec for it. The support in k8s currently is marked experimental (thankfully) and is insufficient. It currently only supports username/password authentication via keystone v2. There's an issue in the works to fix it in k8s: https://github.com

[openstack-dev] [nova][osc] Use of openstack client for admin commands

The plans for generic resource pools[1] include a suite of new commands for creating and updating resource pools. In today's Nova API meeting[2] and afterwards in #openstack-nova[3] we discussed two issues: * Since the placement API associated with resource pools is eventually going to be hois

[openstack-dev] [kolla] xenial or trusty

Which will be the default when kolla begin to support xenial? Xenial or Trusty? One proposal is to support both, at least in this beginning and just do some checks to get which version that the user is using. Regards, __ Open

Re: [openstack-dev] [nova] solving API case sensitivity issues

On 02/24/2016 07:48 AM, Sean Dague wrote: > We have a specific bug around aggregrate metadata setting in Nova which > exposes a larger issue with our mysql schema. > https://bugs.launchpad.net/nova/+bug/1538011 > > On mysql the following will explode with a 500: > >> nova aggregate-create agg1 >>

Re: [openstack-dev] [nova] Distributed Database

On 5/4/2016 12:00 PM, Edward Leafe wrote: On May 3, 2016, at 7:05 PM, Mark Doffman wrote: This thread has been a depressing read. I understand that the content is supposed to be distributed databases but for me it has become an inquisition of cellsV2. Thanks for bringing this up, and I fee

[openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

Hi All, For people who missed the design summit session on Delimiter - Cross project Quota enforcement library here is a gist of what we discussed. Etherpad [1] captures the details. 1. Delimiter will not be responsible for rate-limiting. 2. Delimiter will not maintain data for the projects. 3. D

Re: [openstack-dev] [nova] Distributed Database

On 04/05/16 19:00, "Edward Leafe" wrote: >On May 3, 2016, at 7:05 PM, Mark Doffman wrote: > >> This thread has been a depressing read. >> >> I understand that the content is supposed to be distributed databases but >> for me it has become an inquisition of cellsV2. > >Thanks for bringing this

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On 5/4/16 12:52 PM, Gregory Haynes wrote: On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote: On 04/05/16 15:05 +, Amrith Kumar wrote: I'm emailing the ML on the subject of a review ongoing in the Trove project regarding image building[1]. TL;DR One of the most frequent questions tha

Re: [openstack-dev] [nova] Austin summit versioned notification

Thanks, Jay! We’re looking through everything and will be attending these meetings moving forward. -Travis On 5/3/16, 6:17 AM, "Jay Pipes" wrote: >cc'ing Travis and Steve directly, since they will likely be very >interested in this effort from the Project Searchlight perspective. :) > >On 0

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

On Tue, 3 May 2016 22:11:06 + "Fox, Kevin M" wrote: > If we let go in, and there are no pluggable middleware, where does > RadosGW and other Swift api compatible implementations then stand? They remain where they are now. > Should we bless c++ too? As I understand it, there are a lot of clo

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On 04/05/16 09:46 -0700, Clark Boylan wrote: On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote: On 04/05/16 15:05 +, Amrith Kumar wrote: >I'm emailing the ML on the subject of a review ongoing in the Trove project regarding image building[1]. > >TL;DR > >One of the most frequent questi

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

Thanks for the summary and taking care of the setup, Vilobh! Pretty meticulously written on what was agreed at the session. Kudos! I wanted to add some points that were asked during the Glance contributors' meetup: * The quota limits will be set on the tables in the service that maintains the re

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

On 04/05/16 11:38 +0200, Thierry Carrez wrote: Hayes, Graham wrote: [...] Designate is looking to move a single component of ours to Go - and we were wondering what was the best way to do it. The current policy does allow for the TC to bless different languages on a case by case basis - do we n

Re: [openstack-dev] [kolla] xenial or trusty

I'd like to lock the tag version in certain branch. One branch only support one distro release. For example, the mitaka branch only build on Trusty and the master/newton branch only build on Xenial. So, the branch and OS matrix should like ( fix me and the ?) Ubuntu CentOS Debi

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

On Tue, 3 May 2016 22:37:30 + "Fox, Kevin M" wrote: > RadosGW has been excluded from joining the OpenStack community in part > due to its use of c++. Sounds like sheer lunacy. Nothing like that ever happened, AFAIK. -- Pete __

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

On 04/05/16 19:41, "Nikhil Komawar" wrote: >Thanks for the summary and taking care of the setup, Vilobh! > >Pretty meticulously written on what was agreed at the session. Kudos! > >I wanted to add some points that were asked during the Glance >contributors' meetup: > >* The quota limits will be

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On Wed, May 4, 2016 at 12:08 PM, Chris Dent wrote: > Since then the spec has been updated to reflect using OSC but the > question of whether this is in fact the right place for this style > of commands remains open. Not just for this situation, but > generally. > This came up again last week, an

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On 5/4/2016 12:08 PM, Chris Dent wrote: The plans for generic resource pools[1] include a suite of new commands for creating and updating resource pools. In today's Nova API meeting[2] and afterwards in #openstack-nova[3] we discussed two issues: * Since the placement API associated with resour

Re: [openstack-dev] [kolla] xenial or trusty

On Wed, May 4, 2016 at 1:52 PM, Jeffrey Zhang wrote: > I'd like to lock the tag version in certain branch. One branch only support > one > distro release. > > For example, the mitaka branch only build on Trusty and the master/newton > branch > only build on Xenial. > > So, the branch and OS matrix

Re: [openstack-dev] [neutron] OSC transition

On Wed, May 4, 2016 at 6:10 AM, Na Zhu wrote: > I found Dean Troyer set the *[Blueprint neutron-client] implement neutron > commands*state to obsolete, does the OSC transition continue move along? Other BPs are being used to track the specific work being performed, that BP was nearly empty and

Re: [openstack-dev] [Fuel][Plugins] One plugin - one Launchpad project

Hi all – I think this might’ve gotten buried a bit in the pre-summit and summit madness. I just wanted to kick the thread – I think this is a really good idea. Dogpiling all plugins into a single LP project makes it really difficult to pick out which bugs affect which plugins – and the ecosys

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Mark Doffman's message of 2016-05-03 17:05:54 -0700: > This thread has been a depressing read. > First, I apologize if any of my actions have caused you any undue stress. > I understand that the content is supposed to be distributed databases > but for me it has become an inquisit

Re: [openstack-dev] [neutron] OSC transition

> On May 4, 2016, at 6:10 AM, Na Zhu wrote: > > Hi Richard, > > I read the contents in the link, I think the discussion in Austin summit have > not updated to the webpage. > But from here > https://etherpad.openstack.org/p/newton-neutron-future-neutron-client >

[openstack-dev] [ironic] Newton priorities and primary contacts

Hi, At the Austin summit, we had a session where we discussed and decided on what the top priorities would be for ironic, in the newton development cycle. The etherpad [1] captures that discussion, and there is a patch up to add the newton priorities to our specs [2]. Everyone, and in particular

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

Explicitly, no. I agree. Implicitly... ? Why bother to even propose joining when you know the rules clearly state that its not acceptable? I don't claim to know what has gone on internally in such teams. I'm just saying just because there hasn't been visible signs here of exclusion doesn't mean

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

On 5/4/16 2:09 PM, Tim Bell wrote: > > On 04/05/16 19:41, "Nikhil Komawar" wrote: > >> Thanks for the summary and taking care of the setup, Vilobh! >> >> Pretty meticulously written on what was agreed at the session. Kudos! >> >> I wanted to add some points that were asked during the Glance >> c

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On Wed, May 4, 2016, at 09:57 AM, Ethan Gafford wrote: > > Sahara has support for several image generation-related cases: > 1) Packing an image pre-cluster spawn in Nova. > 2) Building clusters from a "clean" OS image post-Nova spawn, by >downloading and installing Hadoop/Spark/Storm/WhatHave

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

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 messaging patterns and hence should be under oslo.messaging I guess, no? Yes and no, we currently have two APIs (rpc and notification). And personally I regr

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On 05/04/2016 02:16 PM, Dean Troyer wrote: > On Wed, May 4, 2016 at 12:08 PM, Chris Dent > wrote: > > Since then the spec has been updated to reflect using OSC but the > question of whether this is in fact the right place for this style > of commands rem

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

On 04/05/16 20:35, "Nikhil Komawar" wrote: > > >On 5/4/16 2:09 PM, Tim Bell wrote: >> >> On 04/05/16 19:41, "Nikhil Komawar" wrote: >> >>> Thanks for the summary and taking care of the setup, Vilobh! >>> >>> Pretty meticulously written on what was agreed at the session. Kudos! >>> >>> I wanted

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On 2016-05-04 09:52:20 -0700 (-0700), Gregory Haynes wrote: [...] > One of the biggest issues I see users of DIB hit is ease of use > for 'just make me an image, I don't care about twiddling knobs'. A > wrapper script in trove is one way to help with this [...] For example, in openstack-infra/proj

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On 04/05/16 20:54, "Sean Dague" wrote: >On 05/04/2016 02:16 PM, Dean Troyer wrote: >> On Wed, May 4, 2016 at 12:08 PM, Chris Dent > > wrote: >> >> Since then the spec has been updated to reflect using OSC but the >> question of whether this is in fact

[openstack-dev] [Neutron] meeting topics for 5/5/2016 networking-sfc project IRC meeting

Hi everyone, Here are some topics I have for this week's project meeting discussion(The meeting time is not changed, still UTC 1700 Thursday). Feel free to add more. You can also find the meeting topics in the project wiki page. https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMee

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On Wed, May 4, 2016 at 1:54 PM, Sean Dague wrote: > Given these constraints it was as much of an ask as anything else. Can > OSC handle this? Should it handle it from a best practices perspective? > How are commands exposed / hidden based on user permissions? The fact > that we're going to need a

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

On 05/04/2016 11:49 AM, Fox, Kevin M wrote: Ok. Sure. More generically then. There are OpenStack compatible API implementations existing in the world, deployed by a not insignificant number of production clouds, that are currently outside the big tent that may have not considered proposing joi

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

On 05/04/2016 01:31 PM, Fox, Kevin M wrote: Explicitly, no. I agree. Implicitly... ? Why bother to even propose joining when you know the rules clearly state that its not acceptable? I don't claim to know what has gone on internally in such teams. I'm just saying just because there hasn't been

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On Wed, May 4, 2016, at 10:33 AM, Peter MacKinnon wrote: > > Well, certainly one downside in the case of Trove (and probably > elsewhere) with DIB is the src tree matrix of datastore-by-distro > elements required to support various guest image combinations, leading > to a proliferation of direc

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

+1 Walt Hey everyone, I would like to nominate Michał Dulko to the Cinder core team. Michał's contributions with both code reviews [0] and code contributions [1] have been significant for some time now. His persistence with versioned objects has been instrumental in getting support in the Mita

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

> -Original Message- > From: Gregory Haynes [mailto:g...@greghaynes.net] > Sent: Wednesday, May 04, 2016 3:52 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] > discussion of image building in Trove > > On Wed, May 4, 2016,

Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

+1 for me too. -- Kevin Carter IRC: cloudnull From: Matthew Thode Sent: Tuesday, May 3, 2016 1:50 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security O

Re: [openstack-dev] [kolla] xenial or trusty

Hi folks, Based in that request, it follows a proposed patch to add support to Ubuntu Xenial - 16.04. For while, instead to locking distro version in branches this can be used, since Mitaka version is supported by Ubuntu Trusty and Xenial versions. http://paste.openstack.org/show/496142/ Comm

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

The way I see this, these are the 2 main concerns I have been hearing regarding image building in Trove: 1) making the process simple and easy for users 2) addressing the issue of security I dont think there is any argument regarding the benefits of moving the database elements to a seperate repo

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

Excerpts from Fox, Kevin M's message of 2016-05-04 16:49:42 +: > Ok. Sure. More generically then. There are OpenStack compatible API > implementations existing in the world, deployed by a not insignificant number > of production clouds, that are currently outside the big tent that may have >

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

Comments inline. On 5/4/16 2:58 PM, Tim Bell wrote: > > On 04/05/16 20:35, "Nikhil Komawar" wrote: > >> >> On 5/4/16 2:09 PM, Tim Bell wrote: >>> On 04/05/16 19:41, "Nikhil Komawar" wrote: >>> Thanks for the summary and taking care of the setup, Vilobh! Pretty meticulously writte

Re: [openstack-dev] [ironic] Newton priorities and primary contacts

On Wed, May 04, 2016 at 02:29:34PM -0400, Ruby Loo wrote: > Hi, > > At the Austin summit, we had a session where we discussed and decided on > what the top priorities would be for ironic, in the newton development > cycle. The etherpad [1] captures that discussion, and there is a patch up > to add

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On 05/04/2016 01:08 PM, Chris Dent wrote: The plans for generic resource pools[1] include a suite of new commands for creating and updating resource pools. In today's Nova API meeting[2] and afterwards in #openstack-nova[3] we discussed two issues: * Since the placement API associated with reso

[openstack-dev] [neutron][stable] - exception for stable/kilo DVR back-ports

Hello, I would like to propose a freeze exception for https://review.openstack.org/#/c/312253/ and https://review.openstack.org/#/c/312254/ . They address a bug in DVR that causes floating IPs to eventually break after an L3 agent has been restarted. It's a serious bug but it's very subtle because

[openstack-dev] [ironic] API docs now publishing from our tree

Hey y'all, I did the push this week to move the api-ref into our tree, and it's now publishing. \o/ The docs are here: http://developer.openstack.org/api-ref/baremetal/ The source is here: http://git.openstack.org/cgit/openstack/ironic/tree/api-ref/source I know devananda is doing a push to upd

  1   2   >