vyos-cloud-init.git/cloudinit/__init__.py, branch rolling (mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling 2016-12-22T22:04:28+00:00 LICENSE: Allow dual licensing GPL-3 or Apache 2.0 2016-12-22T22:04:28+00:00 Jon Grimm jon.grimm@canonical.com 2016-11-22T23:09:53+00:00 urn:sha1:b2a9f33616c806ae6e052520a8589113308f567c This has been a recurring ask and we had initially just made the change to the cloud-init 2.0 codebase. As the current thinking is we'll just continue to enhance the current codebase, its desirable to relicense to match what we'd intended as part of the 2.0 plan here. - put a brief description of license in LICENSE file - put full license versions in LICENSE-GPLv3 and LICENSE-Apache2.0 - simplify the per-file header to reference LICENSE - tox: ignore H102 (Apache License Header check) Add license header to files that ship. Reformat headers, make sure everything has vi: at end of file. Non-shipping files do not need the copyright header, but at the moment tests/ have it. Moved these functions to utils. 2012-06-12T00:12:29+00:00 Joshua Harlow harlowja@yahoo-inc.com 2012-06-12T00:12:29+00:00 urn:sha1:a987baa675c19c8c2064c7eee786e93468a9c8ec Move most of this functionality to either cloud-init object or utils. 2012-06-09T19:31:56+00:00 Joshua Harlow harlowja@yahoo-inc.com 2012-06-09T19:31:56+00:00 urn:sha1:e78c20b9aba7e031d7e29e9ab4763a6ab430a0dd Remove parsed config cache, and cleanup cmdline function. 2012-06-09T02:10:58+00:00 Joshua Harlow harlowja@yahoo-inc.com 2012-06-09T02:10:58+00:00 urn:sha1:3025072fa803124b4067181c712a758f732f771b This now only holds some simple top level functions. 2012-06-09T00:55:52+00:00 Joshua Harlow harlowja@yahoo-inc.com 2012-06-09T00:55:52+00:00 urn:sha1:3e6217b64ba6436af991e52163fea850f21bb770 TODO: maybe just move them to utils? 1. Move cloud init and cloud config objects to a cloud file. 2012-06-07T20:46:54+00:00 Joshua Harlow harlowja@yahoo-inc.com 2012-06-07T20:46:54+00:00 urn:sha1:32362c0ac63f10d7a33e3b95dd91a544a1cbdf54 2. Cleanup main __init__ file with shell additions, constants usage, os.path usage. move the reading of the cmdline cloud-config url to cloud-init.py 2012-04-05T04:08:42+00:00 Scott Moser smoser@ubuntu.com 2012-04-05T04:08:42+00:00 urn:sha1:67fe09104cb347c03ea608c72a1382e8ea252b1d The reason for moving this from cloudinit/__init__.py was that it was running too late there. The cloudinit.parsed_cfgs variable was already filled by cloud-init.py's reading of cloud config. I'm sure I had done this so that it would not have to re-parse configs. I think the right way to handle this is to move that logic back to cloudinit/__init__.py and add some function like 'reread_configs()' that would re-read all releavent cofnigs and re-setup logging. That seemed more error prone at the moment, with limited time. initial checkin of kernel commandline cloud-config url support 2012-04-05T01:35:32+00:00 Scott Moser smoser@ubuntu.com 2012-04-05T01:35:32+00:00 urn:sha1:7b2fc4e014e6b7a43e6b8fc719d82c3d0b0a8bed rename DataSourceMaaS to DataSourceMAAS, generally use MAAS everywhere 2012-03-16T15:25:52+00:00 Scott Moser smoser@ubuntu.com 2012-03-16T15:25:52+00:00 urn:sha1:3522b7b49368f486f61c220151212f68e9cc9782 instead of MaaS or Maas, use MAAS consistently. The only non 'MAAS' left are all lower case. Warn in user-data processing on non-multipart, non-handled data 2012-03-12T18:56:35+00:00 Scott Moser smoser@ubuntu.com 2012-03-12T18:56:35+00:00 urn:sha1:eefca80065bf9cae734022c0665aa8ffbf3ee81e If user-data is supplied that is not multipart, and is unhandled, then log a warning. A warning by default will get to the console, so the user can see it even if they cannot get into the instance. If they don't see it there, it would still be available in the cloud-init log.