[openstack-dev] [barbican] Nominating Nathan Reller for barbican-core

Hi Everyone, I would also like to nominate Nathan Reller for the barbican-core team. Nathan has been involved with the Key Management effort since early 2013. Recently, Nate has been driving the development of a KMIP backend for Barbican, which will enable Barbican to be used with KMIP devices.

Re: [openstack-dev] [all] oslo.messaging 1.4.0.0a3 released

On Wed, 2014-07-09 at 03:53 +, Paul Michali (pcm) wrote: > Mark, > > > What is the status of adding the newer oslo.messaging releases to > global requirements? I had tried to get 1.4.0.0a2 added to > requirements (https://review.openstack.org/#/c/103536/), but it was > failing Jenkins. Wonder

Re: [openstack-dev] [Neutron][LBaaS] Shim vs Agent Refactor

Modified slightly, my read on the decision was: * Create a v2 agent, and make the ref haproxy driver use the v2 agent and v2 obj model. * At a lower priority, work on a shim for non-agent older drivers. This is de-coupled from the haproxy ref driver, and could happen in parallel if we h

Re: [openstack-dev] [all] Treating notifications as a contract

On Thu, 2014-07-10 at 04:48 -0400, Eoghan Glynn wrote: > TL;DR: do we need to stabilize notifications behind a versioned >and discoverable contract? > > Folks, > > One of the issues that has been raised in the recent discussions with > the QA team about branchless Tempest relates to some

Re: [openstack-dev] [all] Treating notifications as a contract

-Original Message- From: Sandy Walsh Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, July 10, 2014 at 9:31 AM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [all] Treating notifications as a contr

Re: [openstack-dev] [Neutron][LBaaS] Shim vs Agent Refactor

New/updated v2 driver could be done without an agent (same as was possible in v1). From: Doug Wiegley [mailto:do...@a10networks.com] Sent: Thursday, July 10, 2014 8:06 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] Shim vs Agent R

Re: [openstack-dev] [Neutron][LBaaS] Shim vs Agent Refactor

Absolutely, and work on those can start immediately, for any vendor that wants to update their driver. I’d recommend using the driver base class in this review, which modifies the current new one, based on some stuff that Brandon found: https://review.openstack.org/#/c/105610 Thanks, Doug Fr

Re: [openstack-dev] [Neutron][LBaaS] Shim vs Agent Refactor

Samuel, I've heard this mentioned before, but looking at the code the haproxy namespace driver uses the agent driver interface rather the the abstract driver interface. Are you sure the HAProxy driver can be used without the agent, if so could you explain how? Thanks, Dustin Lundquist On Thur

Re: [openstack-dev] [all] Treating notifications as a contract

>From my perspective, the requirement is to be able to have a consistent and >predictable format for notifications that are being sent from all services. >This means: 1. a set of required fields that all events contain and have consistent meaning 2. a set of optional fields, you don’t have to inc

Re: [openstack-dev] [barbican] Nominating Nathan Reller for barbican-core

+1 On Jul 10, 2014, at 12:11 PM, Douglas Mendizabal mailto:douglas.mendiza...@rackspace.com>> wrote: Hi Everyone, I would also like to nominate Nathan Reller for the barbican-core team. Nathan has been involved with the Key Management effort since early 2013. Recently, Nate has been driving

Re: [openstack-dev] [barbican] Nominating Ade Lee for barbican-core

+1 On Jul 10, 2014, at 11:55 AM, Douglas Mendizabal mailto:douglas.mendiza...@rackspace.com>> wrote: Hi Everyone, I would like to nominate Ade Lee for the barbican-core team. Ade has been involved in the development of Barbican since January of this year, and he’s been driving the work to en

Re: [openstack-dev] [TripleO] Proposal to add Jon Paul Sullivan and Alexis Lee to core review team

FWIW, I'm a firm believer in progress over perfection and although I comment on the form, I try to score on the function. I really like this phrase, comment on the form, score on the function. Lately I've been trying to be very specific about things I'm pointing out that are potentially a lear

Re: [openstack-dev] [nova] tox.ini ignores are TODOs?

On Thu, Jul 10, 2014 at 9:02 AM, Sean Dague wrote: > On 07/10/2014 11:46 AM, Moore, Ryan wrote: > > Hi > > > > > > > > tox.ini has the line # The rest of the ignores are TODOs > > > > How serious are we about getting rid of these ignores? > > > > > > > > Is it valid to -1 a patch that does not pa

Re: [openstack-dev] [barbican] Nominating Ade Lee for barbican-core

