Uploaded image for project: 'OpenStack as Infra'
  1. OpenStack as Infra
  2. OSASINFRA-3253

CAPO supports essential installer scenarios

    XMLWordPrintable

Details

    • CAPO supports essential installer scenarios
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-1002 - Remove Terraform from the OpenStack installer
    • OCPSTRAT-1002Remove Terraform from the OpenStack installer
    • 100
    • 100% 100%

    Description

      Goal

      • Implement scenarios in CAPO that can't be worked around on the installer with direct calls to OpenStack API.

      Why is this important?

      • Intermediate, testable deliverable on the path to installer integration.
      • Ultimately required for installer integration.
      • We do not currently intend to support this feature. CAPO will be self-managed only.

      Scenarios

      • User installs OpenShift with CAPO enabled.
      • User deploys CAPI templates in a private namespace which deploy a separate workload OpenShift cluster on OpenStack.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …

      Attachments

        Issue Links

          depends on

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OSASINFRA-3207 Integrate CAPO into cluster-capi-operator (TP)

          • 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 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. OSASINFRA-3254 CAPO is functionally equivalent to terraform

          • 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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OSASINFRA-3379 Upstream CAPO release v0.10

          • 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.
          • Dev Complete

          Task - Represents a small unit of work that is not end-user facing. OSASINFRA-3366 Bump capo-integration branch to new upstream release

          • 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.
          • Closed

          Activity

            People

              rhn-gps-mbooth Matthew Booth
              rhn-gps-mbooth Matthew Booth
              Emilien Macchi, Matthew Booth, Michał Dulko
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: