Difference between revisions of "FrenchSitesInputtoTEGOp"
(→What takes the most effort?) |
(→Strategic directions you would like to recommend) |
||
| Ligne 25: | Ligne 25: | ||
=== What can be dropped?=== | === What can be dropped?=== | ||
| − | === Strategic directions you would like to recommend=== | + | === Strategic directions you would like to recommend=== |
| + | * Middelware compatibilities with the larger set of technical constraints (yaim/quattor, NAS/SAN storage infrastructure,...) (IN2P3-LAPP) | ||
=== Other comments=== | === Other comments=== | ||
Version du 13:23, 10 novembre 2011
Sommaire
Input provided by french sites
Scope
- Middleware operational requirements
- Example topics: log files, error messages, manageability, robustness, system requirements, documentation
- Service and middleware configuration
- Example topics: puppet, quattor, yaim...
- Service and middleware deployment
- Example topics: Packaging, upgrade paths, release schedules, rollout policy
- Middleware distribution
- Example topics: Distros - EMI, EPEL, UMD, OSG, repositories, OS support, source availability
What is in use currently and works well?
Top problems
- Too many information on logfiles or finding the good information on log file is too hard (IN2P3-LAPP)
What takes the most effort?
- Middelware dependency understanding (IN2P3-LAPP)
What can be improved about operational procedures?
What can be dropped?
Strategic directions you would like to recommend
- Middelware compatibilities with the larger set of technical constraints (yaim/quattor, NAS/SAN storage infrastructure,...) (IN2P3-LAPP)
