Uploaded image for project: 'Agent-based Installer for OpenShift'
  1. Agent-based Installer for OpenShift
  2. AGENT-189

Provision IPv4/IPv6 dual-stack and single-stack IPv6 clusters

XMLWordPrintable

    • Provision IPv4/IPv6 dual-stack and single-stack IPv6 clusters
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Done
    • OCPPLAN-8150 - Agent-Based Installer GA
    • OCPPLAN-8150Agent-Based Installer GA
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      You can create the Agent ISO image with the following IP address configurations:
      * IPv4
      * IPv6
      * IPv4 and IPv6 in parallel (dual-stack)
      For more information, see xref:../../installing/installing_with_agent_based_installer/installing-with-agent-based-installer.adoc#installing-ocp-agent_installing-with-agent-based-installer[Dual and single IP stack clusters].
      Show
      You can create the Agent ISO image with the following IP address configurations: * IPv4 * IPv6 * IPv4 and IPv6 in parallel (dual-stack) For more information, see xref:../../installing/installing_with_agent_based_installer/installing-with-agent-based-installer.adoc#installing-ocp-agent_installing-with-agent-based-installer[Dual and single IP stack clusters].
    • Feature
    • Done

      Epic Goal

      As a OpenShift infrastructure owner, I want to deploy OpenShift clusters with dual-stack IPv4/IPv6

      As a OpenShift infrastructure owner, I want to deploy OpenShift clusters with single-stack IPv6

      Why is this important?

      IPv6 and dual-stack clusters are requested often by customers, especially from Telco customers. Working with dual-stack clusters is a requirement for many but also a transition into a single-stack IPv6 clusters, which for some of our users is the final destination.

      Acceptance Criteria

      • Agent-based installer can deploy IPv6 clusters
      • Agent-based installer can deploy dual-stack clusters
      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.

      Previous Work

      Karim's work proving how agent-based can deploy IPv6: IPv6 deploy with agent based installer]

      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>|

          1.
          		 PX Tracker Sub-task Closed Undefined Jean-Francois Saucier
          2.
          		 TE Tracker Sub-task Closed Undefined Jean-Francois Saucier
          3.
          		 QE Tracker Sub-task Closed Undefined zhenying niu
          4.
          		 Docs Tracker Sub-task Closed Undefined Amrita Sakthivel (Inactive)

            [AGENT-189] Provision IPv4/IPv6 dual-stack and single-stack IPv6 clusters

            Robert Fournier added a comment -

            Yes this was added in 4.12, moving to Closed.

            Robert Fournier added a comment - Yes this was added in 4.12, moving to Closed.

            Nicholas Stielau added a comment -

            Should this be Dev Completed or closed?  It has fixVersion=4.12

            Nicholas Stielau added a comment - Should this be Dev Completed or closed?  It has fixVersion=4.12

            Antoni Segura Puimedon added a comment -

            TE Slides: explain that dual VIPs is not in 4.12

            Antoni Segura Puimedon added a comment - TE Slides: explain that dual VIPs is not in 4.12

            Robert Fournier added a comment -

            Yes, we'll have to add the docs for the DualStack VIPs (that feature has recently merged and we haven't tested it yet so don't have an example). However we also need changes to docs to:

            • include the MachineNetwork in addition to the ClusterNetwork and ServiceNetwork
            • show IPv6 addresses with the above addresses for IPv6 single stack
            • shows IPv4 and IPv6 addresses with the above addresses for IPv6

            Robert Fournier added a comment - Yes, we'll have to add the docs for the DualStack VIPs (that feature has recently merged and we haven't tested it yet so don't have an example). However we also need changes to docs to: include the MachineNetwork in addition to the ClusterNetwork and ServiceNetwork show IPv6 addresses with the above addresses for IPv6 single stack shows IPv4 and IPv6 addresses with the above addresses for IPv6

            Zane Bitter added a comment -

            SNO doesn't have VIPs (because it's platform: none), so if anything it's simpler. But it is definitely a special case in that sense.

            Zane Bitter added a comment - SNO doesn't have VIPs (because it's platform: none), so if anything it's simpler. But it is definitely a special case in that sense.

            OpenShift Jira Bot added a comment -

            Zane Bitter - This epic has open tracker sub-tasks which must be resolved before transitioning this epic. Please reach out to the appropriate functional team(s) to review and resolve the open sub-task(s) before marking this epic complete.

            OpenShift Jira Bot added a comment - Zane Bitter - This epic has open tracker sub-tasks which must be resolved before transitioning this epic. Please reach out to the appropriate functional team(s) to review and resolve the open sub-task(s) before marking this epic complete.

            Ramon Acedo added a comment -

            Blocker as part of 4.12 IPv6 epics

            Ramon Acedo added a comment - Blocker as part of 4.12 IPv6 epics

            Ramon Acedo added a comment -

            asegurap1@redhat.com update assignee when ready, thanks.

            Ramon Acedo added a comment - asegurap1@redhat.com  update assignee when ready, thanks.

            Nicholas Stielau added a comment -

            Since we expect this in 4.12, can we set an assignee so there is a clear contact? (via Program meeting)

            Nicholas Stielau added a comment - Since we expect this in 4.12, can we set an assignee so there is a clear contact? (via Program meeting)

              bfournie@redhat.com Robert Fournier
              racedoro@redhat.com Ramon Acedo
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: