openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #01126
Re: server affinity
Are we using the name metadata to describe a different feature than the one that exists in the CloudServers api?
It seems like a different feature for the user-properties metadata to have meaning to the api other than "store this information so I can read it later".
"Justin Santa Barbara" <justin@xxxxxxxxxxxx> said:
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
> 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@xxxxxxxxxxxxx>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@xxxxxxxxxxxxx, and delete the original message.
>> Your cooperation is appreciated.
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>
Follow ups
References
-
server affinity
From: Gabe Westmaas, 2011-02-28
-
Re: server affinity
From: Eric Day, 2011-02-28
-
Re: server affinity
From: Gabe Westmaas, 2011-02-28
-
Re: server affinity
From: Vishvananda Ishaya, 2011-02-28
-
Re: server affinity
From: Justin Santa Barbara, 2011-02-28
-
Re: server affinity
From: Brian Lamar, 2011-02-28
-
Re: server affinity
From: Jay Pipes, 2011-03-01
-
Re: server affinity
From: Jay Pipes, 2011-03-01
-
Re: server affinity
From: Mark Washenberger, 2011-03-01
-
Re: server affinity
From: Justin Santa Barbara, 2011-03-01