From 7a61005e16925c1cae99bab417abf08cd1cbbfea Mon Sep 17 00:00:00 2001 From: Scott Moser Date: Tue, 20 Dec 2011 11:40:51 -0500 Subject: update documentation for bootcmd - reference cloud-init-per - mention that INSTANCE_ID is in environment of bootcmd scripts --- doc/examples/cloud-config.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'doc') 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: -- cgit v1.2.3