On Fri, 2017-03-03 at 17:12 +0000, Chris Dent wrote: <snip>
> > # Capabilities Discovery > > https://etherpad.openstack.org/p/capabilities-pike > > This began as an effort to refine a proposed guideline for > expressing what a cloud can do: > > https://review.openstack.org/#/c/386555/ > > That was modeled as what a cloud can do, what a type of resource in > that cloud can do, and what this specific instance of this resource > can do. > > Discussion was wide ranging but eventually diverged into two > separate directions: > > * Expressing cloud-level capabilities (e.g., does this cloud do floating > ips) at either the deployment or service level. The use of the > URL /capabilities is in the original spec, but since swift already > provides an implementation of an idea like this at /info we should > go with that. It's not clear what the next steps with this are, > other than to iterate the spec. We need volunteers to work on at > least reviewing that, and perhaps picking up the authorship. Unfortunately I won't be able to dedicate time to the spec in nearest timeframe. Anyone can feel free to grab it and update it with PTG's decisions. > > > * Satisfying the use case that prompted the generic idea above: > Making the right buttons show up in dashboards like horizon that > indicate whether or not an instance can be snapshotted and other > similar features. > > The next steps on that latter direction are to modify the server > info representation in the compute api to include a new key which > answers the top 5 questions that horizon wants to be able to answer. > Once we see how well that's working, move on. > __________________________________________________________________________ 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