Recommendation : 3. Adapt the use of technical equipment to needs
Is provisioning / deprovisionning dynamic depending on the load ?
How long after inactivity are the services de-provisioned?
When hosting a service, each component part may have a different lifetime. It is important that all end-of-life procedures are outlined so that the footprint of unused and discontinued components is neutral. This is also the case when the shutdown is temporary due to a drop in activity.
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
Formalized = 100 ; Planned = 75 ; Identified = 50 ; Ignored = 0 / 100
Fin de Vie
11 other criteria related to the recommendation: Adapt the use of technical equipment to needs
Is the size of the physical park in line with the number of virtual machines to be run ?
Are servers / routers turned off when not in use ?
Is the allocated memory based on actual use ?
Is the number of CPU cores allocated based on actual use ?
Is the technical choice (shared, dedicated, clustered) optimised between the actual need and energy efficiency ?
Are unused cores disabled ?
Is the backup system incremental (disk optimization) ?
Is the use of containers over virtual machines preferred ?
Are Open Source solutions implemented when available ?
Is high availability designed in a modular fashion ?
Do storage solutions reduce the number of components (for example: high density SSD media) ?