(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.1 2010-02-03T23:09:48+00:00 2010-02-03T23:09:48+00:00 Scott Moser smoser@ubuntu.com 2010-02-03T23:09:48+00:00 urn:sha1:aed1c1e9fda1e78d19305e90f554d0dcb5388cd7 2010-01-29T15:09:25+00:00 Scott Moser smoser@ubuntu.com 2010-01-29T15:09:25+00:00 urn:sha1:511448c7afdcb5aaeb69a26e570fd600df512610 The sem_and_run and such needs some work, donesn't make a lot of sense for "always". 2010-01-28T20:49:29+00:00 Scott Moser smoser@ubuntu.com 2010-01-28T20:49:29+00:00 urn:sha1:f8eb4061196c8c2489ac7bf084e0fc0d3e6d27fc Also, move swap to use this format for specifying mounts. That way the user can turn off swap if they want with: | mounts: | - [ swap ] Other change wrapped in here is to have DataSourceEc2 read plain text (evalable) text for its metadata rather than pickl. This is really for debuging anyway, so any speed difference is not important. 2010-01-26T21:40:10+00:00 Scott Moser smoser@ubuntu.com 2010-01-26T21:40:10+00:00 urn:sha1:63ba097865e1d038d82a7fa1d6efd282784677f5 Move the writing of sources.list to CloudConfig. This way we have access to the cloud-config user data. Then, allow the user to specify the archive mirror using 'apt_mirror' key. Now, if specified in cloud-config, that is used, otherwise, we get one from the DataSource. One other change here is adding 'apt_preserve_sources_list'. If set to true, then overwriting of the sources.list with the selected mirror will not be done. 2010-01-26T20:51:38+00:00 Scott Moser smoser@ubuntu.com 2010-01-26T20:51:38+00:00 urn:sha1:930328be289ec7ab243b50360a73dab10f17844a 2010-01-26T18:19:49+00:00 Scott Moser smoser@ubuntu.com 2010-01-26T18:19:49+00:00 urn:sha1:262479dfe04e8342843df8851eaef61caaa95f5a This includes support for - signing key import via 'keyid' and 'keyserver' or 'key' - ppa:* support (provided by 'add-apt-repository') now there is a dependency on python-software-properties 2010-01-25T19:48:14+00:00 Scott Moser smoser@ubuntu.com 2010-01-25T19:48:14+00:00 urn:sha1:1252e1a690c5c4f53f01ed4d06b5558cce204fd2 Experimentation indicates that: a.) sshd will start without ssh_host_keys in place b.) sshd does not need to be restarted to read new keys written there any new ssh connection will use new keys see LP: #512377 for example of tests that found the above. With changes to ec2-automated-builds under 512377, the keys will not exist in the image, so the unlink will be generally not needed. The ssh server may start up before this code runs, however it will have no keys availalble until this writes or generates it. 2010-01-22T19:43:36+00:00 Scott Moser smoser@ubuntu.com 2010-01-22T19:43:36+00:00 urn:sha1:8c66ea2f37d34c26ee2f6013aa98605c213d0e02 ---- #cloud-config apt_update: true ssh_keys: rsa_private: | -----BEGIN RSA PRIVATE KEY----- MIIBxwIBAAJhAKD0YSHy73nUgysO13XsJmd4fHiFyQ+00R7VVu2iV9Qcon2LZS/x ... REPPOyrAspdeOAV+6VKRavstea7+2DZmSUgE -----END RSA PRIVATE KEY----- rsa_public: ssh-rsa AAAAB3NzaC1yc2E...18QJvWPocKJtlsDNi3 smoser@host dsa_private: | -----BEGIN DSA PRIVATE KEY----- MIIBuwIBAAKBgQDP2HLu7pTExL89USyM0264RCyWX/CMLmukxX0Jdbm29ax8FBJT ... 8KucvUYbOEI+yv+5LW9u3z/BAoGBAI0q6JP+JvJmwZFaeCMMVxXUbqiSko/P1lsa -----END DSA PRIVATE KEY----- dsa_public: ssh-dss AAAAB3NzaC1kc3M...ybngIy66PMEoQ= smoser@host ---- 2010-01-22T18:59:25+00:00 Scott Moser smoser@ubuntu.com 2010-01-22T18:59:25+00:00 urn:sha1:3c0b9591b5203e60ac3cdda030b6eecbae27e938 2010-01-22T16:21:16+00:00 Scott Moser smoser@ubuntu.com 2010-01-22T16:21:16+00:00 urn:sha1:1108a511010c4497e94bca78769bef30e3c01dff