Re: [openstack-dev] [mistral] Proposing Lingxian Kong as a core reviewer

+1 From: W Chan [mailto:m4d.co...@gmail.com] Sent: Tuesday, June 23, 2015 12:07 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [mistral] Proposing Lingxian Kong as a core reviewer +1 Lingxian, keep up with the good work. :D __

Re: [openstack-dev] [neutron] Regarding Flow classifiers existing proposals

Thanks for being on top of this. I made some comments on the etherpad. IMO probably, this is better as a simple extension of the api and it's datamodels. Since we won't need to extend core resources to connect them to flow classifiers, but in the other hand, we will connect other services to t

Re: [openstack-dev] [neutron] Regarding Flow classifiers existing proposals

Hi All, We have started a etherpad link [1] for collecting various use-cases about flow-classifier. Request all to provide their opinion on the same. We will be discussing the same over SFC IRC meeting [2]. Any contribution will be appreciated. [1] Etherpad Link https://etherpad.openstack.org/

Re: [openstack-dev] [nova][keystone] Nova calls to Keystone

On 06/22/2015 10:13 PM, Sajeesh Cimson Sasi wrote: *From:* Adam Young [ayo...@redhat.com] *Sent:* 23 June 2015 00:01:48 *To:* openstack-dev@lists.openstack.org *Subject:* Re: [openstack-dev] [nova][keystone] Nova calls to

Re: [openstack-dev] [nova][keystone] Nova calls to Keystone

From: Adam Young [ayo...@redhat.com] Sent: 23 June 2015 00:01:48 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova][keystone] Nova calls to Keystone On 06/20/2015 02:46 PM, Sajeesh Cimson Sasi wrote: Hi All, I need your advice for the im

Re: [openstack-dev] M Naming Poll ended - results still need to clear legal

On 06/22/2015 01:30 PM, Clay Gerrard wrote: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8dbc how is the top pick not the author of the book of five rings [1] I say we claim him as the mascot of the release anyway. "This should be given careful thought and thorough reflectio

[openstack-dev] Cross-Project meeting, Tue June 23rd, 21:00 UTC

Dear PTLs, cross-project liaisons and other interested parties: We have a cross-project meeting tomorrow (June 23rd) at 21:00 UTC, with the following agenda: - Team announcements (horizontal, vertical, diagonal) - Return request-id to caller (use thread local to store request-id) - Main use cas

Re: [openstack-dev] [Ironic] Proposal to add a new repository

Oh - one more thing. If ahc-tools depends on data gathered by enovance/hardware, then I'm not sure it makes sense to import one to openstack/ without the other. -Deva On Mon, Jun 22, 2015 at 5:08 PM Devananda van der Veen < devananda@gmail.com> wrote: > I'm > On Mon, Jun 22, 2015 at 8:19 AM

Re: [openstack-dev] [Ironic] Proposal to add a new repository

I'm On Mon, Jun 22, 2015 at 8:19 AM John Trowbridge wrote: > > > On 06/22/2015 10:40 AM, Dmitry Tantsur wrote: > > On 06/22/2015 04:19 PM, Devananda van der Veen wrote: > >> Hi John, > >> > >> Thanks for the excellent summary! I found it very helpful to get caught > >> up. I'd like to make sure I

Re: [openstack-dev] [QA][Tempest] Proposing Jordan Pittier for Tempest Core

+1 :) On Tue, Jun 23, 2015 at 5:23 AM, Matthew Treinish wrote: > > > Hi Everyone, > > I'd like to propose we add Jordan Pittier (jordanP) to the tempest core > team. > Jordan has been a steady contributor and reviewer on tempest over the past > few > cycles and he's been actively engaged in the

Re: [openstack-dev] [ceilometer] can we get ceilometermiddleware to use a config file instead of transport_url?

On 22/06/15 06:39 PM, Chris Dent wrote: On Mon, 22 Jun 2015, Sean Dague wrote: Could we deprecate the use of tranport_url in ceilometermiddleware and move to an actual oslo.config file somewhere instead? That would bring it in line with the rest of the RPC configuration for services, and ensu

Re: [openstack-dev] [Nova] Tracking optional requirements

bindep looks quite cool, and I think would do what I am after here. That's especially true if we use its profiles support. I like the idea that we can hand some form of documentation to distros that verifies that they've noticed all the dependancies we've added in a given release cycle. Cheers, Mi

Re: [openstack-dev] [heat][tripleo]Recursive validation for easier composability

