Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/2373
** Bug watch added: github.com/canonical/cloud-init/issues #2373 https://github.com/canonical/cloud-init/issues/2373 ** Changed in: cloud-init Status: Confirmed => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1185526 Title: Cloudbase merge-back Status in cloud-init: Expired Bug description: To encourage reunification of the cloudbase-init code into cloudinit there are a few change that need to happen in cloudinit to make this possible. 1. Disk 'functions' need to be abstracted into the distro class (since windows does mounting/finding differently) instead of in utils.py. 2. The creation of a 'windows' distro class that implements the current + moved functionality. 3. Adjustment of the 'linux/posix' distro classes with the moved functionality. 4. More movement of os level utils into distro classes. a) See: https://github.com/cloudbase/cloudbase-init/blob/master/cloudbaseinit/osutils/base.py for a possible set of functions. 5. Addition of strict os-validation on cloud-init modules before they run (instead of the 'warning' that is emitted right now). This is needed to stop certain modules from trying to run on windows (or vice-versa). Something like a per 'module' check-if-should-run function that will immediatly stop the module from being ran on distros that it will not work on (ex: emit_upstart will likely never work on windows). 6. Conversion of modules which do not exist in cloud-init to cloud-init modules. a) See: https://github.com/cloudbase/cloudbase-init/tree/master/cloudbaseinit/plugins/windows To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1185526/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
