<H1>VOSpace Brainstorm Meeting</H1> %TOC% --- This is a set of notes made during a meeting to brainstorm ideas on VOSpace. Those present in the meeting were: * WilliamOMullane, GuyRixon, KeithNoddle, Dave Morris, NoelWinstanley, TonyLinde and on the following telecon: * RoyWilliams, JohnGood, MatthewGraham See also: * http://www.ivoa.net/internal/IVOA/IvoaGridAndWebServices/vostore0.15.pdf ---++ Presentations We pretty much made up the agenda as we went along but included a couple of MySpace presentations from AstroGrid people: * MySpace structure & scenarios (Dave Morris): [[%ATTACHURL%/FileStore.html][FileStore.html]], [[%ATTACHURL%/FileManager.html][FileManager.html]] * Security aspects (GuyRixon): [[%ATTACHURL%/vospace-security.ppt][ppt]], [[%ATTACHURL%/vospace-security.pdf][pdf]] ---++ Notes ---+++ Dave's <nop>FileStore presn * in Export: MIME type allowed for data conversion (eg FITS to jpeg) * as yet no negotiation * question of about how dumb is the VOStore * contains metadata per item but does not interpret them * but must do so to implement security * <nop>MyDB vs MySpace: * MySpace returns exact file put in * <nop>MyDB will translate into database and back again * so need to include flag that says 'store exactly' * VOSpace vs VOStore * Wil: implement only VOStore first * AG: <nop>FileStore is dumb and <nop>FileManager has all intelligence (incl who owns items) * coffee discussion * need layer above <nop>FileStore to implement security * VOBroker * but AG could just plug this into its <nop>FileStore --> VOStore ---+++ Dave's <nop>FileManager presn * do we want to introduce replica management into the spec at this stage * for now, AG only implements http protocol for filestore * but could implement other protocols * need to define minimum set of protocols * if http, need to ensure security * need protocol negotiation * minimum: * SOAP with DIME attachment, * HTTP * needs to allow security * VOSpace will support N protocols * will address many underlying filestores * client agent can state which protocol it wants to use * VOSpace will only pass back stores which support that protocol ---+++ Guy's Security presn * Wil: users don't care about how security is implemented * Guy: implementers of VOStores will * SAML as language for tickets? * yes, but not only option * issue of which tickets are needed for an activity * requires policy store/check * look at Shibboleth / PERMIS ---+++ Later discussion * decided we do not need to standardise on VOSpace for now, just VOStore (see Agreements below) ---+++ Telecon * ---++ Arguments * whether we need transformation (RESOLVED with VOStore capabilities) * mandatory if you are putting from file to database * metadata must indicate capabilities of store ---++ Agreements * still only need VOSpace and VOStore layers * VOStore is higher level than AG <nop>FileStore * do *not need VOSpace* protocol at this point * just need common definition of VOStore * includes list method * includes callback api (to know when asynch action finished) * projects implement own VOSpace * will look to standardise afterwards * VOStore will advertise its capabilities * eg ability to return data in given format * AG filestore (currently) will only return in format uploaded * AG will extend filestore to support VOStore * <nop>MyDB will allow return in VOTable, CSV, FITS * ticket-based security looks like way to go * subject to trial (see below) ---++ Action list * Wil: send Dave latest version of VOStore: *end of this week* * Dave: update VOStore doc with new methods: *before May Interop* * synch/asynch * init & data * get & put * Guy/Wil: get prototype security mechanism working: *before May Interop* <br><br><br> <!-- * Set ALLOWTOPICRENAME = %MAINWEB%.TWikiAdminGroup -->
This topic: IVOA
>
TonyLinde
>
VOSpaceBrainstormMeeting
Topic revision: r5 - 2005-03-07 - TonyLinde
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback