[openstack-dev] [all] Gerrit based IRC meetings.

Hi All, We've been using the new gerrit based irc-meetings repo for about 3 week now. There have been teething troubles but by and large I think things are going well. People have identified some tooling changes/enhancements that we're workign on, buyt that's another thread. A couple of thin

[openstack-dev] [Neutron][DevStack] Standing on the shoulders of giants - Linux Bridge testing at the gate

Hi, I wanted to give a quick update on the new experimental job for testing the Linux Bridge mechanism driver for Neutron. I believe that there is only one patch that needs to be merged, in order to get the job to a point where we could move from experimental to non-voting. https://review.openst

Re: [openstack-dev] [Stackalytics] Complementary projects

Paul Belanger wrote: > I am wondering the reason for the complementary projects listing[1] in > Stackalytics? Specifically, why does stackalytics-processor import > docker and cloudfoundry projects into the stats? > > [1] http://stackalytics.com/?project_type=complementary&metric=commits It's no

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

Flavio Percoco wrote: > There's a 95% of deployments using rabbit not because rabbit is the > best solution for all OpenStack problems but because it was the one > that works best now. The lack of support on other drivers caused this > and as long this lack of support on such drivers persist, it wo

Re: [openstack-dev] [all] Gerrit based IRC meetings.

Tony Breeds wrote: > The first thing is using the review to "vote" on meeting times. > - I'm not certain this is the best workflow but it's something worth palying > with. The key is identifying that a review is a suggestion and then > identifying when that suggestion becomes golden are the ke

Re: [openstack-dev] [Nova] Liberty Process, Deadlines and Dates for Nova

A quick bump for this thread because... * liberty-1 is next week * spec freeze is on June 25th * people are unsure about the exception process On 10 June 2015 at 16:45, John Garbutt wrote: > On 4 June 2015 at 12:42, John Garbutt wrote: >> Hi, >> >> Following up from nova-meetings and this summit

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

There's an open question in the API-WG on whether to formalize or otherwise enshrine the concept of a "changes-since" query parameter on collection oriented resources across the projects. The original source of this concept is from Nova's API: http://docs.openstack.org/developer/nova/v2/pol

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

On 06/19/2015 07:14 AM, Flavio Percoco wrote: The qpid family is a set of tools that provide messaging capabilities. Among those you find qpidd (broker daemon), qpid-proton (amqp1.0 library), qpid-dispatch (message router). It's confusing indeed. Apache Qpid is an Apache Software Foundation pro

Re: [openstack-dev] [nova] Low Hanging Fruit etherpad

Le 18/06/2015 22:00, melanie witt a écrit : Hi All, I have started an etherpad for tracking "low hanging fruit" work in Nova: https://etherpad.openstack.org/p/nova-low-hanging-fruit I have linked it on the Nova Mentoring wiki [1] and populated it with a bit of information about the remainin

Re: [openstack-dev] [qa] Status of account creds in the [identity] section of tempest.conf

On Thu, Jun 18, 2015 at 02:13:56PM -0400, David Kranz wrote: > We had a discussion about this at the qa meeting today around the following > proposal: > > tl;dr The test accounts feature provides the same functionality as the > embedded credentials. We should deprecate the account information embe

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

I'd like to resurrect this thread. The patch has been sitting for quite a while. Since it doesn't modify the responses by default of DHCP messages, I'm inclined to just let it merge for now as a dnsmasq-specific change. Then maybe later we can figure out how to expose this via the dhcp opts API or

[openstack-dev] Proposal of nova-hyper driver

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 a hypervisor-agnostic Docker runtime. It is similar to Intel’s ClearContainer, allowing to run a Docker image with any hypervisor. * Why Hyper

Re: [openstack-dev] [Fuel] Improvement of the blueprint specs template

Guys, I’d like to ask all Fuel component leads to take a look at the proposed changes and check whether all important sections were added. - romcheg > 18 черв. 2015 о 13:14 Roman Prykhodchenko написав(ла): > > I realize, that discussing this topic in the email is hard. I filed a review > req

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/18/2015 09:48 PM, Doug Hellmann wrote: > Excerpts from Brian Curtin's message of 2015-06-18 13:17:52 -0500: >> On Thursday, June 18, 2015, Doug Hellmann >> wrote: >> >>> Excerpts from Thomas Goirand's message of 2015-06-18 15:44:17 >>> +0200:

