May 2012 - occi-wg - lists.ogf.org

Dasein Cloud
by Thijs Metsch 23 Jun '13

23 Jun '13

Hi, Just to inform you that there is a cool project going on called Dasein-Cloud. http://dasein-cloud.sourceforge.net/ On the website it reads: Dasein Cloud is an Open Source Java API made available by enStratus Networks LLC under the terms of the Apache License 2.0. This API specifies cloud-independent interfaces for enabling an application to access resources across multiple clouds. If you are interested have a look - and it might be great to implement OCCI in their someday! Cheers, -Thijs -- Thijs Metsch Senior Software Engineer Grid and Cloud Technology Platform Computing GmbH Europaring 60 D-40878 Ratingen http://www.platform.com http://www.nohuddleoffense.de/ - http://www.twitter.com/befreax

3 2

OCCI implementation for VMWware IaaS
by Ignacio Garcia Vega 03 Jul '12

03 Jul '12

Dear OCCI members, I would like to kindly ask you about the current developments in the implementation of an API translation for VMware solution ( VCloud director), so our IaaS cloud management software could be compatible with OCCI specifications. We are wondering whether you are aware of the risks involved, if there are advances in this sense or if anyone have achieve to make it work properly. Any comment on that would be welcome. Thanks in advance. -- Ignacio García Vega Gestor I+D+i/ R&D&i Project Manager igarcia(a)wtelecom.es<mailto:igarcia@wtelecom.es> Charles Darwin s/n (Pabellón Monorrail) Isla de la Cartuja 41092 Sevilla T +34 954151706 F +34 954151729 www.wtelecom.es<http://www.wtelecom.es/> En cumplimiento de lo dispuesto en la Ley Orgánica 13/1999 de 13 de Diciembre de Protección de Datos de Carácter Personal le informamos que los datos personales que nos ha facilitado son tratados por WELLNESS TELECOM SL, de forma confidencial y con la finalidad para la que fueron recabados. Esto es, darles a conocer nuestro trabajo. Dichos datos se encuentran registrados en un fichero de datos de carácter personal del que WELLNESS TELECOM SL es responsable y se encuentra registrado en la Agencia de Protección de Datos. El titular de los datos tiene derecho de acceso, rectificación, cancelación, oposición, para lo que deberá comunicarlo por escrito a WELLNESS TELECOM SL. En caso que no desee que WELLNESS TELECOM SL trate sus datos personales le rogamos nos lo comunique por escrito. NOTA: Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, contiene información de carácter confidencial exclusivamente dirigida a su destinatario o destinatarios. Queda prohibida su divulgación, copia o distribución a terceros sin la previa autorización escrita de WELLNESS TELECOM SL. En caso de haber recibido este correo por error, le rogamos se sirva notificar inmediatamente esta circunstancia mediante reenvío a la dirección electrónica del remitente. Le agradecemos de antemano su colaboración. P Antes de imprimir este e-mail piense bien si es necesario hacerlo. Before printing this email, assess if it is really needed.

2 1

CompatibleOne Hands On Session 13, 14 June: Invitation
by Jean-Pierre.Laisne＠bull.net 29 May '12

29 May '12

Dear all, Due to the significant progress of CompatibleOne since last session, it is time for a new "Hands On" session. We are really enthusiastic with the idea of sharing with you these new features for the second time. This session will be held on 2 days (13th & 14th of June) in Institut Telecom Mines ParisTech, 46, rue Barrault - 75013 Paris (room C128). This session will be the opportunity to answer all the questions you may have concerning usage of CompatibleOne. You will be able to to manipulate CompatibleOne platform with the help and support of the developers themselves. And naturally these sessions will be interactive and will take place in real conditions i.e. in the cloud. The provisional agenda is the following : 13 June 9:30-12:30: Dive into CompatibleOne - CORDS V2: from oriented object model to OO language - ACCORDS Parser, Broker & PROCCI: an OCCI compiler and a run time for provisioning and integrating any type of cloud computing resources (e.g. PAAS for Java developers, Network Services, ...) 14:00-18:00: CompatibleOne Practice Part I - How to create a new service for new documents - How to create a PROCCI 14 June 9:30-12:30: CompatibleOne Practice Part II 14:00-18:00: Open Discussion This session will be dedicated to Open Cloud. Based on what would have been previously shown, CompatibleOne Team will share with you their vision and future roadmap in an open discussion and in presence of renown leaders of the Industry (to be announced later). These session are free but the number of seats being limited, please confirm your participation ASAP on http://doodle.com/azuwtaprt8qr8xqc We look forward at meeting you there, CompatibleOne Team Note: please feel free to forward this invitation to any person who might be interested

