** Description changed: - Currently Cloud-Init requires the ConfigDrive to be available on an - unpartitioned disk, not a CDROM drive. Windows doesn't recognise this - type of devices and mounting them requires the extraction of the data - from the raw disk to an ISO file to be mounted / extracted afterwards. + == Begin SRU Information == + [Impact] + 'config-drive' is a mechanism for passing data from the hypervisor (or + cloud platform) to the guest (instance). cloud-init as delivered in 12.10 + correctly implements locating this drive as it is present in OpenStack + in the folsom release. + + A change is being made in grizzly to allow for the device that contains + the data to be presented as a CD-ROM rather than a block device as it was + done in folsom. This changes is primarily driven by non-linux + hypervisors. + + In order to support Ubuntu cloud images running as a guest on grizzly + hypervisors that choose to attach the config-drive as a CD-ROM, we need + to make a change to cloud-init to consider CD-ROMs as a possible source. + Previously, cloud-init would ignore any device that ended with a digit + (0-9). Now, it allows the data to come from any block device that is + not a partition. + + [Test Case] + Attached to this bug is an ISO that provides config-drive-v2 data. + The following is the current situation: + attached-as-cdrom: cloud-init ignores. + attached-as-disk: cloud-init processes + + After the fix is applied, you will see; + attached-as-cdrom: cloud-init processes + attached-as-disk: cloud-init processes + + The provided ISO file simply sets a password for the 'ubuntu' user to + 'passw0rd'. So, verification that the test worked is as easy as logging + in with 'ubuntu' and 'passw0rd', either via ssh or via the console. + + To perform this test, download a quantal cloud-image from + http://cloud-images.ubuntu.com and boot it with kvm. + + Booting a kvm instance with iso as cdrom: + kvm -drive disk1.img,if=virtio -cdrom lp-1077020.iso + Booting a kvm instance with iso as disk: + kvm -drive disk1.img,if=virtio -drive lp-1077020.iso,if=virtio lp-1077020.iso + + [Regression Potential] + The potential for regression is low. The most likely possibility for + error would be in incorrectly identifying a cd-rom and its content as a + config-drive. + == End SRU Information == + + + Currently Cloud-Init requires the ConfigDrive to be available on an unpartitioned disk, not a CDROM drive. Windows doesn't recognise this type of devices and mounting them requires the extraction of the data from the raw disk to an ISO file to be mounted / extracted afterwards. It should be optionally possible to access the ConfigDrive as a plain CDROM as well to simplify the access on any operating system. The raw HDD option compared to the CDROM one offers slightly better data access protection especially for the admin_pass field, but as this is going to be a deprecated option in the short term, the benefits are very limited compared to the additional complications for accessing the ConfigDrive data.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1100545 Title: It should be possible to access the ConfigDrive as a CDROM drive as well To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1100545/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
