Epic Goal

ACM's graphql endpoint to be able to extract more VM related information:

VM/VMI information:

• get VM state (status.printableStatus),
• CPUs given to VM (spec.template.spec.domain.cores),
• memory given to VM (spec.template.spec.domain.memory.guest),
• volumes (DataVolumes) attached to VM (add related kind: DataVolume?),
• node VM is on,
• cluster VM is on,
• the VM desired running state (spec.running and spec.runStrategy)

DataVolume:

• get size (spec.storage.resources.requests.storage),
• storage class (spec.storage.storageClassName)

Managed Cluster:

• get api url

Why is this important?

Provide a one-stop solution for getting VM details

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.