--- pjcster@gmail.com wrote:
From: Paul Company pjcster@gmail.com To: cobbler mailing list cobbler@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
What's the case?
That NFS is the only supported "access method" for adding a distro without copying the contents locally?
Paul
On Mon, Jul 6, 2009 at 5:04 AM, Simon Woolsgrovesimon@woolsgrove.com wrote:
--- pjcster@gmail.com wrote:
From: Paul Company pjcster@gmail.com To: cobbler mailing list cobbler@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@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
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
On Mon, Jul 6, 2009 at 5:04 AM, Simon Woolsgrovesimon@woolsgrove.com wrote:
--- pjcster@gmail.com wrote:
From: Paul Company pjcster@gmail.com To: cobbler mailing list cobbler@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@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
No, you can use http as well:
That doesn't work for me! Read my original post: (repeated here)
=======
On "myserver1" I mounted CentOS-5.3-x86_64-bin-DVD.iso on /media and NFS exported /media. I also make /media available via Apache - http://myserver1/media/
Then I ran the following on "myserver2", which has cobbler installed.
# 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
I get the following output:
---------------- (adding distros) ---------------- (associating kickstarts)
But, when I run the following:
# cobbler list
There's no output!!!! Isn't this supposed to make the distro available for use?
I'd like to add the distro (CentOS-5.3-x86_64-bin-DVD.iso) but I don't want to copy the contents over.
On Mon, Jul 6, 2009 at 8:27 AM, Ronald J. Yackettayacketrj@potsdam.edu 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
On Mon, Jul 6, 2009 at 5:04 AM, Simon Woolsgrovesimon@woolsgrove.com wrote:
--- pjcster@gmail.com wrote:
From: Paul Company pjcster@gmail.com To: cobbler mailing list cobbler@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@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
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
This is why I wish I never added these options to the import command, it brings up too many user questions related to basically GIGO scenarios.
Most likely what you have there is not what import /needs/, which is the exact copy of what was originally on the DVD images.
Hence why I recommend most folks just try the DVD ISOs.
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.
If you are still stuck, you should do this.
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 Woolsgrovesimon@woolsgrove.com wrote:
---pjcster@gmail.com wrote:
From: Paul Companypjcster@gmail.com To: cobbler mailing listcobbler@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@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Or ftp://, basically anything Anaconda supports.
Or you could just do "cobbler distro add" and skip import...
Neither works for me. Read my original post. After running the command you suggested, nothing is shows after "cobbler distro list".
Also, using "cobbler distro add" requires that you include --kernel and --initrd and their values have to be on the local filesystem, which is what I'm trying to avoid.
Am I missing something here? It sounds like I should be able to do what I want, but I it's not working for me. I'm running on RHEL 5.1 w/ cobbler 1.6.6.
Paul
On Mon, Jul 6, 2009 at 8:46 AM, Michael DeHaanmdehaan@redhat.com 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 Woolsgrovesimon@woolsgrove.com wrote:
--- pjcster@gmail.com wrote:
From: Paul Company pjcster@gmail.com To: cobbler mailing list cobbler@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@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
On 07/06/2009 12:01 PM, Paul Company wrote:
Or ftp://, basically anything Anaconda supports.
Or you could just do "cobbler distro add" and skip import...
Neither works for me. Read my original post. After running the command you suggested, nothing is shows after "cobbler distro list".
Also, using "cobbler distro add" requires that you include --kernel and --initrd and their values have to be on the local filesystem, which is what I'm trying to avoid.
Am I missing something here? It sounds like I should be able to do what I want, but I it's not working for me. I'm running on RHEL 5.1 w/ cobbler 1.6.6.
I suggest you just import from DVD or use cobbler distro add.
--available-as for filers does work /if/ you have the right content... and the right paths, and such, but often confuses people.
It is usually much much quicker for them to just use "cobbler distro add" than to sort it out, and there is not much lost in doing so.
Paul
On Mon, Jul 6, 2009 at 8:46 AM, Michael DeHaanmdehaan@redhat.com 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 Woolsgrovesimon@woolsgrove.com wrote:
--- pjcster@gmail.com wrote:
From: Paul Companypjcster@gmail.com To: cobbler mailing listcobbler@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@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
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.
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
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 DeHaanmdehaan@redhat.com 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 Woolsgrovesimon@woolsgrove.com wrote:
--- pjcster@gmail.com wrote:
From: Paul Company pjcster@gmail.com To: cobbler mailing list cobbler@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@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
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 DeHaanmdehaan@redhat.com 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 Woolsgrovesimon@woolsgrove.com wrote:
--- pjcster@gmail.com wrote:
From: Paul Companypjcster@gmail.com To: cobbler mailing listcobbler@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@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
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 DeHaanmdehaan@redhat.com 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 DeHaanmdehaan@redhat.com 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 Woolsgrovesimon@woolsgrove.com wrote:
--- pjcster@gmail.com wrote:
From: Paul Company pjcster@gmail.com To: cobbler mailing list cobbler@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@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
On 07/06/2009 02:59 PM, Paul Company wrote:
So bottom line is: distros have to live locally on the cobbler server filesystem. PERIOD!
No. Please don't shout :)
The command works, it's just hard to tell /what/ about that isn't working for you.
We use import in that way daily here to pull in trees from NFS.
It is easier to say "just use distro add" rather than to debug what may be different about your paths.
You'll be up in running quicker than you can reply to this email series :)
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.
The kernels and initrds must be local so they can be PXE booted. The trees do not have to be.
I say this because "cobbler distro add" requires that the values of --kernel and --initrd are paths on the local filesystem.
Not local, just on a mounted filesystem.
Please don't shout :)
Sorry for shouting. I'm just frustrated. Love cobbler, but this issue is just driving me nuts. ;-0
You'll be up in running quicker than you can reply to this email series :)
It's not a matter of getting things working - I can get things working with local distros, no problem. This issue is I'm trying to get this to work from a remote location that contains distros. Having everything local on my cobbler server is not at option at this point.
We use import in that way daily here to pull in trees from NFS.
So I'm assuming you can do the same using HTTP?
The kernels and initrds must be local so they can be PXE booted. The trees do not have to be.
Ah! Ha! (ok I said I wouldn't shout, but I can still get excited)
So you don't consider kernel and initrd as part of a Distribution? So I can not setup a cobbler server and have kernels and initrds remote? Correct?
The command works, it's just hard to tell /what/ about that isn't working for you.
I think it's that I don't have the kernel and initrd local. I was assuming --available-as= would deal with finding their location.
I guess my final question would be: What absolutely needs to reside locally on the cobbler server, and what can be remote?
Paul
On Mon, Jul 6, 2009 at 12:06 PM, Michael DeHaanmdehaan@redhat.com wrote:
On 07/06/2009 02:59 PM, Paul Company wrote:
So bottom line is: distros have to live locally on the cobbler server filesystem. PERIOD!
No. Please don't shout :)
The command works, it's just hard to tell /what/ about that isn't working for you.
We use import in that way daily here to pull in trees from NFS.
It is easier to say "just use distro add" rather than to debug what may be different about your paths.
You'll be up in running quicker than you can reply to this email series :)
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.
The kernels and initrds must be local so they can be PXE booted. The trees do not have to be.
I say this because "cobbler distro add" requires that the values of --kernel and --initrd are paths on the local filesystem.
Not local, just on a mounted filesystem.
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
On 07/06/2009 03:42 PM, Paul Company wrote:
Please don't shout :)
Sorry for shouting. I'm just frustrated. Love cobbler, but this issue is just driving me nuts. ;-0
You'll be up in running quicker than you can reply to this email series :)
It's not a matter of getting things working - I can get things working with local distros, no problem. This issue is I'm trying to get this to work from a remote location that contains distros. Having everything local on my cobbler server is not at option at this point.
We use import in that way daily here to pull in trees from NFS.
So I'm assuming you can do the same using HTTP?
Absolutely.
Anaconda (kickstart) supports network installs over http, nfs, or ftp... import will handle all of these, but if it's giving trouble, distro add is basically just the same thing.
You still need kernels on the filesystem in order to PXE. Cobbler will copy them into the right locations.
-
The kernels and initrds must be local so they can be PXE booted. The trees do not have to be.
Ah! Ha! (ok I said I wouldn't shout, but I can still get excited)
So you don't consider kernel and initrd as part of a Distribution?
They are the most important part of the distribution. The tree, however, is only loosely associated.
if you do a cobbler import, it will store a --ksmeta variable called "tree" that will point to a URL and that will be used in the kickstart templating, but it can exist /anywhere/.
(Import is a command that (when run normally, i.e. not --available-as) helps folks make sure their content is web accessible nd automatically sets up those variables.)
So I can not setup a cobbler server and have kernels and initrds remote? Correct?
You at minimum need them somewhere on a filesystem. That can be remote, i.e. NFS is fine, or it could be the trees are remote and you just copied the installer kernel/initrds to /srv or /opt or wherever.
The command works, it's just hard to tell /what/ about that isn't working for you.
I think it's that I don't have the kernel and initrd local. I was assuming --available-as= would deal with finding their location.
I guess my final question would be: What absolutely needs to reside locally on the cobbler server, and what can be remote?
Nothing needs to be local.
Kernels and initrds must be on a mounted filesystem.
Trees can be local or remote (if remote, ftp, nfs, or http access is required).
Remember import is nothing more than a macro around "cobbler distro add" and "cobbler profile add" and sometimes a little bit of copying. It is optional, so if you think you are smarter than it or know better, it's totally fine to not use it.
--Michael
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?
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).
Trees can be local or remote (if remote, ftp, nfs, or http access is required).
What's your definition of 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"?
Paul
On Mon, Jul 6, 2009 at 12:50 PM, Michael DeHaanmdehaan@redhat.com wrote:
On 07/06/2009 03:42 PM, Paul Company wrote:
Please don't shout :)
Sorry for shouting. I'm just frustrated. Love cobbler, but this issue is just driving me nuts. ;-0
You'll be up in running quicker than you can reply to this email series :)
It's not a matter of getting things working - I can get things working with local distros, no problem. This issue is I'm trying to get this to work from a remote location that contains distros. Having everything local on my cobbler server is not at option at this point.
We use import in that way daily here to pull in trees from NFS.
So I'm assuming you can do the same using HTTP?
Absolutely.
Anaconda (kickstart) supports network installs over http, nfs, or ftp... import will handle all of these, but if it's giving trouble, distro add is basically just the same thing.
You still need kernels on the filesystem in order to PXE. Cobbler will copy them into the right locations.
The kernels and initrds must be local so they can be PXE booted. The trees do not have to be.
Ah! Ha! (ok I said I wouldn't shout, but I can still get excited)
So you don't consider kernel and initrd as part of a Distribution?
They are the most important part of the distribution. The tree, however, is only loosely associated.
if you do a cobbler import, it will store a --ksmeta variable called "tree" that will point to a URL and that will be used in the kickstart templating, but it can exist /anywhere/.
(Import is a command that (when run normally, i.e. not --available-as) helps folks make sure their content is web accessible nd automatically sets up those variables.)
So I can not setup a cobbler server and have kernels and initrds remote? Correct?
You at minimum need them somewhere on a filesystem. That can be remote, i.e. NFS is fine, or it could be the trees are remote and you just copied the installer kernel/initrds to /srv or /opt or wherever.
The command works, it's just hard to tell /what/ about that isn't working for you.
I think it's that I don't have the kernel and initrd local. I was assuming --available-as= would deal with finding their location.
I guess my final question would be: What absolutely needs to reside locally on the cobbler server, and what can be remote?
Nothing needs to be local.
Kernels and initrds must be on a mounted filesystem.
Trees can be local or remote (if remote, ftp, nfs, or http access is required).
Remember import is nothing more than a macro around "cobbler distro add" and "cobbler profile add" and sometimes a little bit of copying. It is optional, so if you think you are smarter than it or know better, it's totally fine to not use it.
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
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
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:
# 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 DeHaanmdehaan@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
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
On Mon, Jul 6, 2009 at 2:28 PM, Paul Companypjcster@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 DeHaanmdehaan@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
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 Schroederjeffschroed@gmail.com wrote:
On Mon, Jul 6, 2009 at 2:28 PM, Paul Companypjcster@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 DeHaanmdehaan@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@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
On 07/06/2009 06:30 PM, Paul Company wrote:
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
I don't understand where you are going with this thread, but it has been spelled out:
* you don't have to use cobbler import, you can use cobbler distro add if you don't like what import does for you * Anaconda supports http, ftp, and nfs:// URLs -- you are welcome to use any of these * Cobbler uses HTTP by default, and this is what "cobbler import --name=foo --path=/mount/point" will make things available as * Your kernel and initrd files but be on a filesystem somewhere because we have to copy them for various things including TFTP.
I don't see the behavior of import changing as a result of this thread -- this feature has been around a long while and seems to meet most everyone's requirements, so let's not speculate on that.
If you are still trying to understand what to do or how something works, ask a question along those lines, and we'll answer it.
--Michael
If you are still trying to understand what to do or how something works, ask a question along those lines, and we'll answer it.
On the "how something works" front: I see value in supporting the following: # cobbler distro add --kernel=http://path/to/vmlinuz --initrd=http://path/to/initrd.img --name=foo
This command would copy vmlinuz and initrd.img in the correct places under /tftpboot making them available for PXE booting. It would allow people to use machines on the Internet (via http) instead of being forced to copy things locally (via NFS or other means). Have you ever tried to NFS mount something from a remote machine on the Internet? Doesn't work.
ON the "what to do" front: I currently have this issue at work, where our distros (vmlinuz & initrd.img) are available via http but they are not available via NFS (and will never be).
On Mon, Jul 6, 2009 at 3:35 PM, Michael DeHaanmdehaan@redhat.com wrote:
On 07/06/2009 06:30 PM, Paul Company wrote:
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
I don't understand where you are going with this thread, but it has been spelled out:
- you don't have to use cobbler import, you can use cobbler distro add if
you don't like what import does for you
- Anaconda supports http, ftp, and nfs:// URLs -- you are welcome to use any
of these
- Cobbler uses HTTP by default, and this is what "cobbler import --name=foo
--path=/mount/point" will make things available as
- Your kernel and initrd files but be on a filesystem somewhere because we
have to copy them for various things including TFTP.
I don't see the behavior of import changing as a result of this thread -- this feature has been around a long while and seems to meet most everyone's requirements, so let's not speculate on that.
If you are still trying to understand what to do or how something works, ask a question along those lines, and we'll answer it.
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
If you are still trying to understand what to do or how something works, ask a question along those lines, and we'll answer it.
On the "how something works" front: I see value in supporting the following: # cobbler distro add --kernel=http://path/to/vmlinuz --initrd=http://path/to/initrd.img --name=foo
This command would copy vmlinuz and initrd.img in the correct places under /tftpboot making them available for PXE booting. It would allow people to use machines on the Internet (via http) instead of being forced to copy things locally (via NFS or other means). Have you ever tried to NFS mount something from a remote machine on the Internet? Doesn't work.
ON the "what to do" front: I currently have this issue at work, where our distros (vmlinuz & initrd.img) are available via http but they are not available via NFS (and will never be).
so just wget them yourself to the cobbler server and use the paths from there - i dont see what the issue is?
cobbler@lists.fedorahosted.org