I used this to get up as fast as possible on RHEL 6…even used the template he has listed in the tutorial:
http://terrarum.net/administration/centos-6-cobbler-server.html <http://terrarum.net/administration/centos-6-cobbler-server.html> My reasoning for getting up and running as fast as possible was to do a proof of concept system between cobbler vs foreman to see which worked better for my needs. -Jim From: [email protected] [mailto:[email protected]] On Behalf Of Michael DeHaan Sent: Thursday, February 23, 2012 1:43 PM To: cobbler mailing list Subject: Re: [cobbler] Documentation for RHEL Sure. I'd say start a new Wiki page about "Rapid Cobbler Server Bootstrapping From Scratch" or something similar, and make sure it encourages them to read all the other docs towards the bottom. On Thursday, February 23, 2012 at 12:20 PM, Gerhardus Geldenhuis wrote: I guess I am trying to make one size fits all. The scenario I have in my head is that "Pete" (fictitious sysadmin) has heard about cobbler and want to give it a go in a lab environment. Pete like most sysadmins is lazy and is likely not going to read most of the documented... but if he can get going quickly he would like the product more and more quickly start to do "real" work as in build the servers that generate the money. Once he has the server up and going is bound to start reading the documentation as he wants to scale and do more. Regards On 23 February 2012 16:47, Michael DeHaan < [email protected] <mailto:[email protected]> > wrote: Well… You're always going to have to read the configuration file… I'm not sure I understand what you're trying to accomplish in making it one size fits all. Mostly we're talking about picking config settings and restarting the service. Keep in mind there are some people with 20 machines here and others with tens of thousands -- the options are decidedly different in every case. Once set up, yes, copying configuration files around is, I would think, totally normal. But cobbler itself should not be fully automated in setting up itself, no… there are just too many variables. I think Owen's issue is different -- namely that the release didn't have sufficient upgrade instructions. On Thursday, February 23, 2012 at 11:44 AM, Mann, Owen wrote: I think there's some value here; when I upgraded from a RHEL5 Cobbler 1.6 machine to a RHEL6 Cobbler 2.0 machine, I had to do some jiggering since Cobbler 1.6 doesn't support RHEL6. From: [email protected] <mailto:[email protected]> [ mailto:[email protected] <mailto:[email protected]> ] On Behalf Of Gerhardus Geldenhuis Sent: Thursday, February 23, 2012 11:40 AM To: cobbler mailing list Subject: Re: [cobbler] Documentation for RHEL Not quite, Its about having a virgin environment with nothing on it apart from a link to the internet and starting to build a server. One size certainly does not fit all but having a vanilla flavoured version to use and learn on could be useful. I want to be able to get a cobbler server up and running and then subsequently my servers in a very quick time and I do not feel it is currently possible. But let me do some more head scratching and contribute a few updates to the docs and take it from there. Regards On 23 February 2012 16:33, Michael DeHaan < [email protected] <mailto:[email protected]> > wrote: 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 <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 <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 <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 <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 <https://fedorahosted.org/mailman/listinfo/cobbler> _______________________________________________ cobbler mailing list [email protected] <mailto:[email protected]> https://fedorahosted.org/mailman/listinfo/cobbler <https://fedorahosted.org/mailman/listinfo/cobbler> -- Gerhardus Geldenhuis _______________________________________________ cobbler mailing list [email protected] <mailto:[email protected]> https://fedorahosted.org/mailman/listinfo/cobbler <https://fedorahosted.org/mailman/listinfo/cobbler> _______________________________________________ cobbler mailing list [email protected] <mailto:[email protected]> https://fedorahosted.org/mailman/listinfo/cobbler <https://fedorahosted.org/mailman/listinfo/cobbler> -- Gerhardus Geldenhuis ******************************************************* This message (including any files transmitted with it) may contain confidential and/or proprietary information, is the property of Interactive Data Corporation and/or its subsidiaries, and is directed only to the addressee(s). If you are not the designated recipient or have reason to believe you received this message in error, please delete this message from your system and notify the sender immediately. An unintended recipient's disclosure, copying, distribution, or use of this message or any attachments is prohibited and may be unlawful. ******************************************************* _______________________________________________ cobbler mailing list [email protected] <mailto:[email protected]> https://fedorahosted.org/mailman/listinfo/cobbler <https://fedorahosted.org/mailman/listinfo/cobbler> _______________________________________________ cobbler mailing list [email protected] <mailto:[email protected]> https://fedorahosted.org/mailman/listinfo/cobbler <https://fedorahosted.org/mailman/listinfo/cobbler> -- Gerhardus Geldenhuis _______________________________________________ cobbler mailing list [email protected] <mailto:[email protected]> https://fedorahosted.org/mailman/listinfo/cobbler <https://fedorahosted.org/mailman/listinfo/cobbler>
_______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
