summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* replace bug links with LP: # syntax, use '$RELEASE' for apt sourceScott Moser2012-04-092-6/+4
| | | | cloud-init expands $RELEASE in a source so it can easily be used.
* Added an example for using Chef with oneiricLorin Hochstein2012-04-071-0/+92
|
* Added GPG keyLorin Hochstein2012-04-071-5/+33
|
* Fixed opscode repo in chef recipeLorin Hochstein2012-04-051-4/+18
| | | | Also added some comments and captured the output
* add reading of 'seedfrom' via DataSourceNoCloud's DataSourceConfigScott Moser2012-04-041-0/+7
| | | | | | | | | | | | | | | | | | | | | What this does is provide an second DataSource that could use the kernel command line url=. For example: ro root=/dev/vda url=http://example.com/i-abcdefg/ http://example.com/i-abcdefg/ would contain: datasource: NoCloud: # default seedfrom is None # if found, then it should contain a url with: # <url>/user-data and <url>/meta-data # seedfrom: http://my.example.com/i-abcde seedfrom: http://example.com/i-abcdefg/ Then, the NoCloudNet DataSource would find that seedfrom config and consume data at http://example.com/i-abcdefg/user-data and http://example.com/i-abcdefg/meta-data
* initial checkin of kernel commandline cloud-config url supportScott Moser2012-04-041-0/+48
|
* allow cloud-config to control if resizefs is blocking or notScott Moser2012-03-211-0/+2
|
* rename DataSourceMaaS to DataSourceMAAS, generally use MAAS everywhereScott Moser2012-03-161-1/+1
| | | | | instead of MaaS or Maas, use MAAS consistently. The only non 'MAAS' left are all lower case.
* add option apt_pipelining to cloud-config to address s3 mirrors (LP: #948461)Scott Moser2012-03-091-0/+9
|\ | | | | | | Thanks to Ben Howard.
| * mention bug number in cloud-config.txtScott Moser2012-03-091-1/+1
| |
| * Simplified proposed patchBen Howard2012-03-081-3/+3
| | | | | | | | | | | | | | | | - Changed values to be more simplistic and intuitive - Only allow pipelining values up to 5 - Changed to per_instance over per_always to remove need for tracking the values - Fixed Python style
| * Added ability of cloud-init to manage apt http pipeliningBen Howard2012-03-071-0/+9
| | | | | | | | | | - cloud-config option of "apt-pipelining" - Address LP: 948461
* | doc fixesScott Moser2012-03-081-6/+2
| |
* | commit initial config information for maas datasourceScott Moser2012-03-051-0/+15
|/
* more documentation on configdriveScott Moser2012-02-171-0/+45
|
* add doc for configdriveScott Moser2012-02-171-0/+73
|
* support reading network interface config from DataSourceNoCloudScott Moser2012-02-171-0/+55
| | | | document usage of DataSourceNoCloud from vfat or iso disk.
* add support for salt minionsJeff Bauer2012-02-111-0/+53
|
* comment fix to cloud-config-chef.txt [Lorin Hochstein]Scott Moser2012-01-201-1/+1
|\
| * Corrected comment: puppet -> chefLorin Hochstein2012-01-201-1/+1
| |
* | Add ca-certs example to docs.Mike Milner2012-01-171-0/+31
|/
* support configuration of landscape-client via cloud-config (LP: #857366)Scott Moser2011-12-201-0/+13
| | | | | | | This adds the ability to configure landscape client code from cloud-config. The fields available are those that were populated to /etc/landscape/client.conf when I ran landscape-config on precise ('11.07.1.1-0ubuntu2')
* update documentation for bootcmdScott Moser2011-12-201-1/+5
| | | | | - reference cloud-init-per - mention that INSTANCE_ID is in environment of bootcmd scripts
* output public ssh host keys to console on boot (LP: #893400)Scott Moser2011-12-201-0/+7
| | | | | | | | | | | | | | | | | | | | | | Currently cloud-init writes something like this to console output: ec2: ############################################################# ec2: -----BEGIN SSH HOST KEY FINGERPRINTS----- ec2: 2048 78:ae:f3:91:04:6f:8d:ee:ef:e1:2d:72:83:6a:d0:82 root@h (RSA) ec2: 1024 d3:b6:32:64:22:d4:43:05:f9:25:b4:f3:65:4e:e2:51 root@h (DSA) ec2: -----END SSH HOST KEY FINGERPRINTS----- ec2: ############################################################# the key fingerprints are useful for humans to read, but not so useful for machines, as you cannot populate a KnownHostsFile (~/.ssh/known_hosts) from the data there. This change adds output like: -----BEGIN SSH HOST KEY KEYS----- ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdH......STI= root@h ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDYRIQe6m......tWF3 root@h -----END SSH HOST KEY KEYS----- Those lines can easily be grabbed and appended to a known_hosts file.
* revert default handling of /etc/hosts to 0.6.1 style (Ubuntu 11.04)Scott Moser2011-12-191-37/+69
| | | | | | | | | | | | | | | | | | | | The default management of /etc/hosts in 0.6.2 (Ubuntu 11.10) was problematic for a couple different uses, and represented a change in what was present in previous releases. This changes the default behavior back to the way it was in 11.04/0.6.1. It makes 'manage_etc_hosts' in cloud-config more than just a boolean. It can now have 3 values: * False (default): do not update /etc/hosts ever * "localhost": manage /etc/hosts' 127.0.1.1 entry (the way it was done in 11.10/0.6.2) * True (or "template"): manage /etc/hosts via template file This addresses bugs * LP: #890501 * LP: #871966
* make DataSourceEc2 more resilliant to slow metadata service (LP: #894279)Scott Moser2011-12-191-8/+6
| | | | | | | | | | | | | | | | | | | This increases the timeout for a metadata request to something that should be easily satisfiable (50 seconds). But hopefully does so while still keeping the case of no-metadata service in mind. Previously, there was a small timeout and many retries (30) would be done. Now, - larger timeout (50 seconds) by default - retry until a given "max_wait" is reached (120 seconds default) The end result is that if we're hitting the timeout, there will only end up being a couple attempts made. But if the requests are coming back quickly then we'll still make several attempts. There is one EC2DataSource config change, now 'retries' is not used, but rather 'max_wait' to indicate generally how long it should try to find a metadata service.
* add apt_proxy doc to cloud-config.txtScott Moser2011-12-161-0/+3
|
* add documentation for mirror selectionScott Moser2011-12-161-0/+23
|
* doc/ovf/README: documentation fix [David Medberry]Scott Moser2011-12-061-1/+1
| | | LP: #900537
* fix doc for ec2 datasourceScott Moser2011-11-221-1/+1
|
* add documentation of new config optionsScott Moser2011-10-311-0/+14
| | | | | This adds doc/examples/cloud-config.txt data for the options that were added when pulling in Fedora support.
* Improve OVF documentation and provide functional demo.Scott Moser2011-10-137-5/+295
|
* [doc] add 'preseed' string to cloud-config for debconf-set-selectionsScott Moser2011-09-131-1/+1
|
* Bringing in proper json support for firstboot.json from ↵Mike Moulton2011-09-131-0/+7
| | | | | | lp:~avishai-ish-shalom/cloud-init/chef Bringing in 'initial_properties' support from lp:~avishai-ish-shalom/cloud-init/chef
* Set sane defaults for 'node_name' and 'environment'Mike Moulton2011-09-121-2/+5
| | | | | Support both 'validation_cert' and 'validation_key' for backwards compatibility Cleaned up line length
* Modifications to properly support both 'gems' and 'packages' install types.Mike Moulton2011-09-101-15/+11
| | | | | Added support for 'node_name' and 'environment' properties. Renamed 'validation_cert' to 'validation_key' to match Chef's nomenclature.
* add awareness of ecdsa keys.Scott Moser2011-08-151-1/+2
|
* minor fixes to docScott Moser2011-08-031-2/+2
|
* cloudinit/util.py: fix syntax errorScott Moser2011-08-031-9/+43
|
* add example part-handler implementing the version 2 part-handlerScott Moser2011-08-031-0/+38
|
* make 'include-once' really "download source once per-instance"Scott Moser2011-07-261-1/+3
| | | | | | | | | | | Marc's implementation would only ever process the include-once urls a single time. This changes that to process them every time, with the second time coming from a file on disk rather than the url. You can then do expiring or one time use URLs in the include-once and have all function of if the content was there every time. The cached file is readable by root-only.
* clarify warning text in mcollective config exampleScott Moser2011-07-261-1/+2
|
* Added ssl cert support to mcollectiveMarc Cluet2011-07-251-0/+33
|
* Added new feature include-onceMarc Cluet2011-07-252-0/+15
|
* add chef [Avishai Ish-Shalom]Scott Moser2011-07-181-0/+38
|\
| * Added Chef pluginAvishai Ish-Shalom2011-04-211-0/+38
| |
* | make the default "fill in" mount entries configurable. (LP: #785542)Scott Moser2011-06-171-1/+6
| | | | | | | | | | | | The primary motivation for this is so that 'nobootwait' is not hard coded to appear in the fs_opts field. LP: #785542
* | make the "cloud-config ready" command configurable (LP: #785551)Scott Moser2011-06-171-0/+12
| | | | | | | | | | | | | | | | | | | | Previously, when cloud-config was ready, cloud-init would emit an upstart event with: initctl emit cloud-config Now, that command is configurable via the 'cc_ready_cmd' value in cloud.cfg or user data. The default behavior is not changed. LP: #785551
* | change, and make configurable the prefix for entries in root authorized_keysScott Moser2011-06-171-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes the prefix for entries added to root's authorized keys configurable. Previously, the value was: command="echo 'Please login as the user \"ubuntu\" rather than the user \"root\".\';echo;sleep 10\"" Now, at is configurable in cloud.cfg or user data by setting 'root_disabled_opts'. Additionally, the default has been changed to include 'no-port-forwarding,no-agent-forwarding,no-X11-forwarding' See LP: #798505 for more information on that. Note, that 'no-pty' was *not* added to this list as adding it means the user who simply does 'ssh root@host' gets a "cannot allocate pty" message rather than seeing warning about using root. LP: #798505
* | Support disabling of byobu.Scott Moser2011-06-141-3/+8
| | | | | | LP: #797336
View Lorry Controller Status