summaryrefslogtreecommitdiff
path: root/doc/sources
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2015-06-01 16:25:15 -0400
committerScott Moser <smoser@ubuntu.com>2015-06-01 16:25:15 -0400
commit5a8f6c82da94ab87f21b39dc30a0e85ddbc85216 (patch)
tree4f8904f65989e60de5d682aea7dd5002546474df /doc/sources
parent12e739da7a0586eabc244a68eed51f5e12dfa087 (diff)
parent09cf2e1caf628f6b61c35a454dbea6b6a8c2e7aa (diff)
downloadvyos-cloud-init-5a8f6c82da94ab87f21b39dc30a0e85ddbc85216.tar.gz
vyos-cloud-init-5a8f6c82da94ab87f21b39dc30a0e85ddbc85216.zip
Doc: include information on vendor-data in OpenStack
Diffstat (limited to 'doc/sources')
-rw-r--r--doc/sources/openstack/README.rst24
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/sources/openstack/README.rst b/doc/sources/openstack/README.rst
new file mode 100644
index 00000000..8102597e
--- /dev/null
+++ b/doc/sources/openstack/README.rst
@@ -0,0 +1,24 @@
+*TODO*
+
+Vendor Data
+~~~~~~~~~~~
+
+The OpenStack metadata server can be configured to serve up vendor data
+which is available to all instances for consumption. OpenStack vendor
+data is, generally, a JSON object.
+
+cloud-init will look for configuration in the ``cloud-init`` attribute
+of the vendor data JSON object. cloud-init processes this configuration
+using the same handlers as user data, so any formats that work for user
+data should work for vendor data.
+
+For example, configuring the following as vendor data in OpenStack would
+upgrade packages and install ``htop`` on all instances:
+
+.. sourcecode:: json
+
+ {"cloud-init": "#cloud-config\npackage_upgrade: True\npackages:\n - htop"}
+
+For more general information about how cloud-init handles vendor data,
+including how it can be disabled by users on instances, see
+https://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/vendordata.txt