OCCI in SSF

Posted December 13th, 2010 in Implementations by admin

Platform Computing developed an implementation of the OCCI protocol/API for the German Research Project DGSI. As part of the Service Sharing Facility (SSF) the occi module is an OCCI implementation written in Python.

Usage is as simple as just saying ‘import occi’ in your code. Since python is an interpreted language and can be easily bind to other programming languages like C/C++ or Java this implementation can be used for several purposes. The module can be installed by either downloading the source and run ‘python setup.py install’ or by running ‘easy_install pyssf’.

The implementation includes demos for Job Submission (SaaS/PaaS), a KeyValue store (PaaS) and of cause a skeleton implementation of the OCCI infrastructure model which only needs to be bound to your hyper-visor to create your IaaS based Cloud.

Features

  • OCCI compliant implementation in Python using as a WSGI application
  • Can be used by and device/programing language which is able to understand HTTP
  • In addition to the Renderings defined by the OCCI Specification is comes with an HTML rendering for easy monitoring using a Web-Browser
  • Easy to use – to give your applications a RESTful OCCI compliant interface (“RESTify your apps”)
  • Build upon Tornado Web for high-performance request handling
  • Multi-user ready, easy to integrate with OpenId service or similar authentication/authorization services (including transport via SSL)
  • Enables you to easily integrate several products, provide service interface to clients/customers, build your Cloud Service offerings
  • Focuses on Integration, Interoperability, Portability and Innovation

Resources

All work © 2010-2011 Platform Computing under LGPL License.

OCCI Implementations

Posted November 17th, 2010 in News by andy

Eucalyptus! OpenStack! LibVirt! Platform! OpenNebula! Apache Tashi!

The pace of development within the OCCI community has been excitedly ever increasing over the past few months. It’s not only been so within the group of people defining the specification but also in the many groups of people and projects implementing OCCI. In our last blog post we mentioned that Eucalyptus will soon have an implementation of OCCI from the good work David Wallom and his FleSSR team in Oxford are doing. In the post we also hinted at something related to OCCI and OpenStack.

As you might be aware, OpenStack is one of the most exciting and vibrant open source Cloud activities on going currently. The OCCI working group has been engaged with OpenStack over the past 3 months with the aim of contributing an implementation of OCCI and we’re happy to say that this will happen with the “Bexar” release of OpenStack. Incidentally, that’s synchronised with the release schedule of Ubuntu 11.04. the You can see the OCCI blueprint on the OpenStack site, which will serve a point of communication for the implementation work.

Not only will OpenStack receive an implementation of OCCI but one of the mainstays of infrastructure management frameworks, libvirt, will also have an implementation of OCCI. This work is being carried out by a team lead by one OCCI community member, Alexander Papaspyrou from TU Dortmund University, Germany.

Platform Computing will provide an OCCI implementation for a German Research Project, DGSI, which allows developers to easily extend their existing applications with an OCCI compliant RESTful interface (RESTify your apps).

Given that OCCI is also implemented in OpenNebula and Apache Tashi (via the SLA@SOI implementation) amongst others (we’re running out of space for this post!), OCCI is fast becoming the API that can provide interoperability between the major Open Source infrastructure management frameworks.

As ever, the OCCI group is always hugely enthusiastic, welcoming and very supportive to people and groups of all types wishing to get involved with OCCI, whether that is through specification contributions or new implementations of it. Curious? Then head on over to IRC (irc.freenode.net #occi), drop a mail on the mailing list or ping some of us on twitter (@dizz@befreax@monadic@papaspyrou).

Stay tuned for more news on OCCI and more implementations of it!