[openstack-dev] [oslo][messaging] Expanding the oslo.messaging core team

Hi Team, We have had active and continuing contributions [1] from the following in Blueprints, Reviews, Commits and Summit/Email discussions: * Ken Giusti * Oleksii Zamiatin * Victor Sergeyev Ken and Oleksii are spearheading important drivers that will help expand choices of messaging infrastruct

[openstack-dev] [nova] Adding vif_type to nova

Hi John and others, for my new neutron ml2 driver [3] I depend on a new vif_type in nova being introduced [1]. I also added Sourabh to cc, as he probably tries to achieve the same goal for another driver. I'm also aware of the current discussion regarding vif-plug-script [2]. This approach only

Re: [openstack-dev] [oslo][messaging] Expanding the oslo.messaging core team

Excerpts from Davanum Srinivas (dims)'s message of 2015-06-19 07:46:47 -0400: > Hi Team, > > We have had active and continuing contributions [1] from the following > in Blueprints, Reviews, Commits and Summit/Email discussions: > * Ken Giusti > * Oleksii Zamiatin > * Victor Sergeyev > > Ken and O

[openstack-dev] [oslo][oslo.service] Bootstrapping oslo.service core

Elena Ezhova and Marian Horban helped get oslo.service off the ground [1] with a lot of testing and are actively coordinating adoption by several projects like Nova, Neutron and Cinder etc. Since we don't have anyone in oslo-service-core at the moment, Let's add them as the initial core members of

Re: [openstack-dev] [all] Gerrit based IRC meetings.

Excerpts from Thierry Carrez's message of 2015-06-19 10:01:46 +0200: > Tony Breeds wrote: > > The first thing is using the review to "vote" on meeting times. > > - I'm not certain this is the best workflow but it's something worth palying > > with. The key is identifying that a review is a sugge

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

On Jun 19, 2015 1:19 PM, "Ihar Hrachyshka" wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 06/18/2015 09:48 PM, Doug Hellmann wrote: > > Excerpts from Brian Curtin's message of 2015-06-18 13:17:52 -0500: > >> On Thursday, June 18, 2015, Doug Hellmann > >> wrote: > >> > >>> Exc

Re: [openstack-dev] [Stackalytics] Complementary projects

Some reasons of having complementary projects in Stackalytics: * to compare efforts in other communities with OpenStack - just to feed curiosity on what is larger OpenStack or Kubernetes? * to light interest to contribute to projects that OpenStack depends on, like OVS and Ansible. * to keep an

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 18/06/15 21:44, Jeremy Stanley wrote: >> Based on that, I am confident in sticking with our plan of gating >> using >>> 3.4 for now and keeping an eye on the 3.5 packages being built >>> by Debian and Canonical. > Unless we shift platforms and go

Re: [openstack-dev] [oslo][oslo.service] Bootstrapping oslo.service core

Excerpts from Davanum Srinivas (dims)'s message of 2015-06-19 08:57:23 -0400: > Elena Ezhova and Marian Horban helped get oslo.service off the ground > [1] with a lot of testing and are actively coordinating adoption by > several projects like Nova, Neutron and Cinder etc. Since we don't > have any

Re: [openstack-dev] [Stackalytics] Complementary projects

On 06/19/2015 09:19 AM, Ilya Shakhat wrote: Some reasons of having complementary projects in Stackalytics: * to compare efforts in other communities with OpenStack - just to feed curiosity on what is larger OpenStack or Kubernetes? * to light interest to contribute to projects that OpenStack

Re: [openstack-dev] [Neutron][DevStack] Standing on the shoulders of giants - Linux Bridge testing at the gate

On Fri, Jun 19, 2015 at 2:20 AM, Sean M. Collins wrote: > Hi, > > I wanted to give a quick update on the new experimental job for testing > the Linux Bridge mechanism driver for Neutron. > > I believe that there is only one patch that needs to be merged, in order to > get the job to a point where

