>> Interesting, I did not notice that on the wiki when I was hunting for >> information this afternoon. > > Thanks for the heads up! I'll put it up there.
It was there, I just didn't notice it. :-S >> Hrmm...my "ks_mirror" directory on my dev box >> is pretty much empty (just a "config" directory). Am I missing >> something? What should be in there? > > That's the directory used by "cobbler import", if you were sourcing > trees externally (without mirroring them) this data would not be in use. Ah...I experimented with "cobbler import" but since I am already using mrepo I did not have the need for it. >> Is this going to replicate my kickstarts and snippets, too, or do I have >> to find a way of sharing them? If the latter, can those be put onto NFS >> safely? What mechanism is used for replication? > > Yes, it can help move over as little or as much as you want. See > "cobbler replicate --help"in 1.2.4. If it can't do something you want, > let me know, and we can see about adding it. Hrmm...I am still using v1.0.3...I'm way behind the times! Time to upgrade... :-) > Replication is achieved using Cobbler XMLRPC for basic data, and files This would be the read-only listener (tcp/25151), correct? > are transferred using scp/rsync. Usage of ssh-agent before cobbler > replicate is therefore recommended unless you are using authorized_keys. That's perfect; we use ssh for a number of tasks similar to this already. Is it possible to specify a key to use? We like to lock down a key to a specific command, host, etc. I still have some questions regarding cobbler's architecture, but this gives me a better understanding. Thanks! Chris _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
