| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
object renaming, copying, and editing -- previously only addition and
removal were supported. This frees uses (hopefully) from the need
to hack YAML and risk damaging their configurations by rendering the
config unparseable. It also makes "cobbler list" print out a simple
tree representation that shows the association between objects.
This also relaxes the requirements for what constitutes a kernel and initrd
filename, just in case they are named something different. They still have
to exist.
|
|
|
|
|
|
|
|
| |
more efficient.
Make both the Config and BootAPI objects Borgs, to prevent duplicate
configuration records. Also do not implicitly serialize configuration
objects unless the with_copy parameter is used.
|
| |
|
|
|
|
|
|
|
| |
kernel-parameters-get-shorter effort
as well as templating and import features. Plus some random things, like case insensitive paths and some
additional argument checking.
|
|
|
|
|
|
| |
which is enabled by default in /var/lib/cobbler/settings.
Users of the API will need to use the with_copy=True and with_delete=True parameters to initiate this behavior. As mentioned in the previous commit, sync() still needs to be run at least once prior to any add commands using this feature.
|
|
|
|
|
|
| |
add/remove commands that do not require running "sync". Sync will only be required when the kickstart files behind systems change, or when YAML is hand edited. This should vastly improve cobbler for use in larger systems, especially when used as a library when all control paths are known.
Sync will still be required once for an initial install (just once), or whenever kickstart or YAML files are edited. It can also be run again at any time for a sanity check -- sync isn't going away.
|
| |
|
| |
|
|
|
|
| |
--kopts. The parameter is a space delimited list of key=value pairs, which allows the variables entered to be evaluated through Cheetah. Thus kickstarts are now Cheetah templates. All templating errors are ignored so usage of a $ in a template is still legal where it doesn't reference a variable. Error ignoring should be finer grained and this does need some tests. Currently this only works for kickstarts on filesystems, and I'm not sure what the behavior for http and nfs should be. Anyhow, fairly useful stuff.
|
|
|
|
| |
test where I changed a command line syntax.
|
|
|
|
|
|
| |
exception
cleanup.
|
|
|
|
| |
all the way up the stack. Still not quite super-consistant, but getting there. Util functions still return true/false since they just ask questions, but API functions will throw errors to ensure they are being dealt with. Main CLI class needs to take advantage of this fact and become simpler. Tests are already modified to detect new exceptions with one exception :)
|
|
|
|
|
|
|
| |
reminded me of the
thing I hated most about Microsoft SDK/DDK programming (that being, last_error and inconsistant
error handling), so it had to go.
|
| |
|
| |
|
| |
|
|
|
|
| |
cleanup but it will get straightened out very soon. The main thing I'm doing here is to remove backreferences from the object tree and make the API simpler, so that folks using the API screw up less. This means making the CLI code simpler as well. The serializer has also been overhauled so it's not as much bolted on, although I have some fixing to do to make it work entirely correctly. Wanted to check all of this in case someone decided to patch something else, making diffing really complex in the interim. I'd recommend not patching anything else to this code as I'm not close to done, really.
|
| |
|
| |
|
|
|