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

Allow node zero ip and ServiceBaseURL to be set by the tui

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • BU Product Work
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-245 - Configure network interfaces interactively with agent-based installer
    • Agent Sprint 230

      The node zero ip is currently hard-coded inside set-node-zero.sh.template and in the ServiceBaseURL template string.

      ServiceBaseURL is also hard-coded inside:

      • apply-host-config.service.template
      • create-cluster-and-infraenv-service.template
      • common.sh.template
      • start-agent.sh.template
      • start-cluster-installation.sh.template
      • assisted-service.env.template

      We need to remove this hard-coding and to allow a user to be able to set the node zero ip through the tui and have it be reflected by the agent services and scripts.

            [AGENT-501] Allow node zero ip and ServiceBaseURL to be set by the tui

            Antoni Segura Puimedon added a comment -

            I am not quite sure. I think it could be beneficial to allow the user to set those after the connectivity checks fail. I am thinking of the following scenario:

             

            1.  User fscks the net conf for all nodes (rendezvous IP was already used by another node
            2.  User uses agent-tui to fix the node0 IP
            3. User needs to update the other nodes rendezvousIP

            The obvious hole with that is that how would a node that it is actually node0 in the previous scenario. I think it would only happen in case the wrong config was static. To make it work we might need more than just this, though.

            Antoni Segura Puimedon added a comment - I am not quite sure. I think it could be beneficial to allow the user to set those after the connectivity checks fail. I am thinking of the following scenario:    User fscks the net conf for all nodes (rendezvous IP was already used by another node  User uses agent-tui to fix the node0 IP User needs to update the other nodes rendezvousIP The obvious hole with that is that how would a node that it is actually node0 in the previous scenario. I think it would only happen in case the wrong config was static. To make it work we might need more than just this, though.

            Richard Su added a comment -

            asegurap1@redhat.com zabitter I added this task under the assumption that it was changeable after viewing Toni's poc demos. But I think we stated for 4.13 that the rendezvous host IP will not be changeable through the TUI. Can you confirm that for 4.13, the rendezvous cannot be changed by the user through the TUI?

            Richard Su added a comment - asegurap1@redhat.com zabitter I added this task under the assumption that it was changeable after viewing Toni's poc demos. But I think we stated for 4.13 that the rendezvous host IP will not be changeable through the TUI. Can you confirm that for 4.13, the rendezvous cannot be changed by the user through the TUI?

              rwsu1@redhat.com Richard Su
              rwsu1@redhat.com Richard Su
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: