Normal Feature Overview
Ability to pull servers already existing in Vendor Management tools like HPE OneView, DELL OME, HPE Compute Ops Mgmt
Goals
This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature
- Import and consume servers from other management tools such as HPE OneView, DELL OME, HPE Compute Ops Mgmt as baremetal hosts into the RHACM inventory
- Importing that way will mean that SSO to iLO will work and there will not be a need to specify credentials and hardware info like mac addresses
Requirements
This Section: A list of specific needs 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.
| Requirement | Notes | isMvp? |
|---|---|---|
| CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
| Release Technical Enablement | Provide necessary release enablement details and documents. |
YES |
| Importing hardware details from vendor tool | HPE OneView | YES |
| Importing hardware details from vendor tool | DELL OME | YES |
| Importing hardware details from vendor tool | HPE Compute Ops Mgmt | NO |
| BMH configuration generated automatically | using info from the vendor tool | YES |
(Optional) Use Cases
- Importing into RHACM inventory using details from other hardware solutions, helping avoid human errors and speed up onpremise/baremetal deployments
Questions to answer
- …
Out of Scope
- …
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
The goal is to pull details from the vendor to avoid typing them again. Each of the tools listed does seem to have an API documented :
- HPE OneView API quick links : https://support.hpe.com/hpesc/public/docDisplay?docId=a00118111en_us&docLocale=en_US&page=index.html
- Dell OME restfull api guide : https://www.dell.com/support/manuals/en-uk/dell-openmanage-enterprise/ome_p_api_guide/revision-history
- HPE Compute Ops Management Dev Guide : https://developer.greenlake.hpe.com/docs/greenlake/services/compute-ops-mgmt/public/guide/
- HPE Compute Ops Management API doc : https://developer.greenlake.hpe.com/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/overview/
Assumptions
We assume it is going to be possible to pull the details required to avoid having to fill in info when adding IMPI, ILO or iDRAC
Customer Considerations
They want to avoid having to fill in details that take time and could easily add errors when inputing mac addresses and other hardware infos
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy.
New content on how to add the connection details to the vendor tool needs to be added to the RHACM Cluster documentation
- What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
They set up a connection to the vendor and there should be an option to pull values from a provider if a match is found
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?
