Oh, this is about replication. AKA: "yum install cobbler (or arrive there by kickstart)" … "configure XXX & start services" … "cobbler replicate". Yes, there's a Wiki page for this -- not the ones I linked.
This is the one you want to add to: https://github.com/cobbler/cobbler/wiki/Replication I don't think we can replicate configuration file differences sanely (or should try), as certain things should need to change, and it's not a one size fits all thing … but you could include those in the kickstart. You could probably use the cobbler configuration file support to ship the config files out too. On Thursday, February 23, 2012 at 11:25 AM, Gerhardus Geldenhuis wrote: > Hi > I will add a few additions. > > My personal aim was to get a cobbler server working as quickly as possible > which I am sure would be a shared goal. > > Problems I am experiencing so far: > * A number of config changes that needs to be performed... they are all easy > but could perhaps be automated more... I might make a few rpm changes in git > for consideration... > * I want servers build from the cobbler server to use the cobbler repos first > time without having to configure it. The auto configuration of the repos does > not work and I need to debug it. > * For some reason koan does not get installed which is likely to be related > to the above point. > > With a bootstrap kickstart I meant a kickstart that I can use when I build my > cobbler server. I want to be able to pop in the CentOS or RHEL CD and type > ks=http://github.com/cobbler/buildserver.ks > > Regards > > On 23 February 2012 15:36, Michael DeHaan <[email protected] > (mailto:[email protected])> wrote: > > This is basically the step by step guide. > > > > https://github.com/cobbler/cobbler/wiki/Start%20Here > > > > The main starter workflow for all new users should be this > > > > https://github.com/cobbler/cobbler/wiki/Using%20Cobbler%20Import > > > > Additions are welcome, reorg not so much. > > > > Including a bootstrap kickstart shouldn't be needed -- this is what > > sample.ks is when you go down the import pathway. As for modifying that, > > I would prefer to just point at the Anaconda docs, which is what we do, > > other than explaining snippets. > > > > --Michael > > > > On Thursday, February 23, 2012 at 10:24 AM, Gerhardus Geldenhuis wrote: > > > > > > > > > Hi > > > I have been going through the process of setting up a cobbler server from > > > scratch recently... up until now I was relying on legacy config files > > > that I kept copying over. Although the documentation on the wiki is > > > useful there was no step by step guide. I also experienced one possible > > > bug but will need to double check. My question is with regards to the > > > re-org of the documentation mentioned a while ago does such a step by > > > step guide fit anywhere or do you purposely not want one? I would be > > > happy to write one and also provide a bootstrap kickstart that anyone can > > > use to build the cobbler server to build the rest his/her servers. > > > > > > Regards > > > > > > -- > > > Gerhardus Geldenhuis > > > _______________________________________________ > > > cobbler mailing list > > > [email protected] (mailto:[email protected]) > > > https://fedorahosted.org/mailman/listinfo/cobbler > > > > > > > > > > > > > > > > > _______________________________________________ > > cobbler mailing list > > [email protected] (mailto:[email protected]) > > https://fedorahosted.org/mailman/listinfo/cobbler > > > > > > -- > Gerhardus Geldenhuis > _______________________________________________ > cobbler mailing list > [email protected] (mailto:[email protected]) > https://fedorahosted.org/mailman/listinfo/cobbler > >
_______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
