Uploaded image for project: 'OpenShift Cloud'
  1. OpenShift Cloud
  2. OCPCLOUD-1263

Integrate openshift/API machine definitions into components

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Critical
    • None
    • None
    • 3
    • CLOUD Sprint 209, CLOUD Sprint 210, CLOUD Sprint 211, CLOUD Sprint 212, CLOUD Sprint 213

    Description

       

      Background

      As a follow up to OCPCLOUD-693, we need to, once all of the API definitions are present in openshift/api, migrate the existing code bases to use the new API locations.

       

      This will include:

      • Machine API Operator
      • Cluster Machine Approver
      • Cluster API Provider AWS|Azure|GCP|IBM|Alibaba|OpenStack|Kubevirt
      • Cluster API actuator pkg
      • Installer
      • WMCO
      • MCO
      • Hive
      • Grep OpenShift for other references to our old APIs

      Steps

      • Replace the Machine API imports with the new openshift/API MAPI locations

      Stakeholders

      • Cluster Infra
      • Owners of the repos listed above

      Definition of Done

      • The openshift/API defintions are used across components in the MAPI ecosystem
      • Docs
      • Generated docs for API types should now come from openshift/API
      • Testing
      • Regular regression testing should be sufficient, this is a copy paste for the most part and we expect the code won't compile if we break this

      Attachments

        Activity

          People

            ademicev@redhat.com Alexandr Demicev (Inactive)
            joelspeed Joel Speed
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: