On Wed, 10 Mar 2010 08:34:51 -0700 (MST), Kevin Cai <kevinc(a)mozy.com>
wrote:
I think it is due to ESX4 install CD doesn't follow the standard
Fedora/RHEL directory structure,
so the cobbler doesn't know how to create the distro/profile,
anyway, you can create the distro/profile yourself manually, be sure to
give the correct initrd and vmlinuz which can be found in the ESX ISO
imange.
Best Regards
Kevin Cai
----- "The H.W. Group LLC" <the.hw.group(a)gmail.com> wrote:
> From: "The H.W. Group LLC" <the.hw.group(a)gmail.com>
> To: cobbler(a)lists.fedorahosted.org
> Sent: Wednesday, March 10, 2010 10:58:46 PM GMT +08:00 Beijing /
> Chongqing / Hong Kong / Urumqi
> Subject: VMware ESX4 cobbler import process?
>
>
Hello All,
Could someone give me an example of how one would import VMware ESX4 into
cobbler? A regular import copies the files from the mounted iso image,
but
does not create distro / profile information. Perhaps I missed a
step.
There really is not much information on the web. Just a brief step by
step
is fine. (and perhaps the rough syntax?)
I would really be grateful for the information.
Yes, it's because the directory is named VMware instead of RedHat or Server
in the root of the tree. The way we do it is to mount the ISO, copy the
files to the ks_mirror directory (after creating a subdirectory there for
it, of course), and then use "cobbler distro add" and "cobbler profile
add"
manually to set things up. After that, create a symlink in
/var/www/cobbler/links/ to your directory in ks_mirror/.
Just remember that when creating the distro you need to specify in the
ksmeta where the install location is, here's what we do:
--ksmeta="tree=http://@@http_server@@/cblr/links/esx-distro-name"
"cobbler import" is essentially just a wrapper for these steps, so any RH
based distro can be imported manually with these steps.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.