Re: [openstack-dev] [Neutron] Proposing YAMAMOTO Takashi for the Control Plane core team

Congratulations and welcome to the team! Edgar From: Kevin Benton Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, June 18, 2015 at 3:22 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [Neutron] Proposing Y

Re: [openstack-dev] [Keystone][OSC] Keystone v3 user create --project $projid does not add user to project?

On Fri, Jun 19, 2015 at 12:30 AM, Matthias Runge wrote: > On 18/06/15 17:58, Dolph Mathews wrote: > >> This was entirely intentional, in order to replace the implicit role >> assignment behavior in v2 with an explicit behavior in v3. >> >> > I must admit, this is quite irritating, as the command

Re: [openstack-dev] [Stackalytics] Complementary projects

On Jun 19, 2015 3:56 PM, "Jay Pipes" wrote: > > On 06/19/2015 09:19 AM, Ilya Shakhat wrote: >> >> Some reasons of having complementary projects in Stackalytics: >> * to compare efforts in other communities with OpenStack - just to >> feed curiosity on what is larger OpenStack or Kubernetes? >>

Re: [openstack-dev] [Keystone][OSC] Keystone v3 user create --project $projid does not add user to project?

Terry Howe wrote on 06/19/2015 10:22:51 AM: > From: Terry Howe > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 06/19/2015 10:25 AM > Subject: Re: [openstack-dev] [Keystone][OSC] Keystone v3 user create > --project $projid does not add user to project? > > On Fri

Re: [openstack-dev] [Neutron][DevStack] Standing on the shoulders of giants - Linux Bridge testing at the gate

- Original Message - > On Fri, Jun 19, 2015 at 2:20 AM, Sean M. Collins < [email protected] > > wrote: > > > Hi, > > I wanted to give a quick update on the new experimental job for testing > the Linux Bridge mechanism driver for Neutron. > > I believe that there is only one patch tha

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

On Fri, Jun 19, 2015 at 2:15 AM Flavio Percoco wrote: > On 18/06/15 16:37 -0400, Doug Hellmann wrote: > >Excerpts from Clint Byrum's message of 2015-06-18 12:47:21 -0700: > >> Hello! I know there's been a lot of churn and misunderstanding over the > >> recent devstack changes, so I wanted to make

Re: [openstack-dev] [Stackalytics] Complementary projects

On 06/19/2015 10:31 AM, Joe Gordon wrote: On Jun 19, 2015 3:56 PM, "Jay Pipes" mailto:[email protected]>> wrote: > > On 06/19/2015 09:19 AM, Ilya Shakhat wrote: >> >> Some reasons of having complementary projects in Stackalytics: >> * to compare efforts in other communities with OpenStack

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

Hrm, well, this is a discussion I was hoping to have in Vancouver, but we never got around to it. I feel we actually want three projects. One, which permits a standalone Ironic Dashboard. One, which integrates Ironic with Horizon. One, which contains as much common code as possible. And, potential

Re: [openstack-dev] [oslo][oslo.service] Bootstrapping oslo.service core

Sounds great to me, welcome! Davanum Srinivas wrote: Elena Ezhova and Marian Horban helped get oslo.service off the ground [1] with a lot of testing and are actively coordinating adoption by several projects like Nova, Neutron and Cinder etc. Since we don't have anyone in oslo-service-core at th

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

Flavio Percoco wrote: On 18/06/15 16:37 -0400, Doug Hellmann wrote: Excerpts from Clint Byrum's message of 2015-06-18 12:47:21 -0700: Hello! I know there's been a lot of churn and misunderstanding over the recent devstack changes, so I wanted to make it clear where we're going with messaging dr

[openstack-dev] [Horizon] Liberty Mid Cycle Meetup

Hi everybody, I got confirmation for hosting the mid cycle meetup at the HP Office in Fort Collins on July 21st - 23rd. I’ve put details on the location with a couple nearby hotels on the following ether pad. The room we have reserved can hold about 40 people, but I’ve requested for it to be

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

