- occi-wg - lists.ogf.org

Reminder: weekly concall today - 07:00 PDT, 10:00 EDT, 15:00 BST, 16:00 CEST
by Thijs Metsch 09 Sep '09

09 Sep '09

Hi, A short reminder that the weekly concall of OCCI takes place today! As usual at 07:00 PDT, 10:00 EDT, 15:00 BST, 16:00 CEST. Please dial in using the attached conference bridge info. The agenda is set to: - document action item discussions - OCCI/OVF demo and OCCI/CDMI demo - OpenNebula OCCI reference implementation All the best, -Thijs Passcode: Participant: 9032568 Dial in numbers: Country Toll Numbers Freephone/Toll Free Number ARGENTINA 0800-777-0463 AUSTRALIA ADELAIDE: 61-8-8121-4868 1-800-249-288 AUSTRALIA BRISBANE: 61-7-3102-0970 1-800-249-288 AUSTRALIA CANBERRA: 61-2-6100-1970 1-800-249-288 AUSTRALIA MELBOURNE: 61-3-9010-7739 1-800-249-288 AUSTRALIA PERTH: 61-8-9467-5249 1-800-249-288 AUSTRALIA SYDNEY: 61-2-8205-8125 1-800-249-288 AUSTRIA 43-1-92-86-506 0800-005-029 BELGIUM 32-1-150-0314 0800-4-8680 BRAZIL 0800-7610674 CHILE 1230-020-2867 CHINA* 86-400-810-4766 10800-712-1433 10800-120-1433 COLOMBIA 01800-9-156430 CZECH REPUBLIC 420-2-25-98-56-54 800-700-173 DENMARK 45-7014-0280 8088-6132 ESTONIA 800-011-1089 FINLAND Land Line: 106-33-146 0-800-1-10100 FINLAND Mobile: 09-106-33-146 0-800-1-10100 FRANCE LYON: 33-4-26-69-12-81 080-563-9647 FRANCE MARSEILLE: 33-4-86-06-00-81 080-563-9647 FRANCE PARIS: 33-1-70-70-74-20 080-563-9647 GERMANY 49-69-2222-2566 0800-000-3441 GREECE 30-80-1-100-0683 00800-12-6973 HONG KONG 852-2286-5731 800-930-705 HUNGARY 06-800-18013 INDIA 000-800-852-1266 INDONESIA 001-803-011-3787 IRELAND 353-1-247-5253 1800-932-145 ISRAEL 1-80-9214916 ITALY 39-02-3600-3642 800-986-570 JAPAN OSAKA: 81-6-7739-4769 0034-800-400828 JAPAN TOKYO: 81-3-5539-5189 0034-800-400828 LATVIA 8000-3025 LUXEMBOURG 352-27-000-1360 MALAYSIA 1-800-80-2812 MEXICO 001-866-627-0574 NETHERLANDS 31-20-718-8533 0800-020-1392 NEW ZEALAND 64-9-970-4769 0800-449-823 NORWAY 47-21-59-00-59 800-15414 PANAMA 011-001-800-5072129 PERU 0800-53733 PHILIPPINES 63-2-858-3715 POLAND 00-800-1212021 PORTUGAL 8008-14061 RUSSIA 8-10-8002-9683011 SINGAPORE 65-6883-9228 800-120-4662 SLOVAK REPUBLIC 421-2-322-422-21 SOUTH AFRICA 080-09-80416 SOUTH KOREA 82-2-6744-1081 00798-14800-6860 SPAIN 34-91-414-62-98 800-099-810 SWEDEN 46-8-505-78-524 0200-890-106 SWITZERLAND 41-44-580-4389 0800-001-523 TAIWAN 886-2-2795-7377 00801-137-766 THAILAND 001-800-1206-65656 UNITED KINGDOM BIRMINGHAM: 44-121-210-9021 0808-238-6025 UNITED KINGDOM GLASGOW: 44-141-202-3221 0808-238-6025 UNITED KINGDOM LEEDS: 44-113-301-2121 0808-238-6025 UNITED KINGDOM LONDON: 44-20-7075-3246 0808-238-6025 UNITED KINGDOM MANCHESTER: 44-161-601-1421 0808-238-6025 URUGUAY 000-413-598-3415 USA 1-203-418-3122 866-692-3163 VENEZUELA 0800-1-00-3733 -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds http://www.twitter.com/befreax Software Engineer Cloud, Grid and Virtualization Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

1 1

Fwd: Link Relations: up/down vs parent/child vs ancestor/descendant etc.
by Sam Johnston 08 Sep '09

08 Sep '09

