diff options
| author | Scott Moser <smoser@ubuntu.com> | 2012-07-10 14:28:04 -0400 |
|---|---|---|
| committer | Scott Moser <smoser@ubuntu.com> | 2012-07-10 14:28:04 -0400 |
| commit | ac867b475eea28429333966fd0f7d10564e8417a (patch) | |
| tree | e2a6acae1d98ec65cd208a9f28ad1c161c92bc41 | |
| parent | c07c5f6c4ec808e680bbbeedb7f06e3c74ecb34f (diff) | |
| parent | b2817ac6dbfadff969aeb1ac28408bf960c94a3c (diff) | |
| download | vyos-cloud-init-ac867b475eea28429333966fd0f7d10564e8417a.tar.gz vyos-cloud-init-ac867b475eea28429333966fd0f7d10564e8417a.zip | |
Add a comment/todo for the future, that instead of having distro
specific modules in cloudinit, that maybe we should encourage a 'config'
website or something similar, and let people host common modules they
find useful there, and keep the ones built-in to cloud-init completly
distribution agnostic.
| -rw-r--r-- | TODO | 9 |
1 files changed, 9 insertions, 0 deletions
@@ -35,3 +35,12 @@ something to remove later, and just recommend using 'chroot' instead (or the X different other options which are similar to 'chroot'), which is might be more natural and less confusing... +- Instead of just warning when a module is being ran on a 'unknown' distribution + perhaps we should not run that module in that case? Or we might want to start + reworking those modules so they will run on all distributions? Or if that is + not the case, then maybe we want to allow fully specified python paths for + modules and start encouraging packages of 'ubuntu' modules, packages of 'rhel' + specific modules that people can add instead of having them all under the + cloud-init 'root' tree? This might encourage more development of other modules + instead of having to go edit the cloud-init code to accomplish this. + |