You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Configuration" is a very generic word. We need to come up with some common language. Here is an initial proposal to get the discussion started:
Network Topology: Placement of network functions across the geographically distributed fleet of clusters, and associated configuration variations. Example resources: FiveGCoreTopology, PackageDeployment, PackageVariantSet
Network Configuration: Configuration representing the runtime behavior of network functions, along with a model for capturing vendor-specific differentiating configuration of those functions. Example resources: UPFDeployment
Network Function Workload: Configuration representing provisioning-time definitions of standards-driven network functions, along with a model for capturing vendor-specific differentiating configuration associated with those functions. Example resources: UPFClass, UPF, NFInstanceSet
Workload Primitives: Standard Kubernetes resources such as Deployments, along with extensions that provide node and node interface level configuration, such as SR-IOV and Multus.
Workload Fabric: Configuration of networking infrastructure driven on a per-workload basis, rather than as part of the platform-level infrastructure. For example, configuration VLAN/VRF-lite in top-of-rack and spine switches.
MEC / Cloud Infrastructure: Configurations for defining virtualized, API-driven on-demand consumption of the physical layer. Includes abstract resources such as Kubernetes clusters. Example resources: Upstream cluster resources, maybe some BIOS resources?
Physical Infrastructure: Physical compute, networking, and storage devices and their associated configurations (out-of-scope).
The text was updated successfully, but these errors were encountered:
Network Topology -> I would say network is an overloaded term. if you would say this to network people they have a total different perspective on this. I would call this NF Topology.
Network Configuration -> I would call this NF Configuration
Network Function Workload -> I would call this NF Deployment
Workload I would call server network config (CNI/Multus) and fabric is network fabric (it can be physical or virtual)
"Configuration" is a very generic word. We need to come up with some common language. Here is an initial proposal to get the discussion started:
The text was updated successfully, but these errors were encountered: