summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
...
| * Merged trunk lp:cloud-initVlastimil Holer2013-09-0511-24/+472
| |\
| * | Example cloud.cfgVlastimil Holer2013-02-211-0/+13
| | |
| * | OpenNebula documentation tuning.Vlastimil Holer2013-02-201-22/+24
| | |
| * | Add OpenNebula DS on list of datasources.Vlastimil Holer2013-02-201-0/+6
| | |
| * | OpenNebula datasource documentation update.Vlastimil Holer2013-02-202-66/+117
| | |
| * | Merged trunk lp:cloud-initVlastimil Holer2013-02-1933-241/+15628
| |\ \
| * \ \ Merged trunk lp:cloud-initVlastimil Holer2012-12-195-14/+87
| |\ \ \
| * | | | Minor OpenNebula's documentation tuning.Vlastimil Holer2012-10-031-5/+5
| | | | |
| * | | | Add documentation for OpenNebula datasource.Vlastimil Holer2012-10-031-0/+66
| | | | |
* | | | | Initial cut at disk partition support.Ben Howard2013-09-111-0/+178
| |_|_|/ |/| | |
* | | | changes to behavior on specifying keys.Scott Moser2013-08-242-6/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The most likely end user operation (or at least a valid one) for base64 encoding would be to encode the user-data, but leave all other values as plaintext. In order to facilitate that, the user can simply add: b64-user-data=true to indicate that user-data is base64 encoded. Other changes here are to change the cloud-config and metadata keynames that are used. base64_all = boolean(True) base64_keys = [list, of, keys] Fixed up tests to accomodate.
* | | | Fixed some typos. Change decode_base64 from sys_cfg to ds_cfgBen Howard2013-08-231-3/+3
| | | |
* | | | Updated merge proposal with current treeBen Howard2013-08-202-20/+3
|\ \ \ \
| * | | | initially add support for apt_ftp_proxy and apt_https_proxy. tests to come.Scott Moser2013-08-062-20/+3
| | | | |
* | | | | Fixed no_base64_decode settingsBen Howard2013-08-202-7/+7
| | | | |
* | | | | Added base64 support to SmartOS datasource.Ben Howard2013-07-301-0/+66
|/ / / / | | | | | | | | | | | | Added documentation on SmartOS datasource.
* | | | azure: support bouncing interfaces to publish new hostnameScott Moser2013-07-252-0/+139
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | See the added doc/sources/azure/README.rst for why this is necessary. Essentially, we now are doing the following in the get_data() method of azure datasource to publish this NewHostname: hostname NewHostName ifdown eth0; ifup eth0
* | | | shorten comments in example cloud-configScott Moser2013-07-241-9/+3
| | | |
* | | | Added blurb to documentation about the datasourceBen Howard2013-07-231-1/+13
| | | |
* | | | commit dev stateScott Moser2013-07-081-0/+4
| | | |
* | | | remove executable on logo.svgScott Moser2013-05-161-0/+0
| | | |
* | | | invoke dist-upgrade instead of upgrade for apt upgradesScott Moser2013-04-031-0/+18
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | dist-upgrade is generally more correct here to get all packages upgraded. We add the options to change these in system_info. Also, document the previous apt configuration change (apt_get_command).
| * | | | invoke 'dist-upgrade' instead of 'upgrade' on for upgrades.Scott Moser2013-04-031-0/+13
|/ / / / | | | | | | | | | | | | | | | | | | | | In general, dist-upgrade is the correct behavior here. It will get a new kernel, though, which could be annoying. So, allow a way to turn it off (by setting 'apt_get_upgrade_subcommand: upgrade').
* | | | Fix the default string used for merging.Joshua Harlow2013-04-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | It had been changed in code, but not in docs. So we needed to reflect the change in docs as well so that both are in sync.
* | | | Enable the merging.txt to be in .rst format for public viewingJoshua Harlow2013-03-083-64/+79
| | | |
* | | | merge from trunkScott Moser2013-03-0735-242/+15660
|\ \ \ \
| * | | | pep8 and pylint fixesScott Moser2013-03-071-4/+4
| | | | |
| * | | | add docScott Moser2013-03-051-0/+24
| | |_|/ | |/| |
| * | | DataSourceNoCloud: allow setting user-data and meta-data in configScott Moser2013-02-071-0/+11
| |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows a single file to declare and activate this data source. This could come from: * cloud-config-url on kernel cmdline * /etc/cloud/cloud.cfg.d * debian preseed of 'cloud-init/local-cloud-config' Also here is * some tests * a small fix to parse_cmdline_data found when writing those tests.
| | * | | make config of nocloud datasource able to specify meta-data and user-dataScott Moser2013-02-041-0/+11
| | | | |
| * | | | Continue adding datasource docs.harlowja2013-02-051-10/+103
| | | | | | | | | | | | | | | | | | | | Add a base set for ec2 and datasource none.
| * | | | Add initial docs about datasources.harlowja2013-02-0410-242/+385
| |/ / / | | | | | | | | | | | | | | | | | | | | Start moving the current README for datasources to a RST format and include those files in the rtd site.
| * | | doc: fix example in cloud-config-write-files.txtScott Moser2013-01-311-3/+3
| | | | | | | | | | | | | | | | | | | | The write_files documentation incorrectly used 'perms' rather than 'permissions'.
| * | | Adding package versioning logic to package installation.Joshua Harlow2013-01-301-0/+4
| |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds the ability to provide specific package versions to Distro.install_packages and subsequently Distro.package_command. In order to effectively use Distro.install_packages, one is now able to pass a variety of formats in order to easily manage package requirements. These are examples of what can be passed: - "package" - ["package1","package2"] - ("package",) - ("package", "version") - [("package1",)("package2",)] - [("package1", "version1"),("package2","version2")] This change also adds the option to install a specific version for the puppet configuration module. This is especially important here as successful puppet deployments are highly reliant on specific puppet versions.
| | * | | Support package versions for the generic package config modulectracey2013-01-301-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Augmenting the package version support to be available when specifying extra packages to be installed at boot via the 'packages:' yaml key. This change also improves type checking and add a configuration example to the docs.
| * | | | Include the resolv.conf example.Joshua Harlow2013-01-281-1/+13
| |/ / /
| * | | Don't forget the hacking 'inclusion' file.Joshua Harlow2013-01-251-0/+1
| | | |
| * | | Integreate HACKING into the rtd site.Joshua Harlow2013-01-253-3/+3
| | | |
| * | | Adding a resolv.conf configuration module (LP: #1100434)Joshua Harlow2013-01-251-0/+20
| |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Managing resolv.conf can be quite handy when running in an environment where you would like to control DNS resolution, despite being provided DNS server information by DHCP. This module will allow one to define the structure of their resolv.conf and write it PER_ONCE. Right now this makes the most sense on RedHat, and therefore, has defined 'distros' as such. Note that when a config drive is used, and dhcp is not used that this module may not be applicable since in the RedHat based distros the config drive typically contains a ubuntu style network configuration which contains nameservers that can be used in /etc/resolv.conf, but for other types of datasources it is useful to have a module which can be specifically configured to write out /etc/resolv.conf
| | * | | Adding a doc example for resolv_conf handler.ctracey2013-01-251-0/+20
| | | |/ | | |/| | | | | | | | | | | | | As per harlowja's suggestion addding an example to the doc directory for cc_resolv_conf.py
| * | | Remove the release for now.harlowja2013-01-241-1/+1
| | | |
| * | | Fix the release variable.harlowja2013-01-241-1/+1
| | | |
| * | | Make the logo better.harlowja2013-01-244-1/+14358
| | | |
| * | | Add docs which can be used on readthedocs.orgJoshua Harlow2013-01-2421-0/+746
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | Include a new set of docs that can be used to create a readthedocs.org site, which includes examples, directory layout, capabilities and such. This in-code documentation then allows for readthedocs.org to create a website directly from the cloud-init codebase.
| * | add 'omnibus' as an install type for chef.Scott Moser2012-12-121-1/+8
| | | | | | | | | | | | Thanks to Anatoliy Dobrosynets
* | | Add some nice docs on what this is.Joshua Harlow2013-03-061-0/+179
|/ /
* | implement power_state with tests.Scott Moser2012-11-131-18/+21
| |
* | add 'finalcmd' module for running code after cloud-init-finalScott Moser2012-11-121-0/+18
| | | | | | | | | | | | | | This allows the user to easily run stuff even after cloud-init-final has finished. The initial reason for it is to be able to run /sbin/poweroff and not have cloud-init complain loudly that it is being killed.
* | sync with trunkScott Moser2012-11-101-2/+1
|\ \
| * | Add a makefile yaml checking targetJoshua Harlow2012-11-071-2/+1
| | | | | | | | | | | | | | | and fix the cases where the cc yaml is not correct.
View Lorry Controller Status