| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
more standard xlat for other distros potentially, (B) fix the kerb module
some more.
|
| |
|
|
| |
prevention feature.
|
| | |
|
| |
|
|
| |
take advantage of this.
|
| |
|
|
| |
make the WebUI use it for much smarter renames and copies.
|
| |
|
|
| |
plans, remove watcher.py reference
|
| |
|
|
|
| |
should be generated on a per-system basis to support --server-override correctly.
This is a fix.
|
| | |
|
| |
|
|
| |
and more usable.
|
| |
|
|
| |
objects.
|
| |
|
|
|
|
|
|
|
|
| |
now a trigger.
This commit adds pre/post sync triggers, for scripting of arbitrary actions. The idea is that
a cobbler user can now modify the restart-services script to rsync DHCP configurations to a remote
box and instead restart them there, for hosting DHCP on a different box. Or do anything
else that might be required. The restart-services trigger will ship in the cobbler RPM. Users
can modify it at will and it is marked as config(noreplace) so upgrades will not affect it.
|
| |
|
|
|
|
| |
saving state, plus
a fix to import that keeps from creating extra yum repo entries for various distros.
|
| |
|
|
| |
is just as likely at this point.
|
| |
|
|
| |
to the find function.
|
| |
|
|
|
|
|
|
| |
multiple NIC support
is still required. Checking kickstarts and the koan modifications are also still to go. Code
in item_system.py is due for cleanup, especially in from_datastruct, where it tries to load
the older configurations implicitly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
format choice in settings (which is something of a Catch-22 situation), this
may end up being a config file setting in /etc.
Module loaders work and still default to yaml, though I've coded up a sample
simple_json serializer that will be functional if users install simple-json.
This is just demoware, JSON isn't replacing yaml and is (at least in this case)
not as readable because of the way it escapes slashes.
This is primarily to enable future work to integrate with other config
file formats, such as possibly getting some of the system info from LDAP.
Possibly.
|
| |
|
|
|
| |
the cobbler server has configured in yum and set them up to be mirrored
automagically.
|
| |
|
|
|
|
|
| |
up the graph, in ksmeta and
possibly kopts. Also added some code to check to make sure an object of the wrong type never gets
added to the wrong collection.
|
| | |
|
| |
|
|
|
|
| |
of find (mpd) to add some error checking, list returns, and other semi-useful
stuff. Plus tests and an optomization to allow name=foo as the only parameter
to be just as fast as before.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Reasonably efficient, and allows for faster display/searching, with the
ability to do arbitrary nesting for config display when we have inheritable
profiles implemented.
|
| |
|
|
| |
triggers, plus my modifications to make them deal with return codes.
|
| |
|
|
| |
case.
|
| |
|
|
|
|
|
| |
translation function and run manual testing to ensure no functional errors in other
places (such as import).
cobbler_msg (strings file) has been removed.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
