You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Launchpad user Scott Moser(smoser) wrote on 2012-11-07T14:54:16.438947+00:00
Previously, I have handled renames of config modules in the Ubuntu packaging.
However, that means that really just throws that maintenance onto the packager. It'd be much nicer if cloud-init handled it somehow. The specific motivation for this is [1]. If the packaging doesn't change to address it, the new "package-update-upgrade-install" would be run again as it has never been run before.
The things I'd like to have:
ability to specify that
apt-update-upgrade was split into 2 pieces: apt-configure, package-update-upgrade-install
foo changed in name to bar
it looks like semaphores can contain '-' in them, based on their name in the config. Also, the config is inconsistent even in itself with respect to usage of '_' or '-'. I'd like to be consistent in the config (config/cloud.cfg) and enforce that 'set_hostname' is the same as 'set-hostname'.
Launchpad user Scott Moser(smoser) wrote on 2012-11-07T18:53:29.728707+00:00
I talked with harlowja about this and we agreed that it makes sense to at least look at a 'cc_fixup' module that would run first, and it would go through and apply updates. psuedocode:
if module_ran("apt-update-upgrade"):
mark_ran("apt-configure", "package-update-upgrade-install")
if module_ran("foo-was-renamed-to-bar"):
mark_ran("bar")
Where 'mark_ran' might even put the cloud-init version that applied the change.
This bug was originally filed in Launchpad as LP: #1075980
Launchpad details
Launchpad user Scott Moser(smoser) wrote on 2012-11-07T14:54:16.438947+00:00
Previously, I have handled renames of config modules in the Ubuntu packaging.
However, that means that really just throws that maintenance onto the packager. It'd be much nicer if cloud-init handled it somehow. The specific motivation for this is [1]. If the packaging doesn't change to address it, the new "package-update-upgrade-install" would be run again as it has never been run before.
The things I'd like to have:
ability to specify that
it looks like semaphores can contain '-' in them, based on their name in the config. Also, the config is inconsistent even in itself with respect to usage of '_' or '-'. I'd like to be consistent in the config (config/cloud.cfg) and enforce that 'set_hostname' is the same as 'set-hostname'.
--
[1] https://code.launchpad.net/~harlowja/cloud-init/pkg-up-install-goodies/+merge/130019
The text was updated successfully, but these errors were encountered: