October 2011 - occi-wg - lists.ogf.org

Re: [occi-wg] Validating the Cloud on, well, the Cloud
by Ralf Nyren 11 Oct '11

11 Oct '11

Hi Alan, I do not think the Google apps test are updated. Last time I checked they where not 1.1 compatible. Thijs has uploaded proper OCCI 1.1 test suite to gridengine. Those test has 100% pass on both my demo and Thijs implementation. Alex, maybe take down the doyouspeakocci page until it has been updated? Regards, Ralf Alan Sill <alansill(a)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(a)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(a)ogf.org >>> http://www.ogf.org/mailman/listinfo/occi-wg >> >> _______________________________________________ >> occi-wg mailing list >> occi-wg(a)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(a)ttu.edu ph. 806-834-5940 fax 806-834-4358 : >==================================================================== > > > > >

1 0

OCCI hosting - server available.
by Michael Behrens 08 Oct '11

08 Oct '11

FYI: We can host additional OCCI test instances at the SNIA Labs if someone want to use that as a server (in a VM). I can host an OCCI test server on r2ad.net if that would be helpful. It's a CentOS platform. Thanks. - Michael B.

2 2

Update on work register to be given at DMTF CMWG meeting tomorrow
by Alan Sill 06 Oct '11

06 Oct '11

OCCI-WG folks, I am at the DMTF cloud management working group in-person meeting this week, attending on behalf of TTU. As part of this meeting I will give an update on the interoperability and work register items between OGF and DMTF tomorrow morning. At this point we are largely waiting for DMTF to complete work on their CIMI specification, especially on its core model and the associated representations (which we would call renderings), so we can see how these map to OCCI and other OGF standards if applicable. As you know, DMTF has published its work on CIMI and its related components as work-in-progress documents, information on which and downloadable copies of which are available at the corresponding public site: http://dmtf.org/standards/cloud There are also related efforts on cloud audit data and license management going on; see their press releases on these topics: http://dmtf.org/news/pressreleases At this point I plan to give the same talk, slightly updated to reflect new implementation information and OGF related work group plans, as you helped me to assemble for last month's SIENA meeting. That talk is still available at the previous URL: http://www.hpcc.ttu.edu/asill/cloud-standards/OGF33-SIENA-Cloud-Update.pdf Those of you involved with DMTF can feel free to send me information that can be related to the group; others can feel free to comment on the talk at the link above. (Any DMTF-specific information will not change the content of the talk as posted and will not change OGF standards processes or documents, but may help with MoU-level discussions.) Thanks Alan

1 2

Re: [occi-wg] Where is the scheme ?
by Ralf Nyren 06 Oct '11

06 Oct '11

Afaik no formal scheme has been defined yet. The upcoming json rendering provides more info in the query interface and could be a (although not optimal) candidate. When Andre set this up we decided on just returning an empty page as a sort of boolean indicator that the category is defined in the spec. Regards, Ralf Alan Sill <Alan.Sill(a)ttu.edu> wrote: >Revisiting this issue... I was testing some schemata today and stumbled acros a permissions error related to the lack of anything at > >http://schemas.ogf.org/occi/ > >That is fixed now, and all we have configured in the tree below is that both of the following URIs will return an empty (blank) document. > >http://schemas.ogf.org/occi/core >http://schemas.ogf.org/occi//infrastructure > >Is this correct, and are any further changes needed for consistency? > >Thanks, >Alan > > >On Apr 6, 2011, at 1:54 AM, Ralf Nyren wrote: > >> >> see below. >> >> On Wed, 6 Apr 2011 07:46:36 +0200, Andre Merzky <andre(a)merzky.net> wrote: >>> For >>> example, I placed an empty document at >>> http://schemas.ogf.org/occi/infrastructure, so that all GET operations >>> on that document return an HTTP 200 (OK). That provides a very simple >>> way to confirm the validity of OCCI identifiers, and also provides a >>> straight-forward way to register OCCI extensions (or rather, their >>> namespaces). >> >> Good idea! Maybe we should let this document include a short text that >> says the schema format is still in progress or something? >> >> There has been several discussion regarding exactly what should be found >> at the schema URIs but nothing has yet been specified. I believe it was >> said that the schema definition will have to wait until OCCI 1.1 has be >> properly finished. Andy, Thijs, to you remember the rough time plan for >> this? >> >>> One could also link the normative documents for the >>> extension at http://schemas.ogf.org/occi/infrastructure#specification; >>> one could verify the #target elements; etc. However, that is as of >>> yet unspecified AFAICS, and is likely a rather naive proposal, given >>> my somewhat limited knowledge of HTTP itself. >> >> There is a little problem with the fragment part of the URI, i.e. the >> #xxxx. According to the RFCs it is not part of the URL sent to the HTTP >> server. It is something that the client has to handle by itself. >> >> For example: >> - Clicking on the http://schemas.ogf.org/occi/infrastructure#compute URL >> in your favorite browser will yield an HTTP request as follows: >> GET /occi/infrastructure HTTP/1.1 >> >> - In other words the _whole_ infrastructure "document" will be retrieved. >> The client (in this case your browser) will attempt to translate the >> #compute part into something useful with regard to the content-type of the >> document received. In case of text/html it is to jump to the fragment >> marker in the document. >> - How to handle the URL fragments in a future OCCI schema definition must >> be defined together with the format. However it is still the client which >> has to do the processing. >> >> regards, Ralf >> >> _______________________________________________ >> occi-wg mailing list >> occi-wg(a)ogf.org >> http://www.ogf.org/mailman/listinfo/occi-wg >

