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

Mon Apr 4 02:59:40 CDT 2011

Sure, no problem. After 2pm CEST would be great.

-Alexander

Am 02.04.2011 um 12:40 schrieb Thijs Metsch:

> 
> @Alex: maybe we can Skype on Monday about this?
> 
> Cheers,
> 
> -Thijs
> 
> -----Original Message-----
> From: occi-wg-bounces at ogf.org on behalf of alexander.papaspyrou at tu-dortmund.de
> Sent: Fri 01.04.2011 22:28
> To: andy.edmonds at gmail.com
> Cc: occi-wg at ogf.org
> Subject: Re: [occi-wg] Validating the Cloud on, well, the Cloud
> 
> Hey Andy,
> 
> Am 01.04.2011 um 20:12 schrieb Andy Edmonds:
> 
> > Great stuff!!! Excellent idea, Alex!
> 
> thanks... :-)
> 
> > 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?
> 
> I'll have to stick my head together with Thijs, but it will probably boil down to splitting Thjis' code into two .py files -- one for the def test_<something> stuff, and one for the CLI / GUI handling. This needs to be done, because Thijs' code won't even compile on GAE (mostly because of awkward problems with "Exception as e" lines).
> 
> I'd rather stick to github for the code until we get a replacement for GridForge ;-) but I'm happy to move my code elsewhere... I don't know whether it would be ok for Thijs to move test_occi.py to github, though...
> 
> > 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.
> 
> Great. I guess Sam does not have time to give some love to the GAE HTML/CSS stuff, does he?
> 
> > I don't suppose you could throw a few lines together as the content of
> > a blog post?
> 
> Next week maybe. Currently, things are a bit packed...
> 
> Best,
> Alexander
> 
> 
> > 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
> 
> 