What does iPXE do exactly?, What are the implications of having this enabled by default? Cheers, Miguel Ángel Kevin Benton wrote: I'd like to resurrect this thread. The patch has been sitting for quite a while. Since it doesn't modify the responses by default of DHCP messages, I'm inclined t

Re: [openstack-dev] [oslo][messaging] Expanding the oslo.messaging core team

+1 Le 2015-06-19 14:54, Doug Hellmann a écrit : Excerpts from Davanum Srinivas (dims)'s message of 2015-06-19 07:46:47 -0400: Hi Team, We have had active and continuing contributions [1] from the following in Blueprints, Reviews, Commits and Summit/Email discussions: * Ken Giusti * Oleksii Zam

Re: [openstack-dev] [Stackalytics] Complementary projects

On 06/19/2015 11:40 AM, Jay Pipes wrote: > On 06/19/2015 10:31 AM, Joe Gordon wrote: >> On Jun 19, 2015 3:56 PM, "Jay Pipes" > > wrote: >> > >> > On 06/19/2015 09:19 AM, Ilya Shakhat wrote: >> >> >> >> Some reasons of having complementary projects in Stackalytics: >>

Re: [openstack-dev] [Neutron][DevStack] Standing on the shoulders of giants - Linux Bridge testing at the gate

On 06/19/2015 03:20 AM, Sean M. Collins wrote: > Hi, > > I wanted to give a quick update on the new experimental job for testing > the Linux Bridge mechanism driver for Neutron. > > I believe that there is only one patch that needs to be merged, in order to > get the job to a point where we could

Re: [openstack-dev] [Neutron] [QOS] Request for Additional QoS capabilities

Hi John, I guess it totally makes sense as a new type of rule for QoS, once the framework is ready, it could make sense to add a "connection per second limit" or "max connection limit" type of rule. John Joyce (joycej) wrote: Gal: I had seen the brute force blueprint and noticed how close the

Re: [openstack-dev] [nova] Online Migrations.

There are multiple nova objects that each have their own version and each object corresponds to a database model. I think this might be the best solution for being able to determine if rows are migrated or not. My basic thought is that each table has a the corresponding object class noted in th

Re: [openstack-dev] [os-ansible-deployment] Core team nomination

