Virtuozzo containers boot from volume

Registered by Maxim Nestratov on 2015-05-06

Currently, in case boot from volume is chosen for Virtuozzo container ("parallels" libvirt driver hypervisor type with vm_mode=exe) an incorrect libvirt xml config is generated with two disk assigned to the instance. One for filesystem type disk and the other for bootable block device following in incorrect order which makes it impossible to boot shuch instances. This change intends to address this issue.

Blueprint information

Status:
Complete
Approver:
John Garbutt
Priority:
Low
Drafter:
Maxim Nestratov
Direction:
Approved
Assignee:
Maxim Nestratov
Definition:
Approved
Series goal:
Accepted for liberty
Implementation:
Implemented
Milestone target:
milestone icon 12.0.0
Started by
Maxim Nestratov on 2015-05-29
Completed by
John Garbutt on 2015-08-03

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/virtuozzo-container-boot-from-volume,n,z

Addressed by: https://review.openstack.org/186858
    libvirt: don't add filesystem disk to parallels containers unconditionally

We decided to approve the blueprint in the recent nova-meeting, but with a note that if the code seems like it needs more design work, we may revert this and force a spec review --johnthetubaguy 11 June 2015

Addressed by: https://review.openstack.org/189632
    libvirt: Always default device names at boot

Addressed by: https://review.openstack.org/180638
    libvirt: implement get_device_name_for_instance

Addressed by: https://review.openstack.org/229612
    libvirt: Always default device names at boot

Addressed by: https://review.openstack.org/229613
    libvirt: implement get_device_name_for_instance

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.