Feature Overview

Today after scaling out compute nodes in the deployment the human operator needs to manually execute nova-manage cell_v2 discover_hosts to make the new compute usable. We should try to automate this as it is a constant source of support requests and CI instabilities.

For ironic computes this is already automated by the nova-operator.

For EDPM computes nova-operator has no way today to detect when a new EDPM compute is deployed and therefore nova-operator cannot run the discovery. At the moment dataplane-operator knows when an EDPM deployment finished but it does not track if this means a new compute is deployed (it does not even have a concept of an EDPM compute just and EDPM node).

Goals

• Enable Nova scheduler based host discovery by default in RHOSO installer
• Update documentation accordingly

Requirements (mandatory -_ Complete while in Refinement status):
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

Done - Acceptance Criteria:

• edpm nodes are discovered automatically without human operator actions

Use Cases - i.e. User Experience & Workflow

• As cloud operator I don't want to execute edpm host discovery manually, but want to have edpm host discovered

Documentation Considerations
Documentation has to be updated accordingly, because currently it describes manual host discovery process. This process will still be functional after this update, but is not necessary any more unless cloud operator cannot accept a minor delay which scheduler auto-discovery introduced.

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone