cobbler would still have to copy the file locally for tftp to work.
Yes, I get that.
So cobbler uses http to copy things over instead of NFS.
http is better than NFS in the context of availabilty.
You're no longer dependent on NFS.
I think that's a really really good thing. No?
Paul
On Mon, Jul 6, 2009 at 3:16 PM, Jeff Schroeder<jeffschroed(a)gmail.com> wrote:
On Mon, Jul 6, 2009 at 2:28 PM, Paul Company<pjcster(a)gmail.com>
wrote:
>> We need to crawl the tree, and http:// is unsuitable for this.
>
> Do you really need to crawl the tree, or do you just need the locations of
> kernel (vmlinuz) and initrd (initrd.img)?
>
> Why isn't the following reasonable:
Because in.tftpd doesn't support serving files from http. Even if that
cobbler command worked, cobbler would still have to copy the file
locally for tftp to work.
> # cobbler distro add --name=foo --kernel=http://path/to/vmlinuz
> --initrd=http://path/to/initrd.img
> # cobbler profile add --name=foo-profile --distro=foo
> --kickstart=http://path/to/ks.cfg etc.
>
> Limiting things to NFS severely limits your availability.
> http is accessible almost everywhere on the Internet, but NFS is not.
>
> My guess is you're crawling the tree to find if there are other
> distros in there.
> For example, CentOS-5.3-x86_64-bin-DVD.iso, includes both
> CentOS-5.3-x86_64 and CentOS-5.3-xen-x86_64
>
> You would have to add them separately if you didn't crawl the tree.
> But the tradeoff between adding distro's separately and making distros
> more available seams to favor availability? No?
>
> Paul
>
> On Mon, Jul 6, 2009 at 1:53 PM, Michael DeHaan<mdehaan(a)redhat.com> wrote:
>> On 07/06/2009 04:44 PM, Paul Company wrote:
>>
>> Nothing needs to be local.
>> Kernels and initrds must be on a mounted filesystem.
>>
>>
>> So only NFS is supported for making kernel and initrd appear local.
>> HTTP can't be used to copy them locally automatically.
>> --path=http:// is illegal - should it be?
>>
>>
>> We can't traverse directories over http nearly as easily, so no, it should
>> not be.
>>
>>
>>
>> It doesn't really make sense to me that --available-as= allows http,nfs,ftp
>> but --path= only allows local paths (well, an NFS mount isn't local
>> but appears local).
>>
>>
>>
>> We need to crawl the tree, and http:// is unsuitable for this.
>>
>> Trees can be local or remote (if remote, ftp, nfs, or http access is
>> required).
>>
>>
>> What's your definition of Tree?
>>
>>
>> An install tree is a set of packages plus other metadata needed by Anaconda
>> in order to install OS. It is an installation source.
>>
>> The contents are what you feed to "url --url=http://foo" in kickstart,
that
>> is the tree.
>>
>> When I inspect a distro, say CentOS-5.3-x86_64-bin-DVD.iso,
>> I see kernel (vmlinuz) and initrd (initrd.img) in the
>> images/pxeboot/initrd.img directory.
>> Do you consider the CentOS directory the "Tree"?
>>
>>
>> The thing above images is the root of the install tree, yes.
>>
>>
>> Paul
--
Jeff Schroeder
Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler