On Fri, 25 Feb 2011 17:17:53 +0000, Jonathan Underwood <jonathan.underw...@gmail.com> wrote: > Hi, > > I have been thinking about how best to set up a cobbler server for > deploying the Scientific Linux 6 rolling release, but this applies to > any situation where a distribution is actually a moving target, for > example rawhide. As far as I can make out a "cobbler reposync" will > only re-sync repositories, and not imported distributions. I think it > would be useful to have a distrosync command which allowed for the > re-syncing of an imported distribution (obviously only for distros > imported from a network resource rather than a DVD) . A brief glance > over the code makes me realize the source URL isn't presently stored > for distros. Before I put any more time into researching this and > coming up with a patch - is this functionality desirable, or have I > missed something quite obvious in the current capabilities of cobbler?
I can see the use case, but I think it is already covered by existing functionality. Currently, I have base profiles and profiles that are actually used. The base profiles are things like RHEL-5.6-x86_64. Then I create sub profiles, e.g. RHEL5-x86_64, that the systems actually use. That way, when rhel5.7 comes out, I import that and move the rhel5 profile to it. Also, for applying updates we have repositories, which can be reposynced. I think this is close to what the SL6 rolling release is. Though it can cause issues with the install time. What I would do is import the latest SL6 on a biweekly basis, then have a repo that tracks updates. Having said the above, if a patch were to appear to do this, I think I would merge it. My main concern would be that it doesn't interrupt the above work flow. -- Scott Henson Red Hat CIS Operator WVU Alum BSAE/BSME
pgpvAUucQVN68.pgp
Description: PGP signature
_______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
