Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-4594

[Cisco ACI RFE ]-Support for CNI chaining on Secondary CNI interface

XMLWordPrintable

    • False
    • None
    • False
    • Not Selected

      Partner: 

      Cisco ACI 
      Account#: 5576336

      Cisco ACI offering a new Cisco Network Operator formerly called Cisco Kubernetes Operator.  CNO will allow 3rd party CNIs to talk to an ACI Fabric via OpenShift Operator. 

      We are currently targeting a Sept/Oct 2023 POC featuring Cisco ACI, OpenShift, OVN, E/// 5G workloads for Bharti Airtel

      CNO Presentation:
      https://drive.google.com/file/d/10AlBOoBKq_Ioqmn6498DslQ2a5fSWO8B/view?usp=sharing

      CNO Engineering Spec:
      https://drive.google.com/file/d/1uus38fkQe09c_YRcl12DQzXP07NdFV9X/view?usp=drive_link

      Logs from demo:
      https://drive.google.com/file/d/1DcEHNyFHRyDZZytEH_VsFDT5bsEW_Cdh/view?usp=drive_link
       

      As outlined in the Engineering Spec, Cisco is looking to chain CNIs on Pri & Sec CNI interfaces,   RH (Dan W, Doug S, Marc C) shared RH concerns with chaining on Pri-CNI interface as outlined in Cisco's Eng Spec

      • Primary CNI Red Hat OVN, CNO-CNI (chained)    <----NOT SUPPORTED
      • Secondary Interface CNIs Multus, MacVLAN, SR-IOV, CNO-CNI (chained). <---- SUPPORTED

      This is an RFE for RH to identify any issues/concerns and/or officially support CNI Chaining on OpenShift Secondary CNI interfaces.

       

       

              adakopou@redhat.com Antonios Dakopoulos
              adakopou@redhat.com Antonios Dakopoulos
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: