On Wed, Nov 14, 2018 at 4:39 PM Jacob Green <jgreen(a)aasteel.com&gt; wrote: > > I just have a few simple questions, have you migrated a fiber > channel storage domain from one ovirt environment to another? And how > did it go, did it just work aside from having to import all the vms and > configure their settings was it any more difficult than that? > > We want to migrate our fiber channel storage with VM's intact from an > oVirt 4.1 environment to a brand new oVirt 4.2 environment. Hello Jacob, we just did in our production environment using EMC VNX and EMC VPLEX as storage backends. We simply zoned the new servers' hba with the storage and on storage side we gave access to the same luns as the older setup. Once done this we stopped all the vms on source side (4.1), detached the storage domain and imported on the new one (4.2). Then, imported all the vms. Please note that you MUST detach from source BEFORE attaching on destination or you'll break everything. Nothing special required. The only simplification is using the same network names on both sides, so is easier to import. We didn't automate anything, but you can do it for sure with ansible. Luca -- "E' assurdo impiegare gli uomini di intelligenza eccellente per fare calcoli che potrebbero essere affidati a chiunque se si usassero delle macchine" Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) "Internet è la più grande biblioteca del mondo. Ma il problema è che i libri sono tutti sparsi sul pavimento" John Allen Paulos, Matematico (1945-vivente) Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , < lorenzetto.luca(a)gmail.com&gt; _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/HGFMMXGCSFP...

I migrate from ovirt 4.0.5 to 4.2.6. You Just need to present luns to new servers, restart all nodes to recognize all new disks,

the vms and thats all. 😋 Em qua, 14 de nov de 2018 16:52, Rogério Ceni Coelho < rogeriocenicoelho(a)gmail.com&gt; escreveu: > If you use Snapshot or clone on Storage side you can Migrate vms on many > steps .... Some vms each time... > > I use EMC VNX and EMC Unity and EMC Vplex. > > Good Luck !!!! > > Em qua, 14 de nov de 2018 às 15:27, Luca 'remix_tj' Lorenzetto < > lorenzetto.luca(a)gmail.com&gt; escreveu: > >> On Wed, Nov 14, 2018 at 4:39 PM Jacob Green <jgreen(a)aasteel.com&gt; wrote: >> > >> > I just have a few simple questions, have you migrated a fiber >> > channel storage domain from one ovirt environment to another? And how >> > did it go, did it just work aside from having to import all the vms and >> > configure their settings was it any more difficult than that? >> > >> > We want to migrate our fiber channel storage with VM's intact from an >> > oVirt 4.1 environment to a brand new oVirt 4.2 environment. >> >> Hello Jacob, >> >> we just did in our production environment using EMC VNX and EMC VPLEX >> as storage backends. We simply zoned the new servers' hba with the >> storage and on storage side we gave access to the same luns as the >> older setup. >> >> Once done this we stopped all the vms on source side (4.1), detached >> the storage domain and imported on the new one (4.2). Then, imported >> all the vms. >> >> Please note that you MUST detach from source BEFORE attaching on >> destination or you'll break everything. >> >> Nothing special required. The only simplification is using the same >> network names on both sides, so is easier to import. >> >> We didn't automate anything, but you can do it for sure with ansible. >> >> Luca >> -- >> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare >> calcoli che potrebbero essere affidati a chiunque se si usassero delle >> macchine" >> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) >> >> "Internet è la più grande biblioteca del mondo. >> Ma il problema è che i libri sono tutti sparsi sul pavimento" >> John Allen Paulos, Matematico (1945-vivente) >> >> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , < >> lorenzetto.luca(a)gmail.com&gt; >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HGFMMXGCSFP... >> > _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TGI46QI4MZN...

On Wed, Nov 14, 2018 at 4:39 PM Jacob Green <jgreen(a)aasteel.com&gt; wrote: > I just have a few simple questions, have you migrated a fiber > channel storage domain from one ovirt environment to another? And how > did it go, did it just work aside from having to import all the vms and > configure their settings was it any more difficult than that? > > We want to migrate our fiber channel storage with VM's intact from an > oVirt 4.1 environment to a brand new oVirt 4.2 environment. Hello Jacob, we just did in our production environment using EMC VNX and EMC VPLEX as storage backends. We simply zoned the new servers' hba with the storage and on storage side we gave access to the same luns as the older setup. Once done this we stopped all the vms on source side (4.1), detached the storage domain and imported on the new one (4.2). Then, imported all the vms. Please note that you MUST detach from source BEFORE attaching on destination or you'll break everything. Nothing special required. The only simplification is using the same network names on both sides, so is easier to import. We didn't automate anything, but you can do it for sure with ansible. Luca