- occi-wg - lists.ogf.org

Reminder: Special SAJACC group talk Tuesday, March 29, 3:00 pm Eastern time (2:00 pm Central, noon Pacific)
by Sill, Alan 28 Mar '16

28 Mar '16

** REMINDER: Special SAJACC group call Tuesday March 29, 3:00 pm EDT / 2:00 pm CDT / 12:00 noon PDT ** ---------- Dear NIST SAJACC working group members and related groups, You are invited to attend a SAJACC group meeting to discuss comparisons of the OCCI version 1.1 and CIMI v1.2 standards-based API call sequences and OpenStack native API conducted by Mahesh Gurram. This comparison has been carried out using the methodologies resulting in Phase I and Phase II of the SAJACC project and could serve as a pilot and example for future tests of cloud services, standards and API comparisons using the SAJACC use case documentation methods. Mahesh has conducted this work as part of a Masters Degree project at Texas Tech University, with the hope that it will serve as a template for future work going forward. The meeting will take place Tuesday, March 29 at 3:00 pm Eastern Daylight Time. Join by Skype for Business at https://meet.ttu.edu/alan.sill/GUOS7M0P (Note the first round character in this sequence is an O as in "oh", and the second one is a zero.) Select the "join as guest" option and type your name to enter in order to see the slides. Or join by phone +1 (855) 834-4888 - Toll-free Conference ID: 8519016 Depending on interest from the group, the testbeds being used to conduct these comparisons can be made available for further similar SAJACC testing. We will discuss the technologies used for this work being made available by the National Science Foundation through its CloudLab and Chameleon projects and the NIST-oriented public work being conducted by the NSF Cloud and Autonomic Computing Center on behalf of NIST and other center members. Please join early if you can in order to establish the Skype for Business web connection. Alan for the SAJACC group leaders (Alan Sill, Eugene Luster and Brett Berlin) Alan Sill, Ph.D Interim Senior Director, High Performance Computing Center Site Director, NSF Center for Cloud and Autonomic Computing Adjunct Professor of Physics ==================================================================== : Alan Sill, Texas Tech University Office: Drane 162, MS 4-1167 : : e-mail: Alan.Sill(a)ttu.edu<mailto:Alan.Sill@ttu.edu> ph. 806-834-5940 fax 806-834-4358 : ====================================================================

1 0

Special SAJACC group talk Tuesday, March 29, 3:00 pm Eastern time
by Sill, Alan 26 Mar '16

26 Mar '16

Dear NIST SAJACC working group members and related groups, You are invited to attend a SAJACC group meeting to discuss comparisons of the OCCI version 1.1 and CIMI v1.2 standards-based API call sequences and OpenStack native API conducted by Mahesh Gurram. This comparison has been carried out using the methodologies resulting in Phase I and Phase II of the SAJACC project and could serve as a pilot and example for future tests of cloud services, standards and API comparisons using the SAJACC use case documentation methods. Mahesh has conducted this work as part of a Masters Degree project at Texas Tech University, with the hope that it will serve as a template for future work going forward. The meeting will take place Tuesday, March 29 at 3:00 pm Eastern Daylight Time. Join by Skype for Business at https://meet.ttu.edu/alan.sill/GUOS7M0P (Note the first round character in this sequence is an O as in "oh", and the second one is a zero.) Select the "join as guest" option and type your name to enter in order to see the slides. Or join by phone +1 (855) 834-4888 - Toll-free Conference ID: 8519016 Depending on interest from the group, the testbeds being used to conduct these comparisons can be made available for further similar SAJACC testing. We will discuss the technologies used for this work being made available by the National Science Foundation through its CloudLab and Chameleon projects and the NIST-oriented public work being conducted by the NSF Cloud and Autonomic Computing Center on behalf of NIST and other center members. Please join early if you can in order to establish the Skype for Business web connection. Alan for the SAJACC group leaders (Alan Sill, Eugene Luster and Brett Berlin) Alan Sill, Ph.D Interim Senior Director, High Performance Computing Center Site Director, NSF Center for Cloud and Autonomic Computing Adjunct Professor of Physics ==================================================================== : Alan Sill, Texas Tech University Office: Drane 162, MS 4-1167 : : e-mail: Alan.Sill(a)ttu.edu<mailto:Alan.Sill@ttu.edu> ph. 806-834-5940 fax 806-834-4358 : ====================================================================

