[Ovirt-devel] iSCSI questions and VM Creation questions

Wed Aug 5 18:13:10 UTC 2009

On Wed, Aug 05, 2009 at 03:33:48PM +0200, sylvain.desbureaux at orange-ftgroup.com wrote:
> Thanks for the super quick answer :-)!
> My answers in the bottom
> 
> --
> Sylvain Desbureaux
> +33 296 051 380
> 
> 
> -----Message d'origine-----
> De : Hugh O. Brock [mailto:hbrock at redhat.com] 
> Envoyé : mercredi 5 août 2009 15:10
> À : DESBUREAUX Sylvain RD-BIZZ-LAN
> Cc : ovirt-devel at redhat.com
> Objet : Re: [Ovirt-devel] iSCSI questions and VM Creation questions
> 
> On Wed, Aug 05, 2009 at 02:58:18PM +0200, sylvain.desbureaux at orange-ftgroup.com wrote:
> >> Hi,
> >> I finally managed to have one node working.
> >> I added a iSCSI LUN (ok if selinux is set to 0) and wanted to create my first VM.
> >
> > Good. For what it's worth, there is now an updated selinux policy for
> > libvirt, should allow you to leave selinux turned on.
> 
> I've seen it pass on the last update (perhaps It wasn't necessary to turn selinux off)

Sigh... turns out the selinux fix doesn't quite work... we're working on
it still. In the meantime setting permissive is the workaround.

> >
> >> So I created a VM and had some issues:	
> >> *	I can choose boot from HD but I'm just able to choose the LUN, not a specific size in the LUN like you can do in vmware ESX. So, do I have to create a LUN per VM? If yes, it's quite complicated...
> >
> > We had intended people to create LVM partitions on top of an iSCSI LUN, so you have some flexibility on the size and allocation of your VM partitions. You should be able to do this from the UI.
> 
> When you talk about the UI, is it the oVirt UI? Because I don't see where (I've got the 0.102 version)

Yes. From the oVirt UI, once you have iSCSI storage set up, you should
be able do go to the storage page and add a volume group + some logical
volumes to your iSCSI LUN. 

> >
> >> *	If I choose boot from HD, there's no way to specify another boot parameter (I would like to use a liveCD to install a distro). Is it possible to do that?
> >
> > Hmm, I think what you want to do here is create an ISO image profile in Cobbler for your liveCD and boot from that to install. You will just need to put your ISO in a shared storage volume that the nodes can mount; cobbler will supply the node with the path to the ISO on shared  storage, and it will then boot the VM from there.
> 
> Ok, I'll take a deeper look at cobbler (I've read that it was impossible to do that with cobbler but it was perhaps an old version).

Cobbler added ISO image management for us recently. All it really is is
a pointer in the cobbler profile to an NFS share with an ISO file; the
VM description then pulls that ISO as the boot device.

> 
> >> *	I've three networks (the VM created are supposed to act like routers), one management/guest/storage and two others. When I boot, all these interfaces are put on the same bridge (I've got 5 ethernet interfaces) instead of being put in three different bridges. Is it normal? FYI, I've created a bug (https://bugzilla.redhat.com/show_bug.cgi?id=515684) because the igb kernel module (needed  for some Intel Ethernet cards) wasn't working. Now it works (changed a little bit blacklist.ks) but I have to manually modprobe at the end of the boot so perhaps that's why only one bridge is created?
> 
> > Hmm... we have been having some issues with network config. The bridging of the interfaces depends on how you have the host networking set up ("edit networks" dialog from the Host details pane). I'd love it if you would try again with the release we are building today (some new network config UI and code) and let us know if it works -- if not, detailed info on how the NICs are supposed to be configured vs. what is actually happening would be really helpful.
> 
> I've edited the networks but I can do that only for eth0 (which is a Broadcom interface that I use for the admin networks). For the others interfaces, I'm not able to set it up (no choices for network, perhaps because I have to manually do the modprobe or because they don't have IP addresses).
> No problem to test it with the new release (I assume I'll have to wait tomorrow for that because I'm based in Europe).

Interesting. The way this *should* work is, when the node boots, it
should inform the server about all the NICs it has, whether they are
active or not. It will then ask the server what it is supposed to do
with them (bring them up/down, bridge them, bond them, etc.) and do
that. If this is the first time the node is booting, obviously the
server won't know yet how to configure the NICs. So you have to go to
the Host details pane for that node in the UI and click "edit networks"
for that node. You should then be able to assign the various NICs on the
host to different networks in the UI.

If you then reboot the node, it should automatically acquire and
implement the NIC configuration you have specified.

> A question about that. How do I upgrade a previous version? Just the yum part or do I have to do also ovirt-installer + ace?

RPM upgrade plus a "rake db:migrate" as root from
/usr/share/ovirt-server should do the job. However be warned we are not
explicitly testing upgrades yet, so YMMV...

Take care,
--Hugh

> 
> Thanks,
> 
> > Thanks in advance,
> > 
> >  <<Picture (Device Independent Bitmap)>> 
> > Sylvain Desbureaux
> > Recherche et DÃ©veloppement, Service aux entreprises
> > IngÃ©nieur concepteur dÃ©veloppeur de services rÃ©seaux pour les entreprises
> > tÃ©l. 02 96 05 13 80
> > sylvain.desbureaux at orange-ftgroup.com
> >  <<Picture (Device Independent Bitmap)>> 
> > 
> > 
> 
> 
> 
> 
> > _______________________________________________
> > Ovirt-devel mailing list
> > Ovirt-devel at redhat.com
> > https://www.redhat.com/mailman/listinfo/ovirt-devel
> 
> 
> _______________________________________________
> Ovirt-devel mailing list
> Ovirt-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/ovirt-devel