Re: [openstack-dev] [infra] [cinder] CI via infra for the DRBD Cinder driver

> this is a reflection of the discussion I just had on #openstack-infra; it's > about (re-)using the central CI infrastructure for our Open-Source DRBD > driver too. As this is done now, I'd like to discuss a few points. First of all -- thanks to everybody involved; if you happen to find someon

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On 06/20/2015 02:14 AM, Devananda van der Veen wrote: Almost all of our discussions so far on this topic have left something out, which Monty pointed out to me last week. I'm following up now because E_TRAVEL... tldr; What we're versioning here are API's, not packages. It's not a question of num

Re: [openstack-dev] Debian already using Python 3.5: please gate on that

Hi, Le 18/06/2015 15:44, Thomas Goirand a écrit : As per the subject line, we already have Python 3.5 in Debian (AFAICT, from Debian Experimental, in version beta 2). As a consequence, we're already running (unit) tests using Python 3.5. Some have failures: I could see issues in ceilometerclient

Re: [openstack-dev] [Neutron][Ironic] Setting IPXE tag for dnsmasq

Thanks Kevin!, Kevin Benton 20 Jun 2015 01:01via Postbox As I understand it, it just allows other rules to be written that specifically target pxe requests. So just enabling it won'

Re: [openstack-dev] [Neutron][Ironic] Setting IPXE tag for dnsmasq

Thanks Kevin!, Kevin Benton 20 Jun 2015 01:01via Postbox As I understand it, it just allows other rules to be written that specifically target pxe requests. So just enabling it won'

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

On Sun, Jun 21, 2015 at 07:18:10PM +0300, Joe Gordon wrote: > On Fri, Jun 19, 2015 at 12:55 PM, Peng Zhao wrote: > > >Hi, all, > > > > I would like to propose nova-hyper driver: > > https://blueprints.launchpad.net/nova/+spec/nova-hyper. > > > >- What is Hyper? > >Put simply, Hyper is

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

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 sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3 -> sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 Whats happening is that the r

[openstack-dev] [glance] Progress of the Python 3 port

Hi, We made great progress on porting Glance to Python 3. tox -e py34 now pass with a subset of tests and there is a non-voting py34 check job. I propose to make the py34 gate voting to avoid Python 3 regressions: https://review.openstack.org/194048 "Make gate-glance-python34 voting" When th

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

On 22 June 2015 at 09:18, Sahid Orentino Ferdjaoui wrote: > On Sun, Jun 21, 2015 at 07:18:10PM +0300, Joe Gordon wrote: >> On Fri, Jun 19, 2015 at 12:55 PM, Peng Zhao wrote: >> >> >Hi, all, >> > >> > I would like to propose nova-hyper driver: >> > https://blueprints.launchpad.net/nova/+spec/n

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On 22 June 2015 at 00:14, Michael Still wrote: > As an aside, do we think that exposing the exact version of a server > process is safe from a security perspective? During discussions in the Nova API meeting, it was noted that while we do expose the exact API version, we are not exposing the git

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

Thanks everybody! I will do my best! On 06/21/2015 03:56 AM, Paul Michali wrote: Congratulations Rossella! Great addition to the team! On Sat, Jun 20, 2015 at 12:13 PM Miguel Lavalle mailto:[email protected]>> wrote: Complimenti per il nuovo lavoro! On Fri, Jun 19, 2015 at 5:50 PM, K

[openstack-dev] [Heat][Oslo] Versioned objects compatibility mode

Hello, I wanted to start discussion about versioned objects backporting for conductor-less projects. In Vancouver we discussed compatibility mode, which works like that: 1. We define one version for every object we use, this means adding base object, for example: Class HeatObject: VERS

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

On Sun, Jun 21, 2015 at 11:14:00AM -0500, Matt Riedemann wrote: > > > On 6/20/2015 3:35 PM, Daniel P. Berrange wrote: > >On Sat, Jun 20, 2015 at 01:50:53PM -0500, Matt Riedemann wrote: > >>Waking up from a rare nap opportunity on a Saturday, this is what was > >>bothering me: > >> > >>The proposa

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

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 > sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3 > -> > sph

Re: [openstack-dev] [Heat][Oslo] Versioned objects compatibility mode

Michał, we are adding that reread config to oslo.service, there's a test version on pypi 0.1.0 (API not yet stable) that you can try and see if it works for you. thanks, dims On Mon, Jun 22, 2015 at 5:40 AM, Jastrzebski, Michal wrote: > Hello, > > I wanted to start discussion about versioned ob

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

On 06/19/2015 08:18 PM, Alec Hothan (ahothan) wrote: > > Do we have a good understanding of what is expected of zmq wrt rabbitMQ? > Like in what part of the bell curve or use cases would you see it? Or > indirectly, where do we see RabbitMQ lacking today that maybe ZMQ could > handle better? > I h

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

‎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?  [1] https://review.openstack.org/#/c/162468/ I plan to reread everyone's comm

[openstack-dev] [Designate] Setting after adding new BIND9 server

