On Fri, Jul 3, 2009 at 9:47 PM, Paul Company<[email protected]> 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 [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