3 4

OCCI JSON Rendering Draft v2
by Feldhaus, Florian 27 May '12

27 May '12

I updated the OCCI JSON Rendering with the input from Ralf. Heres the list of changes: - cleanup of examples - detailed examples in separate section - hightlighting of examples through minted latex package - moved title, summary and id to top level in resource and link Especially the last change has a lot of implications. See my explanation in the other thread, why I would do it this way. Cheers, Florian ------------------------------------------------------------------------------- GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Fon: 0551 39-20364 Fax: 0551 201-2150 E-Mail: florian.feldhaus(a)gwdg.de WWW: www.gwdg.de ----------------------------------------------------------------------------------- Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 -----------------------------------------------------------------------------------

3 2

June 2012 Cloud Plugfest - Registration is now open
by Mancuso, Tom 23 May '12

23 May '12

All, The next OGF/SNIA organized Cloud Plugfest is scheduled for June 14 - 17 with locations in Shenzhen, CN, Amsterdam, NL, and Chicago, IL. This event is the 5th in the series and is proudly co-sponsored by Cleversafe<http://www.cleversafe.com/>, Huawei<http://www.huawei.com/en/>, OGF<http://www.ogf.org/> and the SNIA Cloud Storage Initiative<http://www.snia.org/forums/csi>, with ETSI<http://www.etsi.org/> providing testing support. Registered participants may attend any of the physical locations or remotely via dial-in. Registration is free and open to all who are looking to implement cloud standards such as CDMI or OCCI. Seating is limited to 5 - 15 seats at some locations and will be filled on a first-registered-first-served basis. For more information, or to register to attend, please visit www.cloudplugfest.org<http://www.cloudplugfest.org> and complete the registration form. The February/March Cloud Plugfest held in Dusseldorf, DE attracted over 35 participants. The www.cloudplugfest.org<http://www.cloudplugfest.org> website is a new tool being deployed for this activity and will be updated and expanded to become a one-stop resource for cloud plugfest activities, so please bear with us as this site continues to evolve. Plugfest Logistics Contacts: * Shenzhen, CN - Mark Carlson/SNIA - mark.carlson(a)oracle.com<mailto:mark.carlson@oracle.com> * Amsterdam, NL - Joel Repogle/OGF - replogle(a)ogf.org<mailto:replogle@ogf.org> * Chicago, IL - Chad Thibodeau/SNIA - cthibodeau(a)cleversafe.com<mailto:cthibodeau@cleversafe.com> * Remote - Tom Mancuso/SNIA - tom.mancuso(a)snia.org<mailto:tom.mancuso@snia.org> Regards, - Tom Tom Mancuso Senior Program Manager, SMI Storage Networking Industry Association _______________________________________ SNIA Mobile: 719.491.2614 tom.mancuso(a)snia.org<mailto:tom.mancuso@snia.org> www.snia.org<http://www.snia.org>

1 0

OCCI implementation for Synnefo IaaS
by John Giannelos 23 May '12

23 May '12

Dear OCCI members, I would like to make an announcement about a new OCCI implementation. Here in GRNET [1] we are currently developing an API translation proxy in order Synnefo [2], our IaaS cloud management software to be compatible with OCCI specifications. Synnefo can be seen in action, powering the ~okeanos service, at http://okeanos.grnet.gr. ~okeanos aims to deliver advanced IaaS for the Greek academic and research community. Some resources about our work regarding OCCI can be found here [3]. *About snf-occi* snf-occi implements an API bridge between OCCI and OpenStack APIs using the kamaki [4] client library and associated CLI tool to translate between interfaces. So far, the Compute part of the implementation has been completed, with Network and Storage support soon to follow. We hope snf-occi will prove helpful for other OpenStack-compatible projects to gain interoperability with OCCI, with little (or no) changes to our initial work. I would also like to know whether it will be possible to make our project public in occi-wg blog for people who may be interested but are not subscribed to this mailing list. Thanks, The ~okeanos team! [1] http://www.grnet.gr [2] http://docs.dev.grnet.gr/synnefo [3] http://docs.dev.grnet.gr/snf-occi/latest/index.html [4] http://docs.dev.grnet.gr/kamaki/latest/index.html

4 4

Cloud Plugfest planning meeting
by Alan Sill 22 May '12

22 May '12

Going on now: 1-866-439-4480 US - Toll Access - 1-212-786-7191 Participant PIN Code - 16651018# International Access Numbers: http://www.snia.org/international/support WebEx - http://snia.webex.com Meeting number: 793 124 513 Meeting password: cloud2012 Host key: 473844

1 0

