Feature Overview
Main goal of this feature is to deliver deployment logic of GPU related dependencies into edpm-ansible, so that it can be used within operators for automated deployment. This will enable automated dataplane hosts management which can then enable development of new features on Nova or Cyborg side.

Goals (mandatory - Complete while in New status)

• To provide relevant GPU drivers deployment logic via Ansible playbook(s)/role(s)
• To provide other GPU-related deployment logic via Ansible playbook(s)/role(s)

Requirements (mandatory -_ Complete while in Refinement status):

Done - Acceptance Criteria (mandatory - Complete while in Refinement status):

• It is possible to deploy GPU drivers and other GPU-related software in automated fashion by using edpm-ansible playbooks/roles

Out of Scope __(Initial completion while in Refinement status):
The relevant OpenStack operators' integration is out of scope for this feature. That will happen on-demand once the features for Nova or Cyborg will be under development

Documentation Considerations __(Initial completion while in Refinement status):
Given the fact that the deliverables are dependencies for future features there should not be documentation required unless the customer will require the automation before the Nova/Cyborg features are delivered. In that case the manual execution of the playbooks/roles can be documented in KCS articles, but this is not necessarily part of deliverables for this feature.

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

• …