On 08/25/2016 07:52 PM, Andrew Laski wrote:
> On Thu, Aug 25, 2016, at 12:22 PM, Everett Toews wrote:
>> Top posting with general comment...
>>
>> It sounds like there's some consensus in Nova-land around these
>> traits (née "capabilities"). The API Working Group [4] is
>> also aware of similar
On Thu, Aug 25, 2016, at 12:22 PM, Everett Toews wrote:
> Top posting with general comment...
>
> It sounds like there's some consensus in Nova-land around these traits
> (née "capabilities"). The API Working Group [4] is
> also aware of similar efforts in Cinder [1][2] and Glance [3].
To be
Top posting with general comment...
It sounds like there's some consensus in Nova-land around these traits (née
"capabilities"). The API Working Group [4] is also aware of similar efforts in
Cinder [1][2] and Glance [3].
If these are truly the same concepts being discussed across projects, it
Le 15/08/2016 22:59, Andrew Laski a écrit :
On Mon, Aug 15, 2016, at 10:33 AM, Jay Pipes wrote:
On 08/15/2016 09:27 AM, Andrew Laski wrote:
Currently in Nova we're discussion adding a "capabilities" API to expose
to users what actions they're allowed to take, and having compute hosts
expose
> On Aug 15, 2016, at 10:49 AM, Doug Hellmann wrote:
>
> Excerpts from Jim Meyer's message of 2016-08-15 09:37:36 -0700:
>> A fast reply where others will expand further (I hope):
>>
>>> On Aug 15, 2016, at 9:01 AM, Doug Hellmann wrote:
>>>
On Mon, Aug 15, 2016, at 10:33 AM, Jay Pipes wrote:
> On 08/15/2016 09:27 AM, Andrew Laski wrote:
> > Currently in Nova we're discussion adding a "capabilities" API to expose
> > to users what actions they're allowed to take, and having compute hosts
> > expose "capabilities" for use by the
Excerpts from Jim Meyer's message of 2016-08-15 09:37:36 -0700:
> A fast reply where others will expand further (I hope):
>
> > On Aug 15, 2016, at 9:01 AM, Doug Hellmann wrote:
> >
> >> My vote is the following:
> >>
> >> GET /capabilities <-- returns a set of *actions*
A fast reply where others will expand further (I hope):
> On Aug 15, 2016, at 9:01 AM, Doug Hellmann wrote:
>
>> My vote is the following:
>>
>> GET /capabilities <-- returns a set of *actions* or *abilities* that the
>> user is capable of performing
>
> Does this
On 08/15/2016 12:01 PM, Doug Hellmann wrote:
Excerpts from Jay Pipes's message of 2016-08-15 10:33:49 -0400:
On 08/15/2016 09:27 AM, Andrew Laski wrote:
Currently in Nova we're discussion adding a "capabilities" API to expose
to users what actions they're allowed to take, and having compute
Excerpts from Jay Pipes's message of 2016-08-15 10:33:49 -0400:
> On 08/15/2016 09:27 AM, Andrew Laski wrote:
> > Currently in Nova we're discussion adding a "capabilities" API to expose
> > to users what actions they're allowed to take, and having compute hosts
> > expose "capabilities" for use
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Monday, August 15, 2016 3:34 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Nova][API] Need naming suggestions for
> "capabilities"
>
> On 08/15
On 08/15/2016 10:50 AM, Dean Troyer wrote:
On Mon, Aug 15, 2016 at 9:33 AM, Jay Pipes > wrote:
On 08/15/2016 09:27 AM, Andrew Laski wrote:
After some thought, I think I've changed my mind on referring to
the adjectives as
On Mon, Aug 15, 2016 at 9:33 AM, Jay Pipes wrote:
> On 08/15/2016 09:27 AM, Andrew Laski wrote:
>
>> After some thought, I think I've changed my mind on referring to the
>> adjectives as "capabilities" and actually think that the term
>> "capabilities" is better left for the
On Mon, Aug 15, 2016 at 8:27 AM, Andrew Laski wrote:
> An API "capability" is going to be an action, or URL, that a user is
> allowed to use. So "boot an instance" or "resize this instance" are
> capabilities from the API point of view. Whether or not a user has this
>
On 08/15/2016 09:27 AM, Andrew Laski wrote:
Currently in Nova we're discussion adding a "capabilities" API to expose
to users what actions they're allowed to take, and having compute hosts
expose "capabilities" for use by the scheduler. As much fun as it would
be to have the same term mean two
Currently in Nova we're discussion adding a "capabilities" API to expose
to users what actions they're allowed to take, and having compute hosts
expose "capabilities" for use by the scheduler. As much fun as it would
be to have the same term mean two very different things in Nova to
retain some
16 matches
Mail list logo