+1 John Vrbanac From: Douglas Mendizabal [douglas.mendiza...@rackspace.com] Sent: Thursday, July 10, 2014 11:55 AM To: OpenStack Development Mailing List (not for usage questions); a...@redhat.com Subject: [openstack-dev] [barbican] Nominating Ade Lee for barbican

Re: [openstack-dev] [barbican] Nominating Nathan Reller for barbican-core

+1 John Vrbanac From: Douglas Mendizabal [douglas.mendiza...@rackspace.com] Sent: Thursday, July 10, 2014 12:11 PM To: OpenStack Development Mailing List (not for usage questions); Nathan Reller Subject: [openstack-dev] [barbican] Nominating Nathan Reller for barbi

Re: [openstack-dev] [trove] Discussion of capabilities feature

On Wed, Jul 9, 2014 at 5:30 PM, Nikhil Manchanda wrote: > > Joe Gordon writes: > > > [...] > >> This sounds very similar to the v3/v2.1 discussion happening in nova. > All > >> OpenStack projects need to address these issues and it would be a shame > if > >> each project chose a different solutio

Re: [openstack-dev] [Ironic] handling drivers that will not be third-party tested

I would rather not require operators to change deployment configuration merely because a driver is more or less tested upstream. Communication of our level of confidence in a driver is good, but requiring breaking config file changes (with or without a deprecation period) doesn't seem like a polite

Re: [openstack-dev] [all] Treating notifications as a contract

On 7/10/2014 2:59 PM, Daniel Dyer wrote: > From my perspective, the requirement is to be able to have a consistent and > predictable format for notifications that are being sent from all services. > This means: > 1. a set of required fields that all events contain and have consistent > meaning >

Re: [openstack-dev] [Ironic] handling drivers that will not be third-party tested

Thanks for putting this back on my radar I think a separate directory to indicate "these are contributed but less tested drivers" is a fair middle ground here, though time will tell how much addtitional code-maintenance burden that places on developers. Since this is just a power interface, I

Re: [openstack-dev] [barbican] Nominating Ade Lee for barbican-core

On 07/10/2014 12:55 PM, Douglas Mendizabal wrote: > Hi Everyone, > > I would like to nominate Ade Lee for the barbican-core team. > > I'm not a member of the barbican core team but I'd like to endorse Ade anyway with a +1. I've worked with Ade for years and consider him an exceptional engineer wh

Re: [openstack-dev] [trove] Discussion of capabilities feature

One mechanism for this for Neutron advanced services, that’s being discussed right now, is here: https://review.openstack.org/#/c/102723/ Thanks, doug From: Joe Gordon mailto:joe.gord...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@l

Re: [openstack-dev] [Neutron][LBaaS] Shim vs Agent Refactor

The haproxy reference is dependent on the agent. Radware’s solution does not use an agent. I was making sure that solutions such as ours will be possible. From: Dustin Lundquist [mailto:dus...@null-ptr.net] Sent: Thursday, July 10, 2014 8:51 PM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [all] oslo.messaging 1.4.0.0a3 released

