Instances

Deltacloud instances are (of course) equivalent to RHEV-M VMs.

One possibility is that we might only support stateless RHEV-M VMs initially. Why would we do that, though?

When starting an instance, the client may supply a hardware profile ID and some profile parameters. We need to pass the default or supplied parameters to RHEV-M's VM start action.

An instance's instance_profile attribute describes the actual hardware profile used.

image_id should be the template name. realm_id should be the data center name.

owner_id should probably be derived from which user has admin permissions on the VM?

We'll need to map RHEV-M's various instance states to PENDING, STOPPED or RUNNING.

The public_addresses attribute could be obtained from the RHEV-M guest agent reported hostname and IP address properties. There's no equivalent to private_addresses.

The launch_time attribute is equivalent to RHEV-M's start_time attribute.

There's no equivalent to the keyname attribute.

The actions we need to support are start, stop and reboot.