Hi trialotto, cloud-init has default settings for Azure instances that ensure that the first partition of the ephemeral disk is formatted as ext4. It does this by providing default values for disk_setup and fs_setup; you can see these at http://bazaar.launchpad.net/~cloud-init-dev/cloud- init/trunk/view/head:/cloudinit/sources/DataSourceAzure.py#L54.
cloud-init, by default, mounts the first partition of the first ephemeral disk at /mnt. You can see the code that does this at http://bazaar.launchpad.net/~cloud-init-dev/cloud- init/trunk/view/head:/cloudinit/config/cc_mounts.py#L236. If you are changing the layout of the disk, you will also need to provide mount configuration (using the `mounts` configuration key) so that cloud-init knows what it should mount where. We could, potentially, look at making cloud-init a little smarter about automatically working out mounts, but this would require a fair bit of testing across different platforms. Please let me know if this addresses your issues. Thanks, Dan -- 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/1410835 Title: Azure ephemeral disk and custom mount points To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1410835/+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