1 0

Questions about OCCI Monitoring
by Vincent ZURCZAK 23 Mar '16

23 Mar '16

Hi, I have questions about OCCI Monitoring. I read the specifications [0] and the Slideshare's presentation [1] of Augusto Ciuffoletti. I would like some clarifications, just be sure I understand correctly the scope of this specification. In the same way than OCCI Infrastructure provides an API to create infrastructure resources (virtual machines, network configurations...), OCCI Monitoring allows to configure probes and measures collection. So, assuming I have a model of OCCI resources associated with the following Software architecture... ... that is to say machines, network and storage resources (IaaS), applicative resources (web server, application server, database - and assuming I wrote OCCI extensions for them), then OCCI Monitoring would allow me to configure their monitoring through a single (REST) API. One API to configure the monitoring of several cloud layers / providers. So far, so good, right? What is not clear to me for the moment is the following. Does this API also allow to request directly a sensor? Assuming I have a sensor that collect CPU usage, is it this same API that can give me the probe's value (i.e. the CPU usage at this specific moment)? This is not the same question than "can I implement a sensor / collector / publisher that makes my monitoring data available through a REST service" (to this, the answer is definitely yes). For what I understand, the answer is no. OCCI Monitoring is about monitoring configuration, not about monitoring itself. An API that implements OCCI Monitoring is not an API that exposes a probe as a REST service (or at least, it is not its spirit). This has the great advantage of letting users keep the rendering / analyzing tools they want. I was also wondering whether there were real implementations of OCCI Monitoring. I saw Augusto will present "Beyond Nagios - Design of a cloud monitoring system" in Rome, in April. Unfortunately, I will not be able to attend it. What level of maturity does it have? Best regards, Vincent. [ 0 ] : https://redmine.ogf.org/attachments/182/monitoring.pdf [ 1 ] : http://slideshare.net/AugustoCiuffoletti/2013-03-occimonitoring-26159563 -- Vincent Zurczak Linagora: www.linagora.com <http://www.linagora.com/> Twitter <https://twitter.com/VincentZurczak> Vincent Zurczak @ LinkedIn <http://fr.linkedin.com/pub/vincent-zurczak/18/b35/6a7> My Skype ID <callto://vincent.zurczak> My English blog <http://vzurczak.wordpress.com>

2 2

Fwd: Liaison Statement from ITU-T SG13 to OGF
by Sill, Alan 29 Feb '16

29 Feb '16

FYI. ITU-T likes to send its attachments as zip files. I have unzipped these to improve the likelihood that they will get through your email filters. The relevant page seems to be the second page of the second document, which puts forward a table in the form of a matrix of functionalities in the cloud computing area. Comments and ideas for a response from OGF would be welcome. Alan Begin forwarded message: From: "Kurakova, Tatiana" <tatiana.kurakova(a)itu.int<mailto:tatiana.kurakova@itu.int>> Subject: Liaison Statement from ITU-T SG13 to OGF Date: February 19, 2016 at 8:39:44 AM CST To: "Alan.Sill(a)ttu.edu<mailto:Alan.Sill@ttu.edu>" <Alan.Sill(a)ttu.edu<mailto:Alan.Sill@ttu.edu>> Cc: "Leo.Lehmann(a)bakom.admin.ch<mailto:Leo.Lehmann@bakom.admin.ch>" <Leo.Lehmann(a)bakom.admin.ch<mailto:Leo.Lehmann@bakom.admin.ch>>, "jamil.chawki(a)orange.com<mailto:jamil.chawki@orange.com>" <jamil.chawki(a)orange.com<mailto:jamil.chawki@orange.com>>, "Lu, Hui-Lan (Huilan)" <huilan.lu(a)alcatel-lucent.com<mailto:huilan.lu@alcatel-lucent.com>>, 이강찬 <chan(a)etri.re.kr<mailto:chan@etri.re.kr>>, "caiysh(a)ctbri.com.cn<mailto:caiysh@ctbri.com.cn>" <caiysh(a)ctbri.com.cn<mailto:caiysh@ctbri.com.cn>>, "TSB SG13 Secretariat, ITU" <tsbsg13(a)itu.int<mailto:tsbsg13@itu.int>> Dear Mr Sill, On behalf of ITU-T Study Group 13 Chairman, Mr Leo Lehmann, I am pleased to send you the communication from the ITU-T Study Group 13. Please find enclosed the Liaison Statement agreed by SG13 at its last meeting (30 November – 11 December 2015, Geneva) for OGF. It is for your action, please, preferably before 12 April 2015. Thank you for acknowledging the receipt. Best regards, Tatiana Kurakova Counsellor, Study Group 13 "Future networks including cloud computing, mobile and next-generation networks" International Telecommunication Union Place des Nations, CH-1211 Geneva, Switzerland Tel : +41 22 730 5126 Mobile : +41 79 2494834 tatiana.kurakova(a)itu.int<mailto:tatiana.kurakova@itu.int> www.itu.int<http://www.itu.int/> [cid:ebbb93cb-1f4a-46f6-a6b1-55aabf522257@default.ttu.edu]

