Chris O'Regan wrote: >>> What if I have a sub-cobbler that will manage its own set of systems? >>> Won't it want to write into /var/www/cobbler? I would prefer that only >>> my master cobbler have write access to this directory and mount it >>> read-only on the sub-cobblers. >>> >> In this case, use could use "cobbler import" with --available-as to add >> trees that are on NFS. >> > > In this particular case, NFS won't be possible. The purpose of this > Cobbler is for students to build their own servers, and as a policy we > do not export NFS to untrusted subnets. Hrmmm... --available-as need not > be NFS, right? I suppose I can work around this by making the trees > available through the web server manually and do a "cobbler import" with > --available-as=http://... >
Correct! > >> You could also use cobbler replicate to copy /var/www/cobbler between >> the systems. That's all rsync powered so why you'd need a bit of storage >> the install trees would not change often. >> > > This might be a reasonable alternative since this server has a single > purpose and plenty of local disk space that will otherwise go unused, > but I would like to avoid the duplicate data, if possible. > > > Thanks again, > > Chris > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