On 23/06/15 06:49, Thomas Spatzier wrote: From: Jay Dobies To: openstack-dev@lists.openstack.org Date: 22/06/2015 19:22 Subject: Re: [openstack-dev] [heat][tripleo]Recursive validation for easier composability On 06/22/2015 12:19 PM, Steven Hardy wrote: Hi all, Lately I've been giving some

Re: [openstack-dev] [ceilometer] can we get ceilometermiddleware to use a config file instead of transport_url?

On Mon, 22 Jun 2015, Sean Dague wrote: Could we deprecate the use of tranport_url in ceilometermiddleware and move to an actual oslo.config file somewhere instead? That would bring it in line with the rest of the RPC configuration for services, and ensure that all connections in a cluster have a

Re: [openstack-dev] [nova][qa] Do we turn on voting for the tempest-dsvm-cells job?

On 6/22/2015 4:38 PM, Matt Riedemann wrote: On 6/22/2015 4:32 PM, Russell Bryant wrote: On 06/22/2015 05:23 PM, Matt Riedemann wrote: The check-tempest-dsvm-cells job has been in nova's check queue since January as non-voting and has been stable for a couple of weeks now, so before it's reg

Re: [openstack-dev] [all] [qpid] [zmq] [RabbitMQ] [oslo] Pending deprecation of driver(s).

On Mon, Jun 22, 2015 at 2:27 PM Adam Young wrote: > On 06/20/2015 10:28 AM, Flavio Percoco wrote: > >> > > > > As promissed: https://review.openstack.org/#/c/193804/ > > > > Cheers, > You can't deprecate a driver without providing a viable alternative. > > Right now, QPID is the only driver that

Re: [openstack-dev] [puppet] Clarification of 'Puppet Modules' Project Scope

Hi Richard, On 06/22/2015 01:05 PM, Richard Raseley wrote: > I am currently hoping to build consensus (or seek clarity if I am the > only one with this question) about the appropriate scope for our 'Puppet > Modules' project. > > The question in my mind is if we: > > A) Only include those module

Re: [openstack-dev] [ceilometer] can we get ceilometermiddleware to use a config file instead of transport_url?

On Mon, Jun 22, 2015 at 2:43 PM, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2015-06-22 13:30:44 -0400: > > On 06/22/2015 01:15 PM, Michael Krotscheck wrote: > > > Having _just_ done this, a couple of suggestions. > > > > > > - If the middleware is NOT optional - that is, it prov

Re: [openstack-dev] [QA][Tempest] Proposing Jordan Pittier for Tempest Core

+1 :-) 2015年6月23日(火) 5:24 Matthew Treinish : > > > Hi Everyone, > > I'd like to propose we add Jordan Pittier (jordanP) to the tempest core > team. > Jordan has been a steady contributor and reviewer on tempest over the past > few > cycles and he's been actively engaged in the Tempest community.

Re: [openstack-dev] [nova][qa] Do we turn on voting for the tempest-dsvm-cells job?

On 6/22/2015 4:32 PM, Russell Bryant wrote: On 06/22/2015 05:23 PM, Matt Riedemann wrote: The check-tempest-dsvm-cells job has been in nova's check queue since January as non-voting and has been stable for a couple of weeks now, so before it's regressed melwitt proposed a change to making it v

Re: [openstack-dev] [nova][qa] Do we turn on voting for the tempest-dsvm-cells job?

On 06/22/15 at 04:23pm, Matt Riedemann wrote: The check-tempest-dsvm-cells job has been in nova's check queue since January as non-voting and has been stable for a couple of weeks now, so before it's regressed melwitt proposed a change to making it voting and gating on nova changes [1]. I rai

Re: [openstack-dev] [nova][qa] Do we turn on voting for the tempest-dsvm-cells job?

On 06/22/2015 05:23 PM, Matt Riedemann wrote: > The check-tempest-dsvm-cells job has been in nova's check queue since > January as non-voting and has been stable for a couple of weeks now, so > before it's regressed melwitt proposed a change to making it voting and > gating on nova changes [1]. >

[openstack-dev] [nova][qa] Do we turn on voting for the tempest-dsvm-cells job?

The check-tempest-dsvm-cells job has been in nova's check queue since January as non-voting and has been stable for a couple of weeks now, so before it's regressed melwitt proposed a change to making it voting and gating on nova changes [1]. I raised a concern in that change that the tempest-d

Re: [openstack-dev] M Naming Poll ended - results still need to clear legal

