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. Seems like "import" only works if things get copied locally? Can cobbler work without having the distro locally on the cobbler server?
Paul
On Fri, Jul 3, 2009 at 9:47 PM, Paul Companypjcster@gmail.com wrote:
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. Seems like "import" only works if things get copied locally? Can cobbler work without having the distro locally on the cobbler server?
"cobbler import" is currently just a pretty wrapper around "cobbler distro add" and "cobbler profile add". You can achieve what you want by using distro add and then profile add. It isn't quite as magical as "cobbler import" but this comes up a lot.
You can achieve what you want by using distro add and then profile add.
"distro add" requires kernel= and initrd= to be on the local filesystem.
Remember what I was asking:
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.
Is this possible or do I need to run cobbler on my distro/repo server (has lots of disk). That doesn't really make cobbler flexible. My guess is I just don't understand something.
Thank you,
Paul
On Fri, Jul 3, 2009 at 10:21 PM, Jeff Schroederjeffschroed@gmail.com wrote:
On Fri, Jul 3, 2009 at 9:47 PM, Paul Companypjcster@gmail.com wrote:
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. Seems like "import" only works if things get copied locally? Can cobbler work without having the distro locally on the cobbler server?
"cobbler import" is currently just a pretty wrapper around "cobbler distro add" and "cobbler profile add". You can achieve what you want by using distro add and then profile add. It isn't quite as magical as "cobbler import" but this comes up a lot.
-- 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 Sat, Jul 04, 2009 at 12:45:22PM -0700, Paul Company wrote:
Remember what I was asking:
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.
Is this possible or do I need to run cobbler on my distro/repo server (has lots of disk). That doesn't really make cobbler flexible. My guess is I just don't understand something.
Personally, I have the OS sources on NFS, and just mount them onto the cobbler server -- which most of the time is a VM in my case anyways.
My rationale is that they have to be somewhere, they might as well be somewhere the cobbler server can see them.
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
On Sat, Jul 4, 2009 at 9:41 PM, David.Mackintosh@xdroop.com wrote:
On Sat, Jul 04, 2009 at 12:45:22PM -0700, Paul Company wrote:
Remember what I was asking:
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.
Is this possible or do I need to run cobbler on my distro/repo server (has lots of disk). That doesn't really make cobbler flexible. My guess is I just don't understand something.
Personally, I have the OS sources on NFS, and just mount them onto the cobbler server -- which most of the time is a VM in my case anyways.
My rationale is that they have to be somewhere, they might as well be somewhere the cobbler server can see them.
-- /\oo/\ / /()\ \ David Mackintosh | dave@xdroop.com | http://www.xdroop.com
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler@lists.fedorahosted.org