3:08 a.m.
This is a multi-part message in MIME format.
--------------040909090108000803090007
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi guys,
I built my hosted-engine with three nodes (3.4, CentOS), and built a
Gluster ISO domain, connected it up, all good.
Until I come to engine-iso-uploader, it is present on the hosted-engine
but not on the VMs.
And my gluster subnet is not routed. So the VM can't see it to upload
ISOs into.
How are other people getting around this?
I can see:
1. Obvious - make the Gluster LAN routed. It wouldn't hurt, just for
transferring a few ISOs.
2. Add a second NIC to the hosted-engine VM, so that it can see the
gluster LAN
3. put engine-iso-uploader on one of the nodes, is that possible?
My preference is to connect hosted-engine to the Gluster LAN.
Is it possible to add another NIC to the VM, after it's built? (I don't
want to rebuild if avoidable; I've done that enough times).
I know that the ovirt GUI isn't aware of the first NIC on the VM, so I
haven't dared to try adding a NIC there. Is that safe?
Thanks in advance for your thoughts on this.
cheers,
*Garry
*
--------------040909090108000803090007
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi guys,<br>
<br>
I built my hosted-engine with three nodes (3.4, CentOS), and built a
Gluster ISO domain, connected it up, all good.<br>
<br>
Until I come to engine-iso-uploader, it is present on the
hosted-engine but not on the VMs.<br>
And my gluster subnet is not routed. So the VM can't see it to
upload ISOs into.<br>
<br>
How are other people getting around this?<br>
<br>
I can see:<br>
1. Obvious - make the Gluster LAN routed. It wouldn't hurt, just for
transferring a few ISOs.<br>
2. Add a second NIC to the hosted-engine VM, so that it can see the
gluster LAN <br>
3. put engine-iso-uploader on one of the nodes, is that possible?<br>
<br>
My preference is to connect hosted-engine to the Gluster LAN. <br>
<br>
Is it possible to add another NIC to the VM, after it's built? (I
don't want to rebuild if avoidable; I've done that enough times).<br>
I know that the ovirt GUI isn't aware of the first NIC on the VM, so
I haven't dared to try adding a NIC there. Is that safe?<br>
<br>
Thanks in advance for your thoughts on this.<br>
<br>
cheers,<br>
<div class="moz-signature">
<p class="MsoNormal"><font face="Verdana"
size="2"><span
style="font-size:10.0pt;font-family:Verdana"><b><font
color="#46166c"><span
style="color:#46166C;font-weight:bold">Garry <br>
</span>
</font>
</b>
</span>
</font>
<font face="Verdana" size="1">
<span style="font-size:9.0pt;font-family:Verdana"><!-- ***
TITLE *** --></span></font><br>
</p>
<br>
</div>
</body>
</html>
--------------040909090108000803090007--
11:17 p.m.
Hi Garry,
I hope I understand your case here, the terminology is a little "different".
Adding the hosted-engine to the gluster network is an interesting
approach I tried. It works to an extent but will have issues with
quorum (depending on your setup).
Anyway try this:
# Generate random UUID and MAC Address - or create your own by hand..
yum -y install python-virtinst
echo 'import virtinst.util ; print
virtinst.util.uuidToString(virtinst.util.randomUUID())' | python
echo 'import virtinst.util ; print virtinst.util.randomMAC()' | python
hosted-engine --set-maintenance --mode=global
# On all installed hosts
nano /etc/ovirt-hosted-engine/vm.conf
# insert under earlier nicModel
# replace macaddress and uuid from above
# increment slot
devices={nicModel:pv,macAddr:00:16:3e:j1:4b:22,linkActive:true,network:storage_network,filter:vdsm-no-mac-spoofing,specParams:{},deviceId:fds24208-a234-z123-6053-32c9c0361f96,address:{bus:0x00,slot:0x04,
domain:0x0000, type:pci,function:0x0},device:bridge,type:interface}
hosted-engine --vm-shutdown
hosted-engine --vm-start
hosted-engine --set-maintenance --mode=none
Now your hosted-engine VM should come up with another NIC, this'll
work for modifying your existing hosts. But I'm not sure how to apply
this to the answers file if you were to add a new host to the
configuration.
HTH
On Tue, Apr 29, 2014 at 6:08 PM, Garry Tiedemann
<garrytiedemann(a)networkvideo.com.au> wrote:
Hi guys,
I built my hosted-engine with three nodes (3.4, CentOS), and built a Gluster
ISO domain, connected it up, all good.
Until I come to engine-iso-uploader, it is present on the hosted-engine but
not on the VMs.
And my gluster subnet is not routed. So the VM can't see it to upload ISOs
into.
How are other people getting around this?
I can see:
1. Obvious - make the Gluster LAN routed. It wouldn't hurt, just for
transferring a few ISOs.
2. Add a second NIC to the hosted-engine VM, so that it can see the gluster
LAN
3. put engine-iso-uploader on one of the nodes, is that possible?
My preference is to connect hosted-engine to the Gluster LAN.
Is it possible to add another NIC to the VM, after it's built? (I don't want
to rebuild if avoidable; I've done that enough times).
I know that the ovirt GUI isn't aware of the first NIC on the VM, so I
haven't dared to try adding a NIC there. Is that safe?
Thanks in advance for your thoughts on this.
cheers,
Garry
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3654
days inactive
3659
days old
1 comments
2 participants
participants (2)
-
Andrew Lau -
Garry Tiedemann