cncf / cncf/telecom-user-group

[whitepaper][1.5.4]: Comments on legacy VNF-s

Open
#46 3 comments 1 reaction 0 assignees View on GitHub
Dominant language
No language data
Stars
129
Forks
30
PR merge metrics
No merged PRs in 30d

Description

I have serious doubts that we can run "legacy VNF-s" (let's assume, that these are legacy because of their need for CPU pinning, NUMA alignement, SR-IOV or even PCI passthrough) using KubeVirt or Virtlet. It is possible to run these with OpenStack and yes it is possible to run these with an OpenStack on top of Kubernetes, but I think it is a too big simplification to say that OpenStack is an abstraction layer. It is an other orchestrator layer for "legacy VNF-s" on top of the orchestration layer for CNF-s.

Contributor guide

Open the contributing guide

Research direction

Locate the whitepaper section identified as 1.5.4 and read its discussion of legacy VNFs, KubeVirt, Virtlet, and OpenStack. Compare the section's abstraction-layer claim with the concerns raised here, then determine and document the specific wording or scope changes needed; the issue does not define a concrete completion condition.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
documentation, infrastructure
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.