** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Ben Howard (utlemming)
--
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/1374115
Title:
Allow cloud-config to
@Stephen,
The mount location CAN be changed by setting
- ResourceDisk.Format=y (instead of n) AND
- ResourceDisk.MountPoint=/opt (or any other directory, instead of /mnt)
in waagent.conf.
The change becomes effective after a shutdown and start-up sequence (and
I assume the same applies to a
That's what I meant, on Ubuntu images the ResourceDisk.Format should be
n because cloud-init handles this. We do not want the Linux agent and
cloud-init fighting over formatting or reformatting, and then mounting
the resource disk.
You're right, perhaps these parameters should not exist in the
@Stephen,
I think you know why I stated that the ResourceDisk.Format variable is a
remarkable explanation for specific behaviour of waagent.
It must also be clear why I (also) stated that some parts of the waagent
script are rather obsolete or unnecessary.
A huge part of the waagent script can
No, the mount location cannot be modified on Ubuntu via the
waagent.conf, that is the issue. I would like a way to modify the mount
point post-provisioning.
The only way to change the mount point on Azure is to use CustomData
(like user data on other clouds) to send a cloud-config to modify the
The mount location can be reconfigured in the waagent.conf file, after
provisioning of the VM.
A shut-down and start-up sequence is required, in order to let the
changed settings become effective.
It is not desirable and/or advisable to change partitioning and/or mount
locations on creation
