Telefonica, the Spanish and Latin Telco giant, made an interesting announcement today. They are submitting their own API, based on vCloud 0.8 to the DMTF for standard consideration.
TCloud está basado en la especificación de API vCloud 0.8 publicado por VMWare. En esencia, se ha mantenido en TCloud la compatibilidad para las principales operaciones y tipos de datos contemplados en vCloud. Además, TCloud extiende y mejora las capacidades avanzadas para la gestión de cloud computing, que incluyen la provisión de elementos de red (con diferentes variantes para balanceadores de carga y firewalls), almacenamiento compartido para datos de servicio, monitorización, gestión de copias de seguridad, etc.
via www.networkworld.es
In a nutshell, they are extending the kinds of resources the vCloud API can ask for, such as firewalls, load balancers,shared storage, monitoring and security management.
This makes a lot of sense to me. But why stop there? Why not the actual workload? Middleware, database, Message queing, etc?
For one, that would be very complex. We do need that but probably not at the API level. We need something like the service definitions in SPACL.
This is what we are working on at newScale: The ability to define a multitude of things like server, storage, network, apps, stacks and interconnects that make up the widely distributed application environments of this and next decade. Once defined, these can be put under lifecycle management for provision, decommission and a multitude of changes. And do it on a self-service basis.
This is why I get into this kind of API announcement!
My question is: why is a Spanish behemoth feeling the need to do something? I think it speaks to the tremendous disruption that cloud computing represents in the managed hosting world. And also the tremendous opportunity if you are able to lock customers to your API.
So for me: good move Telefonica.
Recent Comments