Anyway, if you want to print t-shirts once legal is cleared, here's a vintage football idea [1]. Little and pointless trivia fact: Como calcio was sponsored for a few years in the 80s by Mita copiers - now known as Kyocera. Salvatore [1] http://www.calciocomo1907.it/images/news/thumbnails/Mattei%

Re: [openstack-dev] [Neutron] Issue with pymysql

Hi, A brief update on the issue that sparked this thread: A little over a week ago, bug [1] was filed. The gist of that was that the switch to pymysql unveiled a number of latent race conditions that made Neutron unstable. To try and nip these in the bud, the Neutron team filed a number of patch

Re: [openstack-dev] [QA][Tempest] Proposing Jordan Pittier for Tempest Core

not a core myself, apologies if this is spamming, but +1. Jordan's been a great help. On 22/06/15 04:23 PM, Matthew Treinish wrote: Hi Everyone, I'd like to propose we add Jordan Pittier (jordanP) to the tempest core team. Jordan has been a steady contributor and reviewer on tempest over the

[openstack-dev] [mistral] Proposing Lingxian Kong as a core reviewer

+1 Lingxian, keep up with the good work. :D __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/

Re: [openstack-dev] [QA][Tempest] Proposing Jordan Pittier for Tempest Core

+1 :) On 2015年6月23日(火) at 5:30 Matthew Treinish wrote: > > > Hi Everyone, > > I'd like to propose we add Jordan Pittier (jordanP) to the tempest core > team. > Jordan has been a steady contributor and reviewer on tempest over the past > few > cycles and he's been actively engaged in the Tempest c

Re: [openstack-dev] [QA][Tempest] Proposing Jordan Pittier for Tempest Core

+1 On 06/22/2015 04:23 PM, Matthew Treinish wrote: Hi Everyone, I'd like to propose we add Jordan Pittier (jordanP) to the tempest core team. Jordan has been a steady contributor and reviewer on tempest over the past few cycles and he's been actively engaged in the Tempest community. Jordan ha

[openstack-dev] [QA][Tempest] Proposing Jordan Pittier for Tempest Core

Hi Everyone, I'd like to propose we add Jordan Pittier (jordanP) to the tempest core team. Jordan has been a steady contributor and reviewer on tempest over the past few cycles and he's been actively engaged in the Tempest community. Jordan has had one of the higher review counts on Tempest for

Re: [openstack-dev] [Oslo][Automaton] Proposal for new core (ruby loo)

+1 On Mon, Jun 22, 2015 at 2:55 PM, Doug Hellmann wrote: > Excerpts from Joshua Harlow's message of 2015-06-22 10:59:27 -0700: >> Greetings all stackers, >> >> I propose that we add Ruby Loo[1] to the automaton-core team. >> >> Ruby has been actively contributing to automaton[2] for a while now,

Re: [openstack-dev] [all][requirements] requirements reviews falling behind

Excerpts from Sean Dague's message of 2015-06-22 15:32:17 -0400: > On 06/22/2015 03:27 PM, Monty Taylor wrote: > > On 06/22/2015 02:49 PM, Doug Hellmann wrote: > >> We have quite a long list of patches to the openstack/requirements > >> repository, many of which are straightforward changes to incr

Re: [openstack-dev] [ceilometer] can we get ceilometermiddleware to use a config file instead of transport_url?

Excerpts from Sean Dague's message of 2015-06-22 13:30:44 -0400: > On 06/22/2015 01:15 PM, Michael Krotscheck wrote: > > Having _just_ done this, a couple of suggestions. > > > > - If the middleware is NOT optional - that is, it provides some kind of > > a fundamental component or specification of

Re: [openstack-dev] [all] [qpid] [zmq] [RabbitMQ] [oslo] Pending deprecation of driver(s).

Excerpts from Adam Young's message of 2015-06-22 11:26:54 -0700: > On 06/20/2015 10:28 AM, Flavio Percoco wrote: > >> > > > > As promissed: https://review.openstack.org/#/c/193804/ > > > > Cheers, > You can't deprecate a driver without providing a viable alternative. > > Right now, QPID is the on

Re: [openstack-dev] [all][requirements] requirements reviews falling behind

