Michael DeHaan wrote: > So we've been talking recently about registration and how best to get > all the info about an existing pool of machines into Cobbler. > > What I'm going to do is create a /usr/bin/cobbler-register which is part > of the koan RPM package. > > It will look like this: > > /usr/bin/cobbler-register [--server=address] --profile=name > [--hostname=X] [...] > > What this will do is query the current running system and create a > system record on the cobbler server for it. The initial version won't > be perfect and likely won't be able to auto-register > bonded interfaces, but I imagine it will be good enough for 90% of the > use cases and we can refine it later. For instance, it also won't flag > network interfaces as static initially. I expect to get things > to be fairly solid, easy to understand, and sufficient to were folks can > send me some patches for things they'd like to improve. Again, > initial version should still be a huge upgrade over how it > works now. > > So, /usr/bin/cobbler-register can be used in two ways: > > (A) at the bottom of a profile kickstart, we'll add a snippet that sees > if it's a per-profile kickstart, and if so, if koan is available, will > register to cobbler to create a new system record. This feature > will not be on by default. > > (B) you could also use koan to deploy a live environment (or even just a > regular throw-away kickstart install) that calls koan register to > quickly add all your systems into Cobbler. > > This will not require any package other than koan, and will use the > existing "register_new_installs" value in settings to turn it on and > off. The existing registration mechanism, which is not smart > enough to detect all interfaces, and also requires installation, will > replaced by the new system. > > To take full advantage of it, make sure koan is installed in each > kickstart you have (which should not be a problem for Fedora users at > all, and EL users can do this by mirroring EPEL and associating > it with their profiles). > > Sidenote -- James Laska has also talked about making a > /usr/bin/cobbler-register --interactive option, which would likely be a > curses based UI for prompting for additional information, browsing > available profiles, and so forth. This may be useful for smaller > environments. Really I'm not as interested in the text-ui for that, > per se, as I am a text UI for doing virt installs, in which case, it's > like a text version of virt manager, only with less things to fill in, > that works nicely over SSH. (This would probably be done in > /usr/bin/koan). > > --Michael > > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler >
I have the above implemented -- you'll need a devel build of cobbler and a devel build of koan. (Check them out of git and do "make rpms") When you install koan, you'll get a /usr/bin/cobbler/register script, and there's also a new cobbler_register snippet for auto registering profile based installs (which I will be testing very soon now). Registration will not succeed when the existing system has any conflicts with macs, ips, or hostnames. I need to modify the snippet slightly so it ignores such failures in %post. Additional modifications to send over more info and be smarter about what is stored (maybe detecting static interfaces or not registering wireless interfaces, etc) would be welcome, as well as any comments/ideas you might have. --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
