Open Stack

We decided in the merge to call it Metadata, despite being fully aware of
the semantic issues, because that's what the CloudServers / OpenStack API
uses.

There are many better terms, but for the sake of avoiding a Tower of Babel,
let's just call it Metadata.



On Tue, Mar 1, 2011 at 6:56 AM, Sandy Walsh <sandy.walsh at rackspace.com>wrote:

> Was just speaking with dabo about this and we agree that metadata is a bad
> name for this capability.
>
> I don't really care about what we call it, but metadata has some
> preconceived notions/meanings. Perhaps Criteria?
>
> Currently we have *some* criteria for creating a new instance on the
> Openstack API side: flavors and operating system. But I think the OS API
> payload allows for additional "criteria" to be passed in with the request
> (not sure).
>
> Eventually all this stuff will have to make it to the Scheduler for
> Server-Best-Match/Zone-Best-Match. That's somewhere on our task list for
> Cactus :/
>
> $0.02
>
> -S
>
>
>
>
>
>
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of
> the
> individual or entity to which this message is addressed, and unless
> otherwise
> expressly indicated, is confidential and privileged information of
> Rackspace.
> Any dissemination, distribution or copying of the enclosed material is
> prohibited.
> If you receive this transmission in error, please notify us immediately by
> e-mail
> at abuse at rackspace.com, and delete the original message.
> Your cooperation is appreciated.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20110301/11da735d/attachment.html>