x/cloud-init
Code Issues Proposed changes

update documentation for bootcmd

Browse Source 
- reference cloud-init-per
 - mention that INSTANCE_ID is in environment of bootcmd scripts
This commit is contained in:
Scott Moser 2011-12-20 11:40:51 -05:00
parent eb7ea6c08c
commit 4042ddf94f
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/examples/cloud-config.txt
View File

@ -228,9 +228,13 @@ runcmd:
# in the boot process, only slightly after a 'boothook' would run. # in the boot process, only slightly after a 'boothook' would run.
# bootcmd should really only be used for things that could not be # bootcmd should really only be used for things that could not be
# done later in the boot process. bootcmd is very much like # 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: bootcmd:
- echo 192.168.1.130 us.archive.ubuntu.com > /etc/hosts - echo 192.168.1.130 us.archive.ubuntu.com > /etc/hosts
- [ cloud-init-per, once, mymkfs, mkfs, /dev/vdb ]
# cloud_config_modules: # cloud_config_modules:
# default: # default: