January 2011 - occi-wg - lists.ogf.org

Introduction
by Ross Cooney 18 Jan '11

18 Jan '11

Hi List, My name is Ross Cooney and I work for StormMQ, a cloud based message queue based around the open AMQP standard. We are members of the AMQP working group and very interested in open standards. I am interested in getting to understand the OCCI and how we can help. I will attend the conference call tomorrow, I am happy to give a brief introduction to the skills of the StormMQ team to see if we can help in any way. Cheers, Ross Cooney Commercial Director <mailto:ross.cooney@StormMQ.com> ross.cooney(a)StormMQ.com StormMQ Limited UK Office: Gateshead int'l Business Centre, Mulgrave Terrace, Gateshead, NE8 1AN, United Kingdom Telephone: 08453 712 567 Registered office: 78 Broomfield Road, Chelmsford, Essex, CM1 1SS, United Kingdom StormMQ Limited is Registered in England and Wales under Company Number 07175657 StormMQ.com

1 0

Reminder: occi-wg concall tomorrow at 3pm UTC
by Thijs Metsch 18 Jan '11

18 Jan '11

Hi @all, Just a quick reminder - bridge details can be found here: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Teleconferen… Thanks, -Thijs

2 1

Ruby OCCI Client Bindings
by Ignacio M. Llorente 14 Jan '11

14 Jan '11

Hi You may be interested in this contribution to the OpenNebula community. http://blog.opennebula.org/?p=1234 Cheers, -- Ignacio M. Llorente, Full Professor (Catedratico): http://dsa-research.org/llorente DSA Research Group: web http://dsa-research.org and blog http://blog.dsa-research.org OpenNebula Open Source Toolkit for Cloud Computing: http://www.OpenNebula.org

3 3

OCCI & Wikipedia
by Edmonds, AndrewX 12 Jan '11

12 Jan '11

Is there anyone here that might have the bandwidth to update the Wikipedia entry [1] for OCCI? Andy [1] http://en.wikipedia.org/wiki/Open_Cloud_Computing_Interface ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

2 3

Test client for OCCI
by Thijs Metsch 12 Jan '11

12 Jan '11

Hi, I hacked (literally) together some test client which tries to verify if an OCCI implementation is compliant to the specification. The code is neither perfect nor does it give a definite proof that your implementation is compliant to the spec. It will only say that if all tests run your implementation could be compatible. Nevertheless I wanted to share the code so people can use it, update it and enhance the functionalities. The code can be found in the repository of gridforge: http://forge.ogf.org/integration/viewcvs/viewcvs.cgi/trunk/tests/?root=occi… Cheers, -Thijs

2 2

Reminder: occi-wg concall today at 3pm UTC
by Thijs Metsch 12 Jan '11

12 Jan '11

Hi @all, We'll have our next concall of the year today at 3pm UTC. You can find all the details on how-to join here: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Teleconferen… We'll cover some topics surrounding NIST and the HTTP rendering. Hope to talk to you soon, -Thijs P.S. sorry for the late reminder!

1 0

Website update
by Thijs Metsch 10 Jan '11

10 Jan '11

Hi @all, I'm pleased to announce that the reworked http://www.occi-wg.org website is now on-line. More information will be added in the coming weeks. I would like to thank Andy and the Guys from DSA-Research of the University of Madrid who helped making this possible. Feel free to post any comments, thoughts and ideas! Since this is an community effort I would like to invite you all to write blog posts, add information, dig out interesting material, and help making this website a vivid, interesting site to visit! Cheers, -Thijs P.S. Small note: 2 of our documents are still in public comment please let your friends, family or co-workers read the spec and post comments on: http://ogf.org/gf/docs/?public_comment (Hint: share the link!)

3 3

OCCI testing tutorial and q on use with secured services
by Alan Sill 10 Jan '11

10 Jan '11

How about an OCCI testing tutorial using some of the deployed instances as an example? A starting point might be the tool at the following link. (Version 2.3.3 released today.) Project: rest-client - Project Hosting on Google Code Link: http://code.google.com/p/rest-client/ I'd also like to see a test with SSL-secured httpd services, preferably in a GSI AuthZ or other user cert-secured context. I know this will be trivial but I'd just like to see if anyone has done it in a deployed context to date. Any links? Thanks, Alan P.S.: Please ignore the auto-reply message - I'm reading messages on this topic this holiday...

6 11

Fwd: OCCI feedback
by Andy Edmonds 10 Jan '11

10 Jan '11