1 0

OCCI Test Procedures
by Jamie Marshall 05 Oct '11

05 Oct '11

Dear All, I met with Florian Feldhaus yesterday at the Open World Forum and we discussed the existance of an OCCI implementation test suite. Is there any one that could point me in the right direction to find this so that I may validate an important piece of work that has been done using OCCI at its heart. Yours Sincerely Iain James Marshall CompatibleOne Accords Lead Expertise Manager Prologue

3 3

OCCI compliance tests updated
by Thijs Metsch 05 Oct '11

05 Oct '11

Just a quick note that the tests at gridforge [1] have been updated. Please note that it is not a replacement for your [unit/integration/system/...]tests of your OCCI implementation. Also note that this test suite also is not a proof for your OCCI implementation that it is 100% specification compliant. The tests generally follows the HTTP rendering specification. Ralf's and my implementation currently pass all tests. This does not mean that the tests are perfect - Ideas for improvements (we all love code) are welcome. Cheers, -Thijs [1] http://forge.ogf.org/sf/scm/do/viewRepository/projects.occi-wg/scm.occi_ wg

1 0

Where is the scheme ?
by Gary Mazz 04 Oct '11

04 Oct '11

Hi There is no scheme @ http://schemas.ogf.org/occi/ cheers, gary

7 15

Proposal: SLA Agreement, Negotiation, Execution
by Thijs Metsch 04 Oct '11

04 Oct '11

Hi, The attached document contains a proposal for monitoring and SLA handling with OCCI. Although described in one document they can be seen as separate features. This document still has some rough edges - and probably requires some other features/renderings like JSON to be implemented - but feel free to reply with you feedback. Or if you like directly edit the document here: https://docs.google.com/document/d/1nWqOHuwpDnMVDYzDx2VxZ2ym79aU1W4laqj6 -_FuYxs/edit?authkey=CI-lg6gJ&hl=en_US&authkey=CI-lg6gJ Please note that this message has been posted to graap-wg(a)ogf.org and occi-wg(a)ogf.org - please considered this when pushing the reply button (cross-posting warning). Looking forward to your feedback, -the authors

2 1

AUTO: Li Gong Liu is out of the office. (returning 2011-10-10)
by Li Gong Liu 04 Oct '11

04 Oct '11

I am out of the office until 2011-10-10. For emergency, please call me by 86-10-13466350820. Note: This is an automated response to your message "occi-wg Digest, Vol 31, Issue 1" sent on 4/10/11 20:53:52. This is the only notification you will receive while this person is away.

1 0

FW: [members] CIMI WIP Specifications Released
by florian.feldhaus＠tu-dortmund.de 04 Oct '11

04 Oct '11

FYI Am 30.09.11 20:53 schrieb "admin(a)dmtf.org" unter <admin(a)dmtf.org>: >DMTF Members, > >The Cloud Infrastructure Management Interface (CIMI) work-in-progress >specifications are now available for public review and comment at >www.dmtf.org/cloud <http://www.dmtf.org/cloud> . All DMTF members are >encouraged to review the specifications and provide feedback through the >DMTF Feedback Portal at http://www.dmtf.org/standards/feedback ><http://www.dmtf.org/standards/feedback> . > >CIMI is part of DMTF's overall cloud management efforts focused on >standardizing interactions between cloud environments by developing >specifications that help to achieve interoperable cloud management >between service providers and their consumers and developers. The CIMI >specs are the first specifications produced by DMTF's Cloud Management >Work Group (CMWG). > >Please be sure to stay tuned for additional announcements from other DMTF >cloud-related groups, including the Cloud Auditing Data Federation (CADF) >Work Group. > >For more information on DMTF cloud management, visit www.dmtf.org/cloud ><http://www.dmtf.org/cloud> . Thank you- we look forward to hearing your >input and feedback through the above portal. > >Best Regards, >DMTF >

2 1