Re: [openstack-dev] [Resend] [api] Who owns API versioning and deprecation policy?

Thanks. I’ll figure out which of my colleagues should get involved. Geoff > On Aug 21, 2015, at 2:10 PM, Everett Toews > wrote: > > On Aug 21, 2015, at 3:13 PM, Geoff Arnold wrote: > >> After reading the following pages, it’s unclear what the current API >> de

[openstack-dev] [Resend] [api] Who owns API versioning and deprecation policy?

After reading the following pages, it’s unclear what the current API deprecation policy is and who owns it. (The first spec implies that a change took place in May 2015, but is silent on what and why.) Any hints? An authoritative doc would be useful, something other than an IRC log or mailing l

[openstack-dev] [Mercador] Meeting this week

The Mercador meeting this week will be a break-out from the Keystone sprint (as well as on IRC). See https://wiki.openstack.org/wiki/Meetings/MercadorTeamMeeting Geoff

Re: [openstack-dev] [Product] Product WG considering holding a mid-cycle sprint

OK, let’s try again. Anyone who is interested in participating in a Product WG sprint, please complete this Doodle poll: https://doodle.com/sskuwycqfa3vhu9e Thanks, Geoff > On Jun 29, 2015, at 6:34 PM, Geoff Arnold wrote: > > My apologies: I seem to have triggered a bug in Do

Re: [openstack-dev] [Product] Product WG considering holding a mid-cycle sprint

