Donal, I think that your statement is both incorrect and unjustified. There is much value in CIM for both provisioning and runtime management. There is complexity there also - since the managed environment is quite complex. If you would care to expand further on what is wrong with CIM, I would be happy to address the issues with you. BTW, as regards the requirements of a Job, these can indeed be modeled/associated as instances of SoftwareResource in CIM V2.9. Just because the info is not in JSIM does not mean that it is not in CIM. Andrea
-----Original Message----- From: owner-jsdl-wg@gridforum.org [mailto:owner-jsdl-wg@gridforum.org] On Behalf Of Donal K. Fellows Sent: Thursday, November 11, 2004 2:36 AM To: Ali Anjomshoaa Cc: JSDL WG Subject: Re: [jsdl-wg] Re: Matching JSDL Terms to Other Specs
Ali Anjomshoaa wrote:
Thanks for looking at the intersection of the two though. A useful exercise I think.
I think the key lesson is that we don't need to worry about what's going on in CIM or JSIM; they address a completely different stage of the job lifecycle (i.e. after submission) to JSDL (which is a description of what the submitter wants the job to do and what it needs in order to do it). This is probably a good thing; I've heard many things about CIM and "the roach motel of data integration" was among the more polite... :^)
Donal.