Hi, I'm using the "designate stable/kilo" and BIND9. After new Bind9 server created, how should I set the existing domain information to new BIND9 server? (Is there this setting function in Designate?) Could you please advise me for it? Best Regards, Kenichiro Matsuda. ___

[openstack-dev] [Nova] Tracking optional requirements

Hi, https://review.openstack.org/#/c/149625 made me think about optional requirements for nova. Some hypervisor drivers have requirements that are either only needed for their driver, or are optional to their driver. Examples include the ironic driver depending on the ironic client, and the review

Re: [openstack-dev] Add table to Nova DB

Hi, I've subscribed this list just now, so I didn't read your answer before today. I'm gonna explain better what I sould do. I know that Ceilometer collects statics about the network state, but as far as I know, those are related to the virtual network. I'm putting an ovs managed by an SDN controll

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

On 06/22/2015 06:37 AM, Michael Still wrote: > Hi, > > https://review.openstack.org/#/c/149625 made me think about optional > requirements for nova. Some hypervisor drivers have requirements that > are either only needed for their driver, or are optional to their > driver. Examples include the iro

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On 06/22/2015 05:28 AM, John Garbutt wrote: > On 22 June 2015 at 00:14, Michael Still wrote: >> As an aside, do we think that exposing the exact version of a server >> process is safe from a security perspective? > > During discussions in the Nova API meeting, it was noted that while we > do expo

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

Michael, We talked about it in Vancouver in the context of oslo.messaging: https://etherpad.openstack.org/p/YVR-oslo-optional-dependencies Consensus was: "optional dependencies should be specified with extras in setup.cfg; conditional ones via markers." Robert is driving towards making this real

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

On 22/06/15 11:28, [email protected] 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? [1] https://review.ope

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

Am 20.06.2015 um 02:34 schrieb Knight, Clinton : > Funny you should mention needing all of the CG methods... > > A VD group (ConsistencyGroupVD) was added to contain the 4 CG methods from > Juno. Then more CG methods were added to VolumeDriver in Kilo, but they > weren’t added to ConsistencyG

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

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 dependancy. So, I think something human readable is still required?

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

(Noting that its kind of late where I am). Sean, I totally agree that we should fix uname. Let's get on that. Michael On Mon, Jun 22, 2015 at 8:52 PM, Sean Dague wrote: > On 06/22/2015 05:28 AM, John Garbutt wrote: >> On 22 June 2015 at 00:14, Michael Still wrote: >>> As an aside, do we think

Re: [openstack-dev] [Heat][Oslo] Versioned objects compatibility mode

Davanum, Can we also use SIGHUP signal tool instead of for these restarts? Regards, Sergey. On 22 June 2015 at 13:12, Davanum Srinivas wrote: > Michał, > > we are adding that reread config to oslo.service, there's a test > version on pypi 0.1.0 (API not yet stable) that you can try and see if

Re: [openstack-dev] [Heat][Oslo] Versioned objects compatibility mode

At the moment, We have reload config files in place: https://github.com/openstack/oslo.service/blob/master/oslo_service/service.py#L487 there are patches against Nova and Neutron where we are looking at how this works and what else we can do. -- dims On Mon, Jun 22, 2015 at 7:21 AM, Sergey Kray

[openstack-dev] [Fuel][Plugins] Certification schedule is shifted due to the Fuel GA date

Hi to all, Please, be informed that the plugin certification schedule is shifted due to the Fuel GA date [1]. *This means the following:* if you've sent your plugin targeted at 6.1 for certification, it will be tested using GA, but not Release Candidates. If you have any further questions relate

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

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/devstack/blob/master/lib/swift#L388 The connection to the RPC mechanism from ceilometermiddleware inside of swift uses a transpor

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

This is a proposal to add a new repository governed by the ironic inspector subteam. The current repository is named ahc-tools[1], however there is no attachment to this name. "ironic-inspector-extra" would seem to fit if this is moved under the Ironic umbrella. What is AHC? * AHC as

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

On Sun, Jun 21, 2015 at 9:54 AM, Mohammad Banikazemi wrote: > During the last couple of ML2 group meetings, the subject of Modular L2 > Agents has come up again and I was tasked to bring up the subject to the > attention of the larger community. > We are aware of the ongoing efforts to improve th

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 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/devstack/blob/master/lib/swift#L388 > > The connection t

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

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] [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] [nova] Stuck on VIF plugin script?

On 06/22/2015 06:59 AM, Neil Jerram wrote: On 22/06/15 11:28, [email protected] 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

[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

[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] [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

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

On Mon, Jun 22, 2015 at 11:28:35AM +0100, [email protected] 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] [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] [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

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] [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] 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] [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] [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] [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] [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, [email protected] 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?

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] [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?

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] [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] [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] [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

[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] [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".

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

[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] [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

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 -

[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] [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

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] 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] [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] [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] [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

[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] [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

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] [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

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] [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 > >

[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

[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

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

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, 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] [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] [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] [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] 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] [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

[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] 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. ;) __

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] [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

[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] [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] [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] [heat][tripleo]Recursive validation for easier composability

> From: Jay Dobies > To: [email protected] > 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

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] [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] [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] [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] [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] [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

  1   2   >