September 2012 - occi-wg

Dasein Cloud
by Thijs Metsch 23 Jun '13

23 Jun '13

Hi, Just to inform you that there is a cool project going on called Dasein-Cloud. http://dasein-cloud.sourceforge.net/ On the website it reads: Dasein Cloud is an Open Source Java API made available by enStratus Networks LLC under the terms of the Apache License 2.0. This API specifies cloud-independent interfaces for enabling an application to access resources across multiple clouds. If you are interested have a look - and it might be great to implement OCCI in their someday! Cheers, -Thijs -- Thijs Metsch Senior Software Engineer Grid and Cloud Technology Platform Computing GmbH Europaring 60 D-40878 Ratingen http://www.platform.com http://www.nohuddleoffense.de/ - http://www.twitter.com/befreax

3 2

TelCo next week
by Feldhaus, Florian 29 Oct '12

29 Oct '12

Hi, I just spoke with Thijs and we would suggest to skip the TelCo today and encourage everyone to join the TelCo next week 18:00 CET. We would like to discuss all remaining issues with the OCCI Core and OCCI JSON documents and then prepare them for submission to the OGF review process. It is very important, that everyone checks the documents again. The latest versions of the documents can be found here: http://redmine.ogf.org/projects/occi-wg/repository/revisions/core-errata/ch… http://redmine.ogf.org/projects/occi-wg/repository/revisions/json/changes/j… Cheers, Florian

5 9

OCCI JSON data format
by Feldhaus, Florian 02 Oct '12

02 Oct '12

After the discussion in the OCCI ConfCall Ralf and I went through the JSON document and identified open issues and how we would solve them. The result is attached as pdf and committed to the new JSON branch in the OCCI WG Git. Following is a short explanation of the design goals: * the overall design goal was to create a data format which is independent from the transport protocol * also important was a compact representation of all OCCI Entities as they may be exchanged very often * OCCI Categories could be verbose to describe the Model in detail * information should be easily accessible Some explanations on specific sections: 4.1 - for attributes the dot notation should be used and each namespace should be rendered as a separate object. This follows best practice in JavaScript to handle nested attributes and should help adoption. 4.2 - type identifiers as used for 'kind', 'mixins' and 'action_categories' are pointers to other objects within the OCCI Core scope and thus are rendered in the top level object. 4.2 - id is rendered in the top level object. The reason is, that id is a pointer to the object itself, thus it is not an attribute, but a OCCI Core property of the object itself comparable to 'self' in many programming languages. Besides it is difficult to specify rules on how id must be rendered if it is not in the top level object. 4.2 - links are represented by the URN of their id following RFC 4122. This is a more compact representation of the link as we had it before. Also it resembles the behavior of id. Thus it is rendered in the top level object 4.3 - source and target are also pointers to objects within the OCCI Core object scope. Thus they are rendered in the top level object. Similar to id it is difficult to specify rules on how source and target must be rendered if they are not within the top level object. 4.3 - the type identifier in 'rel' is a pointer to a OCCI Category and thus rendered in the top level object 4.4 - instantiated actions need to be represented in a format similar to that of OCCI Entities. Actions don't have an 'id' as they are only used once and are not persistent 4.5 - term, scheme, attributes, actions and related are OCCI Core properties of the 'kind' object and thus rendered in the top level scope 4.5 - location is transport protocol specific, but must be an URI. Each transport protocol must specify guidelines for location 4.7 - the action category format is used to define actions similar to kinds describing OCCI entities 4.8 - the attribute description format has been simplified. The general description of attributes went to 4.1. The attribute properties have been reduced to mutable, required, type, default and description. As Pattern complicated matters a lot it was removed. Cheers, Florian

3 5

Core errata
by Ralf Nyren 25 Sep '12

25 Sep '12

