Open Stack

On 3 Aug 2016, at 16:47, Jay Pipes wrote:

> Hi Novas and anyone interested in how to represent capabilities in a consistent fashion.
>
> I spent an hour creating a new os-capabilities Python library this evening:
>
> http://github.com/jaypipes/os-capabilities
>
> Please see the README for examples of how the library works and how I'm thinking of structuring these capability strings and symbols. I intend os-capabilities to be the place where the OpenStack community catalogs and collates standardized features for hardware, devices, networks, storage, hypervisors, etc.
>
> Let me know what you think about the structure of the library and whether you would be interested in owning additions to the library of constants in your area of expertise.
>
> Next steps for the library include:
>
> * Bringing in other top-level namespaces like disk: or net: and working with contributors to fill in the capability strings and symbols.
> * Adding constraints functionality to the library. For instance, building in information to the os-capabilities interface that would allow a set of capabilities to be cross-checked for set violations. As an example, a resource provider having DISK_GB inventory cannot have *both* the disk:ssd *and* the disk:hdd capability strings associated with it -- clearly the disk storage is either SSD or spinning disk.
>
> Anyway, lemme know your initial thoughts please.

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.

--john


>
> Best,
> -jay
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160811/da3f72f8/attachment.pgp>