re: https://fedorahosted.org/cobbler/ticket/130 and https://fedorahosted.org/cobbler/ticket/205
Background info: When you turn on yum_post_install_mirror in /etc/cobbler/settings, what that means is that you want your installed systems to point back to cobbler to get updates -- it makes cobbler an install server, but also an update server, as managed with "cobbler reposync". This is a fairly useful feature that many people use. Cobbler then inserts magic into the %post section wherever you have $yum_config_stanza that puts in the appropriate wgets, so that every system you install with cobbler makes sure to set up installed systems so that they use cobbler as a mirror. Basically it configures yum on each installed system. Pretty simple. (Note that changing any extra files from /etc/yum.repos.d that you don't want is still your responsibility to do in %post). Further background info: In 0.9/1.0, we made the kickstart files fully dynamic -- they were dynamically generated by mod_python (on demand) as opposed to saved on the filesystem. However, the repo configs used by yum_post_install_mirror were still static, as required a "cobbler sync" to update changes -- for instance, if you reconfigured a repo or changed what repos a profile used, you had to run "cobbler sync". This means cobbler had to write more files on the filesystem and that "cobbler sync" needed to be a command that was frequently used. Not so anymore. Today, I changed that for 1.1/1.2 so that yum configs are now served from mod_python. An example URL like http://cobbler.example.com/cblr/svc/op/yum/profile/sTEST-s390x will serve up the yum config file as needed for any particular system, with multiple repos in the same config file. $yum_config_stanza will then be substituted as: wget "http://cobbler.example.com/cblr/svc/op/yum/profile/sTEST-s390x"; --output-document=/etc/yum.repos.d/cobbler-config.repo Note that: "Cobbler reposync" is still an important command, and you'll need to know about "cobbler sync" if you are using DHCP/DNS management -- but otherwise, it's less important. When using DHCP with omapi engaged for instance, "cobbler sync" is not needed to make DHCP changes -- but it is still needed for DNS changes. Hopefully that was not too confusing, the purpose of this is to explain why more files in /var/www/cobbler are no longer being generated and a bit about URLs for those that pay attention to how cobbler serves things up. This has already been pushed to cobbler's devel branch. If you have any questions/comments, please ask! Thanks, Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