On 06/22/2015 03:27 PM, Monty Taylor wrote: > On 06/22/2015 02:49 PM, Doug Hellmann wrote: >> We have quite a long list of patches to the openstack/requirements >> repository, many of which are straightforward changes to increase the >> minimums for libraries we develop within the community (mean

Re: [openstack-dev] [all][requirements] requirements reviews falling behind

On 06/22/2015 02:49 PM, Doug Hellmann wrote: > We have quite a long list of patches to the openstack/requirements > repository, many of which are straightforward changes to increase the > minimums for libraries we develop within the community (meaning we are > holding up projects from using new

Re: [openstack-dev] [oslo] Updates from the Summit

Any progress on this? Let me know and if not I can throw something together to (if you are busy or pre-occupied, or other) :) -Josh Joshua Harlow wrote: Feel free to add it, or open a blueprint, or make a spec to :) Any of the above are ok with me. I did start prototyping something @ https

Re: [openstack-dev] [Ironic][Horizon][Tuskar-ui] Making a dashboard for Ironic‏

Hi! Just as an FYI, we use this for a dashboard: https://github.com/rackerlabs/onmetal-dashboard That might be useful when moving forward with using Horizon or the ironic-dashboard project. Mario On Thu, Jun 18, 2015 at 7:43 PM, niuzhenguo wrote: > Hi Thai Q Tran, > > > > Thanks for the links

Re: [openstack-dev] [Cinder] Implementation of ABC MetaClasses

On 20 June 2015 at 02:59, John Griffith wrote: > > ​Sure, I guess my question is what's the real value in this intermediate > step. The bulk of these are things that I'd argue shouldn't be optional > anyway (snapshots, transfers, manage, extend, retype and even migrate). > Snapshots in particula

Re: [openstack-dev] [Oslo][Automaton] Proposal for new core (ruby loo)

Excerpts from Joshua Harlow's message of 2015-06-22 10:59:27 -0700: > Greetings all stackers, > > I propose that we add Ruby Loo[1] to the automaton-core team. > > Ruby has been actively contributing to automaton[2] for a while now, > both in helping make automaton better via reviews (she has be

Re: [openstack-dev] [heat][tripleo]Recursive validation for easier composability

> From: Jay Dobies > To: openstack-dev@lists.openstack.org > Date: 22/06/2015 19:22 > Subject: Re: [openstack-dev] [heat][tripleo]Recursive validation for > easier composability > > > > On 06/22/2015 12:19 PM, Steven Hardy wrote: > > Hi all, > > > > Lately I've been giving some thought to how we m

[openstack-dev] [all][requirements] requirements reviews falling behind

We have quite a long list of patches to the openstack/requirements repository, many of which are straightforward changes to increase the minimums for libraries we develop within the community (meaning we are holding up projects from using new features, or we’re not being accurate about our curre

Re: [openstack-dev] [nova][keystone] Nova calls to Keystone

On 06/20/2015 02:46 PM, Sajeesh Cimson Sasi wrote: Hi All, I need your advice for the implementation of the following blueprint. https://review.openstack.org/#/c/160605 . All the use cases mentioned in the blueprint have been implemented and the

[openstack-dev] [Infra] Meeting Tuesday June 23rd at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday June 23rd, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone intereste

Re: [openstack-dev] [puppet] Installing dependent modules in functional testing

On Thu, Jun 18, 2015 at 2:24 PM, Colleen Murphy wrote: > Now that we have the basic beaker-rspec framework set up in the modules > and working in infra's CI, we need to start making our testing aware of > Zuul dependencies. The infra team is facing similar challenges so it would > be nice to work

Re: [openstack-dev] [all] [qpid] [zmq] [RabbitMQ] [oslo] Pending deprecation of driver(s).

On 06/20/2015 10:28 AM, Flavio Percoco wrote: As promissed: https://review.openstack.org/#/c/193804/ Cheers, You can't deprecate a driver without providing a viable alternative. Right now, QPID is the only driver that supports Kerberos. TO support Kerberos, tyou need support for the GSSA

Re: [openstack-dev] M Naming Poll ended - results still need to clear legal

Excerpts from Clay Gerrard's message of 2015-06-22 10:30:49 -0700: > http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8dbc > > how is the top pick not the author of the book of five rings [1] > Agreed. I don't think people fully appreciated the reputation of Mr. Musashi. ;) __

[openstack-dev] [Oslo][Automaton] Proposal for new core (ruby loo)

Greetings all stackers, I propose that we add Ruby Loo[1] to the automaton-core team. Ruby has been actively contributing to automaton[2] for a while now, both in helping make automaton better via reviews (she has been involved from the start in helping sanity check that code) and helping get

Re: [openstack-dev] [ceilometer] can we get ceilometermiddleware to use a config file instead of transport_url?

On 06/22/2015 01:15 PM, Michael Krotscheck wrote: > Having _just_ done this, a couple of suggestions. > > - If the middleware is NOT optional - that is, it provides some kind of > a fundamental component or specification of the API, like ETag caching, > CORS, or DB Session management - then the mi

