Background

• Doc impact - yes
• support updating the firmware of BMH in OCP, currently this is something people need to do manually for each server they are using as BMH.

Our plan is to provide a CRD that will allow this action for BMH basically, so we will need to document how people can use it.

• What are we introducing to the customer with this epic?
  • How to configure YAML for CRD to update BMH in OCP.
• What market problem are we trying to solve?
• What is the use case? As an operator I want to install specific versions of firmware in my machines before installing the Operating System.
• Where in the Content journey does this fit?
• Does this apply only to a Telco use case or does it apply to other OCP/ACM use cases as well? OCP
• Why do we need this documentation for this epic?
• What is the support level status of this Epic (DP, TP, full support) in this release? Full support
• If this is new content for existing documentation, what are the changes?
• Do we need a diagram? No
• Do we need API reference doc?
• How hard is it to set up for testing? Is a development environment already available
• Are there any changes to the command line input?
• Are there any changes to the command line output?
• What changes will the user see?
• What is the target release? 4.15

People

• SME: imelofer , dbelyavs@redhat.com , janders@redhat.com 
• QE: jadha 

Resources and links

• Design doc
• What other Epics does this relate to for end-to-end customer facing workflows?
• How does it fit in with existing documented use cases?

Release Note

• Yes

(Day 2) Administer, Maintain, Upgrade/update (procedures)

• Are there administration tasks?
• Are there upgrade steps? Upgrade or downgrading BMH firmware.
• How do you troubleshoot fault conditions and conflicts?