Feature Overview (mandatory - Complete while in New status)

This feature aims to implement and (or) integrate (existing) solution of dynamic management tool or framework for resources such as GPUs, NVMe devices or similar. The tool/framework needs be able to provide the managed resources to Nova service, so that it is possible to attach such devices to VM instances in Nova.

Goals (mandatory - Complete while in New status)

This feature will be beneficial for OpenStack users, who won't need to manage accelerator resources manually, so that those can be attached to VMs.

RHOSO currently doesn't have possibility to effectively manage resources in dynamic fashion. The goal is to allow dynamic accelerator resource management within RHOSO which improves competitiveness of the product. 

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 (mandatory - Complete while in Refinement status):

It is possible to manage accelerator resources such as GPU and NVMe resources via OpenStack user interface (whether CLI or GUI).

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
<your text here>

Out of Scope __(Initial completion while in Refinement status):
High-level list of items or persona’s that are out of scope.
<your text here>

Documentation Considerations __(Initial completion while in Refinement status):
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..
<your text here>

Questions to Answer __(Initial completion while in Refinement status):
Include a list of refinement / architectural questions that may need to be answered before coding can begin.
<your text here>

Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>

Customer Considerations __(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

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

• …