Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-4471

Add support for multiple network interfaces used for egressIP on public clouds

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • OVN Kubernetes
    • None
    • Add support for multiple network interfaces used for egressIP on public clouds
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-1173 - Add support for multiple network interfaces used for egressIP on public clouds
    • 100% To Do, 0% In Progress, 0% Done
    • ---
    • 0
    • 0

      Template:

      Networking Definition of Planned

      Epic Template descriptions and documentation

      Epic Goal

       

      Currently any one  using OpenShift cluster on AWS EC2 instances have limitation of IP addresses per EC2 instance network interface.

      • Objectively, mapping too many egressIP's to the existing interface will hit the network IP limitation and prevent creation of all the desired EgressIP's needed for the project.
      • Secondary/additional interfaces would potentially allow to bypass this limitation.
      • Currently this is supported on Bare metal environment only and goal is to extend this to all public clouds. 

      Planning Done Checklist

      The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

      • Priority+ is set by engineering
      • Epic must be Linked to a +Parent Feature
      • Target version+ must be set
      • Assignee+ must be set
      • (Enhancement Proposal is Implementable
      • (No outstanding questions about major work breakdown
      • (Are all Stakeholders known? Have they all been notified about this item?
      • Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)
        1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
        2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

      Additional information on each of the above items can be found here: Networking Definition of Planned

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement
        details and documents.

      ...

      Dependencies (internal and external)

      1.

      ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

            Unassigned Unassigned
            ddharwar@redhat.com Deepthi Dharwar
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: