Libvirt - Start LXC from a block device volume

Registered by Vladik Romanovsky on 2014-02-19

Currently, lxc containers can only be started from an image.

The purpose of this blueprint is to enable the lxc containers
to be started from a block device volumes.

Blueprint information

Status:
Started
Approver:
John Garbutt
Priority:
Low
Drafter:
Vladik Romanovsky
Direction:
Needs approval
Assignee:
Vladik Romanovsky
Definition:
Pending Approval
Series goal:
Accepted for trunk
Implementation:
Needs Code Review
Milestone target:
None
Started by
John Garbutt on 2014-09-16

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/libvirt-start-lxc-from-block-devices,n,z

Addressed by: https://review.openstack.org/74537
    libvirt: start lxc from block device

Gerrit topic: https://review.openstack.org/#q,topic:bp/libvirt-start-lxc-from-block-devices,n,z

Addressed by: https://review.openstack.org/74537
    libvirt: start lxc from block device

If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

Addressed by: https://review.openstack.org/88062
    libvirt: start LXC from a block device volume

Addressed by: https://review.openstack.org/89870
    replace NovaException with VirtualInterfaceCreate when neutron fails

Approved blueprint, now spec is approved. --johnthetubaguy (24th June 2014).

Addressed by: https://review.openstack.org/99973
    Method to filter only non root block device mappings

Addressed by: https://review.openstack.org/99974
    libvirt: persist lxc attached volumes across reboots and power down

Addressed by: https://review.openstack.org/104046
    libvirt: removing lxc specific disk mapping

Addressed by: https://review.openstack.org/104047
    libvirt: keeping lxc rootfs mounted until instance termination

Addressed by: https://review.openstack.org/104048
    libvirt: do not fail instance destroy, when volume is missing a mount_device

Not all the reviews have +2s and are not all are close to approval, so moving to juno-3. But please move this back to juno-2, should you get your patches approved in time. --johnthetubaguy 21st July 2014

Has a +2, so leaving in juno for now. --johnthetubaguy 2nd September 2014

Sorry, this has not yet been approved, so this will have to wait until kilo. Please contact me on IRC, or via email, for more details. Thank you. --johnthetubaguy 3rd September 2014

FFE granted --johnthetubaguy 5th September 2014

Sorry, FFE has now expired, this needs to have a spec merged in kilo, before getting merged. Please contact me for more details. --johnthetubaguy 16th September 2014

Addressed by: https://review.openstack.org/128825
    libvirt: virtio-net multiqueue

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.