Hi everyone, our occi4java is now on github (https://github.com/occi4java/occi4java) under the LGPL license and we are ready to write an implementation experience guide, like: http://ogf.org/documents/GFD.176.pdf Are there any ideas about the content? It would be very helpful for us. Thanks in advance Sebastian Heckmann Sebastian Laag
Hi Sebastian, my colleagues and I would be very interested to help writing such an implementation guide. We could provide a section on our Ruby implementation and share our idea for handling namespaces by using a location registry. Together we might also come up with some best practice hints. Do you intend to attend the next SNIA Cloud Plugfest? Cheers, Florian Am 27.04.11 15:12 schrieb "Sebastian Heckmann" unter <sebastian.heckmann@uni-dortmund.de>:
Hi everyone,
our occi4java is now on github (https://github.com/occi4java/occi4java) under the LGPL license and we are ready to write an implementation experience guide, like: http://ogf.org/documents/GFD.176.pdf
Are there any ideas about the content? It would be very helpful for us.
Thanks in advance Sebastian Heckmann Sebastian Laag
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
Experience documents can be of any form, and there can be more than one if needed. Many projects take the step of doing this as part of the process of moving from a proposed to a full recommendation, and for that reason, often wait until collection of experiences from several different implementations can be gathered and published together. The process of moving from a P-REC to a REC is documented in GFD.152: http://ogf.org/documents/GFD.152.pdf (basically: 6 months, documentation of multiple implementations, evidence of community buy- in, etc.). Starting the draft process for your experience document might provide an opportunity for others to chime in. Alternatively, other people may choose to compile their own experiences separately in internal documents and the group can optionally gather them together into a larger document later. Other experience documents are available; search on "experience" in the page http://www.ogf.org/gf/docs/?final&all Hope this helps, Alan On Apr 27, 2011, at 8:12 AM, Sebastian Heckmann wrote:
Hi everyone,
our occi4java is now on github (https://github.com/occi4java/ occi4java) under the LGPL license and we are ready to write an implementation experience guide, like: http://ogf.org/documents/GFD.176.pdf
Are there any ideas about the content? It would be very helpful for us.
Thanks in advance Sebastian Heckmann Sebastian Laag
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
Alan Sill, Ph.D Senior Scientist, High Performance Computing Center Adjunct Professor of Physics TTU ==================================================================== : Alan Sill, Texas Tech University Office: Drane 162, MS 4-1167 : : e-mail: Alan.Sill@ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================
Hi all, On Wed, Apr 27, 2011 at 3:12 PM, Sebastian Heckmann <sebastian.heckmann@uni-dortmund.de> wrote:
Hi everyone,
our occi4java is now on github (https://github.com/occi4java/occi4java) under the LGPL license and we are ready to write an implementation experience guide, like: http://ogf.org/documents/GFD.176.pdf
It would be great to see work on an OCCI experience document!
Are there any ideas about the content? It would be very helpful for us.
In general, the goal of an experience document is to evaluate the viability of a proposed standards specification, and to inform an iteration of that spec to improve it. Towards that, an experience document should address the following points: - was the specification clear, understandable, complete, contradiction free etc? E.g., was the specification implementable without any further documentation, or were additional information from the OCCI mailing list needed which were not available in the spec itself? - were the resulting implementations interoperable with other implementations, without additional arrangements, code or configuration exchange, etc? IMHO it is important to realize that the experience document provides a crucial opportunity to improve the specification before it gets frozen in its final stage (OGF recommendation). Hope that helps, Andre.
Thanks in advance Sebastian Heckmann Sebastian Laag
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
-- So much time, so little to do... [Garfield]
participants (4)
-
Alan Sill -
Andre Merzky -
florian.feldhaus＠tu-dortmund.de -
Sebastian Heckmann