Evening all, FYI - there's been some discussion about OCCI dependencies on other lists but I've been avoiding cross-posting given the audiences are quite different. The latest is about wiring resources together using generic link relations as it's preferable that we avoid rolling our own standards where we can use ones that already exist. Sam ---------- Forwarded message ---------- From: Sam Johnston <samj(a)samj.net> Date: Tue, Sep 8, 2009 at 7:08 PM Subject: Link Relations: up/down vs parent/child vs ancestor/descendant etc. To: Atom Syntax <atom-syntax(a)imc.org>, HTTP Working Group < ietf-http-wg(a)w3.org> Evening all, I am busy designing a protocol for cloud computing[1] and want clients to be able to discover children of a given resource in order to navigate a tree structure. I had been considering defining a new "collection" link relation but then found draft-divilly-atom-hierarchy<http://tools.ietf.org/html/draft-divilly-atom-hierarchy> which defines a "down" relation. My concern is that the terms "up" and "down" are ambiguous in this context and indeed we may end up defining [URI] relations for "up" and "down" as state changes for network resources. Furthermore there has been come commentary/confusion of late around the use of multiple attributes (e.g. "up up up") and now seems as good a time as ever to clarify given we have the link relation I-D and HTML 5 WD on the table at the IETF and W3C respectively. I wonder whether it would be possible to instead use "parent" and "child" (for first generation relationships) or "ancestor" and "descendant" (for more generic n-generation relationships, where n is specified as an attribute like "level=2")? This is simple and self-describing and could resolve the issue once and for all. Alternatively the terms could be abbreviated to "asc" and "desc" respectively (as in "ascend" and "descend"). I also wonder whether "collection" isn't a bad idea anyway - consider a resource describing a bookshelf where the collection consists of books. Sam 1. http://www.occi-wg.org/

1 0

Final round of comments for Use case and req. document before submission
by Thijs Metsch 08 Sep '09

08 Sep '09

Hi all, I would like to encourage you all to have a look at our first deliverable 'Requirements and Use Cases for a Cloud API'. I would ask to send you comments, ideas and thoughts by Friday. The document can be found here: http://forge.ogf.org/sf/go/doc15732 Friday is not a 'real' deadline. But I will submit it into the OGF editor pipeline on Friday. Then it will go into a public review - after that it will be released as our first informal document. All the best, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds http://www.twitter.com/befreax Software Engineer Cloud, Grid and Virtualization Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

4 5

Prototype implementation of the OCCI draft specification
by Tino Vazquez 05 Sep '09

05 Sep '09

Dear OCCI members, We are happy to announce the availability of a prototype implementation of the OCCI draft specification. As the specification is not finished nor final, we tried to adjust as much as possible to the spirit distilled by the spec document found in the wiki. We believe that is important to have an implementation in order to demo the standard, which we think will provide value to OCCI, to be able to show people how the standard will look like and behave, and, even more importantly, provide feedback. Along with the server implementation, client command are implemented in order to use the service, enabling the access to the full functiolity of the interface. The code has been upload to OpenNebula's subversion trunk, and can be downloaded from [1], using the following command: $ svn co http://svn.opennebula.org/one/trunk one Documentation on how to configure the OpenNebula OCCI service [2] and a user guide [3] are also available. Also, a design document is also ready [4]. This implementation will be distributed with OpenNebula 1.4 [5] and has been developed in the context of the RESERVOIR project. OpenNebula 1.4 also includes the implementation of the EC2 Query API [6], and allows the managing of the virtual infrastructure using both interfaces simultaneously. Best regards, -Tino [1] http://redmine.opennebula.org/ [2] http://opennebula.org/doku.php?id=documentation:rel1.4:occicg [3] http://opennebula.org/doku.php?id=documentation:rel1.4:occiug [4] http://opennebula.org/doku.php?id=documentation:rel1.4:occidd [5] http://opennebula.org/doku.php?id=documentation:rel1.4 [6] http://opennebula.org/doku.php?id=documentation:rel1.4:ec2qug -- Constantino Vázquez, Grid Technology Engineer/Researcher: http://www.dsa-research.org/tinova DSA Research Group: http://dsa-research.org Globus GridWay Metascheduler: http://www.GridWay.org OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org

2 1

Note: GridForge is currenty done
by Thijs Metsch 04 Sep '09

04 Sep '09

Hi, The GridForge seems to be unreachable at the moment. I did ping the Administrators. Sorry for the inconvenience, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds http://www.twitter.com/befreax Software Engineer Cloud, Grid and Virtualization Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

4 4

Simplified OCCI VM lifecycle diagram
by Gary Mazz 04 Sep '09

04 Sep '09

Hi, I put together a simplified version of the OCCI life cycle (state) diagram. I'll be using this as an overview and for discussion purposes. I'll provide a description in a couple of days. -gary

5 7

Re: [occi-wg] OGF Strategic Directions for OCCI
by Alexis Richardson 03 Sep '09

03 Sep '09

