OCP: add /workloads endpoint

[bennyz]

No description provided.

[fabiand]

@bennyz what was your idea about the /workloads endpoint?

[bennyz]

@bennyz what was your idea about the /workloads endpoint?

it is currently missing for OCP providers, the main benefit is for UI, see linked issue (kubev2v/forklift-console-plugin#672)

[fabiand]

Thanks!

@yaacov how important is this for the UI?

[yaacov]

@fabiand hi, we expect the UI to help us by giving us hints / suggestions, for example suggesting some initial mappings, in some providers this information is spread across multiple inventory API calls.

Currently we don't hint users about the network mappings for OCP to OCP migration plans, and ask them to create a mapping manually:

Adding a "one stop" inventory call will help the UI implement better default "suggestions" for example in the above case of initial network and storage mappings for OCP to OCP plans.

Note:
we can also gather the same information in multiple calls to the inventory, but it makes more sense that if this information is useful and already available to have one call.