Martin, guests are just systems. People can and do use lvm and raid in cloud guests quite commonly. Its even defined good practice in many cases (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html). with regard to "cloud images on real hardware". Thats explicitly what maas does. We use the "maas ephemeral image". Which is built starting from the cloud image. we then install the -generic kernel inside, and a very few other packages (cloud-initramfs-dyn-netconf maas-enlist open-iscsi). We could add mdadm and lvm2 to that list. However, we're interested in reducing that delta rather than increasing it.
Wrt boot delays, there should not be significant boot delay (if any) in cases where root= does not require it. Am I wrong in that assumption? We're really looking to *reduce* deltas and "things" that we produce, rather than create more. I would also probably at some point add 'cloud- initramfs-dyn-netconf' and 'open-iscsi' to the cloud-image and then drop maas-enlist above. Then the only difference between a cloud image and a "real system" from the point of view of a default install would be the kernel selection. We've even investigated if we could reasonably get rid of that difference. There are costs to having one image that is expected to work in all cases, but there are also lots of benefits. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491102 Title: [FFE] add mdadm and lvm2 to cloud image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1491102/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
