[occi-wg] OCCI Monitoring API

[Augusto Ciuffoletti]

Gary,

do you mean the "NIST RATAX metrics / sla meeting"?

Augusto

2013/1/14 Gary Mazz <garymazzaferro at gmail.com>

>  Hi Augusto,
>
> The NIST SAJACC group is meeting in DC this week. The results from that
> meeting may affect the specification. If you can wait another 2 weeks to
> see if there is any impact to your specification, it would be appreciated.
>
> b/r
> gary mazzaferro
>
>
> On 1/14/2013 8:08 AM, Augusto Ciuffoletti wrote:
>
> Dear all,
>
> the OCCI-monitoring document (https://www.writelatex.com/26835vgbcrc) is
> in public review since mid-december, and untouched. So I think it's time to
> freeze it (following Alan suggestion) as an intermediate revision of a
> future document. I'd like to open a discussion about it, so that it can be
> checked-in during the first days of February.
> Topics are:
>
> -) Type of document we aim to (white paper, recommendation,
> specification), of which this one will be an initial revision;
> -) Formatting (standard, free);
> -) Authors
>
> I wait for your valuable opinions...
>
> Thank you for your attention
>
> Augusto
>
> 2012/12/19 Augusto Ciuffoletti <augusto at di.unipi.it>
>
>> Dear all,
>>
>> following the extremely fruitful meeting in Zurich, here is the revision
>> of the proposed document. A few anticipations about the content:
>>
>>    - the concepts are always the same: abstraction from short-lived
>>    details using mixins, extract/aggregate/publish pipe for the measurements
>>    - the syntax is different: I tried to make it simpler and more
>>    powerful: only 2 kinds in the model (one resource and one link), but the
>>    monitoring infrastructure may be hierarchical from 0 to n levels
>>    - a section about conformance levels has been added: the monitoring
>>    API is optional, so we need to define a level 0 to avoid confusion. The
>>    other two levels corresponds to the capability of creating user mixins
>>    (level 2) or not (level 1)
>>    - there is a detailed example of a simple case using an HTTP rendering
>>
>> You can directly interact with the LaTeX document if you like, though the
>> pdf is attached as well.
>>
>> The LaTeX document is available on a specific collaboration platform:
>> www.writeLatex.com. It is possible to update the document, but I ask you
>> to follow these simple instruction, to avoid to lose the control of the
>> document. If you want to add a note, please use the \rem command, whose
>> usage is described by the following example:
>>
>> \rem{Augusto Ciuffoletti}{My comment goes here}
>>
>> placed near the sentence you want to comment. A footnote will be
>> generated ("My comment goes here"), signed with your id ("Augusto
>> Ciuffoletti").
>>
>> You can access the document here https://www.writelatex.com/26835vgbcrcwithout authentication needed. The browser window is divided into two
>> parts: on one side you can edit the source, on the other you see the
>> updated document view. You can also download the pdf or a zip of the
>> current state of the document. There is no "revision history", so it is
>> impossible to "undo" a change.
>>
>> Augusto
>>
>> --
>> Augusto Ciuffoletti
>> Dipartimento di Informatica
>> Università di Pisa
>> 56100 - Pisa (Italy)
>>
>
>
>
> --
> Augusto Ciuffoletti
> Dipartimento di Informatica
> Università di Pisa
> 56100 - Pisa (Italy)
>
> _______________________________________________
> occi-wg mailing listocci-wg at ogf.orghttps://www.ogf.org/mailman/listinfo/occi-wg
>
>
>
> _______________________________________________
> occi-wg mailing list
> occi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/occi-wg
>
>


-- 
Augusto Ciuffoletti
Dipartimento di Informatica
Università di Pisa
56100 - Pisa (Italy)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/occi-wg/attachments/20130114/1fc6ca69/attachment-0001.html>