Adding a new usecase checker for Repair Location Identification

[dchanman]

I'd like to propose a usecase for identifying components in repair locations, Google has published a public specification here: https://github.com/google/ecclesia-machine-management/blob/master/ecclesia/lib/redfish/g3doc/topology.md

We're hoping this usecase is general enough and uses only standard Redfish fields that this may be appropriate to be added to this tool.

Just wanted to ask what the process of doing so would be. Are there any requirements of consensus or cross-company agreements required for a usecase to be considered appropriate for adding?

Thanks,
Derek

[mraineri]

I certainly like the idea. My only concern at this time would be if the test logic would be too strict to be realistically enforceable; not all system architectures will necessarily follow the same labeling and serviceability semantics.

It might be good to propose sample pass/fail test logic to see if others can weigh in on the proposal.