My apologies: I seem to have triggered a bug in Doodle. The support staff are on the case; I’ll update you when I have more information. > On Jun 29, 2015, at 5:33 PM, Geoff Arnold wrote: > > [Note: I’m copying this to openstack-dev in case there are potential > participants who

[openstack-dev] [Product] Product WG considering holding a mid-cycle sprint

[Note: I’m copying this to openstack-dev in case there are potential participants who have not yet joined the product-wg list.] The OpenStack Product WG is considering whether to hold a 2-day mid-cycle sprint to accelerate its work. We understand that scheduling during the summer is difficult,

[openstack-dev] [mercador] Meeting schedule

My apologies for the delay in getting things set up. The weekly meeting for the Mercador project will be held each Friday at 1700 UTC. The first meeting will be this Friday, June 26. The meetings will take place on IRC in #openstack-meeting. The agenda will be tracked at https://wiki.openstac

[openstack-dev] Liberty mid-cycle meetups?

I’ve been trying to pull together a list of Liberty mid-cycle meetups from emails, Etherpads, wikis, etc. Many of the usual suspects are missing. Can we use this thread to gather the full list? (Alternatively, if there’s an authoritative source that I’ve missed, please share the link.) What I h

[openstack-dev] UPDATED: [new][mercador] Announcing Mercador, a project to federate OpenStack cloud services.

Geoff Arnold David Cheperdak Orran Krieger Raildo Mascena For more details, check out our Wiki: https://wiki.openstack.org/wiki/Mercador In anticipation of a lively debate, I’m appending an FAQ [2] Regards, Geoff Arnold -- [1] https://github.com/openstack-dev/cookiecutter [2] FAQ Q. What exact

[openstack-dev] [new][mercador] Announcing Mercador, a project to federate OpenStack cloud services.

am includes: Geoff Arnold (Cisco) David Cheperdak (Cisco) Orran Krieger (MOC) For more details, check out our Wiki: https://wiki.openstack.org/wiki/Mercador <https://wiki.openstack.org/wiki/Mercador> However, in view of the lively debates which have followed recent project announcements,

Re: [openstack-dev] [Keystone] Midcycle planning

Yes please. I’ll be making private accommodation requirements. I have family in the area. Geoff > On May 30, 2015, at 9:28 AM, Adam Young wrote: > > Now that we are through the summit, it is time to plan the Midcycle. We have > had a consensus that the Keystone Midcycle would be in Boston th

Re: [openstack-dev] [horizon][keystone][heat] Are "AVAILABLE_REGIONS" and multi-region service catalog mutually exclusive?

If we don’t want to deprecate AVAILABLE_REGIONS, we certainly need to clean up the ambiguity. And to be honest, the existing documentation for both "multi-region” schemes (AVAILABLE_REGIONS and Keystone based) is completely inadequate. Geoff > On May 14, 2015, at 1:13 PM, Mathieu Gagné wrote

Re: [openstack-dev] [horizon][keystone][heat] Are "AVAILABLE_REGIONS" and multi-region service catalog mutually exclusive?

+1 A wiki page laying out a mutually agreeable taxonomy seems like a good starting point. Geoff > On May 14, 2015, at 7:47 AM, Anne Gentle > wrote: > > > > On Thu, May 14, 2015 at 9:39 AM, Geoff Arnold <mailto:ge...@geoffarnold.com>> wrote: > +1 >

Re: [openstack-dev] [horizon][keystone][heat] Are "AVAILABLE_REGIONS" and multi-region service catalog mutually exclusive?

. [citation needed] Puzzled. Geoff > On May 14, 2015, at 7:56 AM, Zane Bitter wrote: > > On 14/05/15 10:39, Geoff Arnold wrote: >> +1 >> >> There seems to be a significant disconnect between Heat, Horizon and >> Keystone on the subject of multi-region configuration

Re: [openstack-dev] [horizon][keystone][heat] Are "AVAILABLE_REGIONS" and multi-region service catalog mutually exclusive?

his means you can configure an >> Horizon installation to login to multiple independent OpenStack >> installations. >> >> So I don't fully understand what "enhancing the multi-region support in >> Keystone" would mean. Would you be able to configure Horizon t

Re: [openstack-dev] [horizon][keystone][heat] Are "AVAILABLE_REGIONS" and multi-region service catalog mutually exclusive?

multi-region Heat. Thoughts? Geoff > On May 13, 2015, at 12:01 PM, Geoff Arnold wrote: > > I’m looking at implementing dynamically-configured multi-region support for > service federation, and the prior art on multi-region support in Horizon is > pretty sketchy

[openstack-dev] [horizon][keystone][heat] Are "AVAILABLE_REGIONS" and multi-region service catalog mutually exclusive?

I’m looking at implementing dynamically-configured multi-region support for service federation, and the prior art on multi-region support in Horizon is pretty sketchy. This thread: http://lists.openstack.org/pipermail/openstack/2014-January/004372.html is the only real discussion I’ve found, and

[openstack-dev] [all] Why the Cloud Service Federation project is a good subject for the Cross-project track.

tl;dr I’d like to use a slot in the cross-project track to discuss the best way of managing cross-project, multi-cycle initiatives, using the forthcoming Cloud Service Federation (Broker) project to make it concrete rather than theoretical. Desired outcome: recommendations to Product group, vert

Re: [openstack-dev] [Keystone][Glance] Hierarchical multitenancy and Glance?

unchpad.net/cinder/+spec/cinder-nested-quota-driver > <https://blueprints.launchpad.net/cinder/+spec/cinder-nested-quota-driver>) > > Tim > > From: Geoff Arnold [mailto:ge...@geoffarnold.com] > Sent: 28 April 2015 08:11 > To: OpenStack Development Mailing L

Re: [openstack-dev] [Keystone][Glance] Hierarchical multitenancy and Glance?

ion of domains / vs > hierarchical projects? Is there a wiki or something that highlights what > the desired path forward is with regard to domains? > > Thanks, > Travis > > On 4/27/15, 7:16 PM, "Geoff Arnold" wrote: > >> Good points. I¹ll add some detail

Re: [openstack-dev] [Keystone][Glance] Hierarchical multitenancy and Glance?

Good points. I’ll add some details. I’m sure the Reseller guys will have some comments. Geoff > On Apr 27, 2015, at 3:32 PM, Nikhil Komawar > wrote: > > Thanks Geoff. Added some notes and questions. > > -Nikhil > > ________ >

[openstack-dev] [Keystone][Glance] Hierarchical multitenancy and Glance?

In preparation for Vancouver, I’ve been looking for blueprints and design summit discussions involving the application of the Keystone hierarchical multitenancy work to other OpenStack projects. One obvious candidate is Glance, where, for example, we might want domain-local resource visibility a

Re: [openstack-dev] [all] Introducing the Cloud Service Federation project (cross-project design summit proposal)

egion" metadata schema that will allow a tenant (or a broker) to determine the characteristics of virtual regions. (Such a model might be a useful complement to the RefStack work.) Geoff > On Apr 16, 2015, at 3:00 PM, Joe Gordon wrote: > > > > On Thu, Apr 16, 2015 at 12:16 AM,

Re: [openstack-dev] [all] Introducing the Cloud Service Federation project (cross-project design summit proposal)

he review process of the general keystone > contributors, thus > getting a more robust code. > > > Best regards, > Miguel > >> On 16/4/2015, at 6:24, Geoff Arnold > <mailto:ge...@geoffarnold.com>> wrote: >> >> Yeah, we’ve taken account o

Re: [openstack-dev] [all] Introducing the Cloud Service Federation project (cross-project design summit proposal)

. (The Cisco term “Intercloud” is accurate, but probably inappropriate!) Geoff > On Apr 15, 2015, at 7:07 PM, Adam Young wrote: > > On 04/15/2015 04:23 PM, Geoff Arnold wrote: >> That’s the basic idea. Now, if you’re a reseller of cloud services, you >> deploy Horizon+Aggregat

Re: [openstack-dev] [all] Introducing the Cloud Service Federation project (cross-project design summit proposal)

emote keystone and generate project scoped tokens, though you'd need > project+region scoped tokens, which I'm not sure exists today? > > Thanks, > Kevin > > ____ > From: Geoff Arnold [ge...@geoffarnold.com] > Sent: Wednesday

[openstack-dev] [all] Introducing the Cloud Service Federation project (cross-project design summit proposal)

identify unexpected dependencies as soon as possible. For this reason, we’d like to discuss it in Vancouver as part of the cross-project track in the Design Summit. Geoff Arnold Cisco Cloud Services geoff(at)geoffarnold.com geoarnol(at)cisco.com @geoffarnold

Re: [openstack-dev] [all] Design Summit - Cross-project track - Session suggestions

Thanks Thierry. I really like the Google Docs form to submit new proposals. Now if someone could please fix the form so that the Topic fields in new entries are word-wrapped correctly… ;-) Geoff > On Apr 9, 2015, at 7:33 AM, Thierry Carrez wrote: > > Hi everyone, > > If you have ideas for

