- occi-wg - lists.ogf.org

OCCI - SNIA coordination
by Mark A. Carlson 15 Jul '09

15 Jul '09

Not sure if folks have already seen this, but this is the reference model that the SNIA has come up with for describing the CDMI interface. It would be great if folks that are working on the storage aspects of OCCI could read and understand how the storage industry is approaching this. I will try and make next week's call (I didn't realize the time was moved up this week) if anyone has questions about this model. Thanks, -- mark

1 0

Status of OCCI - Welcome to all newcomers!
by Thijs Metsch 15 Jul '09

15 Jul '09

Hi @all, As of today we got more than 170 members on the mailing-list and 30 members for our gridforge project. First of all thank you all and welcome to OCCI! With this email I want to welcome everybody who recently joined and give a short update of what we are currently up to! The group started as Cloud API earlier this year (March) and got a constant grow from there on. In the beginning we actively discuss the charter and the very basics of our RESTful API. At OGF26 we presented our progress and we try to present a first implementable draft by OGF27 later on this year. So we will be one of the first standardized APIs in the Cloud area. If you want to know who is involved (and maybe add your own name) have a look at our Memberslist in the Wiki (Can be found via http://www.occi-wg.org) Currently we are writing up the documents - that is the reason why the discussions on the mailing-list have stalled a little bit. For a current status do not hesitate to look at our gridforge page and have a look in the SVN. If you want to get involved have a look at http://www.occi-wg.org. There you will find links to our Meeting-materials, Press releases, Presentations, collaboration efforts with other groups etc. Our weekly teleconference call is scheduled every Wednesday @4pm CET. If you have questions, ideas or want a more detailed status update feel free to join! I am looking forward to hear you there! You can find all the details howto connect in the Wiki! All the best, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds Software Engineer Grid Computing Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

1 0

Reminder: weekly concall tomorrow @4pm CET
by Thijs Metsch 15 Jul '09

15 Jul '09

Hi guys, Just a short reminder that we have our weekly concall tomorrow. Information about your timezone and the teleconference bridge information can be found here: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Teleconferen… I do not have agenda yet but will create on until tomorrow! All the best, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds Software Engineer Grid Computing Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

1 1

LinkedIn API Presentation
by Randy Bias 10 Jul '09

10 Jul '09

Just wondering if folks saw this: http://blog.linkedin.com/2009/07/08/brandon-duncan-java-one-building-consis… --Randy Randy Bias, Cloud Strategist +1 (415) 939-8507 [m], randyb(a)neotactics.com BLOG: http://cloudscaling.com

1 0

Priorities of the requirements
by Thijs Metsch 09 Jul '09

09 Jul '09

Hi, I started working on the document which will describe the use cases and requirements. Therefore I need to add priorities to each of the requirement we have. I would lik to ask you to have a look at our Use Cases and then at our requirements and then edit the 'Priority' field. The requirements Wiki page can be found here: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Requirements Valid values would be either High, Medium or Low. I will start soon adding my thoughts on this issue. But feel free to edit the Wiki page yourself! We will also discuss this on our next concall! All the best, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds Software Engineer Grid Computing Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

1 0

OCCI Latest Draft
by Sam Johnston 07 Jul '09

07 Jul '09

Morning all, I've been doing some more work on the draft over the weekend and today as I hope to have it in good condition in time for the various cloud interop events next week. It's finally starting to take shape now that extensions (e.g. state machines), attributes and registries (e.g. HTTP status codes) have been added, even if they're a long way from finished. The OCCI Core profile is generic and can be used with any resource, while OCCI Infrastructure defines compute, network and storage nouns (with attributes that are designed to be both extensible and trivially mapped to txt, json and xml formats) as well as extensions for relevant functionality like state machines. Anyway the GridForge subversion repository just blew up and my local version doesn't build any more so given it's after 4am already I'm going to call it a day and send what I have so far by mail (attached). The master's DocBook v5 but there's HTML, XML-FO and PDF renderings too... I'll fix the subversion repository tomorrow so others can get in on the action. If you do plan to contribute though, please bear in mind that I am making personal contributions available under CC-BY-SA in addition to the standard OGF terms which I consider far too restrictive. I'd very much rather other editors follow my example so as the spec is not inextricably bound to any single organisation, as is customary for other cloud APIs (e.g. GoGrid, Sun Cloud API). Thanks, Sam

7 19

Weekly OCCI concall - Wednesday July 8, 2009 at 4pm CET
by Thijs Metsch 06 Jul '09

06 Jul '09

Hi all, Our next weekly concall is scheduled for this wednesday @ 4pm CET! IMPORTANT: Please see the new time! - We will start one our earlier from now on! So our weekly concalls will be on Wednesdays @4pm CET! For the conference bridge and the time in your timezone see: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Teleconferen… The agenda is set to: 1. API status 2. Draft of the OCCI Spec. 3. Draft of the OCCI Use case and requirements document You can add your topics here: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Concall20090… Hope to hear you all on Wednesday, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds Software Engineer Grid Computing Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

1 0

Opinion Poll: IaaS or PaaS ?
by Gary Mazz 03 Jul '09

03 Jul '09

Sam Johnston's timely IaaS feature matrix brings up some interesting issues, one in particular, what are the specific features that can be included in an IaaS. Many of the IaaS provider are also providing one or more operating systems while other are providing closer to bare metal. Is the OS part of the Infrastructure or part of the Platform ? The question is: " Do operating systems belong in IaaS or PaaS. " Please lets us know you opinion -cheers gary mazz

9 30

IMPORTANT: Scheduling our weekly concalls
by Thijs Metsch 03 Jul '09

03 Jul '09

Hi Guys, I already heard from numerous sources that they would like to have the concalls on another day and time. Therefore I would like to ask you to put you best day and time in this doodle event: http://doodle.com/2eq3pxf6ufk9z3rt Currently the dates are for next week but for us the day and time is more important. You can set the timezone in above the table of participants...Consensus based we will then move our concalls to the best fitting day and time. So please help and state your best timeframe! All the best, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds Software Engineer Grid Computing Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

5 6

Categories Internet-Draft (was Re: Templates)
by Sam Johnston 01 Jul '09

01 Jul '09

On Sun, Jun 28, 2009 at 10:44 PM, <shlomo.swidler(a)gmail.com> wrote: > On Sun, Jun 28, 2009 at 3:48 AM, Sam Johnston<samj(a)samj.net> wrote: > > The categories were derived from Atom so in dropping it for individual > > resources we're going to have to reinvent it (think HTTP headers). > <snip> > I would prefer to have the categories implemented in the HTTP headers > for single-resource responses. > Ok so I've written up an IETF Internet-Draft ( draft-johnston-http-category-header-00<http://tools.ietf.org/html/draft-johnston-http-category-header-00>) which specifies a Category: HTTP header based on atom:category (that is, with a term and optional scheme and label). This means there's one less resason to use Atom for individual resources. I've also devised (but not yet documented) a simple, intuitive mechanism for updating (or at least suggesting updates) to these metadata headers. Although we can't reference I-Ds directly from the OCCI standard (as they're only valid for 6 months from the most recent revision), even if it doesn't proceed to a permanent status the content is also available under the usual OGF IPR rules and CC-BY-SA <http://creativecommons.org/licenses/by-sa/3.0/>for good measure. Sam Internet Engineering Task Force S. Johnston Internet-Draft Australian Online Solutions Intended status: Experimental July 1, 2009 Expires: January 2, 2010 Web Categories draft-johnston-http-category-header-00 Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on January 2, 2010. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info) Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Abstract This document specifies the Category header-field for HyperText Transfer Protocol (HTTP), which enables the sending of taxonomy information in HTTP headers. Johnston Expires January 2, 2010 [Page 1] Internet-Draft Abbreviated Title July 2009 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3 2. Categories . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. The Category Header Field . . . . . . . . . . . . . . . . . . . 4 3.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 4.1. Category Header Registration . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 6. Internationalisation Considerations . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 Appendix A. Notes on use with HTML . . . . . . . . . . . . . . . . 7 Appendix B. Notes on use with Atom . . . . . . . . . . . . . . . . 7 Appendix C. Acknowledgements . . . . . . . . . . . . . . . . . . . 8 Appendix D. Document History . . . . . . . . . . . . . . . . . . . 8 Appendix E. Outstanding Issues . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9 Johnston Expires January 2, 2010 [Page 2] Internet-Draft Abbreviated Title July 2009 1. Introduction A means of indicating categories for resources on the web has been defined by Atom [RFC4287]. This document defines a framework for exposing category information in the same format via HTTP headers. The atom:category element conveys information about a category associated with an entry or feed. A given atom:feed or atom:entry element MAY have zero or more categories which MUST have a "term" attribute (a string that identifies the category to which the entry or feed belongs) and MAY also have a scheme attribute (an IRI that identifies a categorization scheme) and/or a label attribute (a human-readable label for display in end-user applications). Similarly a web resource may be associated with zero or more categories as indicated in the Category header-field(s). These categories may be divided into separate vocabularies or "schemes" and/or accompanied with human-friendly labels. [[ Feedback is welcome on the ietf-http-wg(a)w3.org mailing list, although this is NOT a work item of the HTTPBIS WG. ]] 1.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, [RFC2119], as scoped to those conformance targets. This document uses the Augmented Backus-Naur Form (ABNF) notation of [RFC2616], and explicitly includes the following rules from it: quoted-string, token. Additionally, the following rules are included from [RFC3986]: URI. 2. Categories In this specification, a category is a grouping of resources by 'term', from a vocabulary ('scheme') identified by an IRI [RFC3987]. It is comprised of: o A "term" which is a string that identifies the category to which the resource belongs. o A "scheme" which is an IRI that identifies a categorization scheme (optional). Johnston Expires January 2, 2010 [Page 3] Internet-Draft Abbreviated Title July 2009 o An "label" which is a human-readable label for display in end-user applications (optional). A category can be viewed as a statement of the form "resource is from the {term} category of {scheme}, to be displayed as {label}", for example "'Loewchen' is from the 'dog' category of 'animals', to be displayed as 'Canine'". 3. The Category Header Field The Category entity-header provides a means for serialising one or more categories in HTTP headers. It is semantically equivalent to the atom:category element in Atom [RFC4287]. Category = "Category" ":" #category-value category-value = term *( ";" category-param ) category-param = ( ( "scheme" "=" <"> scheme <"> ) | ( "label" "=" quoted-string ) | ( "label*" "=" enc2231-string ) | ( category-extension ) ) category-extension = token [ "=" ( token | quoted-string ) ] enc2231-string = <extended-value, see [RFC2231], Section 7> term = token scheme = URI Each category-value conveys exactly one category but there may be multiple category-values for each header-field and/or multiple header-fields per [RFC2616]. Note that schemes are REQUIRED to be absolute URLs in Category headers, and MUST be quoted if they contain a semicolon (";") or comma (",") as these characters are used to separate category-params and category-values respectively. The "label" parameter is used to label the category such that it can be used as a human-readable identifier (e.g. a menu entry). Alternately, the "label*" parameter MAY be used encode this label in a different character set, and/or contain language information as per [RFC2231]. When using the enc2231-string syntax, producers MUST NOT use a charset value other than 'ISO-8859-1' or 'UTF-8'. 3.1. Examples NOTE: Non-ASCII characters used in prose for examples are encoded using the format "Backslash-U with Delimiters", defined in Section 5.1 of [RFC5137]. Johnston Expires January 2, 2010 [Page 4] Internet-Draft Abbreviated Title July 2009 For example: Category: dog indicates that the resource is in the "dog" category. Category: dog; label="Canine"; scheme="http://purl.org/net/animals" indicates that the resource is in the "dog" category, from the "http://purl.org/net/animals" scheme, and should be displayed as "Canine". The example below shows an instance of the Category header encoding multiple categories, and also the use of [RFC2231] encoding to represent both non-ASCII characters and language information. Category: dog; label="Canine"; scheme="http://purl.org/net/animals", lowchen; label*=UTF-8'de'L%c3%b6wchen"; scheme="http://purl.org/net/animals/dogs" Here, the second category has a label encoded in UTF-8, uses the German language ("de"), and contains the Unicode code point \u'00F6' ("LATIN SMALL LETTER O WITH DIAERESIS"). 4. IANA Considerations 4.1. Category Header Registration This specification adds an entry for "Category" in HTTP to the Message Header Registry [RFC3864] referring to this document: Header Field Name: Category Protocol: http Status: standard Author/change controller: IETF (iesg(a)ietf.org) Internet Engineering Task Force Specification document(s): [ this document ] 5. Security Considerations The content of the Category header-field is not secure, private or integrity-guaranteed, and due caution should be exercised when using it. 6. Internationalisation Considerations Category header-fields may be localised depending on the Accept- Johnston Expires January 2, 2010 [Page 5] Internet-Draft Abbreviated Title July 2009 Language header-field, as defined in section 14.4 of [RFC2616]. Scheme IRIs in atom:category elements may need to be converted to URIs in order to express them in serialisations that do not support IRIs, as defined in section 3.1 of [RFC3987]. This includes the Category header-field. 7. References 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2231] Freed, N. and K. Moore, "MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations", RFC 2231, November 1997. [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. [RFC3864] Klyne, G., Nottingham, M., and J. Mogul, "Registration Procedures for Message Header Fields", BCP 90, RFC 3864, September 2004. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource Identifiers (IRIs)", RFC 3987, January 2005. [RFC4287] Nottingham, M. and R. Sayre, "The Atom Syndication Format", RFC 4287, December 2005. [RFC5137] Klensin, J., "ASCII Escaping of Unicode Characters", RFC 5137, February 2008. 7.2. Informative References [OCCI] Open Grid Forum (OGF), Edmonds, A., Metsch, T., Johnston, S., and A. Richardson, "Open Cloud Computing Interface (OCCI)", <http://purl.org/occi>. [RFC2068] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", Johnston Expires January 2, 2010 [Page 6] Internet-Draft Abbreviated Title July 2009 RFC 2068, January 1997. [W3C.REC-html401-19991224] Raggett, D., Hors, A., and I. Jacobs, "HTML 4.01 Specification", <http://www.w3.org/TR/1999/REC-html401-19991224>. [W3C.WD-html5-20090423] Hyatt, D. and I. Hickson, "HTML 5", April 2009, <http://www.w3.org/TR/2009/WD-html5-20090423>. [draft-nottingham-http-link-header] Nottingham, M., "Web Linking", draft-nottingham-http-link-header-05 (work in progress), April 2009. [rel-tag-microformat] Celik, T., Marks, K., and D. Powazek, "rel="tag" Microformat", <http://microformats.org/wiki/rel-tag>. Appendix A. Notes on use with HTML In the absence of a dedicated category element in HTML 4 [W3C.REC-html401-19991224] and HTML 5 [W3C.WD-html5-20090423], category information (including user supllied folksonomy classifications) MAY be exposed using HTML A and/or LINK elements by concatenating the scheme and term: category-link = scheme term scheme = URI term = token These category-links MAY form a resolveable "tag space" in which case they SHOULD use the "tag" relation-type per [rel-tag-microformat]. Alternatively META elements MAY be used: o where the "name" attribute is "keywords" and the "content" attribute is a comma-separated list of term(s) o where the "http-equiv" attribute is "Category" and the "content" attribute is a comma-separated list of category-value(s) Appendix B. Notes on use with Atom Where the cardinality is known to be one (for example, when retrieving an individual resource) it MAY be preferable to render the Johnston Expires January 2, 2010 [Page 7] Internet-Draft Abbreviated Title July 2009 resource natively over HTTP without Atom structures. In this case the contents of the atom:content element SHOULD be returned as the HTTP entity-body and metadata including the type attribute and atom: category element(s) via HTTP header-field(s). This approach SHOULD NOT be used where the cardinality is guaranteed to be one (for example, search results which MAY return one result). Appendix C. Acknowledgements The author would like to thank Mark Nottingham for his work on Web Linking [draft-nottingham-http-link-header] (on which this document was based) and to the authors of [RFC2068] for specification of the Link: header-field on which this is based. The author would like to thank members of the OGF's Open Cloud Computing Interface [OCCI] working group for their contributions and others who commented upon, encouraged and gave feedback to this draft. Appendix D. Document History [[ to be removed by the RFC editor should document proceed to publication as an RFC. ]] -00 * Initial draft based on draft-nottingham-http-link-header-05 Appendix E. Outstanding Issues [[ to be removed by the RFC editor should document proceed to publication as an RFC. ]] The following issues are oustanding and should be addressed: 1. Is extensibility of Category headers necessary as is the case for Link: headers? If so, what are the use cases? 2. Is supporting multi-lingual representations of the same category(s) necessary? If so, what are the risks of doing so? 3. Is a mechanism for maintaining Category header-fields required? If so, should it use the headers themselves or some other mechanism? Johnston Expires January 2, 2010 [Page 8] Internet-Draft Abbreviated Title July 2009 4. Does this proposal conflict with others in the same space? If so, is it an improvement on what exists? Author's Address Sam Johnston Australian Online Solutions GPO Box 296 Sydney, NSW 2001 Email: samj(a)samj.net URI: http://samj.net/ Johnston Expires January 2, 2010 [Page 9]

2 2