September 2014 - occi-wg

Re: [occi-wg] OCCI-notifications
by Andy Edmonds 22 Dec '14

22 Dec '14

Guys, here a summary of the KIS approaches as discussed at OGF42 https://docs.google.com/presentation/d/1x3_exe7RD6orOhwRajFNJwXxgV1zXHIZR0W… Andy Andy Edmonds Æ Senior Researcher, ICCLab Institute of Information Technology Zürich University of Applied Sciences http://www.cloudcomp.ch, @dizz On 16 September 2014 12:17, Augusto Ciuffoletti <augusto(a)di.unipi.it> wrote: > I agree with you that notification should be considered as a model, as > an extension that introduces new resources and links, just like IaaS > Infrastructure. I guess that this gives us all the tools to produce an > effective model, without the side effects of introducing new core concepts. > > I do not agree about the limitations you address: this depends on how we > model the relevant concepts. If we'd use mixins, you could associate them > virtually to anything, but for the same reason they are weak in formulating > recommendations. So it is really relevant to use the right tool for a given > task. > > I hope to be able to propose my idea about that by the beginning of the > next week. Suggestions are always welcome. > > Augusto > > PS: thanks to all organizers and participants to the OGF sessions, for a > very productive and exciting meeting. In these times it is hard to find one > :-/ > > 2014-09-16 10:10 GMT+02:00 Jean Parpaillon <jean.parpaillon(a)free.fr>: > >> Hi Augusto, all, >> Thanks for all the interesting discussions in OGF, first. >> >> Regarding the notifications, we discussed 2 approaches: >> - the first include the notion of notification into the meta-model, with >> versions of it in each rendering/protocol >> - the second one add categories for a notification system, hence a model >> >> IMO, the second approach, hence simpler, has the problem of being >> limited to notifications on resources. I don't see how to plug >> notifications on collections, links or user mixins, for instance. >> >> Have I missed somthing ? >> >> Another possible approach should be to consider notifications only at >> the level of protocol, not touching meta-model. >> >> My opinion is we should first think about at which level we want to >> introduce this notion of notifications. >> >> Regards, >> Jean >> >> >> Le jeudi 11 septembre 2014 à 10:05 +0100, Augusto Ciuffoletti a écrit : >> > Dear all, >> > >> > >> > talking and listening to people here during OGF42, I perceived that >> > there is a strong demand for a notification mechanism inside OCCI, >> > that is able to carry an asynchronous notification about a relevant >> > event. For instance, "this job is now running" from an hypothetical >> > job resource, or "this VM is going to shut down in 5 seconds" from a >> > Compute. >> > >> > This demand is in fact more compelling than that about monitoring, and >> > may be in fact integrated in OCCI-monitoring at a later time. So I'll >> > give precedence to OCCI-Notification. >> > >> > >> > The specification is very simple: one single link ("Notification"), >> > and two types of mixins, one for the triggering event, one for the >> > triggered action. >> > >> > >> > Any "thumb up" or input from you is relevant, and I will submit soon a >> > proposal about that. >> > >> > -- >> > Augusto Ciuffoletti >> > Dipartimento di Informatica >> > Università di Pisa >> > 56100 - Pisa (Italy) >> > _______________________________________________ >> > occi-wg mailing list >> > occi-wg(a)ogf.org >> > https://www.ogf.org/mailman/listinfo/occi-wg >> >> -- >> Jean Parpaillon >> Open Source Consultant >> Phone: +33 6 30 10 92 86 >> im: jean.parpaillon(a)gmail.com >> skype: jean.parpaillon >> linkedin: http://www.linkedin.com/in/jeanparpaillon/en >> >> > > > -- > Augusto Ciuffoletti > Dipartimento di Informatica > Università di Pisa > 56100 - Pisa (Italy) >

3 6

OCCI SLAs branch in redmine
by Katsaros, Gregory 25 Sep '14

25 Sep '14

Dear all, an updated version (based on the discussions we had during the OGF42) of the OCCI SLAs extension draft is available in the OCCI WG redmine repository. You can find the latex document and related files within the occi-slas branch. Feel free to comment and contribute. Kind regards, Gregory -- Intel Corporation, Cloud and Services Lab --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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. --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 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: One-day Cloud Plugfest going on today!
by Sill, Alan 25 Sep '14

25 Sep '14

Reminder: we are holding a Cloud Plugfest today sponsored by the CloudWATCH project! Details at http://www.cloudwatchhub.eu/cloudwatch-cloud-plugfest-and-standards-profile… Chat room: http://webconf.soaphub.org/conf/room/cloudplugfest WebEx is also available - details at the link below: https://docs.google.com/a/egi.eu/document/d/1s_FTxsbbtSQw0jww179QT1772WwvYC… Send requests for other details and information to Michel Drescher <michel.drescher(a)egi.eu> Alan

1 1

Revision of the monitoring document
by Augusto Ciuffoletti 25 Sep '14

25 Sep '14

The "monitoring extension" document has been updated to take into account the "notification extension" document: in essence, part of the monitoring has been moved inside the notification document. This makes notification independent from monitoring, but the two are to some extent complementary. To enhance their being complementary, the description of the sensor resource has been made uniform with respect to the content of the notification document. The document has been uploaded in the monitoring branch of the repository (now in the root directory), and a pdf is attached. -- Augusto Ciuffoletti Dipartimento di Informatica Università di Pisa 56100 - Pisa (Italy)

1 0

Notes about OCCI Notification (occi-wg@ogf.org)
by Augusto Ciuffoletti (tramite Documenti Google) 19 Sep '14

