...
Case Attributes | Description | Informational |
Type | Blueprint | |
Blueprint Family - Proposed Name | Integrated Cloud Native NFV stack | |
Use Case | SDWAN, Customer Edge, Edge Clouds – deploy VNFs/CNFs and applications as micro-services | |
Blueprint proposed Name | Multi-server Cloud Native stack | |
Initial POD Cost (capex) | 50K minimum | |
Scale & Type | Minimum of 4 Xeon Servers + 1 Xeon server as genesis | |
Applications | SDWAN, ML/DL Analytics, EdgeXFoundry and 360 degree Video streaming | |
Power Restrictions | ||
Infrastructure orchestration | Bare Metal Provisioning : ironic or equivalentwith Metal3 controlled by Cluster API Kubernetes provisioning : Cluster Operator API with KuD. Docker for containers and Virtlet for VMs Service Orchestration : ONAP (Only the components that require VNF/CNF workload deployments via K8S) MEC framework: OpenNESS Site orchestrator : Kubernetes upstream Traffic Orchestration within a cluster: ISTIO Traffic orchestration with external entities : ISTIO-ingress and ISTIO-egress with MCDeployment Knative for function orchestration | Expose HW accelerators Storage Orchestration: Ceph with Rook Futrue: AF-XDP for packet processing based containers, OpenShift for site orchestrator, Kubevirt for VMs. |
SDN | OVN, SRIOV, Flannel | |
Workload Type | Containers, VMs and functions | |
Additional Details | Future: eBPF based CNI (such as PolyCube) |
...