From 13e4412165e73ebf8ec6387eeb8dd8721b60a986 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 13 Oct 2018 21:26:30 -0400 Subject: comment --- ...omment_4_dbd2c399c8ef8ac56ae06f1a701fdc45._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/todo/support_for_libvirt_KVM_VMs/comment_4_dbd2c399c8ef8ac56ae06f1a701fdc45._comment diff --git a/doc/todo/support_for_libvirt_KVM_VMs/comment_4_dbd2c399c8ef8ac56ae06f1a701fdc45._comment b/doc/todo/support_for_libvirt_KVM_VMs/comment_4_dbd2c399c8ef8ac56ae06f1a701fdc45._comment new file mode 100644 index 00000000..8ce06a1c --- /dev/null +++ b/doc/todo/support_for_libvirt_KVM_VMs/comment_4_dbd2c399c8ef8ac56ae06f1a701fdc45._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2018-10-14T01:10:16Z" + content=""" +I do think that the conditional property would be a good way for this to +work. + +I think there could also be VMs where you don't want the overhead of +running propellor inside the VM (especially if the emulation is slow, or +you don't want to allocate that much memory to the VM, or just have a lot +of VMs), and the content is disposable. Then propellor could restart the VM +when it changes the disk image. + +There's room for multiple ways to do it.. + +The disk image building side of this looks easy to me, so if you do the libvirt +stuff, Sean, I might contribute something. :) +"""]] -- cgit v1.2.3