On Wed, Jan 20, 2010 at 1:38 PM, Brian Stevens
<bstevens@redhat.com> wrote:
Masking irrelevant differences is a key goal for the API, enabling developers to write once and interact
with many clouds. At the same time, exposing differentiating behaviour, or methods which cannot be
masked via capability discovery is also important. File injection is perhaps somewhere in the middle.
b
Right - so "masking" - how far do we go to mask something my emulating it in some driver code etc?
Would be nice is one day be able to go to
aws.amazon.com/deltacloud and
rackspacecloud.com/deltacloud and
rimuhosting.com/deltacloud etc and see (modulo api version) enough to get going with. In that case using the discovery stuff would be nice. But in the case of me (as a user) running deltacloud impl locally to provide me with interop - I would be happier to let it emulate for me (perhaps... just thinking aloud of the different ways people will use this).