|
Sandor, * Set "yum_post_install_mirror" to "1" in /var/lib/cobbler/settings. * Create a directory somewhere for your repository. Create a base directory: mkdir -p /my/repo/base * Copy any and all custom or third-party RPMs to the base directory. * Create the metadata for the repository ("yum install createrepo" if you don't have the utility). This may not be necessary, but this will ensure that the metadata is available: createrepo /my/repo # note that the target is not the base directory * Add the repo to cobbler. cobbler repo add --mirror=/my/repo --name=name_of_your_repo * Sync repositories: cobbler reposync * Add repos to your cobbler profiles/distros. cobbler distro edit --name=my_distro --repos='name_of_your_repo ...' cobbler profile edit --name=my_profile --repos='name_of_your_repo...' # Modify only the item that most closely meets your scope; e.g. if all profiles under "my_distro" should include 'name_of_your_repo', you can ignore the '--repos' field whenever creating profiles that exist under "my_distro". * You are done. Just cobbler sync and your systems' kickstart files will include YUM repo stanzas provided by Cheetah template expansions. ---- Note that adding RPMS to existing repositories may require re-running 'createrepo /my/repo' and 'cobbler reposync' to be seen on your deployed systems. You will also need to execute 'yum clean all' (or some variant of 'yum clean') on your client to force it to redownload the repository metadata (which describe the new RPM set). I hope this helps. Regards, -Adam. -A. Sandor W. Sklar wrote:
|
_______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
