2009/5/18 Richard Davies <richard.davies@elastichosts.com>
I would also like to see the current AtomPub example extended with a few actual attributes on the nouns (e.g. cpu cores, memory size, storage size) and showing a few example actuators (e.g. server start/stop, etc) since I understand that they will also appear in the feed.
Ok so for attributes I have thus far been adding them directly to the atom <entry> elements to keep things nice and flat and the <content> free for other purposes (e.g. expanding on a simple OCCI description of a compute or network resource with DMTF/OVF and SNIA standard descriptors respectively). For example: <entry>
<id>...</id> <compute:cores>4</compute:cores> <compute:memory>16Gb</compute:memory> ... </entry>
If you're worried about burning 1's and 0's on namespaces then you can trim them back: <entry>
<id>...</id> <c:cores>4</c:cores> <c:memory>16Gb</c:memory> ... </entry>
For the state transition links you need a few things: - The link itself (URL) - A machine-readable identifier for the link (e.g. http://purl.org/occi/state#start) - A human-friendly identifier for the link in requested/local language (e.g. "Take Snapshot") How this looks in atom: <link title="Start" rel="http://purl.org/occi/state#start" href="
Note that anybody can create new transitions but those that may need to be interoperable would end up in our registries. Cheers, Sam (sending offline) Gary Mazz wrote:
Hi,
Can we see a concrete example of top level storage and network rendering with one layer of decomposition ? I'd like to know what it will look like, especially with links applied.
cheers
-gary
occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg