summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2011-12-20 11:40:51 -0500
committerScott Moser <smoser@ubuntu.com>2011-12-20 11:40:51 -0500
commit7a61005e16925c1cae99bab417abf08cd1cbbfea (patch)
tree958b0048ed614b5129ce43e90f2d3b898a8a9778
parent27e88fe213b0a3505ca565cae63d7d7124b7f969 (diff)
downloadvyos-cloud-init-7a61005e16925c1cae99bab417abf08cd1cbbfea.tar.gz
vyos-cloud-init-7a61005e16925c1cae99bab417abf08cd1cbbfea.zip
update documentation for bootcmd
- reference cloud-init-per - mention that INSTANCE_ID is in environment of bootcmd scripts
-rw-r--r--doc/examples/cloud-config.txt6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/examples/cloud-config.txt b/doc/examples/cloud-config.txt
index d67b572c..4f621274 100644
--- a/doc/examples/cloud-config.txt
+++ b/doc/examples/cloud-config.txt
@@ -228,9 +228,13 @@ runcmd:
# in the boot process, only slightly after a 'boothook' would run.
# bootcmd should really only be used for things that could not be
# done later in the boot process. bootcmd is very much like
-# boothook, but possibly with more friendly
+# boothook, but possibly with more friendly.
+# * bootcmd will run on every boot
+# * the INSTANCE_ID variable will be set to the current instance id.
+# * you can use 'cloud-init-boot-per' command to help only run once
bootcmd:
- echo 192.168.1.130 us.archive.ubuntu.com > /etc/hosts
+ - [ cloud-init-per, once, mymkfs, mkfs, /dev/vdb ]
# cloud_config_modules:
# default: