| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
(find is case agnostic, etc)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
can be done at deserialization time. The result of this is that full graph
listing information can be reconstructed at time of config loading (up and
down links), while only having to store the up links.
This preserves the existing config file format while allowing for arbitrary inheritance and
a reasonable measure of hand-editability.
If changing profile relationships by hand, the cached depth info may be wrong,
so some way to automatically resolve this could potentially be doable,
but it's such a distinct corner case that I don't deem it neccessary at this point.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
some rough edges (like listing the tree).
cobbler profile add --name=profile2 --inherit=profile1 --otherparameters=...
cobbler profile edit --name=profile2 --stillmoreparamters=...
Data is interleaved for hashes, combined for arrays, and overriden for scalar
values. This was heavily inspired by Will-It-Blend, and in this implementation
it all blends.
Implementation notes -- Updating a parent profile doesn't apply changes
to the child objects until a sync, so this seems like a good upgrade
for a future commit. Also, the children mapping that makes this
possible needs some tweaks because they may load out of order,
in which case "cobbler list" can't render a full
tree. There are various approaches to deal with this and it should be
a (relatively) easy change.
|
|
|
|
|
|
|
| |
translation function and run manual testing to ensure no functional errors in other
places (such as import).
cobbler_msg (strings file) has been removed.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
will be possible (Syck needs Python 2.4).
|
|
|
|
| |
test where I changed a command line syntax.
|
|
|
|
| |
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.
|
| |
|
|
|