Validating the Cloud on, well, the Cloud
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
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@tu-dortmund.de" <alexander.papaspyrou@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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
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@tu-dortmund.de" <alexander.papaspyrou@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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
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@tu-dortmund.de" <alexander.papaspyrou@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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
@Alex: maybe we can Skype on Monday about this? Cheers, -Thijs -----Original Message----- From: occi-wg-bounces@ogf.org on behalf of alexander.papaspyrou@tu-dortmund.de Sent: Fri 01.04.2011 22:28 To: andy.edmonds@gmail.com Cc: occi-wg@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@tu-dortmund.de" <alexander.papaspyrou@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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
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@ogf.org on behalf of alexander.papaspyrou@tu-dortmund.de Sent: Fri 01.04.2011 22:28 To: andy.edmonds@gmail.com Cc: occi-wg@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@tu-dortmund.de" <alexander.papaspyrou@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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
On the CSS etc AFAIK Sam's not particularly au fait with CSS - I'll ask. In the meantime, Thijs (correct me if wrong) has some CSS that mirrors colour schemes on the main website and is used in the OpenStack implementation. Andy -----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of alexander.papaspyrou@tu-dortmund.de Sent: Friday, April 01, 2011 9:28 PM To: andy.edmonds@gmail.com Cc: occi-wg@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?
On 1 Apr 2011, at 19:58, "alexander.papaspyrou@tu-dortmund.de" <alexander.papaspyrou@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
Next week maybe. Currently, things are a bit packed... Best, Alexander 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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
I'll add some CSS stuff to the test code... -Thijs -----Original Message----- From: occi-wg-bounces@ogf.org on behalf of Edmonds, AndrewX Sent: Tue 05.04.2011 14:54 To: alexander.papaspyrou@tu-dortmund.de; andy.edmonds@gmail.com Cc: occi-wg@ogf.org Subject: Re: [occi-wg] Validating the Cloud on, well, the Cloud On the CSS etc AFAIK Sam's not particularly au fait with CSS - I'll ask. In the meantime, Thijs (correct me if wrong) has some CSS that mirrors colour schemes on the main website and is used in the OpenStack implementation. Andy -----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of alexander.papaspyrou@tu-dortmund.de Sent: Friday, April 01, 2011 9:28 PM To: andy.edmonds@gmail.com Cc: occi-wg@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?
On 1 Apr 2011, at 19:58, "alexander.papaspyrou@tu-dortmund.de" <alexander.papaspyrou@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
Next week maybe. Currently, things are a bit packed... Best, Alexander 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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
Nice work! Ran the tests on my occi-py demo and got some unexpected failures. Thijs standalone test-program works fine. I did some digging and it appears some of the tests does not properly specify 'Accept: text/occi' where header rendering is expected. text/plain is the default now. Just to verify I changed back to text/occi as the default in my demo and then the tests went through. /Ralf On Fri, 01 Apr 2011 18:57:59 +0200, <alexander.papaspyrou@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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
An increasing number of the tests for Ralf's interface demo at http://www.nyren.net/api are failing using the appspot version... is this because of changes in the test code or changes in the implementation example? Thanks! Alan On Apr 2, 2011, at 2:55 PM, Ralf Nyren wrote:
Nice work!
Ran the tests on my occi-py demo and got some unexpected failures. Thijs standalone test-program works fine.
I did some digging and it appears some of the tests does not properly specify 'Accept: text/occi' where header rendering is expected. text/ plain is the default now. Just to verify I changed back to text/occi as the default in my demo and then the tests went through.
/Ralf
On Fri, 01 Apr 2011 18:57:59 +0200, <alexander.papaspyrou@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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ 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-834-5940 fax 806-834-4358 : ====================================================================
Sorry - this got re-sent by my mailer for some reason. Ralf already answered: we are waiting for updates to the GAppEngine client code, right? Alan On Oct 13, 2011, at 10:29 AM, "Alan Sill" <alansill@highenergy.phys.ttu.edu> wrote:
An increasing number of the tests for Ralf's interface demo at http://www.nyren.net/api are failing using the appspot version... is this because of changes in the test code or changes in the implementation example?
Thanks!
Alan
On Apr 2, 2011, at 2:55 PM, Ralf Nyren wrote:
Nice work!
Ran the tests on my occi-py demo and got some unexpected failures. Thijs standalone test-program works fine.
I did some digging and it appears some of the tests does not properly specify 'Accept: text/occi' where header rendering is expected. text/ plain is the default now. Just to verify I changed back to text/occi as the default in my demo and then the tests went through.
/Ralf
On Fri, 01 Apr 2011 18:57:59 +0200, <alexander.papaspyrou@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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ 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-834-5940 fax 806-834-4358 : ====================================================================
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
Going to update it today. -Alexander Am 13.10.2011 um 18:24 schrieb Sill, Alan:
Sorry - this got re-sent by my mailer for some reason. Ralf already answered: we are waiting for updates to the GAppEngine client code, right?
Alan
On Oct 13, 2011, at 10:29 AM, "Alan Sill" <alansill@highenergy.phys.ttu.edu> wrote:
An increasing number of the tests for Ralf's interface demo at http://www.nyren.net/api are failing using the appspot version... is this because of changes in the test code or changes in the implementation example?
Thanks!
Alan
On Apr 2, 2011, at 2:55 PM, Ralf Nyren wrote:
Nice work!
Ran the tests on my occi-py demo and got some unexpected failures. Thijs standalone test-program works fine.
I did some digging and it appears some of the tests does not properly specify 'Accept: text/occi' where header rendering is expected. text/ plain is the default now. Just to verify I changed back to text/occi as the default in my demo and then the tests went through.
/Ralf
On Fri, 01 Apr 2011 18:57:59 +0200, <alexander.papaspyrou@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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ 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-834-5940 fax 806-834-4358 : ====================================================================
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
-- Alexander Papaspyrou alexander.papaspyrou@tu-dortmund.de
participants (7)
-
Alan Sill -
alexander.papaspyrou＠tu-dortmund.de -
Andy Edmonds -
Edmonds, AndrewX -
Ralf Nyren -
Sill, Alan -
Thijs Metsch