2 1

Fwd: Unified Monitoring
by Augusto Ciuffoletti 24 Feb '16

24 Feb '16

FYI ---------- Forwarded message ---------- From: SourceForge Resources <sourceforge(a)resources.sourceforge.com> Date: 2016-02-23 16:58 GMT+01:00 Subject: Unified Monitoring To: augusto.ciuffoletti(a)gmail.com To view a web version of this message, click here <http://clicks.slashdot.org/c.html?ufl=d&rtr=on&s=x8pb08,2h5cv,54g,7zdr,51ie…> [image: SourceForge Resources] *Unified Monitoring - A Business Perspective * <http://clicks.slashdot.org/c.html?ufl=d&rtr=on&s=x8pb08,2h5cv,54g,lfl3,foh7…> [image: Learn More] <http://clicks.slashdot.org/c.html?ufl=d&rtr=on&s=x8pb08,2h5cv,54g,1g88,614l…> Download <http://clicks.slashdot.org/c.html?ufl=d&rtr=on&s=x8pb08,2h5cv,54g,aiu1,tsp,…> Virtualization, outsourcing, SaaS and cloud computing are creating fundamental changes, and ushering in an era in which enterprises distribute increasingly critical IT assets and applications across multiple service providers. These changes are rendering legacy monitoring tools, which have their roots in the computing environments of a decade or more ago, virtually useless. This paper explores today's computing trends and their monitoring implications in detail. *Download Now »* <http://clicks.slashdot.org/c.html?ufl=d&rtr=on&s=x8pb08,2h5cv,54g,1cj2,4pl5…> You are subscribed to SourceForge Resources as augusto.ciuffoletti(a)gmail.com To unsubscribe, click here <http://clicks.slashdot.org/functions/mailing_list.html?mid=4159327&submitac…> or send an email to: unsubscribe-6640(a)elabs10.com To ensure delivery to your inbox and to enable images, please add sourceforge(a)resources.sourceforge.com to your e-mail address book or safe senders list. SourceForge | 1660 Logan Ave. Ste A | San Diego, CA 92113 To view our Privacy Policy click here <http://clicks.slashdot.org/c.html?ufl=d&rtr=on&s=x8pb08,2h5cv,54g,lrsa,m3j5…> . -- Augusto Ciuffoletti Via Milano 118 38122 - Trento

1 0

Re: [occi-wg] latest revision of the OCCI rev 1.2 docs
by Metsch, Thijs 19 Feb '16

19 Feb '16

Hi, I'll push the document back into redmine this weekend for review by GFSG. I'll include those minor suggestions you have there. Thanks all, -Thijs From: behrens.cloud [mailto:behrens.cloud@r2ad.com] Sent: Friday, February 19, 2016 4:05 AM To: Metsch, Thijs <thijs.metsch(a)intel.com> Cc: occi-wg(a)ogf.org Subject: Re: [occi-wg] latest revision of the OCCI rev 1.2 docs Hello Thijs & All. Docs are looking good! When are comments due by? I have a couple of style related suggestions on the core document. On line 50, the "Open Cloud Computing Interface" could just be OCCI since the acronym has been defined earlier in the paragraph. Also, recently, I've been changing my writing style to avoid the use of passive voice. For example, on line65, it has the phase "can be interacted". That paragraph could be re-written: The OCCI Core specification consists of a single document defining the OCCI Core Model. OCCI interaction occurs through renderings (including associated behaviors) and is expandable through extensions. The copyright date should probably be 2016, I presume. I'm not sure I'm able to post to the occi-wg - please forward as needed. Thanks! Metsch, Thijs wrote: Hi all, Please have a close look at this document set which will become OCCI rev 1.2. A special thanks to all who contributed - but most importantly I want to thank and highlight Boris and Zdenek's work on this revision of the documents! Cheers, -Thijs Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de<http://www.intel.de> Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 _______________________________________________ occi-wg mailing list occi-wg(a)ogf.org<mailto:occi-wg@ogf.org> https://www.ogf.org/mailman/listinfo/occi-wg Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928

