| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
1. Renamed config to modules, then renamed to transforms
2. Enabled checking of transform frequencies before usage (warning the user that something is bad)
3. Adjusting how the cloud object is formed to comply with its new api.
|
|
|
|
1. Adjustments to using more selinux guards around directory creation, chmod...
2. Adding util functions to check if values are false or true (used internally and externally)
3. Move find_devs_with to util.py and allow it to serve multiple use cases
4. Add fork_cb which will fork a process and then call a certain callback (used right now by the resize nonblocking mode)
5. Move functions that performed time_rfc2822 time fetching and uptime fetching to here.
6. Allow the subp util function to act in shell mode
7. Increase logging usefulness in shellify function
|
|
from being valid codes.
2. Log how much we will sleep for
3. If not headers are provided, add a set which will have a cloud init user agent + version
|
|
|
|
Some of the cleanups were the following
1. Using standard (logged) utility functions for sub process work, writing, reading files, and other file system/operating system options
2. Having distrobutions impelement there own subclasses to handle system specifics (if applicable)
3. Having a cloud wrapper that provides just the functionality we want to expose (cloud.py)
4. Using a path class instead of globals for all cloud init paths (it is configured via config)
5. Removal of as much shared global state as possible (there should be none, minus a set of constants)
6. Other various cleanups that remove transforms/handlers/modules from reading/writing/chmoding there own files.
a. They should be using util functions to take advantage of the logging that is now enabled in those util functions (very useful for debugging)
7. Urls being read and checked from a single module that serves this and only this purpose (+1 for code organization)
8. Updates to log whenever a transform decides not to run
9. Ensure whenever a exception is thrown (and possibly captured) that the util.logexc function is called
a. For debugging, tracing this is important to not just drop them on the floor.
10. Code shuffling into utils.py where it makes sense (and where it could serve a benefit for other code now or in the future)
|
|
new structure, using unified util functions, logging and eliminating code and calls.
|
|
use logexc instead of log.exception
|
|
|
|
used to check if user provided frequencies are actually valid or not
|
|
Removed un-used pre debug info option, since this is not used in the prettytable case.
|
|
logger, show how many configs were tried if none succeeded, and for basic logging setup try to mirror more of what is in the default configuration file if all else fails
|
|
2. Throw lock specific exception when semaphores can't be obtained
3. Make the paths constructor config variable named better to its actual usage.
|
|
Mainly this is the following:
1. Hostname updating
2. Package command invocation
3. Network settings writings
4. Timezone setting (needs cleanup)
|
|
|
|
class as needed.
|
|
has been reduced to actual objects.
Added a get template filename helper which can be used to locate template files for various handlers/transforms.
Ensured that the config that we give back out is copied, so that it can't be modified by any 'malicous' handlers/transforms.
Added helper method cycle_logging that can resetup logging, this is mainly used by the rsyslog transform.
|
|
Continued adding more system info sections as needed for various components.
Enabled the welcome transform.
|
|
|
|
python files
|
|
Also converted all the other templates to tempita format instead of the more complicated (and more dependent on other packages) cheetah format.
|
|
"/etc/hosts" file for rhel like systems.
|
|
cloud init that is running for internal messaging, if desired
|
|
for now it seems to make organizational sense to put it here.
|
|
to users.
It is similar to the final msg one, but is used at the start of cloud init instead.
|
|
parser throwing when options + values are being added to unknown sections since it handles the
creation and checking that those sections exist before the option is added. Also it adds a little helper that can turn that config into a string.
|
|
subdir for just the internal handlers.
|
|
|
|
user_data.py file.
It seems to make a little more sense for now to move it to there.
|
|
It seems to make sense to have that file, then have a handler directory for user data handlers.
|
|
Adjust usage of logexc to use that in the utils file for exceptions that occur.
Add in more options to sub function to capture outputs, shell mode and such.
|
|
refactoring stuff and setup.py for both of those.
|
|
|
|
to dummy sem class.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cleanups.
|
|
|
|
|
|
|
|
|
|
|
