[openstack-dev] [Neutron][Dragonflow] IRC Meeting tommorrow (1/2) - 0900 UTC (#openstack-meeting-4)

Hello All, We will have an IRC meeting tomorrow (Monday, 1/2) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow We are going to have a busy meeting, many new specs/design, i have put the links to all specs in t

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

On 01/30/2016 01:25 PM, Julien Danjou wrote: On Sat, Jan 30 2016, Sylvain Bauza wrote: I suggest you look how to revert an RPC API change by thinking of our continuous deployers, you might discover something interesting there. :) This is an interesting thought indeed. If you consider every co

[openstack-dev] [keystone][nova][cinder][horizon] Projects acting as a domain at the top of the project hierarchy

Hi One of the things the keystone team was planning to merge ahead of milestone-3 of Mitaka, was “projects acting as a domain”. Up until now, domains in keystone have been stored totally separately from projects, even though all projects must be owned by a domain (even tenants created via the k

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

Hi Preston, No need to apologize. They are aspect of the same problem. However, VMs backup is one of the many aspects that we are approaching here, such as: - VM backups - Volumes backups - Specific applications consistent data backup (i.e. MySQL, Mongo, file system, etc) - Provide capabilities to

Re: [openstack-dev] [keystone][cross-project] Standardized role names and policy

> On 30 Jan 2016, at 21:55, Adam Young > wrote: > > On 01/30/2016 04:14 PM, Henry Nash wrote: >> Hi Adam, >> >> Fully support this kind of approach. >> >> I am still concerned over the scope check, since we do have examples of when >> there is more than one (target)

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

Seems to me there are three threads here. The Freezer folk were given a task, and did the best possible to support backup given what OpenStack allowed. To date, OpenStack is simply not very good at supporting backup as a service. (Apologies to the Freezer folk if I misinterpreted.) The patches (f

Re: [openstack-dev] [neutron] documenting configuration option segregation between services and agents

Propose it as a devref patch! On Wed, Jan 27, 2016 at 12:30 PM, Dustin Lundquist wrote: > We should expand services_and_agents devref to describe how and why > configuration options should be segregated between services and agents. I > stumbled into this recently while trying to remove a confusi

Re: [openstack-dev] [api] service type vs. project name for use in headers

On 10:55 Jan 28, Kevin L. Mitchell wrote: > On Thu, 2016-01-28 at 11:06 +, Chris Dent wrote: > > I think it is high time we resolve the question of whether the > > api-wg guidelines are evaluating existing behaviors in OpenStack and > > blessing the best or providing aspirational guidelines of

Re: [openstack-dev] [keystone][cross-project] Standardized role names and policy

On 01/30/2016 04:14 PM, Henry Nash wrote: Hi Adam, Fully support this kind of approach. I am still concerned over the scope check, since we do have examples of when there is more than one (target) scope check, e.g.: an API that might operate on an object that maybe global, domain or project s

[openstack-dev] Team meeting this Tuesday at 1400 UTC

Hi neutrinos, According to [1], this is a kind reminder for next week's meeting: please do not get caught by the confusion. The Tuesday meetings will be hosted by Ihar, and I will be working with him to discuss these meeting agendas [2] ahead of time. For this reason, stay tuned for reminder upda

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

On Sat, Jan 30 2016, Sylvain Bauza wrote: > I suggest you look how to revert an RPC API change by thinking of our > continuous deployers, you might discover something interesting there. > :) This is an interesting thought indeed. If you consider every commit to be releasable so then deploy-able,

Re: [openstack-dev] [keystone][cross-project] Standardized role names and policy

Hi Adam, Fully support this kind of approach. I am still concerned over the scope check, since we do have examples of when there is more than one (target) scope check, e.g.: an API that might operate on an object that maybe global, domain or project specific - in which case you need to “match

Re: [openstack-dev] [Cinder] Nominating Patrick East to Cinder Core

+1. Patrick's contributions to Cinder have been notable since he joined us and he is a pleasure to work with! Welcome to the core team Patrick! Jay On Fri, Jan 29, 2016, 19:05 Sean McGinnis wrote: > Patrick has been a strong contributor to Cinder over the last few > releases, both with great

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Using nova interface extension instead of networks extension

Yeah our public cloud does not support that call. We actually have a different endpoint that is almost just like the os-interfaces one! Except the openstack nova client doesn't know about it, of course. If for the time being we can temporarily support the os-networks way as a fall back method if

[openstack-dev] Upstream University: Signup for Mentors and Mentees

Hello all! I'm trying to gather how much interest there is do an Upstream University at the Austin summit as we've done at the summits since Paris. Here's an excerpt from the training guides about the program [1]: We've designed a training program to help professional developers negotiate this hu

[openstack-dev] [keystone][cross-project] Standardized role names and policy

I'd like to bring people's attention to a Cross Project spec that has the potential to really strengthen the security story for OpenStack in a scalable way. "A common policy scenario across all projects" https://review.openstack.org/#/c/245629/ The summary version is: Role name or pattern

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

Sylvain, Let's agree to disagree. This works for Oslo, so lets leave it at that. Also, *please* switch Subject as this is not fair to Alexis's nomination if you wish to continue. -- Dims On Sat, Jan 30, 2016 at 6:55 AM, Sylvain Bauza wrote: > > Le 30 janv. 2016 09:32, "Julien Danjou" a écrit

Re: [openstack-dev] [cinder] Testing Cinder upgrades - c-bak upgrade

On 29 Jan 2016 19:37, "Michał Dulko" wrote: > > Resolution on this matter from the Cinder mid-cycle is that we're fine > as long as we safely fail in case of upgrade conducted in an improper > order. And it seems we can implement that in a simple way by raising an > exception from volume.rpcapi w

Re: [openstack-dev] [Cinder] Nominating Patrick East to Cinder Core

+1 He's been doing great work, and is a pleasure to work with. On 29 Jan 2016 19:05, "Sean McGinnis" wrote: > Patrick has been a strong contributor to Cinder over the last few > releases, both with great code submissions and useful reviews. He also > participates regularly on IRC helping answer

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

Le 30 janv. 2016 09:32, "Julien Danjou" a écrit : > > On Fri, Jan 29 2016, Sylvain Bauza wrote: > > > While my heart is about that, my brain thinks about some regressions could > > be happening because of a +W even for a small change. > > I suggest you read the git-revert manpage then, you might d

Re: [openstack-dev] [stable][ceilometer][all] stable/kilo 2015.1.3 delayed

On 29 January 2016 at 20:36, Jeremy Stanley wrote: > On 2016-01-29 19:34:01 + (+), gordon chung wrote: >> hmm.. that's unfortunate... anything we need to update so this doesn't >> happen again? or just a matter of lesson learned, let's keep an eye out >> next time? > > Well, I backported t

Re: [openstack-dev] [stable][ceilometer][all] stable/kilo 2015.1.3 delayed

On 29 January 2016 at 19:34, gordon chung wrote: > > hmm.. that's unfortunate... anything we need to update so this doesn't > happen again? or just a matter of lesson learned, let's keep an eye out > next time? > > i guess the question is can users wait (a month?) for next release? i'm > willing

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/trove failed

This (likely) relates to a change made on master. I'm looking into it. -amrith -- Amrith Kumar, CTO | amr...@tesora.com Tesora, Inc | @amrithkumar 125 CambridgePark Drive, Suite 400 | http://www.tesora.com Cambridge, MA. 02140| GPG: 0x5e4

Re: [openstack-dev] [Horizon] Recent integration tests failures

Problematic Selenium versions have been successfully excluded from Horizon test-requirements, if you still experiencing the error described above, rebase your patch onto the latest master. On Fri, 29 Jan 2016 at 12:36, Itxaka Serrano Garcia wrote: > Can confirm, had the same issue locally, was fi

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

On Fri, Jan 29 2016, Sylvain Bauza wrote: > While my heart is about that, my brain thinks about some regressions could > be happening because of a +W even for a small change. I suggest you read the git-revert manpage then, you might discover something interesting there. :) The "shit happened" (e