Re: [Users] Storage server
What exactly did you do?
If you've changed the iSCSI storage connection, please check on the hosts if
they have an open iSCSI session with the storage server.
Run on both the active and the problematic hosts:
iscsiadm -m session
Check if there is any difference between them regarding the sessions they have
with the storage. If they don't have the same sessions, try to rescan the
targets and to login to them with 'iscsiadm' commands:
For discover the target:
iscsiadm -m discover -t st -p --discover
To login to the target:
iscsiadm -m node -l
Run 'multipath -ll' to verify which LUNs they are connected to.
- Original Message -
From: "Koen Vanoppen"
To: users@ovirt.org
Sent: Thursday, February 6, 2014 4:44:05 PM
Subject: Re: [Users] Storage server
Damn...
I have 4 hosts in my domain. One host came back up succesfully after changing
the ip. FOr the rest of the 3 hosts in the domain, they just won't come up. I
tried everythin (I think). I removed the hosts from ovirt. Reinstalled the host
rebooted the hosts. I have no further Idea's... THis is the error log:
2014-02-06 15:36:00,261 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(pool-6-thread-43) FINISH, ConnectStorageServerVDSCommand, return:
{f3451e53-68ba-4c40-95ad-abe11ed975ff=0}, log id: 4f691c55
2014-02-06 15:36:00,264 INFO
[org.ovirt.engine.core.bll.storage.ConnectDomainToStorageCommand]
(DefaultQuartzScheduler_Worker-98) ConnectDomainToStorage. After Connect all
hosts to pool. Time:2/6/14 3:36 PM
2014-02-06 15:36:03,309 INFO [org.ovirt.engine.core.bll.InstallerMessages]
(VdsDeploy) Installation soyuz.brusselsairport.aero : Stage: Misc configuration
2014-02-06 15:36:03,339 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1,
Message: Installing Host soyuz. Stage: Misc configuration.
2014-02-06 15:36:03,339 INFO [org.ovirt.engine.core.bll.InstallerMessages]
(VdsDeploy) Installation soyuz.brusselsairport.aero : Setting time
2014-02-06 15:36:03,359 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1,
Message: Installing Host soyuz. Setting time.
2014-02-06 15:36:07,118 INFO [org.ovirt.engine.core.bll.InstallerMessages]
(VdsDeploy) Installation soyuz.brusselsairport.aero : Enrolling certificate
2014-02-06 15:36:07,145 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1,
Message: Installing Host soyuz. Enrolling certificate.
2014-02-06 15:36:08,306 INFO [org.ovirt.engine.core.bll.InstallerMessages]
(VdsDeploy) Installation soyuz.brusselsairport.aero : Stage: Transaction commit
2014-02-06 15:36:08,324 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1,
Message: Installing Host soyuz. Stage: Transaction commit.
2014-02-06 15:36:08,373 INFO [org.ovirt.engine.core.bll.InstallerMessages]
(VdsDeploy) Installation soyuz.brusselsairport.aero : Stage: Closing up
2014-02-06 15:36:08,392 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1,
Message: Installing Host soyuz. Stage: Closing up.
2014-02-06 15:36:09,371 INFO [org.ovirt.engine.core.bll.InstallerMessages]
(VdsDeploy) Installation soyuz.brusselsairport.aero : Starting vdsm
2014-02-06 15:36:09,389 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1,
Message: Installing Host soyuz. Starting vdsm.
2014-02-06 15:36:14,409 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand]
(pool-6-thread-45) Command
org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand return
value
StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=304, mMessage=Cannot
find master domain: 'spUUID=5849b030-626e-47cb-ad90-3ce782d831b3,
msdUUID=f3fd055b-2764-44ed-9d77-81bd58984842']]
2014-02-06 15:36:14,418 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand]
(pool-6-thread-45) HostName = progress
2014-02-06 15:36:14,421 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand]
(pool-6-thread-45) Command ConnectStoragePoolVDS execution failed. Exception:
IRSNoMasterDomainException: IRSGenericException: IRSErrorException:
IRSNoMasterDomainException: Cannot find master domain:
'spUUID=5849b030-626e-47cb-ad90-3ce782d831b3,
msdUUID=f3fd055b-2764-44ed-9d77-81bd58984842'
2014-02-06 15:36:14,428 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand]
(pool-6-t
Re: [Users] Storage server
<mailto:vanoppen.koen@gmail.__com >> <mailto:vanoppen.k...@gmail.com>> >> <mailto:vanoppen.koen@gmail. >> <mailto:vanoppen.koen@gmail.>com >> <mailto:vanoppen.koen@gmail.__com >> <mailto:vanoppen.k...@gmail.com>>>> >> To: "Elad Ben Aharon" > <mailto:ebena...@redhat.com> >> <mailto:ebena...@redhat.com >> <mailto:ebena...@redhat.com>> >> <mailto:ebena...@redhat.com >> <mailto:ebena...@redhat.com> >> <mailto:ebena...@redhat.com >> <mailto:ebena...@redhat.com>>>>__, users@ovirt.org >> <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>>> >> >> 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" >> mailto:ebena...@redhat.com> >> <mailto:ebena...@redhat.com <mailto:ebena...@redhat.com>> >> <mailto:ebena...@redhat.com >> <mailto:ebena...@redhat.com> >> >> <mailto:ebena...@redhat.com >> <mailto:ebena...@redhat.com>>>> 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" >> mailto:vanoppen.k...@gmail.com> >> <mailto:vanoppen.koen@gmail.__com >> <mailto:vanoppen.k...@gmail.com>> >> <mailto:vanoppen.koen@gmail. >> <mailto:vanoppen.koen@gmail.>com >> <mailto:vanoppen.koen@gmail.__com >> <mailto:vanoppen.k...@gmail.com>>>> >> To: users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>>> >> Sent: Tuesday, February 4, 2014 2:32:46 >> PM >> Subject: [Users] Storage server >> >> Dear All, >> >>
Re: [Users] Storage server
<mailto:vanoppen.koen@gmail.__com >> <mailto:vanoppen.k...@gmail.com>> >> <mailto:vanoppen.koen@gmail. >> <mailto:vanoppen.koen@gmail.>com >> <mailto:vanoppen.koen@gmail.__com >> <mailto:vanoppen.k...@gmail.com>>>> >> To: "Elad Ben Aharon" > <mailto:ebena...@redhat.com> >> <mailto:ebena...@redhat.com <mailto:ebena...@redhat.com>> >> <mailto:ebena...@redhat.com >> <mailto:ebena...@redhat.com> >> <mailto:ebena...@redhat.com >> <mailto:ebena...@redhat.com>>>>__, users@ovirt.org >> <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>>> >> >> 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" >> mailto:ebena...@redhat.com> >> <mailto:ebena...@redhat.com <mailto:ebena...@redhat.com>> >> <mailto:ebena...@redhat.com >> <mailto:ebena...@redhat.com> >> >> <mailto:ebena...@redhat.com >> <mailto:ebena...@redhat.com>>>> 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" >> mailto:vanoppen.k...@gmail.com> >> <mailto:vanoppen.koen@gmail.__com >> <mailto:vanoppen.k...@gmail.com>> >> <mailto:vanoppen.koen@gmail. >> <mailto:vanoppen.koen@gmail.>com >> <mailto:vanoppen.koen@gmail.__com >> <mailto:vanoppen.k...@gmail.com>>>> >> To: users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>>> >> 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 >>
Re: [Users] Storage server
On 02/06/2014 12:54 PM, Koen Vanoppen wrote:
What if I remove the "old ip" storage domains and import the same iscsi
luns with the new IP, would that work?
removing a domain *deletes* all disks/vms, other than that...
(we are working on ability to detach/attach domains post 3.4)
Kind Regards
2014-02-06 Koen Vanoppen mailto:vanoppen.k...@gmail.com>>:
Can I change the storagedomain ip from the ovirt-shell?
Thanks in advance
2014-02-06 Itamar Heim mailto:ih...@redhat.com>>:
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 mailto:ih...@redhat.com> <mailto:ih...@redhat.com
<mailto:ih...@redhat.com>>>:
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>
<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"
mailto:ih...@redhat.com>
<mailto:ih...@redhat.com <mailto:ih...@redhat.com>>
<mailto:ih...@redhat.com <mailto:ih...@redhat.com>
<mailto:ih...@redhat.com <mailto:ih...@redhat.com>>>> 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"
mailto:vanoppen.k...@gmail.com>
<mailto:vanoppen.koen@gmail.__com
<mailto:vanoppen.k...@gmail.com>>
<mailto:vanoppen.koen@gmail.
<mailto:vanoppen.koen@gmail.>com
<mailto:vanoppen.koen@gmail.__com
<mailto:vanoppen.k...@gmail.com>>>>
To: "Elad Ben Aharon" mailto:ebena...@redhat.com>
<mailto:ebena...@redhat.com
<mailto:ebena...@redhat.com>>
<mailto:ebena...@redhat.com
<mailto:ebena...@redhat.com>
<mailto:ebena...@redhat.com
<mailto:ebena...@redhat.com>>>>__, users@ovirt.org
<mailto:users@ovirt.org>
<mailto:users@ovirt.org <mailto:users@ovirt.org>>
<mailto:users@ovirt.org
<mailto:users@ovirt.org> <mailto:users@ovirt.org
<mailto:users@ovirt.org>>>
Sent: Tuesday, February 4, 2014 2:57:57 PM
Subject: Re: [Users] Storage
Re: [Users] Storage server
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 : > Can I change the storagedomain ip from the ovirt-shell? > Thanks in advance > > > 2014-02-06 Itamar Heim : > > 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 mailto:ih...@redhat.com>>: >>> >>> >>> 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" >> <mailto:ih...@redhat.com> >>> <mailto:ih...@redhat.com <mailto:ih...@redhat.com>>> 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" >> <mailto:vanoppen.k...@gmail.com> >>> <mailto:vanoppen.koen@gmail.__com >>> <mailto:vanoppen.k...@gmail.com>>> >>> To: "Elad Ben Aharon" >> <mailto:ebena...@redhat.com> >>> <mailto:ebena...@redhat.com >>> <mailto:ebena...@redhat.com>>>, users@ovirt.org >>> <mailto:users@ovirt.org> >>> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >>> >>> 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" >>> mailto:ebena...@redhat.com> >>> <mailto:ebena...@redhat.com >>> >>> <mailto:ebena...@redhat.com>>> wrote: >>> >>>
Re: [Users] Storage server
On 02/06/2014 12:43 PM, Koen Vanoppen wrote:
Can I change the storagedomain ip from the ovirt-shell?
Thanks in advance
anything in the api should work from sdk and shell.
while this falls in the storage domain, juan may know as well?
2014-02-06 Itamar Heim mailto:ih...@redhat.com>>:
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 mailto:ih...@redhat.com> <mailto:ih...@redhat.com
<mailto:ih...@redhat.com>>>:
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>
<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" mailto:ih...@redhat.com>
<mailto:ih...@redhat.com <mailto:ih...@redhat.com>>
<mailto:ih...@redhat.com <mailto:ih...@redhat.com>
<mailto:ih...@redhat.com <mailto:ih...@redhat.com>>>> 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" mailto:vanoppen.k...@gmail.com>
<mailto:vanoppen.koen@gmail.__com
<mailto:vanoppen.k...@gmail.com>>
<mailto:vanoppen.koen@gmail.
<mailto:vanoppen.koen@gmail.>com
<mailto:vanoppen.koen@gmail.__com
<mailto:vanoppen.k...@gmail.com>>>>
To: "Elad Ben Aharon" mailto:ebena...@redhat.com>
<mailto:ebena...@redhat.com <mailto:ebena...@redhat.com>>
<mailto:ebena...@redhat.com
<mailto:ebena...@redhat.com>
<mailto:ebena...@redhat.com
<mailto:ebena...@redhat.com>>>>__, users@ovirt.org
<mailto:users@ovirt.org>
<mailto:users@ovirt.org <mailto:users@ovirt.org>>
<mailto:users@ovirt.org
<mailto:users@ovirt.org> <mailto:users@ovirt.org
<mailto:users@ovirt.org>>>
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
Re: [Users] Storage server
Can I change the storagedomain ip from the ovirt-shell? Thanks in advance 2014-02-06 Itamar Heim : > 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 mailto:ih...@redhat.com>>: >> >> >> 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" > <mailto:ih...@redhat.com> >> <mailto:ih...@redhat.com <mailto:ih...@redhat.com>>> 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" > <mailto:vanoppen.k...@gmail.com> >> <mailto:vanoppen.koen@gmail.__com >> <mailto:vanoppen.k...@gmail.com>>> >> To: "Elad Ben Aharon" > <mailto:ebena...@redhat.com> >> <mailto:ebena...@redhat.com >> <mailto:ebena...@redhat.com>>>, users@ovirt.org >> <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>> >> >> 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" >> mailto:ebena...@redhat.com> >> <mailto:ebena...@redhat.com >> >> <mailto:ebena...@redhat.com>>> 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 thei
Re: [Users] Storage server
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 Thanx! Kind regards, Koen On Feb 5, 2014 9:08 AM, "Itamar Heim" mailto:ih...@redhat.com>> 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" mailto:vanoppen.k...@gmail.com>> To: "Elad Ben Aharon" mailto:ebena...@redhat.com>>, users@ovirt.org <mailto:users@ovirt.org> 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" mailto:ebena...@redhat.com>> 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" mailto:vanoppen.k...@gmail.com>> To: users@ovirt.org <mailto:users@ovirt.org> 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 Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users> _ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users> ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Storage server
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" To: "Elad Ben Aharon" , users@ovirt.org 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" 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" To: users@ovirt.org 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 Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Storage server
OK, Thank you very much! Kind regards, Koen On Feb 4, 2014 3: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. > 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. > > > - Original Message - > From: "Koen Vanoppen" > To: "Elad Ben Aharon" , users@ovirt.org > 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" 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" > > To: users@ovirt.org > > 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 > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Storage server
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. 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. - Original Message - From: "Koen Vanoppen" To: "Elad Ben Aharon" , users@ovirt.org 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" 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" > To: users@ovirt.org > 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 > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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" 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" > To: users@ovirt.org > 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 > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Storage server
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" To: users@ovirt.org 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 Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[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 Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
