September 2009 - occi-wg

Support Documentation for Today's Meeting
by Ignacio Martin Llorente 01 Oct '09

01 Oct '09

Hi, Because we are now (at 16:00 CEST) discussing the OpenNebula OCCI implementation, I am sending some links with relevant info: - OpenNebula OCCI API Specification: http://www.opennebula.org/doku.php?id=documentation:rel1.4:occidd - Usage Guide: http://www.opennebula.org/doku.php?id=documentation:rel1.4:occiug 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 RESERVOIR European Project in Cloud Computing: http://www.reservoir-fp7.eu

2 1

Reminder: IGT on going work groups meetings and events
by IGT 30 Sep '09

30 Sep '09

<http://www.grid.org.il/_pics/NewsLetterHeader.jpg> IGT on going work groups meetings and events http://www.grid.org.il/?CategoryID=384 <http://www.grid.org.il/?CategoryID=384> And.. Please do not forget our annual event on Dec 2-3: IGT2009 – The World Summit of Cloud Computing http://events.myreg.co.il/IGT2009/ <http://events.myreg.co.il/IGT2009/> מחק אותי מתפוצת אימייל זה <http://www.grid.org.il/?pg=subscr_un> | כניסה לאתר <http://www.grid.org.il>

1 0

Comments, Suggested Changes for Walkthrough
by Edmonds, AndrewX 30 Sep '09

30 Sep '09

Hi all, I've gone through the walk through and have a list of comments and suggested changes. I will be continuing on through the spec with a similar intention of contributing comments and suggested changes. Thijs, if you like I can add these to the tracker unless you want to pre-process them? I do not suggest discussing any of these via the mailing list. That discussion can happen via the issue tracker. Andy * General * Would be useful to introduce the notion of OCCI extensions in the walk through * A page break should be inserted to separate the walkthrough and "OCCI Core Specification" * Revise usage of brackets * Paragraph 4 "resource or type of resource" * what's the difference here? * Paragraph 4 "and search" * note that this is an extension and may not be supported in all implementations * Paragraph 5 Bracket usage in the sentence "Certain types of accesses..." * would read better as: Certain types of accesses, such as a compute resource querying OCCI for introspection and configuration, may be possible anonymously in the case where the query has already been authenticated by interface and/or IP address. * Paragraph 6 "Should you be redirected by the API to a node, storage device, etc. (for example, to retrieve a large binary representation) then you should either be able to transparently authenticate or a signed URL should be provided." * If the basic authentication is not cached then this transparent authentication will not happen. Is what I say a correct statement? * Paragraph 6 "(at least not yet!)" * Remove this, not necessary. * Paragraph 6 "and while OCCI standardises a number of them for interoperability" * We can only recommend other standards for use in OCCI not standardise them - that's the responsibility of the relevant standards body * Paragraph 6 List of representations * I do not agree that a screenshot or access to console is an appropriate general entity representation like what OVF/OVA are. These items are more suitable as attributes in an entity representation (OVF/OVA/OCCI). Suggest removing or noting that they are lesser forms. * Paragraph 7 "The client indicates which representation(s) it desires by way of the URL" * An example illustrating this might be useful e.g. * To request a HTML rendering, if supported, of a compute node issue http://example.com/path/to/compute/resource/123-123-123.html * The same might be for the content negotiation. * Paragraph 8 "In addition to the protocol itself," * Remove the protocol includes interaction semantics, syntax and data schemas. * Paragraph 8 "In addition to the protocol itself, OCCI defines a simple key/value based descriptor format for cloud infrastructure resources:". * Reword to: "OCCI defines a simple key/value based descriptor format for cloud infrastructure resources. These infrastructure resources as defined by OCCI are:". * Paragraph 8 Formatting * Embolden compute storage and network - these are core concepts to OCCI. * Paragraph 9 Comment * If we say that it is trivial to translate and present an example that example should show the trivial translation. In this case we should add the XML and JSON examples. * Paragraph 10 Starting "The primary drawback is that" ending "or HTTP 410 Gone otherwise)." * Is this necessary here - might be better moved out of the walkthrough to elsewhere or just removed. * Paragraph 10 Comment * Bracket usage should be reviewed. * Paragraph 12 "UUIDs anyway" * Remove "anyway". * Paragraph 12 "used instead (e.g. http://amazon.com/compute/ami-ef48af86)" * Any significance using this URL - better we use something fictional * Paragraph 12 "can be safely allocated by any node" * What's a "node"? A resource? A resource manager? * Section 2.3 Comment * A brief introduction should be inserted here. * Paragraph 13 "POST it to" * What is "it"? Explicate. * Paragraph 13 "as an HTML form" * More correct to say "POST the attributes and values using the application/x-www-form-urlencoded format" * Paragraph 15 "to GET a template" * New concept introduced with no explanation. Explain briefly (footnote?) or drop and move discussion elsewhere in doc. * Paragraph 15 "POST or PUT it back" * There are semantic differences here that should be noted to the reader. * Paragraph 17 P18 Comment * It would make more sense to inform the user how to get a list of supported renders per provider first and then tell how to request it. As it initially reads it appears that 2 calls are needed. * Paragraph 19 "There are two options:" * Better phrased as "There are two concepts that are supported" * Paragraph 19 "such as searches" * Change to "such as the collections returned from the search extension" * Paragraph 19 Pass-by-ref, pass-by-value * This is more a metaphor - might be worth explaining what is meant by these explicitly, otherwise the reader is left to interpret. * Paragraph 20 "Update" * It says to PUT but I can also update via POST and be naughty. * Paragraph 22 Comment * What about "Resource Child Collections". * Paragraph 22 Comment * These are in effect extensions to the core and so should be noted as such. * Paragraph 24 "Requests" * Just a comment - isn't this very RPC-like something that REST aims to avoid? * Paragraph 24 "Requests" * A number of request types are mentioned but nowhere in the spec are they detailed. Andy Edmonds skype: andy.edmonds tweets: @dizz ------------------------------------------------------------- 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.

