The EU funded projects EGI-Engage and INDIGO-Datacloud have come up with an OCCI interface leveraging the public OpenStack APIs: ooi
An interesting article (by @cloudpundit) from Gartner: Don’t Let OpenStack Hype Distort Your Selection of a Cloud Management Platform in 2012. The recommendations are not specific for OpenStack. The following table form the exact same article gives a nice impression of Garnter’s recommendations:
The second recommendation is probably most interesting: ‘Use a 3rd party cloud API library […]’ – Why not even go for an Open Community Standard Driven Cloud API? OCCI for OpenStack is the answer and an implementation deployed on the EGI FedCloud.
The OCCI working group and the OpenStack team are working together to deliver an OCCI implementation in OpenStack. The implementation blueprint can be found at the OpenStack nova blueprints site. The latest implementation can be found on github.
For more information please visit: http://wiki.openstack.org/occi
We blogged previously about the availability of an OCCI implementation for OpenStack. Below is a screen cast that demonstrates some, not all, of the functionality available.
Hot on the heels of the OCCI OpenStack implementation (wiki, code review) a number of our community members (big thanks to Eugene from R2AD) will be organising an OpenStack Design Summit unconference OCCI session. All are welcome to it from the inquisitive to the sceptical!
Topics to be discussed include:
- What is OCCI and its goals?
- Where does OCCI fit the OpenStack picture?
- How should OpenStack address “extra” APIs?
OpenStack is one of the major players in the cloud community at the moment. Still it currently lacks an standardized Interface which can be used to manage VMs. This changes now! During the Cloud Plugfest OCCI has been demoed on top of OpenStack.
Andy Edmonds presented the following slides during the Cloud Plugfest in Düsseldorf which highlight more details of the OCCI interface for OpenStack
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!
So yes we’ve been quiet but as they say “still waters run deep”. We in OCCI have been deep and active on everything from refining the Core model down through the infrastructure specification and out through the HTTP rendering specification document and, well, things couldn’t be healthier! Following an superb half-week at OGF30 there’s even more great OCCI-related news to share. Coming into OGF30, I was aware of seven OCCI implementations and coming away I knew of twelve! Most notable of those 12 is Eucalyptus who will soon have an implementation through the good work David Wallom and his team in Oxford are doing. You might have noticed a new logo (above) too contributed by Sam You might have also seen the various OCCI articles in the latest ERCIM news and if not go check it out! And there is more, especially in areas related to OpenStack, we’re only dying to share with the community but, soon, very soon you’ll know more!
Much of this work in advocating the adoption and support of OCCI has been carried out by our tireless co-chairs; Thijs, Alexis and I, as well superb support from many people within OGF including Craig Lee (OGF president) and Alan Sill (VP of Standards).
So what was I doing at OGF30 other than working hard and having great fun at the same time with the OCCI guys? Well I presented on the work we’re doing in SLA@SOI. I presented on “Standards-based, SLA-enabled Infrastructure Management”. You can check the presentation out here and I must apologies to those present if I bombarded you with architecture. At least I showed a real live demo! The live demo showed a number of SLA-guaranteed services all managed by OCCI. Incidentally, the OCCI implementation used is open source (BSD) and available on sourceforge. For those not present there’s some screen grabs at the end of the presentation. It’s implemented in the awesome Grails so if you’re interested, take a wander over there. Some interesting pieces coming from SLA@SOI related to OCCI include; a jClouds OCCI implementation, OCCI extensions on Advanced Scheduling and Monitoring.
So if you want to check out what’s going on in OCCI for yourself, why not have a look through the wiki, svn (it’s latex but you can build it ). Come over to IRC (iric.freenode.net #occi). There’s always an OCCI person or more hanging out there and ready to talk.
Finally, as if that wasn’t enough, there was a very interesting DCI-Fed session held where we discussed various use-cases. DCI-Fed (mailing list, wiki) , from a Cloud Computing perspective, is really interesting and exciting. It looks into how various different Cloud Computing providers can interoperate to provide federated services to their clients. Certainly the future!