So bottom line is: distros have to live locally on the cobbler server filesystem. PERIOD!
You can NOT setup a cobbler server and "cobbler import" or "cobbler distro add" + "cobbler add profile" a remote distro? What I mean by remote distro is NFS mounted or available via http. I say this because "cobbler distro add" requires that the values of --kernel and --initrd are paths on the local filesystem. And "cobbler import .... --available-as=http:// or nfs://" does not add the distro! Is my bottom line statement correct? Paul On Mon, Jul 6, 2009 at 11:10 AM, Michael DeHaan<[email protected]> wrote: > On 07/06/2009 01:23 PM, Paul Company wrote: > > Michael, > > > > No, you can use http as well: > > # cobbler import --path=/mnt/cobbler_f11_iso --available-as=http://url > --name=f11 > > > Isn't this what my example shows, but my example doesn't work. > Here's exactly what I do, can you give me the correct line that should > work using http. > > > > I didn't know that your content on the filesystem is correct, hence why I > cannot tell that your example is correct. > > > On "myserver1" I mounted CentOS-5.3-x86_64-bin-DVD.iso on /media > # mount -o loop /usr/distros/iso/CentOS-5.3-x86_64-bin-DVD.iso /media > and I make /media available via Apache - http://myserver1/media/ > Then on "myserver2" I run > # mkdir -p /distros/CentOS-5.3/x86_64 > # cobbler import --path=/distros/CentOS-5.3/x86_64 > --available-as=http://myserver1/media > --name=CentOS-5.3-x86_64 > > > If that is the full and complete root of the DVD, it /should/ work, yes. > > Seems like it is not... though as this is a rather hard thing to debug > remotely I am increasingly in favor of deprecating that support > and suggesting folks use "cobbler distro add" if they don't want to mirror > things through cobbler import, and make import be the way to go for people > who do want cobbler to help set things up. > > Otherwise there really isn't that much that import is doing for you... > > > Aren't you saying that this line should work? It looks like the one > you gave above. > Can you give me a working line ("cobbler import" or "cobbler distro > add" + "cobbler profile add") that works with http. > > Paul > > > > On Mon, Jul 6, 2009 at 8:46 AM, Michael DeHaan<[email protected]> wrote: > > > On 07/06/2009 11:27 AM, Ronald J. Yacketta wrote: > > Paul Company wrote: > > What's the case? > > That NFS is the only supported "access method" for adding a distro > without copying the contents locally? > > Paul > > > > No, you can use http as well: > > # cobbler import --path=/mnt/cobbler_f11_iso --available-as=http://url > --name=f11 > > > Or ftp://, basically anything Anaconda supports. > > Or you could just do "cobbler distro add" and skip import... which is just > some basic automation around those commands (cobbler distro add / cobbler > profile add) anyway. > > --Michael > > > > On Mon, Jul 6, 2009 at 5:04 AM, Simon Woolsgrove<[email protected]> > wrote: > > > --- [email protected] wrote: > > > From: Paul Company <[email protected]> > To: cobbler mailing list <[email protected]> > Subject: Re: Adding a Distribution without copying the contents over? > Date: Sat, 4 Jul 2009 23:05:47 -0700 > > > When you say "see them" you mean "ability to access them via a > transport protocol" or what I liked to call an "access method". NFS is > just one type of "access method". Wouldn't it be good to support http, > https, ftp, rsync, ssh. Have you ever tried to NFS mount something on > the Internet. > > > If you see my original post, I thought "--available-as=nfs://etc." > would do as you described, but it doesn't. > > > So what is the difference between using --available-as=nfs:// and NFS > mounting the path and then using import on the nfs mount point? > > > Paul > > > I think this is the case > > --available-as points to the location rather than importing the entire > tree, which I think you want, vs the latter which would import the entire > tree. > > Cobbler creates a ks_meta value tree which is substitues (in the example ks > for this path) > > >From your post > > # mkdir -p /distros/CentOS-5.3/x86_64 > # cobbler import --path=/distros/CentOS-5.3/x86_64 --arch=x86_64 > --name=CentOS-5.3-x86_64 \ > --available-as=nfs://myserver1:/media > or > # cobbler import --path=/distros/CentOS-5.3/x86_64 --arch=x86_64 > --name=CentOS-5.3-x86_64 \ > --available-as=http://myserver1/media > > Does /distros/CentOS-5.3/x86_64 have an actual copy of the media, as cobbler > still needs to find the boot initrd, kernel, yum repo's etc ? > > It should probably give a message that it does not find anything... > > As others have pointed you do not have to use import and could use > distro/profile and use your own ks_meta variables to locate the data tree > whci can be compeltely seperate from the cobbler server if thats what you > want. > > Cheers, > Simon > > > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > > > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > > > ________________________________ > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > > > > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > > _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