Please join me in welcoming Ian Cordasco to the `os-ansible-deployment` core team! ?? -- Kevin Carter From: Hugh Saunders Sent: Thursday, June 18, 2015 10:00 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [os-a

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

Excerpts from Ken Giusti's message of 2015-06-19 15:01:46 +: > On Fri, Jun 19, 2015 at 2:15 AM Flavio Percoco wrote: > > > On 18/06/15 16:37 -0400, Doug Hellmann wrote: > > >Excerpts from Clint Byrum's message of 2015-06-18 12:47:21 -0700: > > >> Hello! I know there's been a lot of churn and

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

Excerpts from Flavio Percoco's message of 2015-06-19 08:14:49 +0200: > On 18/06/15 16:37 -0400, Doug Hellmann wrote: > >Excerpts from Clint Byrum's message of 2015-06-18 12:47:21 -0700: > >> Hello! I know there's been a lot of churn and misunderstanding over the > >> recent devstack changes, so I w

Re: [openstack-dev] [os-ansible-deployment] Core team nomination

Thanks everyone! On 6/19/15, 11:52, "Kevin Carter" wrote: >Please join me in welcoming Ian Cordasco to the `os-ansible-deployment` >core team! > >​​ >-- > >Kevin Carter > > > > > > > > >From: Hugh Saunders >Sent: Thursday, June 18, 2015 10:00 AM >To: Open

[openstack-dev] [Horizon] [UX] [Glance] Enabling Horizon->Glance images streaming: request for early feedback

Hi folks! Some of you might had hit the problems with uploading large Glance images via Horizon, the problem was so well known that it got its own "solution" in Horizon settings named HORIZON_IMAGES_ALLOW_UPLOAD. So the exact problem is that large images being uploaded to Glance via Horizon may ea

[openstack-dev] [Ceilometer] Liberty Mid Cycle Virtual Meetup

Hi everyone, In this week's Ceilometer IRC meeting, we took a vote[1] and decide that we will have a *virtual* mid-cycle meetup for Liberty cycle. To figure out the convenient dates we created a doodle[2]. Please take a vote at your earliest, so we can settle on a date and get the rest of the d

[openstack-dev] [neutron][ml2] - generic port binding for ml2 and dvr

Hi Rob Kukura, We are seeing an issue in the ML2 device_context that was modified by you in a recent patch to get everything from the PortContext instead of the DVR context. Right now the PortContext does not seem to return the "DVRbinding" status, but just returns the PortContext and it errors o

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

Hi all, I'm glad that by asking the ironic-dashboard creators to propose their project to ironic initially (rather than stackforge) we have prompted this conversation. We now know that two independent groups of people have created standalone ironic dashboards, neither of which is currently part o

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

I've already +1'd this patch - timing issues aside - I think this is a Good Thing from a developer's point of view. Particularly, my own selfish point of view :) I envision the ability to support multiple different messaging services via the amqp1 driver. Having to keep devstack updated with an

Re: [openstack-dev] [neutron][ml2] - generic port binding for ml2 and dvr

Hi Swami, My fix for 1367391 will eventually eliminate the special DVRPortBinding table, so would presumably eliminate this bug, but you are correct that the current WIP patch (https://review.openstack.org/#/c/189410/) isn't quite that far along yet. I'll look for an interim fix. -Bob On 6

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

On Fri, 2015-06-19 at 10:07 +0100, Chris Dent wrote: > * Are there additional relevant pros and cons for the two proposals? > * Are there additional proposals which can address the shortcomings >in either? On the latter question, would using the If-Modified-Since header[1] make any sense as a

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

On 6/19/15, 14:26, "Kevin L. Mitchell" wrote: >On Fri, 2015-06-19 at 10:07 +0100, Chris Dent wrote: >> * Are there additional relevant pros and cons for the two proposals? >> * Are there additional proposals which can address the shortcomings >>in either? > >On the latter question, would us

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

On Wed, Jun 17, 2015 at 7:31 AM Jay Pipes wrote: > On 06/17/2015 06:30 AM, Lucas Alvares Gomes wrote: > >> overlap there rather than competition), how crazy does it sound if we > say > >> that for OpenStack Nova is the compute API and Ironic the Bare Metal > API and > >> so on? Would that be an u

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

On 06/19/2015 03:16 PM, Ken Giusti wrote: > I've already +1'd this patch - timing issues aside - I think this is a > Good Thing from a developer's point of view. Particularly, my own > selfish point of view :) I envision the ability to support multiple > different messaging services via the amqp1

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

On 6/19/15, 14:39, "Ian Cordasco" wrote: > > >On 6/19/15, 14:26, "Kevin L. Mitchell" >wrote: > >>On Fri, 2015-06-19 at 10:07 +0100, Chris Dent wrote: >>> * Are there additional relevant pros and cons for the two proposals? >>> * Are there additional proposals which can address the shortcomings

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

You might need these changes, which are proposed but not merged: https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:stable/kilo+topic:bug/1442787,n,z Salut, Brant On Thu, Jun 18, 2015 at 6:04 AM, J. Pablo Martín Cobos wrote: > Hi all, > > I'm a Python/Django software

Re: [openstack-dev] [Glance] [all] Proposal for Glance Artifacts Sub-Team meeting.

Voting is now closed as we did not hear any concerns and there were positive votes on the review. So, we would like to reserve a spot for the meeting time & date (for the appropriate duration) as per the latest on https://review.openstack.org/#/c/192270/ . Seems like gerrit is best way to detect c

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

On 06/19/2015 04:03 PM, Ian Cordasco wrote: > > > On 6/19/15, 14:39, "Ian Cordasco" wrote: > >> >> >> On 6/19/15, 14:26, "Kevin L. Mitchell" >> wrote: >> >>> On Fri, 2015-06-19 at 10:07 +0100, Chris Dent wrote: * Are there additional relevant pros and cons for the two proposals? * Ar

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

From: Chris Dent Sent: Friday, June 19, 2015 4:07 AM To: [email protected] Subject: [openstack-dev] [api] [all] To changes-since or not to changes-since There's an open question in the API-WG on whether to formalize or otherwise enshrine t

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

On 06/19/2015 05:07 AM, Chris Dent wrote: > > There's an open question in the API-WG on whether to formalize or > otherwise enshrine the concept of a "changes-since" query parameter > on collection oriented resources across the projects. The original > source of this concept is from Nova's API: >

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

Excerpts from Flavio Percoco's message of 2015-06-18 23:14:49 -0700: > On 18/06/15 16:37 -0400, Doug Hellmann wrote: > >Excerpts from Clint Byrum's message of 2015-06-18 12:47:21 -0700: > >> Hello! I know there's been a lot of churn and misunderstanding over the > >> recent devstack changes, so I w

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

Excerpts from Ken Giusti's message of 2015-06-19 08:01:46 -0700: > On Fri, Jun 19, 2015 at 2:15 AM Flavio Percoco wrote: > > > On 18/06/15 16:37 -0400, Doug Hellmann wrote: > > >Excerpts from Clint Byrum's message of 2015-06-18 12:47:21 -0700: > > >> Hello! I know there's been a lot of churn and

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

Clint Byrum wrote: Excerpts from Flavio Percoco's message of 2015-06-18 23:14:49 -0700: On 18/06/15 16:37 -0400, Doug Hellmann wrote: Excerpts from Clint Byrum's message of 2015-06-18 12:47:21 -0700: Hello! I know there's been a lot of churn and misunderstanding over the recent devstack change

Re: [openstack-dev] [Congress] Mid-cycle sprint

Hi Zhou, The requirements for the request_refresh API call came from a customer. It wasn't intended as a replacement for the functionality we'd get by integrating with oslo.messaging. But it was a simple feature to add, with nice properties from Congress's perspective, driven by a real use case.

Re: [openstack-dev] Proposing Brian Haley to Neutron L3 Core Reviewer Team

Thanks for all the support, looking forward to helping out more :) -Brian On 06/18/2015 07:34 AM, Paul Michali wrote: Congratulations Brian! Great addition to the L3 team! On Wed, Jun 17, 2015 at 11:14 PM Edgar Magana mailto:[email protected]>> wrote: Congratulations Brian! Welcom

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

