@Scott (and everyone else),
It has been a while since visiting this launchpad and/or since doing
some decent testing.
Nevertheless, I recall correctly, there is this option (also discussed
on this launchpad) to work with partitions and disk setups on Azure VMs:
just inject some custom data.
The
In cloud-init right now we have the following inputs of configuration
data, in increasing order of precedence.
a.) system configuration in /etc/cloud/cloud.cfg
b.) system configuration in /etc/cloud/cloud.cfg.d/*.cfg
these are increasing in C locale sorted order (thus they use XX-name.cfg ,
X
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
** Changed in: cloud-init (Ubuntu)
Assignee: Ben Howard (utlemming) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374115
Title:
Allow cloud-config to modify partitioning and mo
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Ben Howard (utlemming)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374115
Title:
Allow cloud-config to modify partitioning and mo
@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 b
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,
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 n
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 time.
10 matches
Mail list logo
