From c2e5c6fd4dc917d2d4fb23569b1615b76c695201 Mon Sep 17 00:00:00 2001 From: Joshua Harlow Date: Fri, 31 Aug 2012 18:22:01 -0700 Subject: Add some examples on how to use the new launch-index support in a cloud-archive format as well as a cloud-config format and explain how this will affect the final userdata available to an instance. --- doc/examples/cloud-config-launch-index.txt | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/examples/cloud-config-launch-index.txt (limited to 'doc/examples/cloud-config-launch-index.txt') diff --git a/doc/examples/cloud-config-launch-index.txt b/doc/examples/cloud-config-launch-index.txt new file mode 100644 index 00000000..e7dfdc0c --- /dev/null +++ b/doc/examples/cloud-config-launch-index.txt @@ -0,0 +1,23 @@ +#cloud-config +# vim: syntax=yaml + +# +# This is the configuration syntax that can be provided to have +# a given set of cloud config data show up on a certain launch +# index (and not other launches) by provided a key here which +# will act as a filter on the instances userdata. When +# this key is left out (or non-integer) then the content +# of this file will always be used for all launch-indexes +# (ie the previous behavior). +launch-index: 5 + +# Upgrade the instance on first boot +# (ie run apt-get upgrade) +# +# Default: false +# +apt_upgrade: true + +# Other yaml keys below... +# ....... +# ....... -- cgit v1.2.3