summaryrefslogtreecommitdiff
path: root/doc/sources/openstack
diff options
context:
space:
mode:
authorScott Moser <smoser@brickies.net>2016-11-15 12:06:58 -0500
committerScott Moser <smoser@brickies.net>2016-11-15 12:06:58 -0500
commiteb29af61f9388de7a69bf7112193976dd4feb6db (patch)
tree0a12d1de1bc6bb5527a3f99d01401df95250c0c7 /doc/sources/openstack
parent4613bb45dde05cc859a0b4dec6587d80767b47c7 (diff)
parent584b8434872322a9f617831742cc6b15977ecfbc (diff)
downloadvyos-cloud-init-eb29af61f9388de7a69bf7112193976dd4feb6db.tar.gz
vyos-cloud-init-eb29af61f9388de7a69bf7112193976dd4feb6db.zip
merge from master at 0.7.8-45-g584b843
Diffstat (limited to 'doc/sources/openstack')
-rw-r--r--doc/sources/openstack/README.rst24
1 files changed, 0 insertions, 24 deletions
diff --git a/doc/sources/openstack/README.rst b/doc/sources/openstack/README.rst
deleted file mode 100644
index 8102597e..00000000
--- a/doc/sources/openstack/README.rst
+++ /dev/null
@@ -1,24 +0,0 @@
-*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