What if I remove the "old ip" storage domains and import the same iscsi luns with the new IP, would that work?
Kind Regards 2014-02-06 Koen Vanoppen <[email protected]>: > Can I change the storagedomain ip from the ovirt-shell? > Thanks in advance > > > 2014-02-06 Itamar Heim <[email protected]>: > > On 02/06/2014 12:03 PM, Koen Vanoppen wrote: >> >>> Can I change the storagedomain ip from the ovirt-shell? >>> Thanks in advance >>> >> >> please reply to list, thanks >> >> >>> >>> 2014-02-06 Itamar Heim <[email protected] <mailto:[email protected]>>: >>> >>> >>> On 02/06/2014 05:16 AM, Koen Vanoppen wrote: >>> >>> It's not on DNS... The storage server in ovirt is on IP... So... >>> What >>> are my options in this case? >>> >>> >>> you would need to 'edit the connection'. since 3.3.1 this is >>> possible via the rest api without hacking the db: >>> http://www.ovirt.org/Features/__Manage_Storage_Connections >>> >>> <http://www.ovirt.org/Features/Manage_Storage_Connections> >>> >>> Thanx! >>> >>> Kind regards, >>> Koen >>> >>> On Feb 5, 2014 9:08 AM, "Itamar Heim" <[email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected] <mailto:[email protected]>>> wrote: >>> >>> On 02/04/2014 03:10 PM, Elad Ben Aharon wrote: >>> >>> Actually, the best way to do it would be to create >>> another >>> storage domain and migrate all the VMs's disks to it >>> (you can do >>> it while the VMs are running), then you won't suffer >>> from a down >>> time. >>> >>> >>> notice this will create a snapshot for your vms and may >>> change them >>> from raw to qcow. also, this not supported for shared disks. >>> >>> If you don't have the option to do so, the best way to >>> do it >>> would be to shut down the VMs, put the storage domain to >>> 'Maintenance' and then perform the storage server >>> network >>> change. When the connection to the storage is fixed, >>> activate >>> the domain and resume the VMs manually. >>> >>> >>> that's assuming the domain was added using dns and not ip >>> address, >>> and that the dns expiration/caching on all hosts will >>> notice the new >>> ip address. >>> >>> >>> >>> ----- Original Message ----- >>> From: "Koen Vanoppen" <[email protected] >>> <mailto:[email protected]> >>> <mailto:vanoppen.koen@gmail.__com >>> <mailto:[email protected]>>> >>> To: "Elad Ben Aharon" <[email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected] >>> <mailto:[email protected]>>>, [email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected] <mailto:[email protected]>> >>> >>> Sent: Tuesday, February 4, 2014 2:57:57 PM >>> Subject: Re: [Users] Storage server >>> >>> For the moment, nothing is going on. The change is >>> planned on >>> Thursday. So, >>> correct me if I'm wrong, you say that the fastest and >>> easiest >>> way is to >>> suspend all the machines, make the change of the >>> storage server, >>> rediscover >>> the iscsi server and then bring the vm's back up? >>> >>> Kind regards, >>> Koen >>> On Feb 4, 2014 1:47 PM, "Elad Ben Aharon" >>> <[email protected] <mailto:[email protected]> >>> <mailto:[email protected] >>> >>> <mailto:[email protected]>>> wrote: >>> >>> Hi, >>> >>> I suppose that those VMs are now in 'Paused' state, >>> correct >>> me if I'm >>> wrong. >>> After connectivity with storage comes back, all VMs >>> which >>> couldn't detect >>> their disks should be resumed from 'Paused' to 'Up' >>> state >>> automatically. It >>> shouldn't take them a long time to change their >>> state (a few >>> minutes). >>> >>> ----- Original Message ----- >>> From: "Koen Vanoppen" <[email protected] >>> <mailto:[email protected]> >>> <mailto:vanoppen.koen@gmail.__com >>> <mailto:[email protected]>>> >>> To: [email protected] <mailto:[email protected]> >>> <mailto:[email protected] <mailto:[email protected]>> >>> Sent: Tuesday, February 4, 2014 2:32:46 PM >>> Subject: [Users] Storage server >>> >>> Dear All, >>> >>> At work, the network guys have come to a discovery >>> that they >>> have made a >>> mistake in their network configuration... The >>> Storage server >>> that we use as >>> ISCSI target in oVirt, is in the wrong VLAN, so the >>> wrong IP >>> address... >>> >>> What is the best way to make sure that all of our >>> vms (40) >>> that are using >>> this scsi storage will come up again after the >>> storage >>> server has changed >>> his ip? >>> What are the best steps to be taken...? >>> We are using oVirt Engine Version: 3.3.1-2.el6 >>> >>> Kind Regards, >>> >>> Koen >>> >>> ___________________________________________________ >>> Users mailing list >>> [email protected] <mailto:[email protected]> <mailto:[email protected] >>> <mailto:[email protected]>> >>> http://lists.ovirt.org/____mailman/listinfo/users >>> <http://lists.ovirt.org/__mailman/listinfo/users> >>> <http://lists.ovirt.org/__mailman/listinfo/users >>> <http://lists.ovirt.org/mailman/listinfo/users>> >>> >>> ___________________________________________________ >>> Users mailing list >>> [email protected] <mailto:[email protected]> <mailto:[email protected] >>> <mailto:[email protected]>> >>> http://lists.ovirt.org/____mailman/listinfo/users >>> <http://lists.ovirt.org/__mailman/listinfo/users> >>> <http://lists.ovirt.org/__mailman/listinfo/users >>> <http://lists.ovirt.org/mailman/listinfo/users>> >>> >>> >>> >>> >>> >> >
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
