summaryrefslogtreecommitdiff
path: root/doc/var-lib-cloud.txt
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2016-08-10 09:06:15 -0600
committerScott Moser <smoser@ubuntu.com>2016-08-10 09:06:15 -0600
commitc3c3dc693c14175e110b5fe125d4d5f98ace9700 (patch)
tree8858702c2c8a6ad4bf1bb861a4565e0a9c28e588 /doc/var-lib-cloud.txt
parent5bd3493d732e5b1902872958e8681f17cbc81ce5 (diff)
downloadcloud-init-trunk.tar.gz
README: Mention move of revision control to git.HEADtrunk
cloud-init development has moved its revision control to git. It is available at https://code.launchpad.net/cloud-init Clone with git clone https://git.launchpad.net/cloud-init or git clone git+ssh://git.launchpad.net/cloud-init For more information see https://git.launchpad.net/cloud-init/tree/HACKING.rst
Diffstat (limited to 'doc/var-lib-cloud.txt')
-rw-r--r--doc/var-lib-cloud.txt63
1 files changed, 0 insertions, 63 deletions
diff --git a/doc/var-lib-cloud.txt b/doc/var-lib-cloud.txt
deleted file mode 100644
index 7776d772..00000000
--- a/doc/var-lib-cloud.txt
+++ /dev/null
@@ -1,63 +0,0 @@
-/var/lib/cloud has the following structure:
- - scripts/
- per-instance/
- per-boot/
- per-once/
-
- files in these directories will be run by 'run-parts' once per
- instance, once per boot, and once per *ever*.
-
- - seed/
- <datasource>/
- sys-user-data
- user-data
- meta-data
-
- The 'seed/' directory allows you to seed a specific datasource
- For example, to seed the 'nocloud' datasource you would need to
- populate
- seed/nocloud/user-data
- seed/nocloud/meta-data
-
- - instance -> instances/i-abcde
- This is a symlink to the current instance/<instance-id> directory
- created/updated on boot
- - instances/
- i-abcdefgh/
- scripts/ # all scripts in scripts are per-instance
- sem/
- config-puppet
- config-ssh
- set-hostname
- cloud-config.txt
- user-data.txt
- user-data.txt.i
- obj.pkl
- handlers/
- data/ # just a per-instance data location to be used
- boot-finished
- # this file indicates when "boot" is finished
- # it is created by the 'final_message' cloud-config
- datasource # a file containing the class and string of datasource
-
- - sem/
- scripts.once
- These are the cloud-specific semaphores. The only thing that
- would go here are files to mark that a "per-once" script
- has run.
-
- - handlers/
- "persistent" handlers (not per-instance). Same as handlers
- from user-data, just will be cross-instance id
-
- - data/
- this is a persistent data location. cloud-init won't really
- use it, but something else (a handler or script could)
- previous-datasource
- previous-instance-id
- previous-hostname
-
-to clear out the current instance's data as if to force a "new run" on reboot
-do:
- ( cd /var/lib/cloud/instance && sudo rm -Rf * )
-