> > I assume it works with my own content, because it mirrors a local > directory (RHEL5 doesn't provide all I need). But my suggestion for a > --available-as option for local repositories may become a RFE... > Really, I think that in a packaging workflow, the team providing > packages is not always the teams managing the systems deployment > through cobbler. This way, I manage my package lifecycle (I can't get > Spacewalk in my IT environment due to no-oracle policy). I have the > following cobbler configuration :
Cobbler can add external repos without mirroring them already. This is --mirror-locally=0 as you mention. > > - Distributions imported from DVD (RHEL5.3) and HTTP mirrors (CentOS > 5.2 & Fedora Core 10) > - Official repositories imported from RHN and HTTP mirrors > - The packages are not systematically provided to > servers/workstations. They go through validation process : > 1. Links to specific packages in a local test repo, only available > to test servers > 2. Links to validated packages in another local release repo, > available to all servers > - Local repositories imported for locally generated packages (options > not available in official packages + not packaged softwares) > > Distros and repos (both remote and local) are stored on a NFS share > (storage limited on server) only accessible to my cobbler server > (through NFS server acls). Thus I have kind of bypassed cobbler > management system : > > - For distros I copy the DVD content in a directory on the NFS mount, > then import the distro path with a --available-as option pointing to a > cobbler's http url > (http://<cobbler_server>/cobbler/ks_mirror/<distro_name>). Then I > create a link in /var/www/cobbler/ks_mirror/ pointing to the directory > on my NFS mount. This way, I keep coherence with classical cobbler > config (distros are stored in /var/www/cobbler/ks_mirror). > > - For remote repositories, I use the same method. I declare the > repository in cobbler with 'cobbler repo add'. Before syncing, I > create a directory on my NFS mount and a link in > /var/www/cobbler/repo_mirror pointing to this directory named by the > repo name. Thus, when I launch 'cobbler reposync' the repository is > synced on NFS. I only use paths defined in cobbler. > > - For local repositories (specific packages and testing/validated > updates), the method is the same less the fact I don't need to sync > them. Thus when declaring them with 'cobbler repo add', I use > --mirror-locally=N. > > All this let me declare repositories available through cobbler's HTTP > server, keeping remote repositories synced through cobbler. I have > deployed RHEL5.3 servers and FC10 workstations using cobbler with no > error. > > I want to add that I have first stored my RHEL5.3 distro et repos > locally (less than 25Gb), and I have exactly the same behaviour with > remote NFS storage. Moreover, I think this can be quite useful to > consolidate storage between more than 1 cobbler server : all cobbler > servers could mount the same NFS share and thus provide the same packages. > > Yep, I have bypassed normal cobbler's behaviour, but it works and I > think this can bring to RFE(s). > What do you think of all this ? > Please summarize in less words what you'd specifically like to change that is different from "--mirror-locally=0". _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
