Motivation
We need to move away from ad-hoc management of infrastructure resources. While we have some existing workflows around OpenShift and network switch configuration management, there are other areas that either still require manual procedures or that only recently have adopted some sort of devops workflow.
Completion Criteria
Description
Ideally, for every infrastructure change, we should be able to identify:
Who made the change?
When did they make the change?
Why did they make the change?
Who approved the change?
We should adopt processes and tooling that make it easier to answer these questions. The existing MOC 2.0 documents do not address this requirement in an explicit fashion; while some aspects (like cluster deployment via AutoShift) meet these goals, other areas remain unspecified.
Completion dates
Desired - 2026-07-06
Required - TBD
Motivation
We need to move away from ad-hoc management of infrastructure resources. While we have some existing workflows around OpenShift and network switch configuration management, there are other areas that either still require manual procedures or that only recently have adopted some sort of devops workflow.
Completion Criteria
Description
Ideally, for every infrastructure change, we should be able to identify:
Who made the change?
When did they make the change?
Why did they make the change?
Who approved the change?
We should adopt processes and tooling that make it easier to answer these questions. The existing MOC 2.0 documents do not address this requirement in an explicit fashion; while some aspects (like cluster deployment via AutoShift) meet these goals, other areas remain unspecified.
Completion dates
Desired - 2026-07-06
Required - TBD