I think we need a summary of registry usage, so we make some informed choices. A detailed API like document might help.
* Registry GFac Descriptions (Host, Application, Service) * generated Service WSDL's * Workflow Documents (XBaya XWF Dag, WSDl's, Inputs, Outputs) * Workflow executions and ingested inputs and generated outputs * any others missed from above Any one volunteering to take a stab at all operations we will need? I do not want to volunteer and be a blocker, I know I will not be able to get to it in the next 3, 4 days at the earliest. Suresh On Sep 8, 2011, at 10:05 PM, [email protected] wrote: > Hi, > > Right now, the design of GFAC is that it has the Registry Interface i.e. > save and load HostDescription, list of HostDescription with a given service > name, etc. The only implementation, we have now, is JCR (Jack Rabbit), which > does fine for simple operations e.g. query, insert, update. delete. > > With the current design, I think we can plug in XRegistry (by implementing > the Registry Interface using XRegistry client) if we want to. But, we might > need to change some part of XRegistry to work with this interface. > > Patanachai > > On Thu, Sep 8, 2011 at 9:03 PM, Suresh Marru <[email protected]> wrote: > >> On Sep 8, 2011, at 8:50 PM, Marlon Pierce wrote: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> What's the status of the JCR work? >> >> I will let others chime in, but as far as I can tell (mostly from JIRA >> tickets and commits), GFac is fully using JCR. XBaya is using to some >> purposes but not all. Before we get to a release, the only (or big) missing >> development item (other than documentation and test cases) is to tie the >> loose ends of registry usage. But it will be nice to focus on one API and >> JCR seems to be the way to go. Having XRegistry into the mix might add >> unnecessary complexity (especially with legacy Grid Security tightly >> integrated). >> >> Suresh >> >>> >>> >>> Marlon >>> >>> >>> On 9/8/11 8:35 PM, Suresh Marru wrote: >>>> Hi All, >>>> >>>> Since we decided to move towards JCR compatible registries [1] [2] >>>> and build over out of the box open source solutions like jack >>>> rabbit, I see no reason for us to maintain XRegistry. I suggest we >>>> move it to attic (or delete it) and deprecate support for it from >>>> GFac and XRegistry. >>>> >>>> Opinions? >>>> >>>> Cheers, Suresh >>>> >>>> [1] - http://goo.gl/UWPeq [2] - >>>> https://issues.apache.org/jira/browse/AIRAVATA-73 >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG/MacGPG2 v2.0.16 (Darwin) >>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >>> >>> iQEcBAEBAgAGBQJOaWLPAAoJEOEgD2XReDo5QLcH/Ak3mZDhSbI2a6NfEmhhbASp >>> iXPmBhDT7FWS7zS2lzDoBvuRY3HXx8vCGTTYZ7GPahs+nmtZ5taik3Enpb4cfVcn >>> R4m5q5vQ5dTSby2h1GUe22hmWvp/4imWwZsMEdt69XF8M/ctZb4av0m1MhPr5R0w >>> yLVa5yg0SeRXZqoLAbFBENuHGhwwSvSKVrArdvPH2X6qFa5LFEDSqiHBdvYQ4/JR >>> cYbzhiTlhRisd1zV4oMjRBQYUgBNw6kMnw8l685bQLguQlbTBMVnhLcJf2Od3KHg >>> +PG69ooxSV14dOgU0UxxTNumw6D7xlNGIGUuz7QewZrqN2so2LH6XerZw0ZPymk= >>> =CqmT >>> -----END PGP SIGNATURE----- >> >> > > > -- > Best Regards, > Patanachai Tangchaisin
