Project description and goals
HDV tool came out through the desire to automate the validation of hardware underlying the stack / infrastructure. The current task is to refract the cirv-hdv code to be much friendly for usage, and easily extensible to cover much more hardware model via customize the cases related configuration file and generate the user-friendly test report on the tests results. Current prototype code is based on redfish interface, we also have a future plan to add support for IPMI interface tool.
Benefits: The hdv tool is very useful to larger deployments for verifying the hardware, settings, network wiring, etc., which will save valuable time for operators and users in standing up infrastructure.
Tasks:
| # | Activity | Week | Status |
|---|---|---|---|
| 1. | Existing prototype Overview, Familiar with redfish and connection setup | 0 - 2 weeks | COMPLETED |
| 2. | code refraction on redfish implementation
| 2 - 5 weeks | ACTIVE |
| 3. | redefine the hardware description file per cntt HDV requirements | 5 - 6 week | PENDING |
| 4. | remove the support of excel format configuration file from project | 6 - 7 weeks | PENDING |
| 5. | extend the case configuration template from one hardware model to multiple case | 7 - 8 weeks | PENDING |
| 6 | Bug fixing | 8 - 9 weeks | PENDING |
| 7. | Document user guide | 9 - 10 weeks | PENDING |
| 8. | Start IPMI interface, learn ipmi operation command | 10 - 12 weeks | PENDING |
| 9. | summarize ipmi usage | 12 - 13 weeks | PENDING |
| 10. | ipmi tool of type raw parse rule file definition | 13 - 15 weeks | PENDING |
| 11. | ipmi code implementation | 15 - 24 weeks | PENDING |
Deliverables
- Hardware validation tool
- The Hardware resource description file, which is a large scale of hardware credentials information for servers.
- User Guide
Evaluation Criteria
1st evaluation (end of week 6): Good understanding of project and code refraction for test cases.
2nd evaluation (end of week 12): Completed redfish interface including user guide.
3rd evaluation (end of week 18): summarize ipmi usage and define the rule file.
4th evaluation (end of week 24): Automated hardware validation tool with documentation.