2 1

latest revision of the OCCI rev 1.2 docs
by Metsch, Thijs 28 Jan '16

28 Jan '16

Hi all, Please have a close look at this document set which will become OCCI rev 1.2. A special thanks to all who contributed - but most importantly I want to thank and highlight Boris and Zdenek's work on this revision of the documents! Cheers, -Thijs Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928

2 1

jOCCI usage
by João Paulo Forny 06 Jan '16

06 Jan '16

Hi, I'm developing a java job submission component that needs to speak OCCI with some cloud providers (Initially OpenStack with occi-os installed) to create and manage instances and found jOCCI-api. I'm very inclined to use it, but I can't get through authentication (Receiving HTTP 405 response code). There are several usage examples in their wiki on github, but none regarding Keystone. Before I get deeper into the problem I'm facing, am I in the wrong place for this kind of doubt? Is there anyone of jOCCI team that can give some help? Thanks in advance, João Paulo

1 0

Re: [occi-wg] OCCI Infrastructure 1.2 specification draft
by Boris Parak 21 Dec '15

21 Dec '15

Hello Philippe, thank you! I will add these to our Trello board for discussion. Cheers, Boris On Fri, Dec 18, 2015 at 4:51 PM, Philippe Merle <philippe.merle(a)inria.fr> wrote: > Hello, > > In the context of the OCCIware project (www.occiware.org) I implemented the > OCCI Infrastructure 1.2 specification draft. > Good news: OCCI Infrastructure 1.2 specification is implementable. > > During the implementation, I saw some typos into the specification draft but > also some potential semantics issues: > > 1) Typos and minor semantics issues are corrected in > https://github.com/occiware/occi-wg/commit/ce730cb74428d93a8bafb0b8b033b9d6… > > 2) In Figure 1 page 4: > - the type of occi.storage.size attribute is int when it is Float in > Table 8 page 8. > - there is an occi.compute.speed attribute which is not present in Table > 3 page 5. > - the occi.compute.share attribute of Table 3 page 5 is not present. > - *.state.message attributes are not present. > > 3) Figure 2 page 6 does not contain the new save action, i.e., a transition > from active state to active state. > > 4) The default of attributes is not explicitly defined in Table 5, 8, 10, > and 12. > Especially, the default value of *.state attributes must be defined, it > could be defined to inactive. > > 5) In Figure 10 page 12, there are two occi.compute.speed attributes. But > this attribute has been removed from Table 3. > > 6) At Line 262 and 272, it seems that the schema should contain > 'infrastructure/' in order to be coherent with other schemas defined in this > specification. > > 7) In Table 14, occi.compute.userdata must be immutable (not mutable) when > reading the associated description ("It cannot be updated"). > > 8) Page 17, the item "Removed occi.compute.speed attribute to Compute." > should be added. > > Hoping this could help to improve in progress OCCI 1.2 specifications. > > Best regards > Philippe Merle > Inria >

1 0

Fwd: OCCI Platform 1.2 specification draft
by Sill, Alan 21 Dec '15

21 Dec '15