Re: [openstack-dev] M Naming Poll ended - results still need to clear legal

http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8dbc how is the top pick not the author of the book of five rings [1] -Clay 1. https://en.wikipedia.org/wiki/The_Book_of_Five_Rings On Mon, Jun 22, 2015 at 7:07 AM, Monty Taylor wrote: > Hey all! > > The M naming poll has conclu

Re: [openstack-dev] [nova][ceilometer] proposal to send bulk hypervisor stats data in periodic notifications

On 06/22/15 20:10, Daniel P. Berrange wrote: On Mon, Jun 22, 2015 at 11:10:40AM -0500, Kevin L. Mitchell wrote: On Sat, 2015-06-20 at 21:35 +0100, Daniel P. Berrange wrote: In general I would say that is an unsupported deployment scenario to have other random virt guests running on a nova compu

Re: [openstack-dev] [heat][tripleo]Recursive validation for easier composability

On 06/22/2015 12:19 PM, Steven Hardy wrote: Hi all, Lately I've been giving some thought to how we might enable easier composability, and in particular how we can make it easier for folks to plug in deeply nested optional extra logic, then pass data in via parameter_defaults to that nested tem

Re: [openstack-dev] [puppet] Clarification of 'Puppet Modules' Project Scope

I'm torn on this. Pedantically option A makes the most sense, but option B gives us more control over the supporting modules. I like having OpenStack CI run on vswitch and ceph rather than the typical github merge process. On Mon, Jun 22, 2015 at 11:05 AM, Richard Raseley wrote: > I am currently

Re: [openstack-dev] [nova][ceilometer] proposal to send bulk hypervisor stats data in periodic notifications

On Mon, 2015-06-22 at 18:10 +0100, Daniel P. Berrange wrote: > On Mon, Jun 22, 2015 at 11:10:40AM -0500, Kevin L. Mitchell wrote: > > On Sat, 2015-06-20 at 21:35 +0100, Daniel P. Berrange wrote: > > > In general I would say that is an unsupported deployment scenario to > > > have other random virt

Re: [openstack-dev] [ceilometer] can we get ceilometermiddleware to use a config file instead of transport_url?

Having _just_ done this, a couple of suggestions. - If the middleware is NOT optional - that is, it provides some kind of a fundamental component or specification of the API, like ETag caching, CORS, or DB Session management - then the middleware should be added during the app initialization routi

Re: [openstack-dev] [nova][ceilometer] proposal to send bulk hypervisor stats data in periodic notifications

On Mon, Jun 22, 2015 at 11:10:40AM -0500, Kevin L. Mitchell wrote: > On Sat, 2015-06-20 at 21:35 +0100, Daniel P. Berrange wrote: > > In general I would say that is an unsupported deployment scenario to > > have other random virt guests running on a nova compute node. > > On the other hand, this i

[openstack-dev] [puppet] Clarification of 'Puppet Modules' Project Scope

I am currently hoping to build consensus (or seek clarity if I am the only one with this question) about the appropriate scope for our 'Puppet Modules' project. The question in my mind is if we: A) Only include those modules which represent a 1:1 mapping with other OpenStack projects. B) Al

[openstack-dev] [mistral] Team meeting minutes - 22/06/2015

Thanks everyone for participating our meeting today. Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-06-22-16.00.html Meeting log: http://eavesdrop.openstack.org/meetings/mis

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

Thomas, This may be of interest to you as well: http://specs.openstack.org/openstack/openstack-specs/specs/supported-messaging-drivers.html On Mon, Jun 22, 2015 at 12:57 PM, Davanum Srinivas wrote: > Thomas, > > here's a review for qpid > https://review.openstack.org/#/c/193804/ > > -- dims > >

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

Thomas, here's a review for qpid https://review.openstack.org/#/c/193804/ -- dims On Mon, Jun 22, 2015 at 12:42 PM, Thomas Goirand wrote: > On 06/16/2015 03:22 PM, Sean Dague wrote: >> FYI, >> >> One of the things that came out of the summit for Devstack plans going >> forward is to trim it bac

Re: [openstack-dev] [Neutron] Modular L2 Agent

On Mon, Jun 22, 2015 at 10:47:39AM EDT, Salvatore Orlando wrote: > I would probably start with something for enabling the L2 agent to process > "features" such as QoS and security groups, working on the OVS agent, and > then in a second step abstract a driver interface for communicating with > the

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

