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
Tracked in Github Issues as https:/