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 <d...@doughellmann.com> wrote: > > > >> My vote is the following: > >> > >> GET /capabilities <-- returns a set of *actions* or *abilities* that the > >> user is capable of performing > > > > Does this relate in any way to how DefCore already uses "capabilities”? > > Only a bit, and not in a way I’d be deeply concerned about. > > The Interoperability Working Group (née DefCore) points to a specific Tempest > test which asserts that a service has a “capability” and determines if that > capability is “core,” thus required to be provided in this way in order to > claim that the underlying cloud is an OpenStack cloud.
Do you think that the meanings of "capability of a cloud" and "capability of a user of a cloud" are far enough apart to avoid confusion? Doug __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
