My recent tests of cobbler have been a breath of fresh air after using a configuration management system wonderful in all ways except when provisioning is unnaturally crammed into it.
One problem I'm having is with distro inheritance, which doesn't do what I expect. Attributes set in profiles override attributes set in parent profiles, with the exception of the 'distro' attribute, which is inherited from the furthest (base) profile ancestor. Being able to override distro in child profiles seems useful. I have a base profile with site-wide definitions, and set no distro (though one was randomly assigned). Next generation is one profile for each generation/arch, e.g. sl6-32, sl6-64, fc18-32. Distros are inherited at this level, and metadata for the most common profile are defined. For some networks, a third generation overrides metadata; there are also profiles that set attributes for VMs. I hacked up a quick patch that inherits the distro from the nearest ancestor rather than the furthest. It is just a proof of concept and has been only tested on the tiny subset of cobbler in use here in the shop. It wishes to do away with get_conceptual_parent(), but only does so in a few instances and only when the conceptual_parent is expected to be a distro object. I'm curious what I'm doing wrong that I'm the only one who needs this. ;) Thanks! https://github.com/zultron/cobbler/commit/9369e530fc777cd3f60b310a279538672a4d169f John PS: Another breath of fresh air is the simple code and simple program structure, and readable in an 80-column terminal. REALLY nice after a couple days hacking on Django core, a maze of twisty passages, all so different there's no memorable pattern. _______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
