This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
acelab:cmc_workflow [2018/08/01 10:48] smasoka created |
acelab:cmc_workflow [2021/12/09 16:42] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Document all steps from the beginning | + | ===== Background ===== |
| + | |||
| + | **Change Management Control (CMC)** is a continuous process of ensuring system changes are introduced in a controlled and coordinated manner to minimise service disruptions. | ||
| + | |||
| + | The implementation and maintenance of //lengau// involves integrating many elements e.g. compute nodes, parallel file systems, fast networks, provisioning and configuration systems. The CHPC needed a platform to | ||
| + | |||
| + | * Test updates, upgrades, provisioning and configuration options. For example, High Availability (HA) and Failover. | ||
| + | * Test fairness policies. For example job scheduling and data storage | ||
| + | * Development of new features. | ||
| + | * Enable collaboration between Users and CHPC to test application behaviour, excluding performance, | ||
| + | |||
| + | Without the test cluster (from now on referred to CMC cluster) | ||
| + | |||
| + | The CMC cluster is the platform where CMC actions are evaluated in order to gather enough information to submit a change request for the production environment. The process eliminates uncertainty and raises confidence in system operations which leads to delivering a reliable service to the user community. | ||
| + | |||
| + | ===== CMC Workflow ===== | ||
| + | |||
| + | - Submit a [[acelab: | ||
| + | - Approval and Scheduling process | ||
| + | - Work on the CMC. [[acelab: | ||
| + | - Submit a [[acelab: | ||
| + | - Acceptance and Implementation on //lengau// | ||