Difference between revisions of "FrenchSitesInputtoTEGOp"
(→Input provided by french sites) |
(→Input provided by french sites) |
||
| Ligne 2: | Ligne 2: | ||
| − | === | + | === Input for WG4 - WG 5 === |
* '''Middleware operational requirements''' | * '''Middleware operational requirements''' | ||
| Ligne 16: | Ligne 16: | ||
| − | + | ==== What is in use currently and works well?==== | |
| − | |||
| − | === What is in use currently and works well?=== | ||
* Quattor (FC) | * Quattor (FC) | ||
| − | === Top problems=== | + | ==== Top problems==== |
* Too many information on logfiles or finding the good information on log file is too hard (IN2P3-LAPP) | * Too many information on logfiles or finding the good information on log file is too hard (IN2P3-LAPP) | ||
| − | === What takes the most effort?=== | + | ==== What takes the most effort?==== |
* Middelware dependency understanding (IN2P3-LAPP) | * Middelware dependency understanding (IN2P3-LAPP) | ||
| − | === What can be improved about operational procedures?=== | + | ==== What can be improved about operational procedures?==== |
* A clear and single channel to announce a new release and documentation (IN2P3-LAPP) | * A clear and single channel to announce a new release and documentation (IN2P3-LAPP) | ||
| − | === 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) | * Middelware compatibilities with the larger set of technical constraints (yaim/quattor, NAS/SAN storage infrastructure,...) (IN2P3-LAPP) | ||
| − | === Other comments=== | + | ==== Other comments==== |
* Aware of EGI stage rollout procedure ? (FC) | * Aware of EGI stage rollout procedure ? (FC) | ||
* A clear statement regarding "EGI staged rollout procedures" is required from WLCG. (FC) | * A clear statement regarding "EGI staged rollout procedures" is required from WLCG. (FC) | ||
Version du 13:38, 10 novembre 2011
Sommaire
Input provided by french sites
Input for WG4 - WG 5
- 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?
- Quattor (FC)
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?
- A clear and single channel to announce a new release and documentation (IN2P3-LAPP)
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)
Other comments
- Aware of EGI stage rollout procedure ? (FC)
- A clear statement regarding "EGI staged rollout procedures" is required from WLCG. (FC)