3 9

Proposal for conference call to discuss OCCI attributes in HTTP headers
by Gary Mazz 30 Sep '09

30 Sep '09

I' like to schedule a meeting to discuss Sam Johnston's proposal to move OCCI attributes elusively to HTTP headers. I'd like to schedule this conference on friday Sept 25, 2009, the as time as the weekly call. We need to fully understand the mapping of the attributes to the http protocol structures and the impacts to the specification. cheers, gary mazz

3 8

OCCI Specification draft
by Thijs Metsch 29 Sep '09

29 Sep '09

Hi @all, This is the first (almost final :-)) draft of the OCCI Specification. It reflects the changeset #47 in the source code repository (Date Sep. 21 2009). This release has been tagged. For easier discussion on the concall on Wednesday all the paragraphs have been numbered. The document can be downloaded here: http://forge.ogf.org/sf/docman/do/downloadDocument/projects.occi-wg/docman.… our http://www.occi-wg.org website also links there. We'll do a walkthrough of the complete specification on our concall on Wednesday so please review the document and join the call. 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

5 7

New specification document draft
by Thijs Metsch 29 Sep '09

29 Sep '09

Hi, I uploaded a new draft of the spec. Not much changed so please help filling in the holes: http://code.google.com/p/occi/issues/list Have a look here: http://forge.ogf.org/sf/go/doc15731?nav=1 I will work on the issues: 2, 14, 18 I also updated the issue tracker templates. So when creating a new comment use the document_comment template. It tells you what information is need to comment :-) Is also include the changeset #49 and date 29.09.2009... 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

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

29 Sep '09

Hi @all, Tomorrow will be another important concall...We will have the guys from OpenNebula on the line. So we can discuss the reference implementation they did. So please join! Call takes place: Tomorrow Sep. 30, 2009 @ 07:00 PDT, 10:00 EDT, 15:00 BST, 16:00 CEST...All the contact information is attached... Looking forward to this call, -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 at sun.com D-93049 Regensburg http://www.sun.com -- 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

Mark your calendars - OGF schedule
by Thijs Metsch 29 Sep '09

29 Sep '09

Hi, Our sessions are scheduled for Tuesday: http://www.ogf.org/gf/event_schedule/index.php?event_id=14&matrix Hopefully with dial-in:-) All the best, -Thijs P.S. I will do a build of the document later today...Sorry for the inconvenience - some personal stuff is keeping me busy...

1 0

Re: [occi-wg] Doodle Vote: Time & date to discuss the "Proposal for conference call to discuss moving OCCI attributes to HTTP headers"
by Gary Mazz 25 Sep '09

25 Sep '09

Thanks all, Yup, I put it in the header... Here is the link in the :body" http://doodle.com/wu3m54dnq8a95rus :)g shlomo.swidler(a)gmail.com wrote: > Gary, > > The link is missing from the email. Must be in the HTTP header. ;-) > > .. Shlomo > > On Fri, Sep 25, 2009 at 10:41 AM, Gary Mazz <garymazzaferro(a)gmail.com> wrote: > >> Hi, >> >> This is the doodle link to vote on a time and date to discuss Sam >> Johnston's proposal to move OCCI attributes elusively to HTTP headers. >> >> Participation by experts in web caching and RESTful implementations is >> requested and appreciated >> >> cheers >> gary mazz >> >> Thijs Metsch wrote: >> >>> Sounds interesting...but Sept 25 doesn't work for me... >>> >>> Gary can you Maybe create a doodle for this event? >>> >>> Thanks, >>> >>> -Thijs >>> >>> On Wed, 2009-09-23 at 09:01 -0600, Gary Mazz wrote: >>> >>> >>>> I' like to schedule a meeting to discuss Sam Johnston's proposal to move >>>> OCCI attributes elusively to HTTP headers. >>>> >>>> I'd like to schedule this conference on friday Sept 25, 2009, the as >>>> time as the weekly call. >>>> >>>> We need to fully understand the mapping of the attributes to the http >>>> protocol structures and the impacts to the specification. >>>> >>>> cheers, >>>> >>>> gary mazz >>>> >>>> >>>> _______________________________________________ >>>> occi-wg mailing list >>>> occi-wg(a)ogf.org >>>> http://www.ogf.org/mailman/listinfo/occi-wg >>>> >>>> >> _______________________________________________ >> occi-wg mailing list >> occi-wg(a)ogf.org >> http://www.ogf.org/mailman/listinfo/occi-wg >> >> > >

1 0

Walkthrough of the OCCI spec
by Thijs Metsch 24 Sep '09

24 Sep '09

Hi guys, Yesterdays call was pretty good and thanks for all the people helping and joining! Due to this call some issue arose all written down here: http://code.google.com/p/occi/issues/list We have a list of work items now. From 1-19. I'll work on 2, 14, 18 - But that leaves us with 16 more issues - volunteers? If possible I wanna 'fix' these issues for the next draft build on monday! Cheers, -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 at sun.com D-93049 Regensburg http://www.sun.com

1 0