On Fri, Jun 19, 2015 at 4:47 PM Clint Byrum wrote: > Excerpts from Ken Giusti's message of 2015-06-19 08:01:46 -0700: > > On Fri, Jun 19, 2015 at 2:15 AM Flavio Percoco > wrote: > > > > > On 18/06/15 16:37 -0400, Doug Hellmann wrote: > > > >Excerpts from Clint Byrum's message of 2015-06-18 12:47

[openstack-dev] [all][api] New API Guidelines ready for cross project review

Hi All, We have 3 API Guidelines that are ready for a final review. 1. Add section on filtering https://review.openstack.org/#/c/177468/ 2. http guideline expansion: background https://review.openstack.org/#/c/181931/ 3. Should not return server-side tracebacks https://review.openstack.org/#/c/

[openstack-dev] [app-catalog] App Catalog IRC meeting minutes - 6/18/2015

Thanks to all who joined the meeting this week. After the announcements we had a really good conversation and touched on a few important topics, and there's a lot more to discuss as we work through putting together our near-term roadmap. In addition to the topics noted in the log, we're already s

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

Hi Jim, Your characterization of this is incomplete. These are not two equal projects proposing the same thing in different ways, and while I very much want to encourage collaboration, I value our community and feel that this was not done in the spirit of that community. To be clear: ironic-webcl

Re: [openstack-dev] [puppet] (officially) deprecate stable/{grizzly, havana} branches

I'd vote for stable -2. I think a number of people do an upgrade maybe once a year. I believe CERN just upgraded to juno recently. On Tue, Jun 16, 2015 at 1:36 PM, Richard Raseley wrote: > Matt Fischer wrote: > >> +1 from me for deprecation. >> >> I'd also like to know or have an official poli