Dear all, I have update the Core document to include the changes discussed on the last few confcalls. The LaTeX changes are available from the core-errata branch in the occi-wg Git repository. Please find a compiled document attached. Add a Attribute type to the Core Model -------------------------------------- Many who have implemented the OCCI Core model already added an Attribute type. This change formalise the notion of "attribute properties". Instead of just saying an attribute have a name, an attribute now has its on Attribute type with both name an properties. The new Attribute type is an *identifier* for resource attributes. It does not contain the attribute value. I.e. just as before. A distinction has been added between "client discoverable attributes" (called OCCI Attributes) and attributes internal to the model (called model attributes). occi.core.id, occi.core.source and occi.core.target have been changed back to the model attributes they were until shortly before HTTP Rendering was released. These are determined to be model attributes and thus receive special care in renderings. Change Action to inherit Category --------------------------------- The concept of Action representing the "invocable operation" itself is removed. Instead an Action is just an *identifier* of the operation. An Action instance identifies an invocable operation in much the same way as a Kind instance identifies an Entity sub-type. Impact on the existing HTTP Rendering (occi/1.1) is none. In fact the text/ renderings already use "type=action" in its Category headers. regards, Ralf

5 11

OCCI F2F
by Edmonds Andrew (edmo) 25 Sep '12

25 Sep '12

Hi all, We have great experience with running dedicated OCCI workshops where various issues in the specification can be resolved quickly and easily. As not many can attend OGF36 or have calendaring conflicts, we would like to arrange one on November 13th (Tuesday) and host it in Zurich. Anyone is more than welcome to join so long as their willing to pull up their sleeves and get busy with specification work and related discussions. We will also arrange conference call facilities for those not able to attend. Further details to follow. Andy Andy Edmonds Senior Researcher Institute of Information Technology Zürich University of Applied Sciences http://www.cloudcomp.ch, @dizz

2 2

Re: [occi-wg] Question about OCCI meeting in near future
by Feldhaus, Florian 24 Sep '12

24 Sep '12

Hi, if you would like to participate in the Open Standards for Open Cloud session, we could discuss that with the organization team. If you tell me within the next 2-3 days, that someone from your group wants to participate I guess we still could arrange that. Regarding the status of OCCI, I would like to invite you to join the OCCI mailinglist: http://www.ogf.org/mailman/listinfo/occi-wg Within the OCCI WG we are currently working on a JSON rendering, a document regarding Monitoring & SLAs, integration of OCCI and AMQP and a document regarding PaaS. Besides that we organize 3-4 Cloud Plugfests a year which are intended to bring implementers and SDOs together to test their products and discuss specification details. More information regarding the plugfests can be found here: http://www.cloudplugfest.org/ Cheers, Florian Am 24.09.2012 um 11:17 schrieb Jazz Yao-Tsung Wang: > Hi, > > I saw "Open Standards for Open Cloud: Call for Participation" recently. > http://occi-wg.org/2012/08/15/open-standards-for-open-cloud-call-for-partic… > But I could not make it to send proposal to OCCI by the 10th of September 2012. > > Will there be further OCCI meeting scheduler in the end of 2012? > > We're from NCHC(National Center for High-peformance Computing), Taiwan. > We had been member of OGF during year 2006 to 2009 and will renew > membership recently. > http://www.gridforum.org/Members/members_org_program.php > > We have implemented a software named by "Ezilla" based on OpenNebula and OCCI. > We currently have a project about Cloud interoperability for next 2~3 years. > We would like to know more about OCCI current status and try to work > with OCCI working group. > > So look forward to know how could we join the community in near future. > > Regards, > Jazz Yao-Tsung Wang > Associate Researcher > Software Technology Division > National Center for High-performance Computing > NARL, Taiwan

2 1

OCCI-Monitoring paper
by Augusto Ciuffoletti 24 Sep '12

24 Sep '12

