Age | Commit message (Collapse) | Author | |
---|---|---|---|
2012-07-10 | Change the welcome message to be slightly different | Joshua Harlow | |
when running in local mode vs non-local mode, which is useful when tracking what is happening in the console and in the logs that are written out later. | |||
2012-07-10 | re-setup logging to address cloud-config changes input via user-data | Scott Moser | |
If the user has input logging information in user-data cloud-config we want to set up the logging to accept that after the data source has been read. | |||
2012-07-10 | send welcome message after logging has been applied | Scott Moser | |
in the 'cloud-init init' stages, we want the welcome message to get to the correct output as specified by the system's configuration. Ie, if the local /etc/cloud.config.d had 'output' or 'log_cfg' settings we want those to be able to affect the welcome message also. In normal operation, nothing else will go to stdout or stderr before this, and likely/hopefully nothing terribly important to the logs. | |||
2012-07-09 | cloud-init: do not warn on failure to find local datasource | Scott Moser | |
Instead of a warning, only debug this message. Warnings get to console and look scary to users. | |||
2012-07-09 | Revert back to using cheetah + adjust resultant code + templates | Joshua Harlow | |
At this point there is a mixture of "double hash" cheetah comments and '#*' cheetah comments. | |||
2012-07-02 | 1. Move the welcome message template string to a constant at the top of the ↵ | Joshua Harlow | |
module 2. Fix the usage of multi_log to log to only one of the places (for now) 3. Update comment about multi-log and why write_file isn't used in this case | |||
2012-07-01 | Add a multi log function that can write to stderr, console and a log debug, ↵ | Joshua Harlow | |
useful in certain cases | |||
2012-06-29 | If logging hasn't been enabled via '--debug' at least log the exceptions ↵ | Joshua Harlow | |
that occur to stderr. | |||
2012-06-29 | Add a force option which will allow users to continue running when no ↵ | Joshua Harlow | |
datasource is found. | |||
2012-06-29 | Fix the datasource not being fetched in single running mode. | Joshua Harlow | |
2012-06-29 | Add a message about why the second consume_userdata occurs since its not ↵ | Joshua Harlow | |
very obvious. | |||
2012-06-28 | 1. Update with smosers code review and comments (and put some of those ↵ | Joshua Harlow | |
comments into the files) 2. Rename consume() to consume_userdata() as it helps in figuring out what this does. 3. Fixup the tests due to #2 | |||
2012-06-27 | No longer need to do this special config appending, the config merger class ↵ | Joshua Harlow | |
handles this. | |||
2012-06-22 | 1. Return which modules ran from the run module function | harlowja | |
2. Use that list in the main binary & adjust related comparisions | |||
2012-06-21 | Ensure that nothing was ran by checking the total count | harlowja | |
2012-06-21 | 1. Move all info() logging methods to debug() | harlowja | |
2. Adjust comment on sources list from depends 3. For the /etc/timezone 'writing', add a header that says created by cloud-init | |||
2012-06-20 | 1. Shorten the passed in name for frequency (and expand it later) | Joshua Harlow | |
2. For single modules, if it doesn't run, print a warning and exit with a return code of 1 | |||
2012-06-20 | No need for this now that we have the imports done correctly | Joshua Harlow | |
2012-06-20 | Massive pylint + pep8 fixups! | Joshua Harlow | |
2012-06-20 | 1. Use the name modules where transforms was used | Joshua Harlow | |
2. Reflect the move back to config 'modules' in the other cli options 3. Have the single mode not need to lookup the module but use the general import path | |||
2012-06-20 | Remove the .py extension for this new main program binary. | Joshua Harlow | |