Am Mittwoch, den 18.12.2013, 14:42 +0100 schrieb Jakub Bittner: > Hello, > > I am wondering howto use this feature. Is it possible to install server > from this dialog? I specified kernel and initrd path as http url to our > spacewalk server and to kernel parameters I added > ks=http://spacewalk.server.url/ks.cfg, but it did not start. > > Is it possible to connect oVirt with spacewalk 2.0 (redhat satellite > 5.6) to provision servers? Hey Jakub, I guess that oVirt Engine could be deployed (partly) using a kickstart - but maybe others can correct me here. As for oVirt Node - you can't use a kickstart to roll it out, but you can use a wide range of kernel arguments to deploy a Node onto your machines. Take a look here for a list of kernel argument which can be used to automatically install Node: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Vir... - fabian

I don't know if that's a (current) feature. The host would have to fetch the kernel and initrd from a remote server and then boot the VM with those files. It seems like the current feature can use files on an iso ( e.g. iso:///images/pxeboot/initrd.img )

and maybe local (on the node) files? We use a seperate "linux install" network with a dhcp/tftp/pxe server for kickstart deployments. (you could use cobbler for that with spacewalk). After installation we change the guest network to the final config. On Wed, Dec 18, 2013 at 3:41 PM, Jakub Bittner <j.bittner(a)nbu.cz&gt; wrote: > Dne 18.12.2013 15:24, Fabian Deutsch napsal(a): > >> Am Mittwoch, den 18.12.2013, 14:42 +0100 schrieb Jakub Bittner: >>> >>> Hello, >>> >>> I am wondering howto use this feature. Is it possible to install server >>> from this dialog? I specified kernel and initrd path as http url to our >>> spacewalk server and to kernel parameters I added >>> ks=http://spacewalk.server.url/ks.cfg, but it did not start. >>> >>> Is it possible to connect oVirt with spacewalk 2.0 (redhat satellite >>> 5.6) to provision servers? >> >> Hey Jakub, >> >> I guess that oVirt Engine could be deployed (partly) using a kickstart - >> but maybe others can correct me here. >> As for oVirt Node - you can't use a kickstart to roll it out, but you >> can use a wide range of kernel arguments to deploy a Node onto your >> machines. >> Take a look here for a list of kernel argument which can be used to >> automatically install Node: >> >> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Vir... >> >> - fabian > > I am sorry, but I mean server as oVirt VM. Virtualized guest. Not oVirt > nodes. ;-) > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users