Skip to end of metadata
Go to start of metadata

As the beginning, we start from Kubernetes with SmartNic. In the future, we will enable Openstack and other specific features.

The feature list is in the attachment.

Use Case Details:

Attributes

Description

Informational

Type

New


Industry Sector

Edge Cloud, Telco


Business driver

VPC, 5G UPF can use SmartNIC to accelerate the performance.


Business use cases

  •  Demonstrate SmartNIC accelerated Edge stack
    • OVN-K8s in host and OVS offloaded in SmartNIC
  • Software ecosystem support for SmartNIC platform
  • Kubernetes support for networking acceleration and SmartNIC


Business Cost - Initial Build Cost Target Objective

  • Common drivers for x86 and Arm
  • Full DPDK support
  • Overlay support (VxLAN, GRE)
  • Hardware offload for Linux tc
  • Crypto offload drivers


Business Cost – Target Operational Objective

  • OVN/Open vSwitch
    • Open vSwitch offload on SmartNIC platform
  • Kubernetes
    • SmartNIC for Kubernetes
    • Huge page support
    • Node Feature Discovery
    • Related CNI projects:Multus, Cillium, SR-IOV  and OVS-DPDK
  • Storage:
    • NVMeoF interface


Security need

  • Crypto offload drivers


Regulations

N/A


Other restrictions

N/A


Additional details

N/A



Case Attributes

Description

Informational

Type

New


Blueprint Family - Proposed   Name

Integrated Edge Cloud (IEC)


Use Case

VPC, 5G UPF


Blueprint proposed Name

IEC Type 5: SmartNIC


Initial POD Cost (capex)

VPC: 1 Rack with 2 servers, each server with 1 SmartNIC

UPF: 3 servers, each server with 1 SmartNIC


Scale & Type

In the gateway, infrastructure service, and edge cloud


Applications

Short Video Applications, UPF


Power Restrictions

SmartNIC: 35W


Infrastructure orchestration

  • Bare Metal Provisioning :Ansible 
  • Kubernetes Provisioning :KuD
  • Host OS Level: 
    • Network: cilium/OVN
  • SmartNic Arm cores Level:
    • Network: cilium-BPF/ovs-vswitchd/ovs-dpdk/
  • Docker for containers and Kubelet for VMs


SDN

OVN, SRIOV


Workload Type

  • Containers


Additional Details

SmartNic features:

  • Needs to provide mechanism to recover from the system crashes remotely.
  • Support PXE protocol
  • Secure boot/Secure Key Storage



Committer

Committer

Company

 Committer Contact Info

Committer Bio

Committer Picture

Self Nominate for PTL (Y/N)

Yongsu Zhang

ByteDance

zhangyongsu@bytedance.com




Peng HeByteDancehepeng.0320@bytedance.com


Xiongchun DuanByteDanceduanxiongchun@bytedance.com


Fazil Osman 

Broadcom

fazil.osman@broadcom.com




China Mobilejiaxuan@chinamobile.com

Y
Song ZhuArmsong.zhu@arm.com


Armtrevor.tao@arm.com


Armjingzhao.ni@arm.com


Armjianlin.lv@arm.com


Qihui ZhaoChina Mobilezhaoqihui@chinamobile.com


Sheng WangChina Mobilewangshengyjy@chinamobile.com


China Mobilelijunfen@chinamobile.com


yihui wangChina Mobilewangyihui@chinamobile.com


Yan MouChina Mobilemuyan@chinamobile.com


Frankie FanBroadcomfrankie.fan@broadcom.com


David BerryBroadcomdavid.berry@broadcom.com


Vikram SiwachMobiledgexvikram.siwach@mobiledgex.com


Yong ZhuangMellanoxyong@mellanox.com


Tiejun ChenVMwaretiejunc@vmware.com



Contributors: 

Contributor

Contributor

Company

 Contributor Contact Info

Contributor Bio

Contributor Picture

Arm

tina.tsou@arm.com




Presentations:


Smart Nic features:



  • No labels

2 Comments

  1. Xuan Jia

    1. "Business usecases" in the abive tables, OVN-K8s is mentioned as the CNI with SmartNIC for offloads.   But in "Infrastructure Orchestration" section, you mentioned Cilium, but not OVN-K8s. You may want to remove that confusion by adding OVN-K8s in the infrastructure orchestration.  I guess you may be providing Cilium CNI as option, but I guess there is no SmartNIC involved. Right?  Please confirm.
    2. In case of OVS based offloads, you mentioned that ovs-vswitchd, ovs-dpdk are used in both host and smart-nic.  My understanding is that ovs-vswitchd, ovs-dpdk run in SmartNIC, but not in the host.  Again, this understanding is based on Slide 4.  
    3. As per Slide 4, you have used the term "OVN agent". I assume that it is "OVN Controller".  
    4. Where are you running OVSDB Server?.  Is it in host or smartNIC?
    5. Slide 5 of  the presentation deck, you talked about UPF offload.  Is UPF is being run as a bare-metal container?
    6. As per Slide 8 (Accelerated with SmartNIC), it appears that SmartNIC is exposing vhost interfaces or as SRIOV VFs to the workloads running in host.  But, many times, containers running in the host use host Linux TCP/IP stack and hence the expectation is that packets from SmartNIC land at veth layer of host.  So, curious on how you are handling the situation where containers are running on host Linux TCP/IP stack?

    Srini

    1. Hi Srini:

      1. I have updated business use cases. For Cilium, Cilium-BPF function may run in SmartNic. 

      2. Yes, you're correct. I have updated it (smile)
      3. OVN Controller is correct
      4. For the beginning OVSDB is in host. It will be in SmartNIC in future release.
      5. Bare-metal container
      6. It's a little complex question. xiongchun duan could you answer this question?

      Thanks, Srini.  It makes the BP more understandable.