Re-forwarding the following message with OCCI Platform specification 1.2 comments that came during the mailman outage. Alan Begin forwarded message: From: Philippe Merle <philippe.merle(a)inria.fr<mailto:philippe.merle@inria.fr>> Date: December 17, 2015 at 3:55:32 PM CST To: Boris Parak <xparak(a)mail.muni.cz<mailto:xparak@mail.muni.cz>>, "Sill, Alan" <alan.sill(a)ttu.edu<mailto:alan.sill@ttu.edu>>, <thijs.metsch(a)intel.com<mailto:thijs.metsch@intel.com>>, <andrew.edmonds(a)zhaw.ch<mailto:andrew.edmonds@zhaw.ch>>, <jens.jensen(a)stfc.ac.uk<mailto:jens.jensen@stfc.ac.uk>>, <Wolfgang.Ziegler(a)scai.fraunhofer.de<mailto:Wolfgang.Ziegler@scai.fraunhofer.de>>, "jean.parpaillon(a)inria.fr<mailto:jean.parpaillon@inria.fr>" <jean.parpaillon(a)inria.fr<mailto:jean.parpaillon@inria.fr>>, <enol.fernandez(a)egi.eu<mailto:enol.fernandez@egi.eu>>, <aloga(a)ifca.unican.es<mailto:aloga@ifca.unican.es>>, <sustr4(a)cesnet.cz<mailto:sustr4@cesnet.cz>>, <michel.drescher(a)egi.eu<mailto:michel.drescher@egi.eu>>, <David.Wallom(a)oerc.ox.ac.uk<mailto:David.Wallom@oerc.ox.ac.uk>> Subject: Fwd: OCCI Platform 1.2 specification draft -------- Message transféré -------- Sujet : OCCI Platform 1.2 specification draft Date : Thu, 17 Dec 2015 12:24:10 +0100 De : Philippe Merle <philippe.merle(a)inria.fr><mailto:philippe.merle@inria.fr> Pour : occi-wg(a)ogf.org<mailto:occi-wg@ogf.org> Hello all, In the context of the OCCIware project (<http://www.occiware.org>www.occiware.org<http://www.occiware.org>), I implemented the OCCI Platform 1.2 specification draft. This implementation is freely available at <https://github.com/occiware/ecore/tree/master/clouddesigner/org.occiware.cl…> https://github.com/occiware/ecore/tree/master/clouddesigner/org.occiware.cl…. Good news: OCCI Platform 1.2 specification is implementable and already implemented. During the implementation, I saw some typos into the specification draft but also some potential semantics errors. I corrected most of these issues in my copy of the specification draft. See corrections at https://github.com/occiware/occi-wg/commit/c049165ae45d90ca0ad36037df22ce64… About semantics issues: 1) At Line 78, the spec. defines that "ComponentLink Connects an Application instance to a hosting Component or connects two components.". Is it really wanted that a component link could connect two components? If yes, this intention must be explicitly written again in Section 3.3. If no, text "connects two components" must be removed. 2) Figure 1 at Page 4 must be updated (sorry I have not the right software to do the job): - Text "links" must be placed at the right side of the UML association betwen Resource and Link classes. - Text "source" must be placed at the left side of the UML association betwen Resource and Link classes. - Text "(from occi-core)" must be added into the Link class as it is already present in the Resource class. - The attribute 'state.message: String' may be added to the Application class. - The attribute 'state.message: String' may be added to the Component class. - ComponentLink class contains a 'state: Enum' attribute but this attribute is not discussed in Section 3.3 at Page 6. This attribute must be removed from the figure or discussed in Section 3.3. 3) At Line 97, 'application/' must be added into the scheme of actions of the Application kind. At Line 109, 'component/' must be added into the scheme of actions of the Component kind. If not done, then the two start actions (ditto for stop) will have the same identity (scheme+term) then this creates an ambiguity. 4) In Table 2, 4, 6 and 7, the default attribute of each attribute is not defined. Implicitly, I supposed that all these attributes have no default. But it will be better to specify this point explicitly in the OCCI Platform specification. 5) At Line 102, Application must be replaced by Component as this section talks about components. 6) In all other OCCI specification documents, schemes and terms are in lower case: - At Line 108, replace #Component by #component - At Line 116, replace #componentLink by #componentlink - At Line 157, replace #databaseLink by #databaselink 7) Lines 129 and 142, 'the applies attribute' must be replaced by 'the depends attribute'. 8) Figure 4 page 7: - replace 'term = apllication' by 'term = application' (this is just a typo) - replace 'related' by 'depends' two times (In OCCI Core 1.2, related has been replaced by depends and applies) Best regards Philippe Merle Inria

2 1