Troubles after resizing the iscsi storage.
Hi, I just have 1TB iscsi storage with virtual machine with several disks. After shutdown the vm I just detached storage and removed from the cluster and ovirt totally. 1) Then on the target resized the exported volume to 13TB, 2) iscsiadm -m node -l on the host I resized iscsiadm -m node -l pvresize /dev/mapper/..... iscsiadm -m node -u After importing back to the ovirt over the gui, I can see the vm is in the import field but I cannot see separate disks Importing failing in the stage "Executing". are there way to fix it? On the host with "lvs" I can see the disks are there. thanks, Arman.
On Mon, Feb 20, 2017 at 11:54 AM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Hi, I just have 1TB iscsi storage with virtual machine with several disks. After shutdown the vm I just detached storage and removed from the cluster and ovirt totally. 1) Then on the target resized the exported volume to 13TB, 2) iscsiadm -m node -l on the host I resized iscsiadm -m node -l pvresize /dev/mapper/..... iscsiadm -m node -u
After importing back to the ovirt over the gui, I can see the vm is in the import field but I cannot see separate disks Importing failing in the stage "Executing".
are there way to fix it?
On the host with "lvs" I can see the disks are there.
Hi Arman, You don't need to remove storage from ovirt to resize a LUN, and you don't need to resize the pv, we can do this for you. To resize a LUN: 1. Resize the LUN on the storage server 2. Open the "manage domain", dialog 3. Select the LUN and click the "resize" button in the table (we should detect the new size and display button suggesting to add 11T) 4. Click "OK" The system will make sure all hosts see the new size of the LUN, and then it will resize the PV for you, and update engine database with the new LUN size. Now, in your case, we don't have any information about the issue, but if you restart vdsm on the SPM host your issue may be resolved. If not, please attach engine and vdsm logs. Nir
Thank you Nir for the suggestion, but unfortunately I cannot find the resize button at all... :( Shout be the storage in maintenance or in use? On Mon, Feb 20, 2017 at 10:07 PM, Nir Soffer <nsoffer@redhat.com> wrote:
On Mon, Feb 20, 2017 at 11:54 AM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Hi, I just have 1TB iscsi storage with virtual machine with several disks. After shutdown the vm I just detached storage and removed from the cluster and ovirt totally. 1) Then on the target resized the exported volume to 13TB, 2) iscsiadm -m node -l on the host I resized iscsiadm -m node -l pvresize /dev/mapper/..... iscsiadm -m node -u
After importing back to the ovirt over the gui, I can see the vm is in the import field but I cannot see separate disks Importing failing in the stage "Executing".
are there way to fix it?
On the host with "lvs" I can see the disks are there.
Hi Arman,
You don't need to remove storage from ovirt to resize a LUN, and you don't need to resize the pv, we can do this for you.
To resize a LUN:
1. Resize the LUN on the storage server 2. Open the "manage domain", dialog 3. Select the LUN and click the "resize" button in the table (we should detect the new size and display button suggesting to add 11T) 4. Click "OK"
The system will make sure all hosts see the new size of the LUN, and then it will resize the PV for you, and update engine database with the new LUN size.
Now, in your case, we don't have any information about the issue, but if you restart vdsm on the SPM host your issue may be resolved.
If not, please attach engine and vdsm logs.
Nir
I found in my vdsm.log something like this what does it means?? 2017-02-21 14:12:17,719 INFO (upgrade/995d385) [storage.StorageDomain] Resource namespace 03_lvm_995d3855-70a0-49aa-9370-65c5139bd129 already registered (blockSD:988) 2017-02-21 14:12:17,777 ERROR (upgrade/995d385) [storage.StoragePool] Unhandled exception (utils:371) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 368, in wrapper return f(*a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 180, in run return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/share/vdsm/storage/sp.py", line 232, in _upgradePoolDomain self._finalizePoolUpgradeIfNeeded() File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 77, in wrapper raise SecureError("Secured object is not in safe state") SecureError: Secured object is not in safe state 2017-02-21 14:12:17,822 INFO (tasks/4) [storage.ThreadPool.WorkerThread] FINISH task 9a5fc120-fd33-48fb-968a-06824a178e4f (threadPool:210) 2017-02-21 14:12:19,202 INFO (jsonrpc/5) [dispatcher] Run and protect: getTaskStatus(taskID=u'9a5fc120-fd33-48fb-968a-06824a178e4f', spUUID=None, options=None) (logUtils:49) 2017-02-21 14:12:19,202 INFO (jsonrpc/5) [dispatcher] Run and protect: getTaskStatus, Return response: {'taskStatus': {'code': 0, 'message': '1 jobs completed successfully', 'taskState': 'finished', 'taskResult': 'success', 'taskID': '9a5fc120-fd33-48fb-968a-06824a178e4f'}} (logUtils:52) On Tue, Feb 21, 2017 at 3:06 PM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Thank you Nir for the suggestion, but unfortunately I cannot find the resize button at all... :( Shout be the storage in maintenance or in use?
On Mon, Feb 20, 2017 at 10:07 PM, Nir Soffer <nsoffer@redhat.com> wrote:
On Mon, Feb 20, 2017 at 11:54 AM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Hi, I just have 1TB iscsi storage with virtual machine with several disks. After shutdown the vm I just detached storage and removed from the cluster and ovirt totally. 1) Then on the target resized the exported volume to 13TB, 2) iscsiadm -m node -l on the host I resized iscsiadm -m node -l pvresize /dev/mapper/..... iscsiadm -m node -u
After importing back to the ovirt over the gui, I can see the vm is in the import field but I cannot see separate disks Importing failing in the stage "Executing".
are there way to fix it?
On the host with "lvs" I can see the disks are there.
Hi Arman,
You don't need to remove storage from ovirt to resize a LUN, and you don't need to resize the pv, we can do this for you.
To resize a LUN:
1. Resize the LUN on the storage server 2. Open the "manage domain", dialog 3. Select the LUN and click the "resize" button in the table (we should detect the new size and display button suggesting to add 11T) 4. Click "OK"
The system will make sure all hosts see the new size of the LUN, and then it will resize the PV for you, and update engine database with the new LUN size.
Now, in your case, we don't have any information about the issue, but if you restart vdsm on the SPM host your issue may be resolved.
If not, please attach engine and vdsm logs.
Nir
On Tue, Feb 21, 2017 at 4:17 PM, Arman Khalatyan <arm2arm@gmail.com> wrote:
I found in my vdsm.log something like this what does it means??
2017-02-21 14:12:17,719 INFO (upgrade/995d385) [storage.StorageDomain] Resource namespace 03_lvm_995d3855-70a0-49aa-9370-65c5139bd129 already registered (blockSD:988) 2017-02-21 14:12:17,777 ERROR (upgrade/995d385) [storage.StoragePool] Unhandled exception (utils:371) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 368, in wrapper return f(*a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 180, in run return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/share/vdsm/storage/sp.py", line 232, in _upgradePoolDomain self._finalizePoolUpgradeIfNeeded() File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 77, in wrapper raise SecureError("Secured object is not in safe state") SecureError: Secured object is not in safe state
This is a known issue during upgrade domain flow, It should be harmless and not related to your issue.
2017-02-21 14:12:17,822 INFO (tasks/4) [storage.ThreadPool.WorkerThread] FINISH task 9a5fc120-fd33-48fb-968a-06824a178e4f (threadPool:210) 2017-02-21 14:12:19,202 INFO (jsonrpc/5) [dispatcher] Run and protect: getTaskStatus(taskID=u'9a5fc120-fd33-48fb-968a-06824a178e4f', spUUID=None, options=None) (logUtils:49) 2017-02-21 14:12:19,202 INFO (jsonrpc/5) [dispatcher] Run and protect: getTaskStatus, Return response: {'taskStatus': {'code': 0, 'message': '1 jobs completed successfully', 'taskState': 'finished', 'taskResult': 'success', 'taskID': '9a5fc120-fd33-48fb-968a-06824a178e4f'}} (logUtils:52)
On Tue, Feb 21, 2017 at 3:06 PM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Thank you Nir for the suggestion, but unfortunately I cannot find the resize button at all... :( Shout be the storage in maintenance or in use?
The resize button should be in the "Additional size" column when a LUN can be resized. Vdsm reports the size of each LUN and the size of the PV. If the LUN and the PV can be resized you should see the button. Nir
On Mon, Feb 20, 2017 at 10:07 PM, Nir Soffer <nsoffer@redhat.com> wrote:
On Mon, Feb 20, 2017 at 11:54 AM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Hi, I just have 1TB iscsi storage with virtual machine with several disks. After shutdown the vm I just detached storage and removed from the cluster and ovirt totally. 1) Then on the target resized the exported volume to 13TB, 2) iscsiadm -m node -l on the host I resized iscsiadm -m node -l pvresize /dev/mapper/..... iscsiadm -m node -u
After importing back to the ovirt over the gui, I can see the vm is in the import field but I cannot see separate disks Importing failing in the stage "Executing".
are there way to fix it?
On the host with "lvs" I can see the disks are there.
Hi Arman,
You don't need to remove storage from ovirt to resize a LUN, and you don't need to resize the pv, we can do this for you.
To resize a LUN:
1. Resize the LUN on the storage server 2. Open the "manage domain", dialog 3. Select the LUN and click the "resize" button in the table (we should detect the new size and display button suggesting to add 11T) 4. Click "OK"
The system will make sure all hosts see the new size of the LUN, and then it will resize the PV for you, and update engine database with the new LUN size.
Now, in your case, we don't have any information about the issue, but if you restart vdsm on the SPM host your issue may be resolved.
If not, please attach engine and vdsm logs.
Nir
On Tue, Feb 21, 2017 at 4:46 PM, Nir Soffer <nsoffer@redhat.com> wrote:
The resize button should be in the "Additional size" column when a LUN can be resized.
Vdsm reports the size of each LUN and the size of the PV. If the LUN and the PV can be resized you should see the button.
Nir
Perhaps he can select the storage domain in storage tab and "Scan Disks" to induce an iscsi rescan on hosts and then in manage domain see this additional column? Just a guess... Gianluca
On Tue, Feb 21, 2017 at 5:57 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, Feb 21, 2017 at 4:46 PM, Nir Soffer <nsoffer@redhat.com> wrote:
The resize button should be in the "Additional size" column when a LUN can be resized.
Vdsm reports the size of each LUN and the size of the PV. If the LUN and the PV can be resized you should see the button.
Nir
Perhaps he can select the storage domain in storage tab and "Scan Disks" to induce an iscsi rescan on hosts and then in manage domain see this additional column?
I don't know what "scan disks", does, but it is not required. When you open the "new/manage domain" dialog we fetch the device list from vdsm (getDeviceList) and this perform all the steps needed to detect resized devices. Nir
Here is the feature page : http://www.ovirt.org/develop/release-management/features/storage/lun-resize/ On Tue, Feb 21, 2017 at 6:32 PM, Nir Soffer <nsoffer@redhat.com> wrote:
On Tue, Feb 21, 2017 at 5:57 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, Feb 21, 2017 at 4:46 PM, Nir Soffer <nsoffer@redhat.com> wrote:
The resize button should be in the "Additional size" column when a LUN can be resized.
Vdsm reports the size of each LUN and the size of the PV. If the LUN and the PV can be resized you should see the button.
Nir
Perhaps he can select the storage domain in storage tab and "Scan Disks" to induce an iscsi rescan on hosts and then in manage domain see this additional column?
I don't know what "scan disks", does, but it is not required.
When you open the "new/manage domain" dialog we fetch the device list from vdsm (getDeviceList) and this perform all the steps needed to detect resized devices.
Nir _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I couldn't see what version of oVirt but I think the LUN resize function was introduced in 3.6. On Tue, Feb 21, 2017 at 10:06 PM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Thank you Nir for the suggestion, but unfortunately I cannot find the resize button at all... :( Shout be the storage in maintenance or in use?
On Mon, Feb 20, 2017 at 10:07 PM, Nir Soffer <nsoffer@redhat.com> wrote:
On Mon, Feb 20, 2017 at 11:54 AM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Hi, I just have 1TB iscsi storage with virtual machine with several disks. After shutdown the vm I just detached storage and removed from the cluster and ovirt totally. 1) Then on the target resized the exported volume to 13TB, 2) iscsiadm -m node -l on the host I resized iscsiadm -m node -l pvresize /dev/mapper/..... iscsiadm -m node -u
After importing back to the ovirt over the gui, I can see the vm is in the import field but I cannot see separate disks Importing failing in the stage "Executing".
are there way to fix it?
On the host with "lvs" I can see the disks are there.
Hi Arman,
You don't need to remove storage from ovirt to resize a LUN, and you don't need to resize the pv, we can do this for you.
To resize a LUN:
1. Resize the LUN on the storage server 2. Open the "manage domain", dialog 3. Select the LUN and click the "resize" button in the table (we should detect the new size and display button suggesting to add 11T) 4. Click "OK"
The system will make sure all hosts see the new size of the LUN, and then it will resize the PV for you, and update engine database with the new LUN size.
Now, in your case, we don't have any information about the issue, but if you restart vdsm on the SPM host your issue may be resolved.
If not, please attach engine and vdsm logs.
Nir
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Yes, it was introduced in 3.6 On Wed, Feb 22, 2017 at 10:16 AM, Colin Coe <colin.coe@gmail.com> wrote:
I couldn't see what version of oVirt but I think the LUN resize function was introduced in 3.6.
On Tue, Feb 21, 2017 at 10:06 PM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Thank you Nir for the suggestion, but unfortunately I cannot find the resize button at all... :( Shout be the storage in maintenance or in use?
On Mon, Feb 20, 2017 at 10:07 PM, Nir Soffer <nsoffer@redhat.com> wrote:
On Mon, Feb 20, 2017 at 11:54 AM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Hi, I just have 1TB iscsi storage with virtual machine with several disks. After shutdown the vm I just detached storage and removed from the cluster and ovirt totally. 1) Then on the target resized the exported volume to 13TB, 2) iscsiadm -m node -l on the host I resized iscsiadm -m node -l pvresize /dev/mapper/..... iscsiadm -m node -u
After importing back to the ovirt over the gui, I can see the vm is in the import field but I cannot see separate disks Importing failing in the stage "Executing".
are there way to fix it?
On the host with "lvs" I can see the disks are there.
Hi Arman,
You don't need to remove storage from ovirt to resize a LUN, and you don't need to resize the pv, we can do this for you.
To resize a LUN:
1. Resize the LUN on the storage server 2. Open the "manage domain", dialog 3. Select the LUN and click the "resize" button in the table (we should detect the new size and display button suggesting to add 11T) 4. Click "OK"
The system will make sure all hosts see the new size of the LUN, and then it will resize the PV for you, and update engine database with the new LUN size.
Now, in your case, we don't have any information about the issue, but if you restart vdsm on the SPM host your issue may be resolved.
If not, please attach engine and vdsm logs.
Nir
_______________________________________________ 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
Ok Thanks for the hints. After rebooting SPM host and re-importing the storage the resize button is there, but the disks inside storage still invisible. with lsblk I can see them but not over the ovirt. The rescan disks and initiation of OVF_STORE update does not change the situation. I can even new created disks, but the old disks are not visible. On Wed, Feb 22, 2017 at 9:28 AM, Fred Rolland <frolland@redhat.com> wrote:
Yes, it was introduced in 3.6
On Wed, Feb 22, 2017 at 10:16 AM, Colin Coe <colin.coe@gmail.com> wrote:
I couldn't see what version of oVirt but I think the LUN resize function was introduced in 3.6.
On Tue, Feb 21, 2017 at 10:06 PM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Thank you Nir for the suggestion, but unfortunately I cannot find the resize button at all... :( Shout be the storage in maintenance or in use?
On Mon, Feb 20, 2017 at 10:07 PM, Nir Soffer <nsoffer@redhat.com> wrote:
On Mon, Feb 20, 2017 at 11:54 AM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Hi, I just have 1TB iscsi storage with virtual machine with several disks. After shutdown the vm I just detached storage and removed from the cluster and ovirt totally. 1) Then on the target resized the exported volume to 13TB, 2) iscsiadm -m node -l on the host I resized iscsiadm -m node -l pvresize /dev/mapper/..... iscsiadm -m node -u
After importing back to the ovirt over the gui, I can see the vm is in the import field but I cannot see separate disks Importing failing in the stage "Executing".
are there way to fix it?
On the host with "lvs" I can see the disks are there.
Hi Arman,
You don't need to remove storage from ovirt to resize a LUN, and you don't need to resize the pv, we can do this for you.
To resize a LUN:
1. Resize the LUN on the storage server 2. Open the "manage domain", dialog 3. Select the LUN and click the "resize" button in the table (we should detect the new size and display button suggesting to add 11T) 4. Click "OK"
The system will make sure all hosts see the new size of the LUN, and then it will resize the PV for you, and update engine database with the new LUN size.
Now, in your case, we don't have any information about the issue, but if you restart vdsm on the SPM host your issue may be resolved.
If not, please attach engine and vdsm logs.
Nir
_______________________________________________ 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
On Wed, Feb 22, 2017 at 11:44 AM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Ok Thanks for the hints. After rebooting SPM host and re-importing the storage the resize button is there, but the disks inside storage still invisible. with lsblk I can see them but not over the ovirt. The rescan disks and initiation of OVF_STORE update does not change the situation. I can even new created disks, but the old disks are not visible.
Can you share the output of: lsblk pvs vgs lvs
On Wed, Feb 22, 2017 at 9:28 AM, Fred Rolland <frolland@redhat.com> wrote:
Yes, it was introduced in 3.6
On Wed, Feb 22, 2017 at 10:16 AM, Colin Coe <colin.coe@gmail.com> wrote:
I couldn't see what version of oVirt but I think the LUN resize function was introduced in 3.6.
On Tue, Feb 21, 2017 at 10:06 PM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Thank you Nir for the suggestion, but unfortunately I cannot find the resize button at all... :( Shout be the storage in maintenance or in use?
On Mon, Feb 20, 2017 at 10:07 PM, Nir Soffer <nsoffer@redhat.com> wrote:
On Mon, Feb 20, 2017 at 11:54 AM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Hi, I just have 1TB iscsi storage with virtual machine with several disks. After shutdown the vm I just detached storage and removed from the cluster and ovirt totally. 1) Then on the target resized the exported volume to 13TB, 2) iscsiadm -m node -l on the host I resized iscsiadm -m node -l pvresize /dev/mapper/..... iscsiadm -m node -u
After importing back to the ovirt over the gui, I can see the vm is in the import field but I cannot see separate disks Importing failing in the stage "Executing".
are there way to fix it?
On the host with "lvs" I can see the disks are there.
Hi Arman,
You don't need to remove storage from ovirt to resize a LUN, and you don't need to resize the pv, we can do this for you.
To resize a LUN:
1. Resize the LUN on the storage server 2. Open the "manage domain", dialog 3. Select the LUN and click the "resize" button in the table (we should detect the new size and display button suggesting to add 11T) 4. Click "OK"
The system will make sure all hosts see the new size of the LUN, and then it will resize the PV for you, and update engine database with the new LUN size.
Now, in your case, we don't have any information about the issue, but if you restart vdsm on the SPM host your issue may be resolved.
If not, please attach engine and vdsm logs.
Nir
_______________________________________________ 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
Sure, please check the gists: https://gist.github.com/arm2arm/9ab05bc3f359ea7ce59503446efb0740 BTW, I have seen some hints in the engine.log something is wrong by rescan disks. On Wed, Feb 22, 2017 at 11:50 AM, Nir Soffer <nsoffer@redhat.com> wrote:
On Wed, Feb 22, 2017 at 11:44 AM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Ok Thanks for the hints. After rebooting SPM host and re-importing the storage the resize button is there, but the disks inside storage still invisible. with lsblk I can see them but not over the ovirt. The rescan disks and initiation of OVF_STORE update does not change the situation. I can even new created disks, but the old disks are not visible.
Can you share the output of:
lsblk pvs vgs lvs
On Wed, Feb 22, 2017 at 9:28 AM, Fred Rolland <frolland@redhat.com> wrote:
Yes, it was introduced in 3.6
On Wed, Feb 22, 2017 at 10:16 AM, Colin Coe <colin.coe@gmail.com> wrote:
I couldn't see what version of oVirt but I think the LUN resize function was introduced in 3.6.
On Tue, Feb 21, 2017 at 10:06 PM, Arman Khalatyan <arm2arm@gmail.com> wrote:
Thank you Nir for the suggestion, but unfortunately I cannot find the resize button at all... :( Shout be the storage in maintenance or in use?
On Mon, Feb 20, 2017 at 10:07 PM, Nir Soffer <nsoffer@redhat.com> wrote:
On Mon, Feb 20, 2017 at 11:54 AM, Arman Khalatyan <arm2arm@gmail.com> wrote:
> Hi, > I just have 1TB iscsi storage with virtual machine with several > disks. > After shutdown the vm I just detached storage and removed from the > cluster and ovirt totally. > 1) Then on the target resized the exported volume to 13TB, > 2) iscsiadm -m node -l on the host I resized > iscsiadm -m node -l > pvresize /dev/mapper/..... > iscsiadm -m node -u > > After importing back to the ovirt over the gui, I can see the vm is > in the import field but I cannot see separate disks > Importing failing in the stage "Executing". > are there way to fix it? > On the host with "lvs" I can see the disks are there. >
Hi Arman,
You don't need to remove storage from ovirt to resize a LUN, and you don't need to resize the pv, we can do this for you.
To resize a LUN:
1. Resize the LUN on the storage server 2. Open the "manage domain", dialog 3. Select the LUN and click the "resize" button in the table (we should detect the new size and display button suggesting to add 11T) 4. Click "OK"
The system will make sure all hosts see the new size of the LUN, and then it will resize the PV for you, and update engine database with the new LUN size.
Now, in your case, we don't have any information about the issue, but if you restart vdsm on the SPM host your issue may be resolved.
If not, please attach engine and vdsm logs.
Nir
_______________________________________________ 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
participants (5)
-
Arman Khalatyan -
Colin Coe -
Fred Rolland -
Gianluca Cecchi -
Nir Soffer