Hi all,
this is a reminder about the special session entitled "*Experiences with
OCCI*" that we want to schedule during Closer 2016 (Rome, April 23-25
2016). The deadline for paper submission expires on February 10. If you
want to report and discuss about an adoption, or propose a new application,
you still have more than three weeks to put it on paper and send to us.
All relevant infos are now on Closer site in a dedicated page
<http://closer.scitevents.org/OCCI.aspx>, or in our flier
<https://dl.dropboxusercontent.com/u/1327309/Closer_OCCI_2016.pdf>.
Thank you
Augusto
2015-12-10 16:45 GMT+01:00 Augusto Ciuffoletti <augusto(a)di.unipi.it>:
> Dear all,
>
> there will be a special session dedicated to OCCI during the "Closer 2016"
> conference that will take place in Rome, near to the end of April. The
> session is intended to gather results and proposals about the Open Cloud
> Computing Interface: adoption stories are specifically appreciated, but
> also proposals for extensions, new applications and tools.
>
> The deadline for submission is on February, and you find a flyer with the
> schedule and further info at http://tinyurl.com/clocci16.
>
> Augusto
>
> --
> Augusto Ciuffoletti
> Dipartimento di Informatica
> Università di Pisa
> 56100 - Pisa (Italy)
>
--
Augusto Ciuffoletti
Dipartimento di Informatica
Università di Pisa
56100 - Pisa (Italy)
Hi,
We've had a discussion during last OCCI-wg session in Roma about the
way to specify entity ids.
As specified in current documents, entity ids can be specified in
different ways _at the same time_ at creation time and implementations
behaviour is not specified.
I suppose we should consider either removing different ways to specify
ids either specify implementation behaviour.
Here are the different ways the can be specified:
* JSON rendering:
* 'id' attribute in JSON document
* 'occi.core.id' attribute in the 'attributes' property of the JSON
document
* HTTP protocol:
* PUT request: url of the request + rendering specific (see above)
* POST request: rendering specific
In general, for renderings where core attributes are rendered
differently from others (id, source, target, etc), it is not specified
how to deal with attributes being set twice.
A suggestion will follow in a next e-mail. For me, the most important
being to avoid ambiguities as to improve implementations
interoperability.
Regards,
--
Jean Parpaillon
--
Open Source Consultant
Director @ OW2 Consortium
OCCIware Strategic Orientation Committee Chairman
Research Engineer @ Inria
--
Phone: +33 6 30 10 92 86
im: jean.parpaillon(a)gmail.com
skype: jean.parpaillon
linkedin: http://www.linkedin.com/in/jeanparpaillon/en
Hi all,
I am co-chair for the Utility and Cloud Computing (UCC) 2016 program committee in December of this year and will be general chair for the one we are co-hosting (UCC 2017) the following year in Austin, Texas USA. UCC 2016 will be in Shanghai and UCC 2018 (the year after the one we are hosting in Austin) will most likely be in Zurich.
There are good possibilities to build in good cooperation between OGF and these conferences, and perhaps to co-host workshops, plugfests or data-oriented activities also with this and the usually associated Big Data Science, Engineering and Applications (BDSEA) conferences that are frequently co-located with the UCC conferences.
Jus wanted to poll the group here on this topic, and pass on the Call for Papers and related information about the web sites. If we want to do plugfests or have any associated activities, now is the time to speak up in order to get these included in the plans and to get started on preparations. Please speak up if you are interested and/or can help.
http://computing.derby.ac.uk/ucc2016/http://computing.derby.ac.uk/bdsea2016/
Alan
