Re: cobbler Digest, Vol 38, Issue 24
On Wed, Aug 31, 2011 at 4:07 PM, schuurma <schuurma(a)knmi.nl> wrote:
Hello to all.
I'm/we are using hardlinks to create snapshots van rpm downloads...
We pull daily the rpm's from the internet.
For deploying Fedora we use 3 stages:
1) incoming (repo_mirror) # from the internet, changes daily
2) testing (knmi_test) # copy'd once from incoming to testing and
then frozen !!! this is hardlink'd
3) production (knmi_all) # after acceptance the testing mirror is
copied once to the production repo.
I think cobbler needs some kind of system to make it possible to deploy
"OTAP" --- Ontwikkeling Test Acceptatie en Productie,
or Development, Testing, Acceptance and Production, (DTAP)
For that we must be able to revert back from Production tot
Acceptance/Testing fase...
Agreed, in this regard Cobbler is quite lacking... In our environment
we also have to deal with DTAP procedures.
For repo's, we don't use Cobbler at all, instead we put patches on a
seperate box and use filesystem snapshots to freeze repo's. Then we
generate/distribute the proper repo files to a group of systems with
Puppet, maybe this is a feasable approach for your organization?
--
Grtz,
Jörgen Maas