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
On Mon, Jul 6, 2009 at 5:04 AM, Simon
Woolsgrove<simon(a)woolsgrove.com> wrote:
>> --- pjcster(a)gmail.com wrote:
>>
>> From: Paul Company <pjcster(a)gmail.com>
>> To: cobbler mailing list <cobbler(a)lists.fedorahosted.org>
>> 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
> cobbler(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/cobbler
>
>
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler