<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2016-10-06 14:12 GMT+02:00 Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
</span>Something like the following (I'm assuming you have multiple hosts...):<br>
1. Put host in to maintenance mode<br>
2. Remove it from oVirt<br>
3. Change host network settings<br>
4. Re-attach host with new setting to oVirt<br>
5. Migrate some VMs to the new host and fix their IP settings<br>
6. Repeat for other hosts<br>
<br></blockquote><div><br></div><div>Well, yes, I should add some routing logic before/during migration but it should work<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Things to note:<br>
- If you are using hosted-engine, it will further complicate things for you,<br>
I'm not sure if and how can one change the H.E. IP.<br></blockquote><div><br></div><div>Yep, I'm with HE. Does anyone know if HE engine can be changed?<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- If you are using an IP-based storage that is accessed via the same subnet,<br>
you need to ensure it is still accessible with the same name/IP from the<br>
new subnet.<br></blockquote><div><br></div><div>Luckily storage is already on another vlan/network<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you are only making this change so you can run more VMs, you can<br>
consider adding the new subnet as a new VLAN/physical LAN to the<br>
existing hosts, and keep using old /24 subnet for ovirtmgmt. It is a<br>
good idea to separate ovirtmgmt traffic from other traffic anyway...<br></blockquote></div><br></div><div class="gmail_extra">Well I have a mix of physical hosts (excluding oVirt cluster obviously) and VM that are all on the same network right now, which is the ovirtmgmt network too, and I don't want to have special routing rules only for VMs.<br><br></div><div class="gmail_extra">Thanks for the tips!<br><br></div><div class="gmail_extra">-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Davide Ferrari<br></div>Senior Systems Engineer<br></div></div>
</div></div>