I think these additional/optional request parameters (aka metadata) should just be part of the context that is created when a command is issued and passed around for all services to use as needed.
So I guess that would be a vote for #2 -S ________________________________________ From: Jorge Williams [jorge.willi...@rackspace.com] Sent: Wednesday, March 02, 2011 8:40 AM Given that, I'm still a little fuzzy about whether we've reached a decision as to whether affinity id: 1) Should be part of the core Compute API 2) Should be a more general concept that may span different services, as Eric Day proposes 3) Should be introduced as an extension, which can later be promoted to the core...or not :-) 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 ab...@rackspace.com, and delete the original message. Your cooperation is appreciated. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
