[occi-wg] Validating the Cloud on, well, the Cloud

[Thijs Metsch]

nice! Thanks for the effort!

On Apr 1, 2011, at 8:12 PM, Andy Edmonds wrote:

> Great stuff!!! Excellent idea, Alex!
> 
> Quick question (I'm thinking the answer will be longer! :p) - is there
> anyway to integrate both your and Thijs' code base so they don't run
> out of sync?
> 
> On logos etc - If anyone needs various OCCI branding just drop me a
> line. I'll soon get all various branding and logos up on the main
> website.
> 
> I don't suppose you could throw a few lines together as the content of
> a blog post?
> 
> Andy
> 
> On 1 Apr 2011, at 19:58, "alexander.papaspyrou at tu-dortmund.de"
> <alexander.papaspyrou at tu-dortmund.de> wrote:
> 
>> Folks,
>> 
>> in a moment of boredom, I rewrote Thijs' OCCI testing tool to run in Google App Engine (GAE).
>> 
>> Please take a look at
>> 
>> http://doyouspeakocci.appspot.com
>> 
>> for the application (and, of course, try your service) and see
>> 
>> https://github.com/lxndrp/doyouspeakocci/
>> 
>> for the source code of the application.
>> 
>> The code is largely undocumented, but not very difficult to understand, if you are (like me) a fairly bad Python programmer and ever heard of Django Templates. If you find anything that you wish to improve, feel free to do so. A few rules of thumb for this:
>> 
>> 1. Although the code is released under LGPL2, I consider it "AdviseWare": when making an improvement, let me know where I was too stupid to get it right in the first place.
>> 2. Remember that GAE has certain restrictions in what can be done and how you can do it. See http://code.google.com/intl/de-DE/appengine/docs/ for details.
>> 3. Before making a change, create a ticket in the GitHub tracker.
>> 4. During making a change, remember to add some documentation (for new classes and defs) or at least comments (close to your change).
>> 5. After making a change, enjoy the fuzzy feeling of having contributed to the community.
>> 
>> Even if you are not a Python developer, you can help out: the pages served by the application look, ahem, bad. So if you happen to be an HTML/CSS expert, your help is more than appreciated. Ultimately, the testing tool should look similar to the web pages at http://occi-wg.org (ask Andy whether you can feel free to steal stuff from there for the GAE app!).
>> 
>> Hoping you will enjoy the tool, my mind demands some rest now and advises me to be off for a few beers.
>> 
>> Best,
>> Alexander
>> 
>> 
>> _______________________________________________
>> occi-wg mailing list
>> occi-wg at ogf.org
>> http://www.ogf.org/mailman/listinfo/occi-wg
> _______________________________________________
> occi-wg mailing list
> occi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/occi-wg