Re: [openstack-dev] [Keystone][FFE] - Reseller Implementation

by resource consumption policies (e.g. Nova AZ “foo” is not available to customers of reseller “bar”). I strongly doubt that any of this is particularly original, but I haven’t seen it written up anywhere. Cheers, Geoff Arnold Cisco Cloud Services geoar...@cisco.com <mailto:geoar..

Re: [openstack-dev] [TripleO] Meetup Reminder

Clint: do you have a more precise agenda for the meetup? I like what Morgan’s proposing for the Keystone midcycle next week: Day 1: architecture and requirements Day 2: detail design work Day 3: hackathon Cheers, Geoff > On Jan 4, 2015, at 12:55 PM, Clint Byrum wrote: > > Happy New Year! > >

Re: [openstack-dev] [Neutron][LBaaS] Neutron LBaaS, Libra and "managed services"

There are (at least) two ways of expressing differentiation: - through an API extension, visible to the tenant - though an internal policy mechanism, with specific policies inferred from tenant or network characteristics Both have their place. Please don't fall into the trap of thinking that dif

Re: [openstack-dev] [Neutron] L3 router service integration with Service Type Framework

I’m getting a “Not allowed here” error when I click through to the BP. (Yes, I’m subscribed.) On Oct 24, 2013, at 11:56 AM, Gary Duan wrote: > Hi, > > I've registered a BP for L3 router service integration with service framework. > > https://blueprints.launchpad.net/neutron/+spec/l3-router-se