On Thu, Jul 10, 2014 at 1:06 PM, Mark McLoughlin wrote: > On Wed, 2014-07-09 at 03:53 +, Paul Michali (pcm) wrote: >> Mark, >> >> >> What is the status of adding the newer oslo.messaging releases to >> global requirements? I had tried to get 1.4.0.0a2 added to >> requirements (https://review.o

Re: [openstack-dev] [qa][all] Branchless Tempest beyond pure-API tests, impact on backporting policy

On Thu, Jul 10, 2014 at 11:56 AM, Sean Dague wrote: > On 07/10/2014 09:48 AM, Matthew Treinish wrote: >> On Wed, Jul 09, 2014 at 09:16:01AM -0400, Sean Dague wrote: >>> I think we need to actually step back a little and figure out where we >>> are, how we got here, and what the future of validatio

[openstack-dev] [sahara] team meeting minutes July 10

Thanks everyone who have joined Sahara meeting. Here are the logs from the meeting: Minutes: http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-07-10-18.03.html Logs: http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-07-10-18.03.log.html -- Sincerely yours, Sergey L

Re: [openstack-dev] [Ironic] handling drivers that will not be third-party tested

On Thu, Jul 10, 2014 at 11:21 AM, Devananda van der Veen < devananda@gmail.com> wrote: > Thanks for putting this back on my radar > > I think a separate directory to indicate "these are contributed but less > tested drivers" is a fair middle ground here, though time will tell how > much ad

Re: [openstack-dev] [Heat] stevedore plugins (and wait conditions)

On Jul 10, 2014, at 9:21 AM, Zane Bitter wrote: > On 10/07/14 05:34, Steven Hardy wrote: > >The other approach is to set up a new container, owned by the user, > >every time. In that case, a provider selecting this implementation > >would need to make it clear to customers if th

Re: [openstack-dev] [Ironic] [Horizon] [UX] Wireframes for Node Management - Juno

Awesome! Glad to see the progress since the design summit. Some comments: - slide 1 shows some driver-specific input fields. We have work in progress to expose this list via the API which I'm hoping to land in J2 or very early in J3. https://review.openstack.org/#/c/102914/ That should help the UI

Re: [openstack-dev] [oslo] Asyncio and oslo.messaging

On Jul 10, 2014, at 3:48 AM, Yuriy Taraday wrote: > On Wed, Jul 9, 2014 at 7:39 PM, Clint Byrum wrote: > Excerpts from Yuriy Taraday's message of 2014-07-09 03:36:00 -0700: > > On Tue, Jul 8, 2014 at 11:31 PM, Joshua Harlow > > wrote: > > > > > I think clints response was likely better than wha

Re: [openstack-dev] [TripleO] Proposal to add Jon Paul Sullivan and Alexis Lee to core review team

Excerpts from Clint Byrum's message of 2014-07-09 15:52:27 +: > Hello! > > I've been looking at the statistics, and doing a bit of review of the > reviewers, and I think we have an opportunity to expand the core reviewer > team in TripleO. We absolutely need the help, and I think these two > i

Re: [openstack-dev] [all] Treating notifications as a contract

> Thanks for dusting this off. Versioning and published schemas for > notifications are important to the StackTach team. It would be nice to > get this resolved. We're happy to help out. Great! > > A great outcome would include some or all of the following: > > > > 1. more complete in-tree te

Re: [openstack-dev] [all] Treating notifications as a contract

> Glad to see this coming up again. I've been pushing that since the > Icehouse summit in Hong-Kong, where we had a Oslo session about that > subject and where everybody nod about my initial plan. :) > > I've created a blueprint and started a very primitive implementation > back then: > > htt

Re: [openstack-dev] [all] Treating notifications as a contract

> It's not clear to me in this discussion what it is that is being > versioned, contracted or standardized. Well the statement in the original mail was pretty explicit: "versioned notification payloads to protect consumers from breaking changes in payload format" So it's the standardization

Re: [openstack-dev] [Ironic] [Horizon] [UX] Wireframes for Node Management - Juno

Excerpts from Jaromir Coufal's message of 2014-07-09 07:51:56 +: > Hey folks, > > after few rounds of reviews and feedbacks, I am sending wireframes, > which are ready for implementation in Juno: > > http://people.redhat.com/~jcoufal/openstack/juno/2014-07-09_nodes-ui_juno.pdf > > Let me kn

Re: [openstack-dev] [all] Treating notifications as a contract

> > One of the issues that has been raised in the recent discussions with > > the QA team about branchless Tempest relates to some legacy defects > > in the OpenStack notification system. > > Got links to specifics? I thought the consensus was that there was a > contract here which we need to mai

Re: [openstack-dev] [all] Treating notifications as a contract

> From my perspective, the requirement is to be able to have a consistent and > predictable format for notifications that are being sent from all services. > This means: > 1. a set of required fields that all events contain and have consistent > meaning > 2. a set of optional fields, you don’t ha

Re: [openstack-dev] [all] Treating notifications as a contract

> The original implementation of the notification system was never intended > to be the *final* implementation. I think we all identified the need for > versioning several years ago. As for backwards compatibility, I think the > version field itself, in whatever form it takes, should be optional.

Re: [openstack-dev] [nova][cinder][ironic][qa] Tempest+Ironic volume attachment tests

On Wed, Jul 9, 2014 at 1:58 PM, Matthew Treinish wrote: > > On Wed, Jul 09, 2014 at 10:58:27AM -0400, David Shrewsbury wrote: > > Hi! > > > > The ironic team is working on enabling the API tempest tests with ironic. However, > > ironic doesn’t yet completely support volume attachment, so the cinde

Re: [openstack-dev] [barbican] Nominating Ade Lee for barbican-core

+1 Thanks, John From: Douglas Mendizabal [douglas.mendiza...@rackspace.com] Sent: Thursday, July 10, 2014 11:55 AM To: OpenStack Development Mailing List (not for usage questions); a...@redhat.com Subject: [openstack-dev] [barbican] Nominating Ade Lee for

Re: [openstack-dev] [barbican] Nominating Nathan Reller for barbican-core

+1 Thanks, John From: Douglas Mendizabal [douglas.mendiza...@rackspace.com] Sent: Thursday, July 10, 2014 12:11 PM To: OpenStack Development Mailing List (not for usage questions); Nathan Reller Subject: [openstack-dev] [barbican] Nominating Nathan Reller f

Re: [openstack-dev] [Neutron][LBaaS] Shim vs Agent Refactor

Okay so after talking to Kyle, we've decided to forego creating a new version of the agent right away and just creating a new haproxy driver based off the namespace_driver, but it does not require the agent. This will speed up development and allow for TLS and L7 features to get in with a refer

Re: [openstack-dev] [nova] fastest way to run individual tests ?

On Jul 9, 2014, at 13:51, Matt Riedemann wrote: > I've been beating my head against the wall a bit on unit tests too this week, > and here is another tip that just uncovered something for me when python -m > testtools.run and nosetests didn't help. > > I sourced the tox virtualenv and then ran

[openstack-dev] [barbican] Nominating Ade Lee for barbican-core

+1 Thanks, Chad Lung http://giantflyingsaucer.com/blog/ @chadlung From: Douglas Mendizabal [douglas.mendizabal at RACKSPACE.COM ] Sent: Thursday, July 10, 2014 11:55 AM To: OpenStack Devel

[openstack-dev] [barbican] Nominating Nathan Reller for barbican-core

+1 Thanks, Chad Lung http://giantflyingsaucer.com/blog/ @chadlung From: Douglas Mendizabal [douglas.mendizabal at RACKSPACE.COM] Sent: Thursday, July 10, 2014 12:11 PM To: OpenStack Development Mailing List (not for usage questions); Nathan Reller Subjec

Re: [openstack-dev] [oslo] Asyncio and oslo.messaging

This is not supposed to be from 'Outlook', haha. Using my adjusted mail account so that its don't go to spam on the receiving end due to DMARC/DKIM issues... My fault ;) -Josh On Jul 10, 2014, at 12:51 PM, Outlook wrote: > On Jul 10, 2014, at 3:48 AM, Yuriy Taraday wrote: > >> On Wed, Jul

Re: [openstack-dev] [Neutron][LBaaS] Wednesday meeting agenda topics

I'm OK with essentially skipping the Wednesday video meetings until we're at a point that we're ready to concentrate on Octavia as a project. In previous video meetings there was a general sentiment that more could be accomplished (and faster) using video communications, while avoiding a lot of mi

Re: [openstack-dev] [Neutron][LBaaS] Shim vs Agent Refactor

Brandon, One key limitation of such a driver, is it will not work in installations where the Neutron server is installed across multiple nodes since the HAProxy network namespace will be created or updated on the node which received the Neutron API request. This will work for Devstack and testing

Re: [openstack-dev] [all] Treating notifications as a contract

-Original Message- From: Eoghan Glynn Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, July 10, 2014 at 3:30 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [all] Treating notifications as a cont

Re: [openstack-dev] [TripleO] pypi-mirror is now unsupported - what do we do now?

On 10 July 2014 23:27, Mulcahy, Stephen wrote: > When I last tested bandersnatch, it didn’t work well behind a proxy (in fact most of the existing pypi mirroring tools suffered from the same problem) – pypi-mirror has worked extremely well for mirroring a subset of pypi and doing so behind a proxy

Re: [openstack-dev] [heat] autoscaling across regions and availability zones

On 09/07/14 22:38, Mike Spreitzer wrote: Zane Bitter wrote on 07/01/2014 06:54:58 PM: > On 01/07/14 16:23, Mike Spreitzer wrote: > > An AWS autoscaling group can span multiple availability zones in one > > region. What is the thinking about how to get analogous functionality > > in OpenSta

Re: [openstack-dev] [all] Treating notifications as a contract

tl;dr: Having a minimum payload standard enables more and more robust services on both sides of notification bus. Expanded earnest optimism below. On Thu, 10 Jul 2014, Eoghan Glynn wrote: So it's the standardization of notification payload formats that's being proposed. Generally that payloa

[openstack-dev] [qa] Strange error in non-isolated periodic tests

I was trying to bring the periodic non-isolated jobs back to health. One problem with them is all the scenario tests fail with Captured traceback: 2014-06-26 07:00:42.312

Re: [openstack-dev] [nova] request to tag novaclient 2.18.0

Sorry for the delay here. This email got lost in my inbox while I was travelling. This release is now tagged. Additionally, I have created a milestone for this release in launchpad, which is the keystone process for client releases. This means that users of launchpad can now see what release a giv

Re: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin

On 10 July 2014 08:19, Czesnowicz, Przemyslaw < przemyslaw.czesnow...@intel.com> wrote: > Hi, > > > > Thanks for Your answers. > > > > Yep using binding:vif_details makes more sense. We would like to reuse > VIF_TYPE_OVS and modify the nova to use the userspace vhost when ‘use_dpdk’ > flag is pre

[openstack-dev] [glance] Bug Days - July 15/16

Hi All, Glance is going to have bug days next week on July Tuesday 15 and Wednesday 16. This is a two-days bug day to accommodate most of the Glance contributors (time zones, etc.). Of course, You do not need to be 100% two days… This is a great opportunity to: - triage bugs - fix bugs - tag bu

[openstack-dev] mid-cycle policy summit

The Congress team would like to get us policy people together to discuss how each project is approaching policy and our common future prior to the Paris summit. More details about the Congress can be found here https://wiki.openstack.org/wiki/Congress. I have discussed the idea with mestery and mi

Re: [openstack-dev] mid-cycle policy summit

I'm thinking location as yahoo Sunnyvale or VMware Palo Alto. ~sean > On Jul 10, 2014, at 5:12 PM, sean roberts wrote: > > The Congress team would like to get us policy people together to discuss how > each project is approaching policy and our common future prior to the Paris > summit. More

Re: [openstack-dev] [Neutron][LBaaS] Shim vs Agent Refactor

Dustin, Oh I understand that, but this is just an easy way to get a reference implementation in that can be used for testing newer features such as TLS and L7. Like I said before, sorry I keep course correcting on this but it's a very fluid process when there are so many unknowns. Thanks, Bra

Re: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin

+1 It's totally different between ovs and userspace ovs. also, there is strong need to keep ovs even we have a userspace ovs in the same host On Fri, Jul 11, 2014 at 7:59 AM, Ian Wells wrote: > On 10 July 2014 08:19, Czesnowicz, Przemyslaw < > przemyslaw.czesnow...@intel.com> wrote: > >> Hi,

Re: [openstack-dev] [glance] Bug Days - July 15/16

As for the bug tagging, I just added some tags in the wiki for Glance: https://wiki.openstack.org/wiki/Bug_Tags#Glance, please feel free to complete it. On 11/07/14 12:07, Arnaud Legendre wrote: > Hi All, > > Glance is going to have bug days next week on July Tuesday 15 and > Wednesday 16. This i

[openstack-dev] [keystone/swift] role-based access cotrol in swift

Hi, I looked for info about role-based access control in swift because I would like to prohibit PUT operations to containers like create containers and set ACLs. Other services like Nova, Cinder have "policy.json" file but Swift doesn't. And I found out the following info. - Swift ACL's migra

Re: [openstack-dev] [keystone/swift] role-based access cotrol in swift

There are a couple of places to look to see the current dev effort in Swift around ACLs. In no particular order: * Supporting a service token in Swift https://review.openstack.org/#/c/105228/ * Adding policy engine support to Swift https://review.openstack.org/#/c/89568/ * Fixing ACLs to work wi

[openstack-dev] [Infra] Jenkins gate jobs fails

Several jenkins gate jobs failed since some lib packages in ubuntu source are missing and devstack failed to setup the tempest env. Could there be someone help to fix this? I have filed the bug here: https://bugs.launchpad.net/openstack-ci/+bug/1340514 2014-07-11 02:35:42.333 | + apt_get install

Re: [openstack-dev] [Infra] Jenkins gate jobs fails

On Thu, Jul 10, 2014 at 10:12 PM, stanzgy wrote: > Several jenkins gate jobs failed since some lib packages in ubuntu source > are missing and devstack failed to setup the tempest env. Could there be > someone help to fix this? > I have filed the bug here: > https://bugs.launchpad.net/openstack-ci

[openstack-dev] [all] oslo.config 1.4.0.0a2 released

The Oslo team is pleased to announce the release of oslo.config 1.4.0.0a2, another pre-release in the 1.4.0 series for oslo.config during the Juno cycle: https://pypi.python.org/pypi/oslo.config/1.4.0.0a2 oslo.config provides an API which supports parsing command line arguments and .ini style c

<    1   2