Code review comment for lp:~justin-fathomdb/openstack-manuals/doc-reserve-metadata-prefix

Right. This is a problem in AWS because they overload user metadata. I realize that as the code exists today this is also a problem for us. But if you read the "server affinity" thread on the mailing list the idea is to split user metadata into it's own table...separate from things like aws:cost-last-hour. So even if a user decides to use that as metadata with an aws prefix -- it's not a big deal -- there is no clash because things are in separate tables.

In the Open Stack Compute API you just separate things:

{
   "server" : {
       "id" : 1234,
       "name" : "sample-server",
       "aws-cost:cost-last-hour" : 2.25,
       "metadata" : {
           "values" : {
               "Server Label" : "Web Head 1",
               "Image Version" : "2.1",
        "aws:cost-last-hour" : "0.00?"
           }
       }
   }
}

In the EC2 implementation you can detect when a user uses the prefix and append something to it -- say aws-user. You can document that "feature" in the EC2 implementation.

The important thing to note is there is never a case where aws:cost-last-hour can be modified by user input -- because the data is simply stored in a different tables -- so we don't have to have that restriction at all.

-jOrGe W.

On Mar 3, 2011, at 5:22 PM, justinsb wrote:

> Jorge: My understanding is that AWS Tags map to OpenStack "Metadata" and vice versa.
>
> (AWS Tags documented here: http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/index.html?Using_Tags.html)
>
> Although OpenStack might prefer to expose e.g. "cost-last-hour" in a different way (e.g. extensions), this is just about not painting ourselves into a corner by not reserving the "aws:" prefix, in case AWS decides to expose it "their way".
>
>
>
>
> --
> https://code.launchpad.net/~justin-fathomdb/openstack-manuals/doc-reserve-metadata-prefix/+merge/51974
> You are requested to review the proposed merge of lp:~justin-fathomdb/openstack-manuals/doc-reserve-metadata-prefix into lp:openstack-manuals.

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 <email address hidden>, and delete the original message.
Your cooperation is appreciated.