Telefónica I+D is proud to announce the first release of its OCCI Java implementation.

 After UCM’s efforts to provide the first fully-compliant OCCI server attached to OpenNebula, we release here a second OCCI implementation (Java REST client + server).

This is the result of privately-funded efforts as well as  FP7 European Research projects  (co-funded by Telefónica and the European Commission) such as RESERVOIR.

 Affero GPL has been the chosen license for this OCCI implementation. Comments, critique and feedback are most welcome through our support pages.

 Thanks a lot!!

We are witnessing a new technology race about the definition  APIs to access to IaaS Cloud services. With this post series, we would like to start a review series of the most relevant specifications trying to to analyse their status outstanding aspects  of them.

We are starting this analysis with two initiatives that follows different specification models: VMware’s vCloud in a vendor-driven model (aiming to be the “de facto” standard), and OGF’s OCCI in a open standardization body-driven model.

vCloud is an initiative led by VMware and counts with the collaboration of more than 100 partner including  BT, Rackspace, SAVVIS, Sungard, T-Systems and Verizon Business. The main aim of vCloud is to provide a complete solution to deliver enterprise cloud services based on VMware technologies. The vCloud API will allow application providers to deploy their application among a cloud service provided by one of the vCloud partners.

The OGF’s OCCI (Open Cloud Computing Initiative) Working Group is aiming to deliver an API specification for remote management of cloud computing IaaS.  The proliferation of IaaS providers with their own APIs (Amazon AWS, GoGrid, Flexiscale, …) requires an standardization effort on defining an common API to avoid vendor-locking and to guarantee interoperability.