On Aug 11, 2016, at 4:50 PM, John Dickinson <m...@not.mn> wrote: > Is this intended to be a cross-project thing? The message is tagged "[nova]", > so I'm kinda surprised I saw it, but the library seems to be called openstack > capabilities. So if this is going to be a big thing for everyone, please > update the ML subject tag (and help me understand how it applies to more than > just nova). And if it's just for nova (err... "compute"), then naming it > something that doesn't imply every project will need to use it could help > prevent future misunderstanding.
I will let Jay speak for himself (as if I could somehow prevent that!), but the intent here is that this won’t be for Nova specifically; it is targeted primarily for the forthcoming placement service (you might know it as the scheduler). The goal is to have a standard way of representing *qualitative* aspects of resources. So while we are not actively trying to make this a placement engine for all OpenStack services yet, the goal is to not be Nova-specific, so that once we have this up and running, we can offer it as a general placement service for any other project that has such needs. -- Ed Leafe __________________________________________________________________________ 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