JSON Document
by Edmonds Andrew (edmo) 18 May '12

18 May '12

First, Great work! Here are some editorial comments: - Please ensure line breaks at col 80 - The pdf build is broken. There is a missing dependency of "! LaTeX Error: File `json_rendering.out.pyg' not found." Please fix with a README with directions on installing the dependency. - In all tables, 'name resources' doesn't make sense. Possibly should be 'named resources'? If so I can make the edits or it's at your pleasure :-) - 'Necessity' in all tables. This is some what out of step with existing specs. Can it be aligned along 'Mutability' and 'Multiplicity' as in the existing OCCI specification series? - I've made and committed some minor changes. Review at your leisure. HTH, Andy Andy Edmonds Senior Researcher Institute of Information Technology Zurich University of Applied Sciences http://andy.edmonds.be, @dizz

3 3

Fwd: [Openstack] Third Party APIs
by Alan Sill 17 May '12

17 May '12

FYI. Comments (especially on the openstack list) welcome... Alan Begin forwarded message: > From: Vishvananda Ishaya <vishvananda(a)gmail.com> > Date: May 17, 2012 1:18:19 PM CDT > To: "openstack (openstack(a)lists.launchpad.net)" <openstack(a)lists.launchpad.net > > > Subject: [Openstack] Third Party APIs > > Hello Everyone, > > In the ppb meeting last week[1] we discussed third party apis and > decided that the policy is not to include them in core. > Specifically the motion that passed is: > > An OpenStack project will support an official API in it's core > implementation (the OpenStack API). other APIs will be implemented > external to core. the core project will expose stable, complete, > performant interfaces so that 3rd party APIs can be implemented in a > complete and performant manner. > > So now that we have settled on a long term goal for third party > apis, we need to deal with the short term. We do have a stable > interface in Nova in the form of the OpenStack API but it remains to > be seen whether it is complete and performant enough to allow other > apis to be layered on top of it. > > Ultimately, I would like to see a stable internal python api that > the other apis could speak through (including the OpenStack api > layer), but it will probably take a while to get there. In the short > term I see three possibilities for third party apis. > > 1 Proxy Layer > > This is the approach being taken by AWSOME, and it is definitely the > easiest to maintain. It has some big advantages, like allowing new > apis deployed in a completely decoupled manner. The main potential > drawbacks are performance and an incomplete mapping of concepts from > one api to another. This will most likely require adding OpenStack > api extensions to support some of the extra features in other apis > > 2 Separate Project that talks to internal apis > > It is possible to write a separate component that imports the > compute.api in nova and uses it directly. This will deal with the > performance issues of the above approach, but it runs the risk of > being broken if the compute.api changes over the course of the > release. The advantage of this approach is it will drive > requirements for having a stable/versioned internal api. In this > model, automated testing would be necessary to alert any breakages. > > 3 Feature Branch in Core > > We are doing some work to support Feature and Subsystem branches in > our CI system. 3rd party apis could live in a feature branch so that > they can be tested using our CI infrastructure. This is very similar > to the above solution, and gives us a temporary place to do > development until the internal apis are more stable. Changes to > internal apis and 3rd party apis could be done concurrently in the > branch and tested. Once the branch has stabilized, the updates could > be pushed into the internal apis in nova, and the 3rd party api > could grow up into its own project like option 2 > > > It may be that there are other options that I haven't thought of, > but regardless of the approach taken by the various 3rd party apis, > I think it is valuable for us all to work together on stabilizing > the internal apis. I'd like the ec2 api to be able to live > separately as well. > > Vish > > [1] http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-me…

1 0

"SLA-Enabled Infrastructure Management" Abstract - SpringerLink
by Alan Sill 16 May '12

16 May '12

Thought you would be interested in the following link. Topic: SLA-Enabled Infrastructure Management Abstract This chapter documents a successful reference implementation of an SLA- enabled compute infrastructure. Limitations of current Infrastructure as a Service (IaaS) offerings are discussed, and an SLA-enabled implementation is introduced. Infrastructure SLA and services managers have been developed, as have extensions to Apache Tashi [11] and a low- level monitoring system. Efforts to develop a generic open interface to heterogenous infrastructure have helped to create the recently published Open Cloud Computing Interface (OCCI) [2]. Link: http://www.springerlink.com/content/n300405h87845124/ Alan Alan Sill, Ph.D Senior Scientist, High Performance Computing Center Adjunct Professor of Physics TTU ==================================================================== : Alan Sill, Texas Tech University Office: Drane 162, MS 4-1167 : : e-mail: Alan.Sill(a)ttu.edu ph. 806-834-5940 fax 806-834-4358 : ====================================================================

2 1