TBD - K8s POD connecting to a VM running on VPP OpenStack

[taylor]

Tasks to add a NSM enabled K8s cluster

• Reference https://github.com/networkservicemesh/networkservicemesh/issues/870

• [ ] Add script for deploying k8s to Packet - (using current NSM methods)
• [ ] Add script for adding NSM to k8s cluster
• [ ] Document how to use the new scripts
• [ ] Create pull request for adding new scripts and docs
• [ ] Deploy new k8s cluster to Packet testing project (CNCF CNFs)
• [ ] Share cluster access with team

OpenStack tasks

• [ ] Deploy OpenStack+VPP cluster with two compute node
• [ ] Deploy a VM with VXLAN configuration enabled to each compute node
  • Reference vxlan configuration in #211
  • [ ] verify intra node connectivity between VMS
• [ ] Provider cluster access to team

[taylor]

@fkautz feel free to add additional items here and reference the ticket for pull requests.

[robertstarmer]

@fkautz, I'd like to figure out what we should do to connect resources. I believe I can add the VXLAN endpoint to the underlying Kernel forwarding, but with a performance hit compared to "raw" VPP on a VLAN interface. Not sure if performance is your concern, or if we're initially just hoping for connectivity... Please let me know your thoughts.

[fkautz]

At this point, performance is not a concern. Just showing connectivity is good enough to start. Part of the example is to show it can work with non vpp systems such as ovs. A vxlan implementation is in line with this approach.

We can focus on improving performance after we have a baseline, and show how various implementations compare.

On Mon, Mar 25, 2019, 19:27 Robert Starmer [email protected] wrote:

@fkautz https://github.com/fkautz, I'd like to figure out what we should do to connect resources. I believe I can add the VXLAN endpoint to the underlying Kernel forwarding, but with a performance hit compared to "raw" VPP on a VLAN interface. Not sure if performance is your concern, or if we're initially just hoping for connectivity... Please let me know your thoughts.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cncf/cnf-testbed/issues/213#issuecomment-476449645, or mute the thread https://github.com/notifications/unsubscribe-auth/AAISGo1emUFgA9U7dPoOZAoVDQEnTDnLks5vaYWggaJpZM4cHcyC .