April 2010 - occi-wg - lists.ogf.org

Reminder concall today: 10am EDT, 4pm CET, 3pm BST, 7am PST
by Thijs Metsch 14 Apr '10

14 Apr '10

Hi, This will be just a short concall - I will only be able to host the call for about 20 minutes. We'll discuss some ongoing stuff regarding the spec - Please join by dialing in using this conference bridge: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Teleconferen… Thanks, -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

Logistics for Joint Cloud Demo Staging
by Hope Hines 08 Apr '10

08 Apr '10

All, The first staging for the Joint Cloud Demo will be from April 28 to 30, 2010 at the SNIA Technology Center in Colorado Springs, CO. For hotel information and driving directions to the SNIA Technology Center, please visit http://www.snia.org/tech_activities/tech_center/visitor_info/ . Please note that the SNIA Technology Center has moved to 4410 ArrowsWest Drive, Colorado Springs, CO 80907 and has a new phone number (719-694-1380). Please complete the doodle poll at http://www.doodle.com/g68t4f8p6xtq8frc for registering for the Joint Cloud Demo Staging event, so we have enough food and beverages for everyone. Please let me know if you have any questions. Thank you, Hope Olocity Corporation 1767 Denver West BLVD Suite A Golden, CO 80401 WK: 719-359-8898 Cell: 719-330-4685 www.olocity.com <mailto:Kurt.Krems@Olocity.com> Hope.Hines(a)olocity.com logo_email -- To unsubscribe, reply using "remove me" as the subject.

1 0

Demo Call today
by Mark Carlson 07 Apr '10

07 Apr '10

What: Cloud Demo coordination planning When: Wednesdays: 8amPT/9amMT/11amET Where: 866-545-5227 code 6300276# Agenda: JavaFX update - Mike http://cloud.r2ad.net/ OpenNebula update - Gary CDMI RI update - Mark Staging at the Colorado Springs tech center - Hope Google Group for Cloud Demo http://groups.google.com/group/cloud-demo -- To unsubscribe, reply using "remove me" as the subject.

1 0

Reminder concall tomorrow: 10am EDT, 4pm CET, 3pm BST, 7am PST
by Thijs Metsch 06 Apr '10

06 Apr '10

Hi, Our concall will be all about the OCCI spec and how to finalize them, now that the public comment phase is over. Please join by dialing in using this conference bridge: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Teleconferen… Thanks, -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

[Fwd: Call for Cloud/Grid Demos at OGF-29]
by Thijs Metsch 06 Apr '10

06 Apr '10

Hi @all, This is some great stuff happning so please have a look at this and circulate :-) Cheers, -Thijs > > All, > > Attached is a Call for Demos for OGF-29. > Right now, the OCCI and SNIA CDMI folks plan on participating. On > the last Cloud-Standards.org telecon, DMTF said they also wanted to > have a presence since OVF will almost definitely be used. > > The Open Cloud Consortium is also very interested. They are putting > together a cloud-based, Haiti disaster mitigation demo that they > would like to show-off. Since Bob Grossman is Chicago-based, I think > this makes for a good opportunity. > > Are there any other cloud or grid groups that we should target for recruitment? > > Kate: Is Nimbus interested in showing something? > > I'm sure we should send this to Raj Buyya -- Manjrasoft might want to > demo. We could also send this to all the usual industrial suspects > to see if we get any interest. > Best regards, > > --Craig -- 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

Re: [occi-wg] OCCI Editor Getting Started Guide (docs/README.txt)
by Andre Merzky 06 Apr '10

06 Apr '10

Hi Sam, all, ready to discuss licensing again? :-) here is an update from OGF28: first, we heard rumours that you may show up here - this would be great, not in the least so that we can discuss the licensing thingie F2F. Usually that is way more productive than endless mailing threads like this one, isn't it :) Anyway, I just wanted to tell you that we have been discussing the issues from the recent email exchanges (and I hope sincerely that these are the issues you are in fact concerned about) within the GFSG. So, there was some discussion to review the current IPR text, and to clarify those passages which seem, in your reading, to hide the fact/intent that using any amount of text from a GFD for documentation and any other purpose is legally perfectly fine: "...derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind..." We will be cross-checking with similar texts of other standards bodies, in particular including IETF, which seem to recently have updated their IPR texts as well, to remove some ambiguities. The OGF IPR was originally modeled after IETF's, and, IIRC, was basically reproducing the OGF IPR word by word. Further we have been discussing the point you raised that the state of OGF documents would be frozen in the case of OGF's disappearance. If this turns out to be a concern for the community, we will consider adding a clause which would release the documents into the public domain in the case of OGF's demise - we certainly don't want to hold anybody back in continuing to work with OGF documents in that case. Both of the above changes however need to be evaluated, and need to be approved by the OGF board. While we don't think this is a problem per se, this will need time to be changed. The OGF IPR is designed as it is to fulfil three goals: (a) support the production and consumption of standards, (b) ensure that OGF documents (i.e. documents released under OGF copyright) went through the OGF document process, and (c) secure OGF against legal litigations. The board will need to make sure that in particular (b) and (c) are not affected by the proposed changes. If this sounds overly bureaucratic to you: well, that is the way we work ;-) Please let us know if changes along those lines would make you sleep better :-D FWIW: for the same reasons as above (a-c), we do actually require that OGF documents are under full OGF copyright, and it does not seem likely that a proposal for dual licensing would find much support, if any. Looking forward to see you in Munich! Best, Andre. -- Nothing is ever easy.

10 27

Naming format for occi xsd file
by Gary Mazz 05 Apr '10

05 Apr '10

Hi, I'm writing the xsd files for occi as well as the rdfs definition. We will probably also end up with a number of xsd files, one for occi/xhtml5 another for xml or at the least, different versions of one. To keep the naming convention consistent, we need to agree on a combining the occi name, occi version, xsd name space (XML, RDFa, etc) and xsd version into a coherent naming rule. Suggestions are welcome :) cheers, gary

5 11

Cloud Computing Use Cases: A first step towards getting the discussion into prose
by Drussell4881 02 Apr '10

02 Apr '10

Based on the input received to date, work has begun on formulating the content to develop Version 4 of the Cloud Computing Use Cases White Paper: (http://groups.google.com/group/cloud-computing-use-cases) The initial draft of the definition of a SLA is written as follows: A service-level agreement is a legally-binding contract between a cloud service provider and a cloud service consumer. An SLA contains several things: A set of services the provider will deliver, a specific definition of those services, a set of metrics for ensuring the services are delivered, the responsibilities of the provider and consumer and an explanation of the consumer's options if the services are not delivered. As the SLA portion of the White Paper is developed, there is a need to add in and define elements to consider for a SLA, such as: - Factors which can impact a service - Metrics - Responsibilities of the Provider - Responsibilities of the Consumer - Non-Performance Options The full post can be viewed at http://su.pr/31mSBo . Look forward to your comments.

1 0