DS3 Planning Stage 01

The DS3 Stage01 Planning meeting has been held on Wed 23rd Feb 2005 in Leicester.

Participants

KeithNoddle, TonyLinde, ThomasBoch, AlasdairAllan, PaulHarrison, MarkusDolensky, SebastienDerriere, NoelWinstanley, RiccardoSmareglia, FabioPasian, KonaAndrews, FrancoisBonnarel, GarrySmith, MarcoLeoni

Agenda

10:00	Coffee
10:30	Intro	KN	pdf
10:40	Security	GR	.ppt
11:10	DashBoard	NW	.pdf
11:30	Workflows, Web Services ...	TB (for André Schaaff)	.pdf
12:30	Lunch
13:30	CEA	PH
14:00	Discussions	All
15:00	List requirements	All
15:15	Cycle 1 scope	KN/All
15:30	Summary and close	KN
15:30	Tea & Coffee

Presentations

see Agenda

Notes

KTN talk

Points covered:

• Review of scope and goals of VOTech.
• Division of work between AstroGrid, DS3 and DS4+.
• AstroGrid's project plan for software production.
• Brief list of non-functional goals.
• The EGEE (grid) problem.

GTR talk

Point covered in the talk:

• Review of broad requirements in security.
• Discussion of challenges and some techniques for meeting them; simple approaches to security don't meet all the requirements.
• Suggested outline architecture for VO security.
• List of jobs that might be done by DS3.

Points raised in discussion:

• We seem to need several different ways of SSO (SSH, p/w, X.509 from desktop) => probably have to build our own sign-on service.
• AEL: in security, cycle 1 is mainly planning for cycles 2+. Need to plan security roll-out by end of cycle 1, not at current meeting.

NW talk

Points covered in the talk:

• A desktop proxy for VO services. Desktop apps talk to proxy by XMLRPC.
• Proxy talks to the VO. Most programming languages can do XMLRPC => can use VO services without special delegate support.

Points raised in discussion:

* Java-Perl bridge is available: A::Inline::Java * Desktop was demonstrated using python desktop app that lists applications. Defeated by Windows, therefore not trivial to set up at present. * Suggested that the desktop part could run embedded in the VO, called remotely by XMLRPC (e.g. AA's use of XMLRPC in eSTAR). * Questions about whether the desktop's GUI is necessary. Can it be headless? If it's headless, can it be managed properly?

TB talk

Points covered in the talk:

• Web service goals, for Kyoto interop meeting: WS-I basic profile, VO Support interfaces,

some profile for using attachments.

• CDS goals for Vizier: looking at ADQL service and SOAP endpoint.
• Workflow: CDS planning a prototype of a workflow system.

Points raised in discussion:

• AEL: Vizier changes are really a production activity, but valuable enough to do in DS3 anyway. Unanswered questions about whether it extends AstroGrid DSA or is an alternative.
• AEL: does the proposed CDS workflow system this replace the AstroGrid WF system? TB doesn't have that information. AEL suggests concentrating on a graphical workflow editor.
• AEL: research into basic, new workflow language is not for DS3.
• NW: could use some research into enhancements for AstroGrid WF language; or, more likely, a new language at a higher level, and in addition to, the AstroGrid language.

PH talk

Points raised in the talk:

• Plans for standardizing CEA in IVOA.
• Some areas of possible enhancement in CEA.

Points raised in discussion:

• Some of CEA-related research is already happening in IVOA. Need to tie together the DS3 and IVOA work.
• Some benefit in refactoring CEA to work with Grid (WS-RF) parts.
• How does CEA fit with "real grids"? GTR: in general, CEA services make good facades for grids. Some issues concerning error recovery.

General discussion

• How many FTE in C1? KTN: probably ~5.
• Priority list: see KTN's notes.

DS3 Meeting 01 Actions

Number	Person	Action	Due Date
ds3.m01.01
ds3.m01.02

DS3 Stage 01 Assignments

Number	Person	Partner	Assignment	Deliverable	Due Date
ds3.s01.01	KeithNoddle	AstroGrid	Progress report for end of stage	Report	before next planning mtg
ds3.s01.02