Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Converge on common configuration terminology #266

Open
johnbelamaric opened this issue Feb 13, 2023 · 2 comments
Open

Converge on common configuration terminology #266

johnbelamaric opened this issue Feb 13, 2023 · 2 comments

Comments

@johnbelamaric
Copy link
Member

"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).
@gvbalaji gvbalaji transferred this issue from nephio-project/docs Jun 8, 2023
@henderiw
Copy link
Contributor

henderiw commented Jun 9, 2023

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)

@johnbelamaric
Copy link
Member Author

I think we should still work on this going into R2, we're getting closer but need more common language.

@johnbelamaric johnbelamaric moved this to Todo in Nephio R2 Aug 8, 2023
@gvbalaji gvbalaji added this to the R2-Sprint1 milestone Aug 22, 2023
@liamfallon liamfallon removed this from Nephio R2 May 16, 2024
@liamfallon liamfallon removed this from the R2-Sprint1 milestone May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants