This is an interesting point. There is a definite disconnect with the level of services between networking and storage. In the network model, we are assigning IP addresses that are normally instantiated in the OS network stack, not the VM infrastructure per se. If the OS doesn't use IP, it uses ATM or IB, the IP address is valueless. However a MAC address, which we are not supporting at the moment, is more applicable and insulated from transport protocol implementations. . As functional equivalents in the storage world, an IP address would be on the same level as a controller/target/LUN (ctl). Unfortunately, VMs like to implant storage at dsk device, locating the storage much higher up the storage stack than IP address equivalence. I strongly believe that a source URI is required to identify the origin data storage. This is no different than defining an IP gateway. The spec does include extensible capabilities though linking, as very powerful feature. If a provider wants to include SNIA, native definitions or custom, it can easily be achieved. -gary Randy Bias wrote:
I do want to clarify that I think that eventually an extension to OCCI that allows integrating backends would be very useful. Like the ability to pass in an object store URL and specify that meta-data should be pulled from it, or an object should be stored onto a disk prior to initial bootup. Those would be very powerful possibilities.
Thanks,
--Randy
Randy Bias, Cloud Strategist +1 (415) 939-8507 [m], randyb@neotactics.com <mailto:randyb@neotactics.com> BLOG: http://cloudscaling.com
------------------------------------------------------------------------
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg