[RA2 Ch08] Initial content for Ch08 (Gap analysis) #672
Conversation
rabiabdel
changed the title
rabiabdel
changed the title
rabi-abdel
changed the title
From meeting 5/12/19
tomkivlin
requested review from
tomkivlin,
pgoyal01,
TamasZsiros and
CsatariGergely
There was a problem hiding this comment.
I like the existing text, however I believe there is one topic missing - potentially a new chapter, or maybe an extension of 8.2.4: today in existing networks L3 VPNs are commonly used for traffic separation (e.g. separate L3 VPN for signallin, charging, LI, O&M etc.). CNFs will have to interwork with existing network elements and therefore a K8s POD will somehow need to be connected to a L3 VPN. Today this is only possible via Multus (or DANM), however typically there is a network orchestration respnsibility to connect the network interface to a gateway router (where the L3 VPN is terminated). This network orchestration is not taken care of by K8s, nor there is a production grade solution in the open source space to take care of this.
Note: with an underlying IAAS this is possible, but then it introduces (undesirable) depenency betweenworkload orchestration in K8s and infrastructure orchestration in IAAS.
Interoperability with VNF-based networking
Yes I agree, I have added this in as 8.2.7. |
|
@TamasZsiros if you're happy can you approve the changes please? |
| <a name="8.2.4"></a> | ||
| ### 8.2.4 Multiple network interfaces on Pods | ||
|
|
||
| > As well as having multiple network interfaces on Pods (e.g. Multus), being able to have different network interfaces in differnet Pods using different CNI plugins within the same cluster. |
There was a problem hiding this comment.
We should also have the same features available for all network interfaces.
| - K8s as VM based VNF Orchestrator | ||
|
|
||
| <a name="8.2.1"></a> | ||
| ### 8.2.1 Container run-time Interfaces towards NFVI resources |
There was a problem hiding this comment.
Since Container Run-time Interface (CRI) is well-defined, I think in this context we need to use a different term. Is this the OCI run-time spec?
| <a name="8.2.4"></a> | ||
| ### 8.2.4 Multiple network interfaces on Pods | ||
|
|
||
| > As well as having multiple network interfaces on Pods (e.g. Multus), being able to have different network interfaces in differnet Pods using different CNI plugins within the same cluster. |
There was a problem hiding this comment.
Sentence and a Typo. Suggest "As well as having multiple network interfaces on Pods (e.g. Multus), need to support different network interfaces in different Pods using different CNI plugins within the same cluster."
rabi-abdel
dismissed stale reviews from TamasZsiros and CsatariGergely
@tamas, I believe this has been addressed
|
Approve and merge as no activity or further feedback within 2 days. |
Fixes #397
Fixes #398
Fixes #399
Fixes #400
Fixes #599
This is to look at the southbound interfaces towards the infrastructure resources.