README
- This TOC page has been created with Ahmed El Sawaf Karine Sevilla Petar Torre (Deactivated) Saad Sheikh SID Tomas Fredberg [Ericsson] Walter.kozlowski and Pankaj.Goyal as editors/owners
- Editors/owners can't in-line comments
- To make it easier to mange content, I suggest that individuals take ownership of a topic (e.g., "9.5.1.1. hardware configuration CI/CD")
- Click on the "Create ..." (blue button on the Confluence Ribbon above), the following pop-up window opens
- Select "Blank Page" and click on "Create" (bottom right)
- A new Confluence "Add Page" opens
-
- Enter the section title (e.g., "9.5.1.1. hardware configuration CI/CD") as the Page Title
- Add content as needed
- To save and exit, click on "Publish" (bottom left)
- If you exit prior to publishing the new page and content will be lost
- As the creator of the page you can come and update content while others can comment in-line or at the bottom
- POst publishing the page, copy the page URL and add it to the zection in this ToC page
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
9.5 Automation
9.5.1 Infrastructure LCM Automation ( including Platform Software and CI/CD)
End-2-End understanding of what type of automation ought to be done on what layers and includes
9.5.1.1. hardware configuration CI/CD
9.5.1.2. networking automation
9.5.1.3. software development CI/CD
9.5.1.4. software deployment CI/CD (operator environment)
9.5.1.5. Identify "Closed Loop Automation" as a Gap in Ch10
9.5.2 Workload onboarding automation (including CI/CD)
9.5.2.1. workload onboarding automation - the scope for RM is to describe support only but leave the details to RA/RI;
9.5.2.2. RM will state the requirements including for CI/CD for ensuring software security scans, image integrity checks, OS version checks, etc. prior to deployment -
- the tenant processes for application LCM (such as updates) are out of scope