Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-53

Agent-based Installer Interactive flow

    XMLWordPrintable

Details

    • False
    • False
    • OCPSTRAT-10Install and update OpenShift on Infrastructure Providers
    • 12
    • 12% 12%
    • ?
    • 0
    • 0
    • Program Call

    Description

      Goal

      Guided installation user experience that interacts via prompts for necessary inputs, informs of erroneous/invalid inputs, and provides status and feedback throughout the installation workflow with very few steps, that works for disconnected, on-premises environments.

      Installation is performed from a bootable image that doesn't contain cluster details or user details, since these details will be collected during the installation flow after booting the image in the target nodes.

      This means that the image is generic and can be used to install an OpenShift cluster in any supported environment.

      Why is this important?

      Customers/partners desire a guided installation experience to deploy OpenShift with a UI that includes support for disconnected, on-premises environments, and which is as flexible in terms of configuration as UPI.

      We have partners that need to provide an installation image that can be used to install new clusters on any location and for any users, since their business is to sell the hardware along with OpenShift, where OpenShift needs to be installable in the destination premises.

      Acceptance Criteria

      This experience should provide an experience closely matching the current hosted service (Assisted Installer), with the exception that it is limited to a single cluster because the host running the service will reboot and become a node in the cluster as part of the deployment process.

      • User can successfully deploy OpenShift using the installer's guided experience.
      • User can specify a custom registry for disconnected scenario, which may include uploading a cert and validation.
      • User can specify node-network configurations, at a minimum: DHCP, Static IP, VLAN and Bonds.
      • User can use the same image to install clusters with different settings (collected during the installation).
      • Documentation is updated to guide user step-by-step to deploy OpenShift in disconnected settings with installer.

      Dependencies

      1. Guided installation onboarding design from UXD team.
      2. UI development

       

      Attachments

        Issue Links

          is depended on by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. AGENT-486 OpenShift Installation Image

          • Undefined - Priority not specified.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-275 [Agent] OpenShift Installation Image

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users RFE-3407 MCE Installer support for pre-installed CoreOS nodes

          • Undefined - Priority not specified.
          • Rejected
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OKD-57 Run e2e OKD test on baremetal via MOC

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • In Progress

          Outcome - Organizational objective focused on a measurable outcome. May be in support of larger strategic goals. OCPSTRAT-26 BU Priority (OKD)

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • In Progress

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-465 Agent-based Installer add cluster configs after booting image

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              racedoro@redhat.com Ramon Acedo
              racedoro@redhat.com Ramon Acedo
              Beth White, Matthew Carleton, Tomas Jelinek
              Stephanie Stout Stephanie Stout
              Zane Bitter Zane Bitter
              Jean-Francois Saucier Jean-Francois Saucier
              Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: