Server resource advanced block_mapping - volume boot support.

[hjensas]

What would you like to see implemented?

I would like ORC to support creating Server resources with boot from volume and advanced block_device_mapping.

Example:

block_device_mapping=[
    {
       'uuid': IMAGE_ID,
       'boot_index': 1,
       'source_type': 'image',
       'destination_type': 'volume',
       'device_type': 'disk',
       'volume_size': 20,
       'delete_on_termination': True,
    },
    {
       'uuid': BLANK_IMG_ID,
       'boot_index': 0,
       'source_type': 'image',
       'destination_type': 'volume',
       'device_type': 'cdrom',
       'disk_bus': 'scsi',
       'volume_size': 5,
       'delete_on_termination': True,
    }
]

https://opendev.org/openstack/nova/src/commit/725a307693806e6e32834198e23be75f771bebc1/doc/api_samples/servers/v2.32/server-create-req.json

Additional information

Background - in the future I would like to see if replacing or have k-orc as an option to Openstack Heat in https://github.com/openstack-k8s-operators/hotstack. It uses advanced block device mapping to enable sushy-emulator RedFish virtual-media boot simulation. Ref: https://docs.openstack.org/sushy-tools/latest/user/dynamic-emulator.html#creating-openstack-instances-for-virtual-media-boot

Link to reference documentation

https://docs.openstack.org/api-ref/compute/#servers-servers

[mandre]

Definitely something that is on the roadmap.