On 25/05/17 07:47, Lance Bragstad wrote:
> *Option 2*
>
> Implement global role assignments in keystone.
> /
> /
> /How it works:/
> /
> /
> Role assignments in keystone can be scoped to global context. Users
> can then ask for a globally scoped token
>
> Pros:
> - This approach represents a mo
I'd like to fill in a little more context here. I see three options with
the current two proposals.
*Option 1*
Use a special admin project to denote elevated privileges. For those
unfamiliar with the approach, it would rely on every deployment having an
"admin" project defined in configuration [0
The Mailman listserv on lists.openstack.org will be offline for an
archive-related maintenance for up to an hour starting at 20:00 UTC
May 26, this coming Friday. This activity is scheduled for a
relatively low-volume period across our lists; during this time,
most messages bound for the server wil
On 5/24/2017 10:05 AM, Mathieu Gagné wrote:
* There a multiple supported config drive versions (2012-08-10, ...,
2017-02-22) so we need to document them all.
Yeah, but there are a lot of microversions in the compute REST API too
and we document each one - it's just easier since we made it a
Matt Riedemann wrote:
Rocky tipped me off to a request to document config drive which came up
at the Boston Forum, and I tracked that down to Clark's wishlist
etherpad [1] (L195) which states:
"Document the config drive. The only way I have been able to figure out
how to make a config drive is b
Hey all,
To date we have two proposed solutions for tackling the admin-ness issue we
have across the services. One builds on the existing scope concepts by
scoping to an admin project [0]. The other introduces global role
assignments [1] as a way to denote elevated privileges.
I'd like to get som
On 05/22/2017 01:55 PM, Jay Pipes wrote:
On 05/22/2017 03:53 PM, Jonathan Proulx wrote:
To be clear on my view of the whole proposal
most of my Rescheduling that I've seen and want are of type "A" where
claim exceeds resources. At least I think they are type "A" and not
"C" unknown.
The exact
On May 23, 2017, at 3:15 PM, melanie witt wrote:
>
> Removing the small VM driver from Nova would allow people to keep using what
> they know (Nova API) but would keep a lot of cruft with it. So I would tend
> to favor a new porcelain API.
This.
-- Ed Leafe
_
On Wed, May 24, 2017, at 07:39 AM, Matt Riedemann wrote:
> Rocky tipped me off to a request to document config drive which came up
> at the Boston Forum, and I tracked that down to Clark's wishlist
> etherpad [1] (L195) which states:
>
> "Document the config drive. The only way I have been abl
On Wed, May 24, 2017 at 10:39 AM, Matt Riedemann
wrote:
>
> Rocky tipped me off to a request to document config drive which came up
at the Boston Forum, and I tracked that down to Clark's wishlist etherpad
[1] (L195) which states:
>
> "Document the config drive. The only way I have been able to fi
Rocky tipped me off to a request to document config drive which came up
at the Boston Forum, and I tracked that down to Clark's wishlist
etherpad [1] (L195) which states:
"Document the config drive. The only way I have been able to figure out
how to make a config drive is by either reading nov
On 5/10/2017 1:29 PM, Mike Dorman wrote:
After discussion in the Large Deployments Team session this morning, we
wanted to follow up on the earlier thread [1,2] about overriding
endpoint URLs.
That topic is exposing an underlying implication about the purpose of
the service catalog. The LDT
Dear Ops,
fyi. please chime in.
Thanks,
Dims
-- Forwarded message --
From: Davanum Srinivas
Date: Wed, May 24, 2017 at 6:11 AM
Subject: [tc][all] Etcd as a base service for ALL OpenStack installations
To: "OpenStack Development Mailing List (not for usage questions)"
Team,
H
13 matches
Mail list logo