Hi all, enclosed you find the 7 pages paper about OCCI-Monitoring. While working at the OCCI-SLA/Monitoring draft, I realized that the whole issue was too much for a single document. The reason to modularize it is the same as for modularizing software: in a word, monolithic is bad. So I tried to describe monitoring in OCCI terms: there is a section that explains how this model interacts with the SLA, and with infrastructure resources, and the interface between them is sufficiently small to claim that the modularization was successful. My suggestion for managing the collaboration on this paper (whose source is in LaTeX, but that I send you as a pdf) is by email and annotations: there are many free tools that enable to annotate a pdf. I suggest "xournal" or "okular", that are supported by many platforms. You can annotate and send me the file that contains the annotations (.xoj for xournal). If you send your annotations to the list others --- using the appropriate tool --- can see your annotations. There are LaTeX collaboration platforms, but I think they are not useful at this stage. Augusto 2012/9/18 Augusto Ciuffoletti <augusto(a)di.unipi.it> > Before the end of this week I'll submit to the maillist a paper about > SLA/monitoring. I considered that the whole SLA+monitoring was too much for > a single document, and I concentrated on the monitoring part: the > connection with SLA is explicit, but the paper covers a generic monitoring > infrastructure, not specific for SLA. So the paper is not syntactically > derived from the old one, but it is aligned with it and should hopefully > give a sound basis for discussion. > > Further, I tried to adhere to the revision of the "core" document that > circulated in the maillist. > > Bye > > Augusto > > 2012/9/18 Metsch, ThijsX <thijsx.metsch(a)intel.com> > >> Hi all,**** >> >> ** ** >> >> There will be no call today as many of us are double and or tripple >> booked today.**** >> >> ** ** >> >> Next week we’ll pick up the calls again too hopefully finalize the JSON >> and SLA/Monitoring discussions.**** >> >> ** ** >> >> Cheers,**** >> >> ** ** >> >> -Thijs**** >> >> ------------------------------------------------------------- >> 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. >> >> _______________________________________________ >> occi-wg mailing list >> occi-wg(a)ogf.org >> https://www.ogf.org/mailman/listinfo/occi-wg >> >> > > > -- > Augusto Ciuffoletti > Dipartimento di Informatica > Università di Pisa > 56100 - Pisa (Italy) > -- Augusto Ciuffoletti Dipartimento di Informatica Università di Pisa 56100 - Pisa (Italy)

4 5

No conference call today
by Metsch, ThijsX 18 Sep '12

18 Sep '12

Hi all, There will be no call today as many of us are double and or tripple booked today. Next week we'll pick up the calls again too hopefully finalize the JSON and SLA/Monitoring discussions. Cheers, -Thijs ------------------------------------------------------------- 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 1

Reminder: conference call in 1h
by Metsch, ThijsX 11 Sep '12

11 Sep '12

Hi all, We'll have a quick conference call today to look at the open action items. Cheers, -Thijs Numbers: Austria 0820 4000 1503 Belgium 070 35 99 45 Canada 1 213 289 3444 France 0821 230 748 Germany 01803 001 178 Ireland 0818 270 007 Italy 848 390 166 Netherlands 0870 001 909 Poland 0801 003 533 South Africa 087 550 0375 Spain 902 885 318 Sweden 0939 2066 400 Switzerland 0848 560 190 United Kingdom 0844 4 73 73 73 United States 1 415 363 0833 More: http://pdf.powwownow.com/pdf/USA_en_pwn-dial-in-numbers.pdf PIN code: 698133 ------------------------------------------------------------- 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 1

CompatibleOne in OpenStack Design Summit: Please Vote!
by Jean-Pierre.Laisne＠bull.net 10 Sep '12

10 Sep '12

Dear all, Please Vote For CompatibleOne in OpenStack Design Summit We have proposed a talk for next OpenStack Summit in San Diego https://www.openstack.org/summit/san-diego-2012/vote-for-speakers/#172 The selection of speakers is now open to vote (Note: you need to be registered and at the end of the session, do not forget to close your ballot.) Many thanks, CompatibleOne Team

1 0