XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • None
    • VAF
    • None
    • Lab networking
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Proposed
    • Proposed
    • Done
    • Proposed
    • rhos-workloads-vaf
    • Proposed

      Goal:

      • Solve problem 1: Our ToR switches aren’t redundant. MC-LAG is not working properly.
      • Solve problem 2: Some uplinks from ToR switches are 40Gbps (borrowed transceivers from IT Network team)
      • Solve problem 3: Interfaces in RHOSO cluster aren’t bonded
      • Solve problem 4: We encountered a lot of issues with IPv6 due to RH IPv6 network isolation (can’t access internet)

      Acceptance Criteria:

      • Problem 1 is solved, eg. switches are reconfigured to create a virtual-chassis
      • Problem 2 is solved, eg. slow transceivers are replaced with new transceivers with required speed
      • Problem 3 is solved, eg. ensure VA deployments are able to be deployed with bonds
      • Problem 4 is solved, eg. ensure lab has external IPv6 traffic enabled

      Open questions:

      • Any customer will definitely have redundant infrastructure, maybe we should redeploy VA with bonds?
      • Given the issues with IPv6 shouldn't we rather disable IPv6 for our VLAN?

              Unassigned Unassigned
              mmagr@redhat.com Martin Magr
              rhos-workloads-vaf
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: