- 1.0 Compatibility, Installability & Upgradability
- 2.0 Configuration
- 3.0 Microservices
- 4.0 State
- 5.0 Security
- 6.0 Observability and Diagnostics
- 7.0 Reliability, Resilience & Availability
Best practices affecting the basic management of CNF software - the acceptance of CNFs from a development team, the installation onto the network, the creation of instances in clouds within the network, version management of running software and the compatibility of CNFs on many cloud platforms and with other CNFs.
Working with running CNFs: common patterns for setting and changing the behaviour of network functions.
The best way to use microservice-based design patterns to deliver CNF functionality.
Management of short-lived and long lived state, including state associated with network flows, configuration data, subscriber activity data and other data according to the varying requirements of resiliency, rate of change, access rate and persistence.
How to ensure that components are protected against security issues, including security advisories on software components, defence against attacks, and defence in depth.
Description: Containers have a list of their own users independent of the host system, one of which is UID 0, the root user. Containers should run processes as a user other than root which makes it easier to run the container images securely.
Reference: CBPP-0002
How to get critical data about when things are going wrong and how to determine what must be done to put them right. The detection and correction may be through the actions of an operator or via an automated system. Using logs and metrics from all components in the system to narrow down the area where a problem exists, and to drill down into that area to determine a root cause and a fix.
How to ensure CNFs are resilient to failures that are inevitable in cloud environments.