This is great work - please keep it up guys! alexis (on vacation) On Wed, Sep 2, 2009 at 3:15 PM, Craig A Lee<Craig.A.Lee(a)aero.org> wrote: > > To All in the OCCI/OGF Community, > > As you should know, the OCCI WG will be sending their Use Case and > Requirements document to the OGF Editor soon and is finishing their > draft specification in time for discussion at OGF-27. Given the tremendous > interest in cloud computing, this gives the OCCI WG and OGF a set of > important opportunities that could have high visibility -- and > hopefully high impact. > > I have pinged the potential implementors listed on the wiki, and as > of this email, > * OpenNebula, > * Cisco CTO Cloud Concept Lab, and > * SLA@SOI > have all re-affirmed their commitment to implement the OCCI spec. > > Clearly, once we have some implementations, we will be in a position > to organize a set of open IaaS cloud demonstrations. This was > discussed on the last cloud-standards.org telecon with a very positive > reaction. Any such demos could certainly integrate the use of other > standards, such as DMTF's OVF and SNIA's CDMI. > > The exact demo scenarios to approach is clearly an important issue. > These scenarios should be ones that are important to the major > potential adopters and users of OCCI. The large-scale, national cloud > initiatives that have been announced recently could be a good source > for such scenarios, and help drive open standards, since they will > want portability and interoperability to avoid vendor lock-in. Hence, > OGF is actively pursuing engagement within the Japanese Kasumigaseki > Cloud, the UK G-Cloud, and the US Cloud Storefront efforts. > > Finally I want caveat all of these plans -- this simply is the > strategic direction > that OGF is taking, and obviously no particular outcomes are guaranteed. > We must, however, plan ahead for the implementations that are coming. > As always, comments are welcome. > > Best regards -- and I look forward to seeing you in Banff, > > --Craig > -- > ==================================================== > Dr. Craig A. Lee, lee(a)aero.org > President, Open Grid Forum, www.ogf.org > Senior Scientist, High Performance Computing > The Aerospace Corporation, M1-102 > 2310 East El Segundo Blvd. > El Segundo, CA 90245 USA > cell: +1-310-804-6964 > office: +1-310-336-1381 > fax: +1-310-336-0613 > http://www.aero.org > > The Aerospace Corporation operates a non-profit, > federally funded research and development corporation. > _______________________________________________ > occi-wg mailing list > occi-wg(a)ogf.org > http://www.ogf.org/mailman/listinfo/occi-wg >

2 3

new pdf versions of the documents available
by Thijs Metsch 03 Sep '09

03 Sep '09

Hi, I just uploaded new PDF-versions of our 2 document to the gridforge. The req and use cases document will undergo two major changes. Some References will be added and the feature matrix will be included. After that the document will go into the OGF document process pipeline. First for public review and then for publication...So stay tuned :-) The documents are linked on www.occi-wg.org and can also be found in the drafts folder here: http://forge.ogf.org/sf/go/projects.occi-wg/docman.root.drafts All the best, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds http://www.twitter.com/befreax Software Engineer Cloud, Grid and Virtualization Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

1 0

VMware vCloud API
by Sam Johnston 02 Sep '09

02 Sep '09

Afternoon all, As part of today's call I'd like to take a high level look at the good/bad/ugly of VMware's vCloud API: - Programming Guide<http://communities.vmware.com/static/vcloudapi/vCloud_API_Programming_Guide…> - Specification<http://communities.vmware.com/static/vcloudapi/vCloud_API_Specification_v0.…> The way I see it this is an implementation-specific "private cloud" API (for services running VMware vCloud [Express]) and we're writing a "public cloud" API for various services like/modeled after EC2. That is to say, we have things to learn from their efforts and vice versa. Please have these documents at your disposal for the call. Sam

5 5

OGF Strategic Directions for OCCI
by Craig A Lee 02 Sep '09

02 Sep '09

To All in the OCCI/OGF Community, As you should know, the OCCI WG will be sending their Use Case and Requirements document to the OGF Editor soon and is finishing their draft specification in time for discussion at OGF-27. Given the tremendous interest in cloud computing, this gives the OCCI WG and OGF a set of important opportunities that could have high visibility -- and hopefully high impact. I have pinged the potential implementors listed on the wiki, and as of this email, * OpenNebula, * Cisco CTO Cloud Concept Lab, and * SLA@SOI have all re-affirmed their commitment to implement the OCCI spec. Clearly, once we have some implementations, we will be in a position to organize a set of open IaaS cloud demonstrations. This was discussed on the last cloud-standards.org telecon with a very positive reaction. Any such demos could certainly integrate the use of other standards, such as DMTF's OVF and SNIA's CDMI. The exact demo scenarios to approach is clearly an important issue. These scenarios should be ones that are important to the major potential adopters and users of OCCI. The large-scale, national cloud initiatives that have been announced recently could be a good source for such scenarios, and help drive open standards, since they will want portability and interoperability to avoid vendor lock-in. Hence, OGF is actively pursuing engagement within the Japanese Kasumigaseki Cloud, the UK G-Cloud, and the US Cloud Storefront efforts. Finally I want caveat all of these plans -- this simply is the strategic direction that OGF is taking, and obviously no particular outcomes are guaranteed. We must, however, plan ahead for the implementations that are coming. As always, comments are welcome. Best regards -- and I look forward to seeing you in Banff, --Craig -- ==================================================== Dr. Craig A. Lee, lee(a)aero.org President, Open Grid Forum, www.ogf.org Senior Scientist, High Performance Computing The Aerospace Corporation, M1-102 2310 East El Segundo Blvd. El Segundo, CA 90245 USA cell: +1-310-804-6964 office: +1-310-336-1381 fax: +1-310-336-0613 http://www.aero.org The Aerospace Corporation operates a non-profit, federally funded research and development corporation.

1 0