[openstack-dev] Angular dependencies and the hz.dashboard namespace

The "Adding Angular Identity Dashboard"[1] patch exposed an issue I saw previously that worried me[2]. I believe during recent Horizon work the concept of angular module namespaces and dependencies have been conflated. There's this idea that if you create a submodule inside a module namespace you

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

Hey Everyone, So I've talked a little in bits and pieces regarding the implementations that are going in for the ABC metaclass work. First off, I think the use of ABC is a good idea and has value, particularly as we approach/surpass 50 third party drivers. The only thing that I'm wondering if we

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

It's been a week with no negative feedback. Welcome to the team Rossella! On Mon, Jun 15, 2015 at 2:53 AM, Oleg Bondarev wrote: > +1 > > On Mon, Jun 15, 2015 at 12:14 PM, Ihar Hrachyshka > wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> No doubt +1. >> >> On 06/12/2015 09:4

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

As I understand it, it just allows other rules to be written that specifically target pxe requests. So just enabling it won't have any effect. http://www.richud.com/wiki/Network_iPXE_dnsmasq_Examples_PXE_BOOT On Fri, Jun 19, 2015 at 9:21 AM, Miguel Angel Ajo wrote: > What does iPXE do exactly?,

Re: [openstack-dev] [horizon] Angular dependencies and the hz.dashboard namespace

Heres a summary of what we talked about:1. Need to retain the same file structure so that pluggins continue to work. Example: https://github.com/stackforge/monasca-ui/tree/master/monitoringBasically we have existing pluggins that use this file structure, we need to honor it.This is not directly rel

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

On Fri, Jun 19, 2015 at 3:43 PM, John Griffith wrote: > Anyway, maybe I'm missing a big advantage here, but without understanding > what this gains it makes the code structure a bit hard to maintain and > follow in a number of ways. For example, in order to implement this in the > existing driver

Re: [openstack-dev] [Security] Nominating Michael McCune for Security CoreSec

On 2015-06-15 16:16:57 - (-), Travis McPeak wrote: > I'd like to propose Michael McCune for CoreSec membership. [...] I'm in favor--Michael has been very helpful so far. Thanks! -- Jeremy Stanley signature.asc Description: Digital signature __

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

On Fri, Jun 19, 2015 at 5:31 PM, Mike Perez wrote: > On Fri, Jun 19, 2015 at 3:43 PM, John Griffith > wrote: > > Anyway, maybe I'm missing a big advantage here, but without understanding > > what this gains it makes the code structure a bit hard to maintain and > > follow in a number of ways. F

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

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 numbering and dependency ordering, but of communicating sup

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

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 have tried to find any information on very large scale deployment

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

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 ConsistencyGroupVD. But you *can’t* add them to ConsistencyGroupVD until

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

Excerpts from Alec Hothan (ahothan)'s message of 2015-06-19 17:18:41 -0700: > > 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 coul

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

In line (at the bottom) From: Devananda van der Veen [mailto:[email protected]] Sent: Friday, June 19, 2015 12:40 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header On Wed, Jun 17, 2015 at 7:31 AM J

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

On 06/19/2015 01:08 AM, Osanai, Hisashi wrote: Adam, Thank you for the information RBAC Policy Basics. Thursday, June 18, 2015 1:47 AM, Adam Young wrote: However, we have found a need to have a global override. This is a way a cloud admin that can go into any API anywhere and fix things. Thi

[openstack-dev] [kolla][magnum] Medical semi-emergency with my tooth

Hey Kolla cats (and Magnum cats), I have a tooth infection, which isn’t super serious, but the pain levels are about a 8 out of 10 on the holy fuck scale. As a result, my work is a bit impaired. I may be a bit MIA in the next week while I sort out the medical problem and get my tooth into a m

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

On 19 June 2015 at 02:18, Ian Cordasco wrote: > > > On 6/18/15, 08:44, "Thomas Goirand" wrote: > Does this mean that Debian is going to ignore classifiers for all projects > that list 3.4 without listing 3.5 and will start reporting bugs against > them before upstream projects have time to start