On 06/16/2015 03:22 PM, Sean Dague wrote: > FYI, > > One of the things that came out of the summit for Devstack plans going > forward is to trim it back to something more opinionated and remove a > bunch of low use optionality in the process. > > One of those branches to be trimmed is all the sup

Re: [openstack-dev] [Cinder] Implementation of ABC MetaClasses

Am 20.06.2015 um 01:59 schrieb John Griffith : > * The BaseVD represents the functionality we require from all drivers. > ​Yep > ​ > * The additional ABC classes represent features that are not required yet. > * These are represented by classes because some features require a > bundle of method

[openstack-dev] [heat][tripleo]Recursive validation for easier composability

Hi all, Lately I've been giving some thought to how we might enable easier composability, and in particular how we can make it easier for folks to plug in deeply nested optional extra logic, then pass data in via parameter_defaults to that nested template. Here's an example of the use-case I'm de

Re: [openstack-dev] [requirements] re-ordered specifiers in requirements.txt

On 06/22/2015 05:07 AM, Sean Dague wrote: > On 06/22/2015 04:33 AM, Robert Collins wrote: >> You may have noticed the every repo has just been spammed with some >> no-op changes where specifiers are re-ordered such as in >> https://review.openstack.org/#/c/193973/1/test-requirements.txt >> >> where

Re: [openstack-dev] [nova][ceilometer] proposal to send bulk hypervisor stats data in periodic notifications

On Sat, 2015-06-20 at 21:35 +0100, Daniel P. Berrange wrote: > In general I would say that is an unsupported deployment scenario to > have other random virt guests running on a nova compute node. On the other hand, this is exactly how compute nodes themselves are often deployed—a random guest on t

Re: [openstack-dev] [mistral] Proposing Lingxian Kong as a core reviewer

Hi, +1 for Lingxian! On Mon, Jun 22, 2015 at 7:08 PM, Nikolay Makhotkin wrote: > Hi, > > +1 for Lingxian! > > -- > Best Regards, > Nikolay > -- Best Regards, Nikolay __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] Specify a domain in mapping rules

I'm sorry it does not work still with this commit: https://review.openstack.org/#/c/181007/ I think this commit is for another feature, we does not use keystone like idp. We use shibboleth like idp: http://docs.openstack.org/developer/keystone/configure_federation.html According to the next gui

Re: [openstack-dev] [Nova] Tracking optional requirements

On 2015-06-22 21:05:11 +1000 (+1000), Michael Still wrote: > Sure, except where the thing isn't in pip... I just learned tonight > that the libosinfo thing in the review at the start of this thread is > a c library and some gobject black magic. I think we want it, but it > will never work as a pip

Re: [openstack-dev] [qa] Tempest bug triage questions

On Mon, Jun 22, 2015 at 11:41:56AM -0400, David Kranz wrote: > On 06/22/2015 10:15 AM, Yaroslav Lobankov wrote: > >Hello everyone, > > > >I have some questions about the bug triage procedure for Tempest: > > > >1. Some bugs in Tempest have status "Fix committed". Should we move > >statuses of these

[openstack-dev] [mistral] Proposing Lingxian Kong as a core reviewer

Team, I’d like to propose Lingxian Kong (xylan_kong) to Mistral core team. Over the last ~6 months Lingxian showed really strong technical skills, provided a series of very high quality reviews and has been very active in our IRC channel. He also has a solid vision about Mistral future. His ene

Re: [openstack-dev] Proposal of nova-hyper driver

Thanks John. I’m also not sure what the future would be, but I’d say that it would be nice to have a hybrid OpenStack cluster of both VM/App-Container flavor. And yes, it is more about a unified model between Nova and Magnum. Best, Peng - Hyper -

Re: [openstack-dev] [qa] Tempest bug triage questions

On 06/22/2015 10:15 AM, Yaroslav Lobankov wrote: Hello everyone, I have some questions about the bug triage procedure for Tempest: 1. Some bugs in Tempest have status "Fix committed". Should we move statuses of these bugs to "Fix released"? Yes, tempest doesn't have the kind of releases where

[openstack-dev] [third-party] Third Party CI Working Group Meeting Tuesday June 23 1700UTC

Hi all, The Third Party CI Working Group is meeting at the new time this week - 1700UTC Tuesday, June 23rd in #openstack-meeting. The agenda for the meeting is here: https://wiki.openstack.org/wiki/Meetings/ThirdParty We will be working on the CI systems monitoring dashboard hosting spec and pre

Re: [openstack-dev] [Ironic] Proposal to add a new repository