19 Sep '14

Ho condiviso un contenuto con te: Notes about OCCI Notification https://docs.google.com/document/d/1_vf9Y0V5wjhdXWSapil0Bv3gJHRKe8cK5ZBxPv5… Non è un allegato, ma è memorizzato online. Per aprire il documento, fai clic sul link qui sopra. Dear all, here are the conclusions of yesterday's online discussion. Please comment the document if you like...

1 0

Corekube: Running Kubernetes on CoreOS via OpenStack
by Sill, Alan 17 Sep '14

17 Sep '14

Thought you would also be interested in the following link.This and the previous one show examples of needs for scheduling and controlling containers in various cloud infrastructure environments that we can think about when extending OCCI to these use cases. Topic: In this post, we will be reviewing how to deploy Kubernetes onto a cluster of CoreOS VM's via OpenStack to enable a management system for Docker containers. Specifically, we do so using the ease of OpenStack Heat, Rackspace Cloud Servers & Cloud Networks, CoreOS, its cloud-config model, as well as its etcd and fleet API's to not only lay down the infrastructure, but provision it accordingly. Link: https://developer.rackspace.com/blog/running-coreos-and-kubernetes/ Alan

1 0

Docker in CloudStack
by Sill, Alan 17 Sep '14

17 Sep '14

Thought you would be interested in the following link. Topic: Docker in CloudStack - initial thoughts Link: http://ngtuna.blogspot.com/2013/12/docker-in-cloudstack.html Alan

1 0

OCCI-notifications
by Augusto Ciuffoletti 16 Sep '14

16 Sep '14

Dear all, talking and listening to people here during OGF42, I perceived that there is a strong demand for a notification mechanism inside OCCI, that is able to carry an asynchronous notification about a relevant event. For instance, "this job is now running" from an hypothetical job resource, or "this VM is going to shut down in 5 seconds" from a Compute. This demand is in fact more compelling than that about monitoring, and may be in fact integrated in OCCI-monitoring at a later time. So I'll give precedence to OCCI-Notification. The specification is very simple: one single link ("Notification"), and two types of mixins, one for the triggering event, one for the triggered action. Any "thumb up" or input from you is relevant, and I will submit soon a proposal about that. -- Augusto Ciuffoletti Dipartimento di Informatica Università di Pisa 56100 - Pisa (Italy)

2 2

OGF 42 OCCI Sessions - thank you & notes
by Metsch, Thijs 15 Sep '14

15 Sep '14

Hi, Thanks to all of you for helping the last weeks and months preparing the sessions we just had at the OGF 42 event in London. Also many thanks to those who attended in person. Again: it is the community who uses, lives and defines the standard :-) Here are some rough meeting notes I took over the course of the OGF event. Excuses for the bit longer list - we had a total of 4 sessions with plenty of discussions. Many thanks again, -Thijs, Andy * Roadmap ** Plan to release update of the documents asap ** Ideally finish drafts next month - public comment later this year ** Note: Backward compatibility is key and must! * Introducing the errata of the Core spec. ** Walked through the updates made to the core specification ** Topics to be addressed: *** Required and Mutability members of 'Attribute' should be 1 *** Type of the Attributes should be Object, Hash, List * Introducing the errata of the Infrastructure spec. ** Topics to be addressed: *** Move over ssh key & user_data mixins into Master branch *** Add all error states to the enum of possible states. *** Update the usage of related according to core specification * Introducing the new ToC of the HTTP protocol spec ** Discussion of a new ToC was conducted and agreed upon. - to be circulated soon... ** Topics to be addressed: *** Allow 202 return code upon creation? *** pagination support *** Writeup import and export functionalities on collections to allow for interop between e.g. CIMI/TOSCA/OVF/... with OCCI *** Queries/Filters on the QI *** Queries/Filters on collections * Demo of visualizing OCCI entities and their relationships using D3 ** Gregory demoed the visualizations of any kind of OCCI entities relationship using D3 visual library. * Discussion of JSON rendering ** Topics to be addressed: *** Links of an entity should be fully rendered not a list of URIs *** TBC: addition of a pattern member to the attribute? * Introducing the SLA draft ** Topics to be addressed: *** State models require update with respect to actions available *** Name clashes for the attribute names in the terms needs to resolved *** Make note in spec: If one service term is violated the agreement is violated * Introducing the Platform draft ** Topics to be addressed: *** Add a set of generic mixins for e.g. databases - maybe take look at Bluemix for input help. * Introducing the Billing draft ** Needs to be written up as a spec. * Introducing Inter-PaaS ** TBC * OCCI Monitoring demo ** Augusto introduced his demo implementation of a Monitoring framework using OCCI ** It became clear sth like notification links can be useful - some writeup is under way... * erOCCI implementation/ OCCIware consortium updates ** Jean introduced the OCCIware consortium ** Gave a brief update on the erOCCI implementation * rOCCI discussions ** Boris quickly gave an overview of the rOCCI framework from client to server side. And noted the usage in EGI alongside the parts the rOCCI server can speak too (ONE, EC2, ...) * OCCI/DRMAA v2 bindings ** Meeting took place Wednesday ** Peter walked through the OCCI DRMAA draft specification and cleaned-up minor details ** Biggest change: *Sessions will be managed via HTTP not explicitly through OCCI entities. ** Started dummy implementation to validate the concepts. Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052

1 0

Fwd: Cloud Interop (@cloudinterop) mentioned you on Twitter!
by Sill, Alan 11 Sep '14

11 Sep '14

1 0