Below is some feedback received from vmware (thanks Mark) on the specifications... Andy andy.edmonds.be ---------- Forwarded message ---------- From: Mark Pollack <mpollack(a)vmware.com> Date: Mon, Nov 29, 2010 at 15:08 Subject: RE: OCCI feedback To: Alexis Richardson <alexis(a)rabbitmq.com>, Andy Edmonds < andy.edmonds(a)gmail.com> Cc: Thijs Metsch <tmetsch(a)platform.com>, Adrian Colyer <acolyer(a)vmware.com> Hi, Linking off to another spec, with another metamodel, seems overly complex and quite a high barrier for adoption. I only happened to pick storage by accident as an example, is the same going to hold true for networking or other areas - handing off to other specs via links? I didn't really dive deep into the provisioning aspects of CDMI, I was looking at it more from the development perspective. I remember that the provisioning part was a surprise to most on the call at the time. Is discovering services at runtime practically useful? Dusty images of discovering CORBA services that never got used in reality come to mind - and if they did get used it was a rather up front prescriptive usage vs. dynamic discovery magic. I'll try to send this to the ML... if not, feel free to forward. Mark > -----Original Message----- > From: alexis.richardson(a)gmail.com [mailto:alexis.richardson@gmail.com] > On Behalf Of Alexis Richardson > Sent: Monday, November 29, 2010 9:53 AM > To: Andy Edmonds > Cc: Thijs Metsch; Mark Pollack; Adrian Colyer > Subject: Re: OCCI feedback > > Mark > > Please see below. Andy is co-chair and implementing OCCI at Intel. > > alexis > > > On Mon, Nov 29, 2010 at 2:11 PM, Andy Edmonds <andy.edmonds(a)gmail.com> > wrote: > > Very fair comment especially in the area of moving up a stack wrt > > abstraction. > > With regard to storage, there's little point in developing, imo, a > deep > > specification here given our (OGF-SNIA) agreements towards CDMI. It's > for > > this reason that it would appear to be somewhat anaemic, If one wants > > something more extensive in the area of cloud storage management than > what > > is offered by OCCI then CDMI is the recommended route. Our linking > mechanism > > in OCCI will easily support this. > > On aspects of interoperability, what is expected of a provider is > specified, > > however provider specific extensions can be discovered at runtime > through > > the query interface. What we do want are provider-specific extensions > - > > those that are common amongst a number of users are candidates for > inclusion > > in the main OCCI specification set. > > Would your colleague be happy to submit such feedback to the group, > whether > > be it through the ML, or public comment phase? Such feedback is > important > > :-) > > Andy > > andy.edmonds.be > > > > > > On Mon, Nov 29, 2010 at 13:52, Alexis Richardson > <alexis(a)rabbitmq.com> > > wrote: > >> > >> Andy, Thijs, > >> > >> Some feedback on OCCI from a colleague - > >> > >> a > >> > >> > >> > >> I did a quick read through the spec docs. As it describes at a very > >> basic level what one would want when provisioning infrastructure it > >> runs the risk of specifying too little to be of any true portable > >> value. Take storage for example. All that is required is to > specify > >> the size of disk and manipulate/query a state machine of its status. > >> This seems too simplistic. Then everyone implementing this spec > will > >> come up with their own attribute extensions, thus removing any true > >> portability. Of course there isn't a neat answer here, the problem > >> itself just seems to lend itself only so far to common abstractions. > >> Perhaps the target audience for this type of software doesn't care > >> about those details as the problems one is solving treats the > >> infrastructure as a pure transient commodity, e.g. run a big batch > job > >> for a day, vs. running a mission critical application 24/7. > > > >

1 0

Fwd: NIST CC Reference Architecture & Taxonomy Working Group: Announcement#2 (telecon Monday Jan 10, 2011)
by Alan Sill 10 Jan '11

10 Jan '11

Can someone attend this meeting and comment on it from the point of view of the usage models planned for OCCI and related OGF (and other) standards technologies? Unfortunately this occurs at the same time as a SIENA roadmap editorial board meeting the same day (today, Monday). See documents in the attached zip file. Thanks, Alan Begin forwarded message: > From: "Bohn, Robert B." <robert.bohn(a)nist.gov> > Date: January 7, 2011 2:25:05 PM CST > To: Multiple recipients of list <cc_tax(a)nist.gov> > Subject: NIST CC Reference Architecture & Taxonomy Working Group: Announcement#2 (telecon Monday Jan 10,2011) > Reply-To: "cc_tax(a)nist.gov" <cc_tax(a)nist.gov> > > Colleagues, > > This e-mail announcement is to inform you of the kickoff meeting for the NIST Cloud Computing Reference Architecture & Taxonomy Working Group. It will be held via telecon, next Monday, January 10, 2011 from 1100-1300 EST. The dial-up information is at the end of this message and on the attached agenda. We have a repeating schedule for this working group. It will hold meetings every Monday, Wednesday & Friday from 1100-1300 EST. The Monday sessions will be dedicated to Reference Architecture, Wednesday sessions for Taxonomy & Friday sessions for “Defining Successful Outcomes”. The dial-up information will be the same for each of these meetings. > > In addition to the agenda (NIST CCRATWG 006) , we have also attached several other relevant documents as part of this zip file. They are: > > Project Plan from (now-early April) (NIST CCRATWG 002) > The NIST Cloud Computing Reference Architecture Strawman document (NIST CCRATWG 003) > Cloud Architecture Reference Models (prepared by Knowcean Consulting Inc.) (NIST CCRATWG 004) > Cloud Reference Architecture Subgroup Charter (NIST CCRATWG 001) > Cloud Strawman Taxonomy MindMeld diagram (pdf) (NIST CCRATWG 005) > > All of these documents will be available on the NIST Cloud Computing Twiki under the Reference Architecture link. The URL for the Twiki is: > > http://collaborate.nist.gov/twiki-cloud-computing/bin/view/CloudComputing/W… > > We will use the Twiki as our main collaborative tool and as a place to retrieve and upload documents and deliverables. Since this is our first announcement, we have attached the documents. This mailing list will be used for discussions and announcement. Any new documents should be uploaded to the Twiki and not included as attachments to the mailing list. > > The mailing list will be our primary way of communicating with each other through the process. > > The dial-up information for next Monday’s telecon follows: > > Phone: 877-953-0273 > Participant code: 4564979 > > Sincerely, > > Robert Bohn & John Messina >

1 0