...
Not every thing can be tackled in the MVP, here are two elements that can be tackled for MVP.
- C3: CNF Cloud Native Conformance Olivier Smithto add details on possible things to test in this category for MVPConformance (Per CNCF CNF Conformance Characteristics):
• Compatibility - CNFs should work with any Certified Kubernetes product and any CNI-compatible network that meet their functionality requirements.
• Statelessness - The CNF's state should be stored in a custom resource definition or a separate database rather than requiring local storage. The CNF should also be resilient to node failure.
• Security - CNF containers should be isolated from one another and the host.
• Scalability - CNFs should support horizontal scaling (across multiple machines) and vertical scaling (between sizes of machines).
• Configuration and Lifecycle - The CNF's configuration and lifecycle should be managed in a declarative manner, using ConfigMaps, Operators, or other declarative interfaces.
• Observability - CNFs should externalize their internal states in a way that supports metrics, tracing, and logging.
• Installable and Upgradeable - CNFs should use standard, in-band deployment tools.
• Hardware Resources and Scheduling - The CNF container should access all hardware and schedule to specific worker nodes by using a device plugin.
(Should note that these are currently not characteristics that will be sufficient and/or accurate for Telecom use. As an example, in 5G the CHF (Charging Function) will be required to provide stateful transaction processing for services that are monetized on a metered basis – e.g. charging per minute for a live video chat session to a healthcare professional. It is unclear if these types of distinctions will be specified as work coming from CNTT.).
- B1: CNF Compliance.
Workstreams Proposal
...