...
| Item | Assigned to | Due by Date | Status | ||
|---|---|---|---|---|---|
| 1 | Create PR for TOC and Structure for 9.5 in RM Ch09 | 2020-12-14 1400UTC | Done | ||
| 2 | Approvals of #1 | 2020-12-14 1500 UTC | Done | ||
| 3 | Mege/Squash #1 | 2020-12-14 1500 UTC | Done | ||
| 4 | 9.5.2.1 PR | 2020-12-15 | Done | ||
| 5 | 9.5.2.2 PR | 2020-12-15 | Done | ||
| 6 | 9.5.1.1 and 9.5.1.2 Requirements | 2020-12-17 | Tomas Fredberg [Ericsson] to introduce the concepts and then team can work on requirements | ||
| 7 | 9.5.1.3 Content + Requirements | 2020-12-18 | |||
| 8 | CI/CD pipeline design and job integration | PR #2179 created ans should be reviewed |
| Table of Contents |
|---|
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
...
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
9.5 Automation
9.5.1 Cloud 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
...
- Example, BIOS settings, Reset, Power Modes,
- HW component discovery and status/healt health supervision
- Composability of physical hardware resources (components)
- Hardware Accelerator discovery, loading and assignment
- Firmware Update and supervision (measurement) of Signed FW on known Authentic HW
- Security related certificates, keys and roles
...
- Physical network cabling detection and supervision
- L2, L3 and QoS Automation of Server NIC Network Assignment and Switch Fabric Network Assignment based on HW Provisioning in the HW Infrastructure Layer
- Partitioning, provisioning, enforcement of Overlay switching shared resources e.g. VLAN and VxLAN
9.5.1.3. software development CI/CD for infrastructure (not workloads) – Saad
...
what are the components of "infrastructure software": provisioning and configuration of the infrastructure (servers, network and storage; operations and management software)
Telco DevOps is still not mature within context of Telco infrastructure and service primarily due to reason that software in Telecom is primarily provided by vendors with operators almost no clear visibility about the software constructs itself , it means only Infrastructure and Networking Automation can not automate complete service .
End to End specification of how to deliver automation in a hybrid Infrastructure is required with following features
- CI (Continuous integration) for Telco service
a) When vendor will update new feature or new code files ( Packages , Helm charts etc) how it will be merged with existing software
b) Track and fix bugs of incremental software running on Infrastructure
- CD (Continuous Delivery) for Telco service
a) Testing of new code base e.g Test Bench , vSPerf etc
b) Automation of Code base with Infrastructure e.g Python , GNPy , Heat etc
c) Produce the software artifacts which will be deployed on Infrastructure , example is Sol4 packages , Sol1 templates
d) Testing of packages including Infrastructure DevOps
e) Output and benchmark the packages in staging Environment , key example here is Telco PaaS capability
- CD (Continuous Deployment) for Telco service
a) Software onboarding in the Infrastructure it involves all deployments in both CNTT RM infrastructure and related VNF/CNF codes/configurations including simulation and Test execution environment
b) CI/CD pipeline , when a new VNF/CNF code need onboard or just a simple capacity expansion is required , It is not just about Infrastructure and Networking Automation but E2E automation including VNF/CNF part
c) Here the Key requirement is once a new Release is output all the process from build/test/validate and onboard is done automatically
d) Handover points between Infrastructure and Orchestration need to be validated and verifiable in the form of SLA/KPI's
I think if all team agree then we can output DevOps Reference Architecture after team consensus covering Infra
Lessons Learnt from ETSI NOC and CNCF conformance:
Following two domains we must catch for E2E definition and service
→ CI explaining pipeline view between Lab , Staging and Production
→ CT , the testing of service
→ Pipeline architecture e.g Jira , Jenkins and Necessary SDK's in Orchestration through which we can automate E2E including Infrastructure
CI/CD requirements
| Ref | Description | Comments/Notes |
|---|---|---|
| auto.devops.cicd.001 | The CI/CD pipeline must be model driven i.e characterised by service intent without mapping each component manually | |
| auto.devops.cicd.002 | The CI/CD pipeline must be declarative and not imperative | |
| auto.devops.cicd.003 | Must support necessary SDK's needed for complete E2E automation and service validation | |
9.5.1.4. software deployment CI/CD (operator environment) – covered in 9.5.2.2 (inserted 2020-12-07)
9.5.1.5. Identify "Closed Loop Automation" as a Gap in Ch10 – Done (PR #2123 -need reviews)
9.5.2
...
Software onboarding automation (including CI/CD). Owner: Walter.kozlowski
9.5.2.1.
...
Software onboarding automation - the scope for RM is to describe support only but leave the details to RA/RI; Walter.kozlowski to open PR
The Cloud Infrastructure workload onboarding process describes activities needed for the integration of tenants' workloads into the Cloud Infrastructure environment. Typically, this business process consists of the following key phases:
...