On 06/22/2015 10:40 AM, Dmitry Tantsur wrote: > On 06/22/2015 04:19 PM, Devananda van der Veen wrote: >> Hi John, >> >> Thanks for the excellent summary! I found it very helpful to get caught >> up. I'd like to make sure I understand the direction ahc is going. A >> couple questions... Thanks fo

Re: [openstack-dev] [cross-project] RBAC Policy Basics

On 06/22/2015 12:41 AM, Osanai, Hisashi wrote: On Saturday, June 20, 2015 11:16 AM, Adam Young wrote: What situations does a shared policy file require? For example, there are policy files for Nova and Cinder and they have same targets such as "context_is_admin", "admin_or_owner" and "default".

[openstack-dev] [Murano] Watch new murano demos

Hi all! Recently murano team has recorded some demos describing features, introduced in Kilo. They can be found at murano wiki page [1]. Demo - is the easiest way to stay in touch with project news! The list of updated demos: - Importing Murano Packages from Murano Repository

Re: [openstack-dev] [Nova] Tracking optional requirements

Excerpts from Michael Still's message of 2015-06-22 21:05:11 +1000: > Sure, except where the thing isn't in pip... I just learned tonight > that the libosinfo thing in the review at the start of this thread is > a c library and some gobject black magic. I think we want it, but it > will never work

Re: [openstack-dev] [Ironic][Horizon][Tuskar-ui] Making a dashboard for Ironic

Hi Devananda, > The git history appears to be squashed [1], and most files don't have an > attribution header [2], and > none of the headers refer to the company who > appears to be behind this (Huawei). What's the > rationale for these > inconsistencies, and who is actua

Re: [openstack-dev] [Ironic] Proposal to add a new repository

Hi, > I see that ahc is storing its information in swift. That's clever, but if > Ironic provided a blob store for each node, would that be better? > I can try to answer that. The initial implementation was doing that but, AHC collect a fine-grained amount of data, e.g: * it runs benchmark on al

Re: [openstack-dev] [ceilometer] can we get ceilometermiddleware to use a config file instead of transport_url?

Excerpts from Doug Hellmann's message of 2015-06-22 10:50:06 -0400: > Excerpts from Sean Dague's message of 2015-06-22 09:02:02 -0400: > > On 06/22/2015 08:58 AM, Doug Hellmann wrote: > > > Excerpts from Sean Dague's message of 2015-06-22 08:08:04 -0400: > > >> In extracting the contract for RPC ba

Re: [openstack-dev] [Neutron] Modular L2 Agent

I see Kyle's point that this is not something in-scope for liberty at this stage. However, on the other hand I would rather avoid having multiple agents on the compute node performing various tasks in an un-coordinated way (well, actually relying on neutron-server coordination). QoS is an example

Re: [openstack-dev] [ceilometer] can we get ceilometermiddleware to use a config file instead of transport_url?

On 22/06/15 09:02 AM, Sean Dague wrote: On 06/22/2015 08:58 AM, Doug Hellmann wrote: Excerpts from Sean Dague's message of 2015-06-22 08:08:04 -0400: In extracting the contract for RPC backends in devstack (to have most of them live in plugins) one bit of an edge case was discovered. https:/

Re: [openstack-dev] [nova] Stuck on VIF plugin script?

On 22/06/15 15:11, Daniel P. Berrange wrote: On Mon, Jun 22, 2015 at 11:28:35AM +0100, neil.jer...@metaswitch.com wrote: ‎It seems like we're possibly stuck now on the VIF plugin script spec [1]; there being core comments in apparently conflicting directions. I wonder if it's still feasible fo

Re: [openstack-dev] [ceilometer] can we get ceilometermiddleware to use a config file instead of transport_url?

Excerpts from Sean Dague's message of 2015-06-22 09:02:02 -0400: > On 06/22/2015 08:58 AM, Doug Hellmann wrote: > > Excerpts from Sean Dague's message of 2015-06-22 08:08:04 -0400: > >> In extracting the contract for RPC backends in devstack (to have most of > >> them live in plugins) one bit of an

Re: [openstack-dev] [all] devstack plugin writers guide

On 06/22/2015 10:36 AM, Davanum Srinivas wrote: > Sean, > > Can we please add a bit about what things in devstack can they assume > to be available when their script is running (example: can they use > stuff from functions-common without actually sourcing it?) Sure, the answer is that functions-c

Re: [openstack-dev] [Ironic] Proposal to add a new repository

