Please refer to the updated version at: https://twiki.cern.ch/twiki/bin/view/EGEE/EGEEgLiteWorkPlans

Workplan for WMS and CE

TCG items for which no further short term (by the end of 2006) development action is currently planned:

• TCG Item 309/101:

- Support for VOviews in Glue schema for matchmaking was back-ported from glite 3.1 to glite 3.0 - tag sent to Integration and Testing last Friday, May 26th.

- G-PBOX service available for policy distribution and evaluation, already integrated with matchmaking, optionally removed. Can be re-added on request.

• TCG Item 302:

This is a "real" High Availability configuration for the WMS.

- Would need to be designed anew and implemented in LB, WMproxy, CE, assuming all back-end services (filesystem, database, Condor) are configured and test OK in their highly-available configuration.

- No plan for this currently.

TCG items for which short term (by the end of 2006) development action is planned (but not started yet):

• TCG Item 301:

Changes to the current round-robin machinery in the UI need to be agreed upon and specified. Once specified, can be implemented in ~1 month.

Developers involved: F. Pacini, A. Maraschini

• TCG Item 303:

"Hot standby" configuration of a pool of WMS services

- Clients will use the existing failover mechanism.

- Will need to configure a highly available database (MySQL) back-end.

- The 'filelists' used for internal communication need to be replaced with mailboxes that can be efficiently run on a distributed filesystem, shared among the nodes.

- One 'hot standby' node can be used to quickly replace a failed node. ~1 month of development, plus ~2 months of testing

Developers involved: F. Giacomini, M. Cecchi.

• TCG Item 304:

At least two bottlenecks in the current pipe:

- Matchmaking. Can add a 'bulk' matchmaking feature (same as "significant attribute" matchmaking in Condor). ~1 month of development, ~1 month of testing

Developers involved: S. Monforte, E. Martelli, requiring interaction with F. Giacomini.

- Submission to CE. This can be expedited via CREAM.

Developers involved: L. Zangrando, A. Dorigo

• TCG Item 306:

- File download: Jobwrapper and UI modifications are needed to download regular HTTP files, and to enable the deployment of customary WWW caches. This requires ~1 week of development, ~1 month of testing, plus integration of some WWW cache in site configuration.

Developers involved: A. Maraschini, M. Cecchi

- File upload: Need to determine whether this can be achieved via existing Data services. Otherwise, further specification and development is needed.

• TCG Item 310:

- Access to CE by restricted shell. Still need to define exactly which sommands should be allowed by the restricted shell. As long as outbound network connectivity from the WN and inbound network connectivity to the UI is granted, can be addressed by ~2 months of development, ~1 month of testing. If a network switchboard needs to be added, this will have to be provided by security.

-- Main.grandic - 27 Jun 2006