Principles

Strategies

Tactics

Constraints

Maximize science/$

Find a project that will allow more open systems with less extra cost

Coordinate grid work and support across PPDG according to all these priniciples

Security in the same style as Integrated Safety Management

Involve security and sysadmin people early

Don't push security boundaries
- or-

Push security boundaries but accept extra costs (monitoring staff, etc.)

Don't require uniformity of:

Hardware

Systems (batch, mss,…)

Network & disk access site config

[EDG principle opposite – require extreme uniformity]

Create awareness of grid in facility people

Obtain site admin buy-in (when PPDG is only a small player)

Only adiabatic changes are possible for facilities

Network & disk access policies are site specific and not driven by grid projects

Obtain uniformity of:

Grid middleware interfaces

Make VDT useful/correct/complete

Install VDT

LCG does not use pure VDT

Grid middleware interfaces must be flexible enough to support innovation at facility level

Work with Grid groups to ensure IF's well defined

Identify core vs less crucial services

Minimize # supported site configurations – because validation of applications is very heavyweight

Promote common linux distributions to the extent possible;

….

Only adiabatic changes are possible for experiments

Interoperate with LCG and other peer grids with useful resources

Influence LCG development

Keep PPDG development projects fully conversant with LCG projects

Do not require specific implementations of any service

Urge reasonable stability and upwards compatibility of grid middleware interfaces

Be chary of requiring root privileges as part of Grid services

Provide very detailed documentation of:

Expectations of grid from site

Expectations of site from grid

Drive software to production quality

Be accountable for grid resources: usage by group, identity of troublemakers