summaryrefslogtreecommitdiff
path: root/cloud-init-run-module.py
AgeCommit message (Collapse)Author
2010-02-11rename EC2Init class to CloudInitScott Moser
2010-02-04add copyright informationScott Moser
2010-02-03globally remove ec2init and rename to cloudinitScott Moser
2010-01-07functional state now in kvm testsScott Moser
supports user data as mime-multipart and handling types of text/x-shellscript - execute at rc.local text/cloud-config - feed to cloud config text/upstart-job - add to /etc/init as upstart job text/x-include-url - include urls as if they were in-line
2010-01-06put upstart files in upstart/, minor other changesScott Moser
adding cat-cloud-config.conf, a debug file that just cats the config
2010-01-06add cloud-init-run-module and ec2init/execute.pyScott Moser
cloud-init-run-module handles some boilerplate code for running items on a 'frequency'. It has the following usefulness - a config module can be put into ec2init dir and implement a 'run' method that takes a list of arguments and the path to a config file - it handles invoking module.run() only at a given frequency This is similar to karmic's ec2init's "run_once_ever" or run_once_per_ami execute.py is an example module that executes the arguments given to it An example usage in an upstart job would be with a 'exec' line like: exec cloud-init-run-module once_per_ami clean-core execute rm /var/run/core The above would then run the command 'rm /var/run/core' only once