On 06/22/2015 04:19 PM, Devananda van der Veen wrote: Hi John, Thanks for the excellent summary! I found it very helpful to get caught up. I'd like to make sure I understand the direction ahc is going. A couple questions... Let me add my $0.5 :) I see that ahc is storing its information in

Re: [openstack-dev] [Neutron] Proposing Rossella Sblendido for the Control Plane core team

I missed this one!, congratulations Rosella :-) Anna Kamyshnikova 20 Jun 2015 11:55via Postbox Congratulations Rossella!

Re: [openstack-dev] [all] devstack plugin writers guide

Sean, Can we please add a bit about what things in devstack can they assume to be available when their script is running (example: can they use stuff from functions-common without actually sourcing it?) -- dims On Mon, Jun 22, 2015 at 10:12 AM, Sean Dague wrote: > There has been a bit of confus

Re: [openstack-dev] [Neutron] Modular L2 Agent

In the context of Quality of Service, we need to extend the L2 agents (SR-IOV, OVS and LB), and we didn't want to simply hijack the processing loop of the agents, but take a moment, and put together a Modular L2 design https://review.openstack.org/#/c/189723/ If you find it reasonable to do

Re: [openstack-dev] [Ironic] Proposal to add a new repository

Hi John, Thanks for the excellent summary! I found it very helpful to get caught up. I'd like to make sure I understand the direction ahc is going. A couple questions... I see that ahc is storing its information in swift. That's clever, but if Ironic provided a blob store for each node, would tha

[openstack-dev] [qa] Tempest bug triage questions

Hello everyone, I have some questions about the bug triage procedure for Tempest: 1. Some bugs in Tempest have status "Fix committed". Should we move statuses of these bugs to "Fix released"? 2. Many bugs have statuses "In progress", but patches for these bugs have -1 from someone (or their work

Re: [openstack-dev] [nova] Stuck on VIF plugin script?

On Mon, Jun 22, 2015 at 11:28:35AM +0100, neil.jer...@metaswitch.com wrote: > ‎It seems like we're possibly stuck now on the VIF plugin script spec [1]; > there being core comments in apparently conflicting directions. I wonder if > it's still feasible for a version of this to land during Liberty

[openstack-dev] [all] devstack plugin writers guide

There has been a bit of confusion about writing plugins for devstack, especially as we moved the primary model from in tree to out of tree plugins. To help clarify I did a big restructure of the DevStack Plugin Guide on Friday - http://docs.openstack.org/developer/devstack/plugins.html For new pro

[openstack-dev] M Naming Poll ended - results still need to clear legal

Hey all! The M naming poll has concluded. I'd say "and the winner is ..." except we still need to get the winning choice(s) vetted for legal entanglements. Feel free to go and look at the results, they are publicly available - but please DON'T start making t-shirts or having parties (ok, have as

[openstack-dev] [puppet][keystone] How to uniquely name Keystone v3 resources in puppet?

The problem with puppet-keystone and Keystone v3 domains is naming of puppet resources contained within domains - users, groups, projects. Suppose you have an admin user in domain "dom1" and an admin user in domain "dom2". How do you declare these in puppet? You can't do keystone_user { 'ad

Re: [openstack-dev] [nova] Stuck on VIF plugin script?

On 06/22/2015 06:59 AM, Neil Jerram wrote: On 22/06/15 11:28, neil.jer...@metaswitch.com wrote: ‎It seems like we're possibly stuck now on the VIF plugin script spec [1]; there being core comments in apparently conflicting directions. I wonder if it's still feasible for a version of this to land

Re: [openstack-dev] [api] [all] To changes-since or not to changes-since

Keystone also has a resource that provides changes since[1], the query parameter used is "since". [1] http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3-os-revoke-ext.html#list-revocation-events Ciao, Brant On Fri, Jun 19, 2015 at 3:25 PM, Sean Dague wrote: > On 06/19

Re: [openstack-dev] Proposal of nova-hyper driver

Hyper is using hypervisor to run Docker image, therefore it can support most features in the matrix, both mandatory and optional/choice. - Hyper - Make VM run like Container On Mon, Jun 22, 2015 at 4:18 PM, Sahid Orentino Ferdjaoui < sahid.fer

Re: [openstack-dev] [ceilometer] can we get ceilometermiddleware to use a config file instead of transport_url?

On 06/22/2015 08:58 AM, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2015-06-22 08:08:04 -0400: >> In extracting the contract for RPC backends in devstack (to have most of >> them live in plugins) one bit of an edge case was discovered. >> >> https://github.com/openstack-dev/devstac

  1   2   >