<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
><br>
> hmmm<br>
> If it needs to be really unattended you either have to attach the right disk with install ISO and supply(point to) the desired kickstart? You'd need to have a template only per each OS install iso.<br>
><br>
</div>> Yes exactly. And the "iso" file could be a net address (for example directly on the centos servers). And you could have more than one kickstart per iso (that is the list proposed to the oVirt user):\<br>
so - can you do that already by supplying these on kernel boot line - in Edit VM dialog? I thin that should work.<br></blockquote><div><br></div><div>I tried but it does not work. For what I understood (but I didn't find lot of doc about this) the 3 parameters are used to specify kernel information but for an already installed machine. Means for example that the Kernel and Initd location should already be on the vm disk. I tried putting a remote location but my machine wouldn't start up... So I think I can't use the kernel parameters in oVirt</div>
<div><br></div><div>Marco</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
><br>
> Centos6 64 bit 10GB disk lvm no selinux<br>
> Centos6 64 bit All avaiable disk space<br>
> Centos6 64 bit with puppet and mcollective<br>
> ....<br>
><br>
> Marco<br>
><br>
><br>
><br>
> ><br>
> > To be clear, here yuo are what I'm traying in this moment:<br>
> ><br>
> > <a href="https://www.aeolusproject.org/redmine/projects/aeolus/wiki/RHEV-M_Setup?version=52" target="_blank">https://www.aeolusproject.org/redmine/projects/aeolus/wiki/RHEV-M_Setup?version=52</a><br>
> ><br>
> > And if someone has aeolus experience and suggestions is welcome :D<br>
> ><br>
> > Marco<br>
> ><br>
> > On Thu, Oct 11, 2012 at 1:38 PM, Michal Skrivanek <<a href="mailto:michal.skrivanek@redhat.com">michal.skrivanek@redhat.com</a>> wrote:<br>
> > On Oct 11, 2012, at 13:26 , Oved Ourfalli wrote:<br>
> ><br>
> > > Hey Marco.<br>
> > ><br>
> > > I see. My mistake...<br>
> > > We don't have such a feature built-in yet, but I guess there may be other 3rd party products that integrate with oVirt in order to do so.<br>
> > > Let's wait for other people to answer this thread.<br>
> > ><br>
> > > Oved<br>
> > ><br>
> > > ----- Original Message -----<br>
> > >> From: "Marco Mornati" <<a href="mailto:mornatim@gmail.com">mornatim@gmail.com</a>><br>
> > >> To: "Oved Ourfalli" <<a href="mailto:ovedo@redhat.com">ovedo@redhat.com</a>><br>
> > >> Cc: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
> > >> Sent: Thursday, October 11, 2012 1:09:56 PM<br>
> > >> Subject: Re: [Users] Virtual Machine Provisiong<br>
> > >><br>
> > >><br>
> > >> Hello Oved,<br>
> > >><br>
> > >><br>
> > >> thanks for your response, but, for me, provisioning means "Install<br>
> > >> Operating System and other packages". Is it possibile to do this<br>
> > >> directly using oVirt? I didn't find anything about it and that's the<br>
> > >> resason why I'm looking for others tools.<br>
> > well, if you want to select packages, etc., how would you present that to the user in ovirt GUI?<br>
> > Isn't it essentially the same as installing a VM with whatever you need using the desired OS installation method/GUI and save it as a template? And then deploy the template and do minor customizations (e.g. hostname change). We do plan to have support for such things in near future - we already have sysprep for Windows guests.<br>
> ><br>
> > Thanks,<br>
> > michal<br>
> ><br>
> > >> By and I can just start oVirt VM in "Run Once" mode, and putting the<br>
> > >> mac address in my PXE installation could start automatically.<br>
> > >> Problem is that I need to modify my PXE to create an automatic<br>
> > >> system. That's the reason puu me to look for anything else.<br>
> > >><br>
> > >><br>
> > >> Marco<br>
> > >><br>
> > >><br>
> > >> On Thu, Oct 11, 2012 at 12:25 PM, Oved Ourfalli < <a href="mailto:ovedo@redhat.com">ovedo@redhat.com</a> ><br>
> > >> wrote:<br>
> > >><br>
> > >><br>
> > >> oVirt exposes REST API that allows you to perform almost every<br>
> > >> operation in the oVirt engine, including provisioning, monitoring,<br>
> > >> performing different actions on the different entities, and etc.<br>
> > >><br>
> > >> We also have both SDK and CLI, which are based on this REST API.<br>
> > >><br>
> > >> Useful wiki pages:<br>
> > >> <a href="http://wiki.ovirt.org/wiki/Architecture" target="_blank">http://wiki.ovirt.org/wiki/Architecture</a><br>
> > >> <a href="http://wiki.ovirt.org/wiki/SDK" target="_blank">http://wiki.ovirt.org/wiki/SDK</a><br>
> > >> <a href="http://wiki.ovirt.org/wiki/CLI" target="_blank">http://wiki.ovirt.org/wiki/CLI</a><br>
> > >><br>
> > >> and I guess you'll find more pages on <a href="http://ovirt.org" target="_blank">ovirt.org</a> .<br>
> > >><br>
> > >> Good luck,<br>
> > >> Oved<br>
> > >><br>
> > >><br>
> > >><br>
> > >> ----- Original Message -----<br>
> > >>> From: "Marco Mornati" < <a href="mailto:mornatim@gmail.com">mornatim@gmail.com</a> ><br>
> > >>> To: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
> > >>> Sent: Thursday, October 11, 2012 12:09:53 PM<br>
> > >>> Subject: [Users] Virtual Machine Provisiong<br>
> > >>><br>
> > >>><br>
> > >>> Hello guys,<br>
> > >>><br>
> > >>><br>
> > >>> I'm trying to integrate an automatic provisioning to my oVirt<br>
> > >>> installation. Something like: API to create VM, NIC and Disk, tool<br>
> > >>> to install SO (??).<br>
> > >>><br>
> > >>><br>
> > >>> I'm actually working around aeolus (after a useless test with<br>
> > >>> koan),<br>
> > >>> but I'm not sure I can do what I want. I prefer not to use a PXE to<br>
> > >>> get all things really automatic (something cloud style).<br>
> > >>><br>
> > >>><br>
> > >>> Have you got any idea, suggestion and/or guide about it?<br>
> > >>><br>
> > >>><br>
> > >>> Thanks a lot<br>
> > >>> Marco<br>
> > >>> _______________________________________________<br>
> > >>> Users mailing list<br>
> > >>> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> > >>> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
> > >>><br>
> > >><br>
> > >><br>
> > >> _______________________________________________<br>
> > >> Users mailing list<br>
> > >> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> > >> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
> > >><br>
> > > _______________________________________________<br>
> > > Users mailing list<br>
> > > <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> > > <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
> ><br>
> ><br>
><br>
><br>
<br>
</div></div></blockquote></div><br>