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

Be able to cope with DHCP provided network configuration for all the nodes

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Minor Minor
    • openshift-4.12
    • None
    • None
    • None
    • Deploy with datacenter provided network configuration
    • False
    • False
    • Green
    • Done
    • OCPPLAN-8150 - Agent-Based Installer GA
    • OCPPLAN-8150Agent-Based Installer GA
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      With the Agent-based {product-title} Installer, you can deploy to environments where you rely on DHCP to configure networking for all the nodes, as long as you know the IP that at least one of the systems will receive. This IP is required so that all nodes use it as a meeting point. For more information, see
      xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adocl#dhcp[DHCP].
      Show
      With the Agent-based {product-title} Installer, you can deploy to environments where you rely on DHCP to configure networking for all the nodes, as long as you know the IP that at least one of the systems will receive. This IP is required so that all nodes use it as a meeting point. For more information, see xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adocl#dhcp[DHCP].
    • Enhancement
    • Done

      Epic Goal

      • As an OpenShift deployer, I want to be able to generate the installation image and boot it on the target machines without needing to pre-populate any node network configuration

      Why is this important?

      • Providing the detailed network configuration needed for nmstate is a significant barrier of entry to deploy OpenShift as NMStateConfig, while accessible, doesn't exactly roll off the tongue

      Scenarios

      1. I want to boot the baremetal node that will run the assisted service and the nodes that will be worker nodes all at once without needing to care about their IPs/VLANs, etc
      2. I want to make an "AMI" of the tool generated ISO to create my openshift clusters in my no-name cloud and I don't know which IP I am going to get (This scenario will need other work in other epics)

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • Deployment completes successfully without providing NMStateConfig for any node.

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      1. If we don't know what IP the assisted service is going to get, how do the agents know where to register to? asegurap1@redhat.com node0 agent-config must be provided
      2. If all the ISOs are the same and there's no prior knowledge of the IP configuration for the nodes, how do we decide which is going to run the assisted service? asegurap1@redhat.com the node that finds itself to match node0 config will set itself to be node0.

      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>

            ppinjark@redhat.com pawan pinjarkar
            asegurap1@redhat.com Antoni Segura Puimedon
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: