Any way to correlate a VM disk (e.g. /dev/vda) to the vdsm ovirt disk?
I want to correlate virtual disks back to their originating storage under ovirt. Is there any way to do this? e.g. (made up example) /dev/vda maps to ovirt disk disk1_vm serial 978e00a3-b4c9-4962-bc4f-ffc9267acdd8
Hi ccox, you can see the disk id mapping to device if you execute 'ls -l /dev/disk/by-id/' . Second way, and easier, is to make sure you have guest-agent installed on your guest virtual machine and using rest API you can run GET command: GET on .../api/vms/{vm_id}/disks You will see an attribute called "<logical_name>" . I hope that helps Thanks, Raz Tamir Red Hat Israel On Tue, Oct 6, 2015 at 11:07 PM, <ccox@endlessnow.com> wrote:
I want to correlate virtual disks back to their originating storage under ovirt. Is there any way to do this?
e.g. (made up example)
/dev/vda
maps to ovirt disk
disk1_vm serial 978e00a3-b4c9-4962-bc4f-ffc9267acdd8
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_985C56DB-ED80-4C7F-8DE8-9B251713BAA3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 You can also find the disk under the =E2=80=9CDisks=E2=80=9D tab in the = web gui, selecting it will yield the uuid of the virtual disk as ID in = the disk description panel.=20
On Oct 7, 2015, at 12:43 AM, Raz Tamir <ratamir@redhat.com> wrote: =20 Hi ccox, you can see the disk id mapping to device if you execute 'ls -l = /dev/disk/by-id/' . Second way, and easier, is to make sure you have guest-agent installed = on your guest virtual machine and using rest API you can run GET = command: GET on .../api/vms/{vm_id}/disks =20 You will see an attribute called "<logical_name>" . I hope that helps =20 =20 =20 Thanks, Raz Tamir Red Hat Israel =20 On Tue, Oct 6, 2015 at 11:07 PM, <ccox@endlessnow.com = <mailto:ccox@endlessnow.com>> wrote: I want to correlate virtual disks back to their originating storage = under ovirt. Is there any way to do this? =20 e.g. (made up example) =20 /dev/vda =20 maps to ovirt disk =20 disk1_vm serial 978e00a3-b4c9-4962-bc4f-ffc9267acdd8 =20 _______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users = <http://lists.ovirt.org/mailman/listinfo/users> =20 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_985C56DB-ED80-4C7F-8DE8-9B251713BAA3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D"">You can also find the disk under the =E2=80=9CDisks=E2=80=9D = tab in the web gui, selecting it will yield the uuid of the virtual disk = as ID in the disk description panel. <div class=3D""><br = class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On = Oct 7, 2015, at 12:43 AM, Raz Tamir <<a = href=3D"mailto:ratamir@redhat.com" class=3D"">ratamir@redhat.com</a>> = wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div = dir=3D"ltr" class=3D""><div class=3D"gmail_default" = style=3D"font-family:times new roman,serif;font-size:large">Hi = ccox,</div><div class=3D"gmail_default" style=3D"font-family:times new = roman,serif;font-size:large">you can see the disk id mapping to device = if you execute 'ls -l /dev/disk/by-id/' .</div><div = class=3D"gmail_default" style=3D"font-family:times new = roman,serif;font-size:large">Second way, and easier, is to make sure you = have guest-agent installed on your guest virtual machine and using rest = API you can run GET command:</div><div class=3D"gmail_default" = style=3D"font-family:times new roman,serif;font-size:large">GET on = .../api/vms/{vm_id}/disks</div><div class=3D"gmail_default" = style=3D"font-family:times new roman,serif;font-size:large"><br = class=3D""></div><div class=3D"gmail_default" style=3D"font-family:times = new roman,serif;font-size:large">You will see an attribute called = "<logical_name>" .</div><div class=3D"gmail_default" = style=3D"font-family:times new roman,serif;font-size:large">I hope that = helps</div></div><div class=3D"gmail_extra"><br clear=3D"all" = class=3D""><div class=3D""><div class=3D"gmail_signature"><div dir=3D"ltr"= class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div = class=3D""><div dir=3D"ltr" class=3D""><div class=3D""><div dir=3D"ltr" = class=3D""><font face=3D"times new roman, serif" size=3D"4" class=3D""><br= class=3D""></font></div><div dir=3D"ltr" class=3D""><font face=3D"times = new roman, serif" size=3D"4" class=3D""><br class=3D""></font></div><div = dir=3D"ltr" class=3D""><font face=3D"times new roman, serif" size=3D"4" = class=3D"">Thanks,</font><div class=3D""><font face=3D"times new roman, = serif" size=3D"4" class=3D"">Raz Tamir</font></div><div class=3D""><font = face=3D"times new roman, serif" size=3D"4" class=3D"">Red Hat = Israel</font></div></div></div></div></div></div></div></div></div></div> <br class=3D""><div class=3D"gmail_quote">On Tue, Oct 6, 2015 at 11:07 = PM, <span dir=3D"ltr" class=3D""><<a = href=3D"mailto:ccox@endlessnow.com" target=3D"_blank" = class=3D"">ccox@endlessnow.com</a>></span> wrote:<br = class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 = .8ex;border-left:1px #ccc solid;padding-left:1ex">I want to correlate = virtual disks back to their originating storage under<br class=3D""> ovirt. Is there any way to do this?<br class=3D""> <br class=3D""> e.g. (made up example)<br class=3D""> <br class=3D""> /dev/vda<br class=3D""> <br class=3D""> maps to ovirt disk<br class=3D""> <br class=3D""> disk1_vm serial 978e00a3-b4c9-4962-bc4f-ffc9267acdd8<br class=3D""> <br class=3D""> _______________________________________________<br class=3D""> Users mailing list<br class=3D""> <a href=3D"mailto:Users@ovirt.org" class=3D"">Users@ovirt.org</a><br = class=3D""> <a href=3D"http://lists.ovirt.org/mailman/listinfo/users" = rel=3D"noreferrer" target=3D"_blank" = class=3D"">http://lists.ovirt.org/mailman/listinfo/users</a><br = class=3D""> </blockquote></div><br class=3D""></div> _______________________________________________<br class=3D"">Users = mailing list<br class=3D""><a href=3D"mailto:Users@ovirt.org" = class=3D"">Users@ovirt.org</a><br = class=3D"">http://lists.ovirt.org/mailman/listinfo/users<br = class=3D""></div></blockquote></div><br class=3D""></div></body></html>= --Apple-Mail=_985C56DB-ED80-4C7F-8DE8-9B251713BAA3--
Hi ccox, you can see the disk id mapping to device if you execute 'ls -l /dev/disk/by-id/' . Second way, and easier, is to make sure you have guest-agent installed on your guest virtual machine and using rest API you can run GET command: GET on .../api/vms/{vm_id}/disks
You will see an attribute called "<logical_name>" . I hope that helps
should have said I'm running 3.4. I don't think there's a logical_name in that version. And by-id or by-uuid doesn't seem to match anything. Maybe this can't be done in 3.4?
You are right, there is no logical_name attr in disk object before 3.5 [1] [1] http://www.ovirt.org/Features/ReportGuestDisksLogicalDeviceName Thanks, Raz Tamir Red Hat Israel On Wed, Oct 7, 2015 at 6:49 PM, <ccox@endlessnow.com> wrote:
Hi ccox, you can see the disk id mapping to device if you execute 'ls -l /dev/disk/by-id/' . Second way, and easier, is to make sure you have guest-agent installed on your guest virtual machine and using rest API you can run GET command: GET on .../api/vms/{vm_id}/disks
You will see an attribute called "<logical_name>" . I hope that helps
should have said I'm running 3.4. I don't think there's a logical_name in that version. And by-id or by-uuid doesn't seem to match anything.
Maybe this can't be done in 3.4?
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Wed, Oct 7, 2015 at 6:49 PM, <ccox@endlessnow.com> wrote:
Hi ccox, you can see the disk id mapping to device if you execute 'ls -l /dev/disk/by-id/' . Second way, and easier, is to make sure you have guest-agent installed on your guest virtual machine and using rest API you can run GET command: GET on .../api/vms/{vm_id}/disks
You will see an attribute called "<logical_name>" . I hope that helps
should have said I'm running 3.4. I don't think there's a logical_name in that version. And by-id or by-uuid doesn't seem to match anything.
Maybe this can't be done in 3.4?
Can you share the ouput of: tree /dev/disk On the guest? And the output of pvscan --cache lvs -o vg_name,name,tags On the host? On the guest, the the disk serial number should be the first 20 characters of the disk uuid (I think it is the image uuid in vdsm terms, or disk uuid in engine terms). The image uuid should appear in a lv tag on the host, and the prefix of this uuid should be found on the guest. Can you describe why do you need this information? Nir
This is a cryptographically signed message in MIME format. --------------ms070607010005010406080300 Content-Type: multipart/mixed; boundary="------------090904070300050807040602" This is a multi-part message in MIME format. --------------090904070300050807040602 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable Hi, Dne 6.10.2015 v 22:07 ccox@endlessnow.com napsal(a):
I want to correlate virtual disks back to their originating storage und= er ovirt. Is there any way to do this?
e.g. (made up example)
/dev/vda
maps to ovirt disk
disk1_vm serial 978e00a3-b4c9-4962-bc4f-ffc9267acdd8
In oVirt there are two storage types - filesystem based (NFS, posix,=20 glusterfs - uses files for storing images) and block device based (FC,=20 iSCSI - uses lvm) If I understand correctly, you would like know where exactly is stored a = virtual disk. Right? All you know is on which storage domain is your virtual disk stored and=20 disk uuid (imgUUID)), right? My approach is this (I am using block device based FC stroage so my=20 virtual disks are stored as logical volumes). Probably there is much=20 easier way ;-) please correct me ssh to any host list storage domains (sdUUID) vdsClient -s 0 getImageDomainsList find your domain uuid by name vdsClient -s 0 getStorageDomainInfo sdUUID you will get also pool (spUUID) now you can search for volume(s) the image consists of getVolumesList sdUUID spUUID imgUUID you will get volUUID (one or more) now you can check volume info getVolumeInfo sdUUID spUUID imgUUID volUUID and also you can get volume path getVolumePath sdUUID spUUID imgUUID volUUID you will get something like /rhev/data-center/mnt/blockSD/088e7ed9-84c7-4fbd-a570-f37fa986a772/images= /be5c56de-6a22-4d1a-8579-f0f5d501d90c/0681822f-3ac8-473b-95ce-380f8ab4de0= 6 it is symlink which points to target block device it looks to me that on block devices the path is /dev/sdUUID/volUUID btw. I am using oVirt3.5... Cheers, Jiri
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------090904070300050807040602 Content-Type: text/x-vcard; charset=utf-8; name="jiri_slezka.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="jiri_slezka.vcf" begin:vcard fn;quoted-printable:Ing. Ji=3DC5=3D99=3DC3=3DAD Sl=3DC3=3DA9=3DC5=3DBEka n;quoted-printable;quoted-printable:Sl=3DC3=3DA9=3DC5=3DBEka;Ji=3DC5=3D99= =3DC3=3DAD org;quoted-printable;quoted-printable:Slezsk=3DC3=3DA1 univerzita v Opav=3D= C4=3D9B;Centrum informa=3DC4=3D8Dn=3DC3=3DADch technologi=3DC3=3DAD adr;quoted-printable;quoted-printable:Na Rybn=3DC3=3DAD=3DC4=3D8Dku 1;;CI= T, Slezsk=3DC3=3DA1 univerzita v Opav=3DC4=3D9B;Opava;;74601;Czech Republ= ic email;internet:jiri.slezka@slu.cz title;quoted-printable:Spr=3DC3=3DA1vce s=3DC3=3DADt=3DC4=3D9B a aplikac=3D= C3=3DAD tel;work:+420 553 684 696 x-mozilla-html:FALSE url:http://www.slu.cz version:2.1 end:vcard --------------090904070300050807040602-- --------------ms070607010005010406080300 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: Elektronicky podpis S/MIME MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC CWcwggScMIIDhKADAgECAhEAuOSLPwlcx/l5IqBlguM0fDANBgkqhkiG9w0BAQUFADA7MQsw CQYDVQQGEwJOTDEPMA0GA1UEChMGVEVSRU5BMRswGQYDVQQDExJURVJFTkEgUGVyc29uYWwg Q0EwHhcNMTQxMTEwMDAwMDAwWhcNMTYxMTA5MjM1OTU5WjBlMQswCQYDVQQGEwJDWjElMCMG A1UECgwcU2xlenNrw6EgdW5pdmVyeml0YSB2IE9wYXbEmzEYMBYGA1UEAwwPSmnFmcOtIFNs w6nFvmthMRUwEwYJKoZIhvcNAQkCFgZzbGV6a2EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAw ggEKAoIBAQDNcPHUXg4ZfD3shn/1zeMf8tyn/ZplDk1756hc+PVHYNO2VRP2p1HKRdtcfj1i 2V87na0EfMmfxM77dJJklSnAsCXrs0by2eHzdCz746vErs5VkSnZ1nhOWH7FViKadiyxmAv+ zXL+jkzb678GHsT2jPWdHjfhgQXAzd0hE5AqkQ3sRGRspsfruRmfgStEoE2+Ubq4jC69pBYW i80zdAUOc+9Kl5Zfolfo/TpFViXIo4i1FMgDRNYZAhBKpHz70zN/7VUqTl/7x9z3a6ytNC8J TbbMdj8SdWhRV0oyOOhYlFHL+1ZS0KtQ0iz5yWs9dCkq77LrTXCXaWSGBRlQ8H/5AgMBAAGj ggFvMIIBazAfBgNVHSMEGDAWgBRjTUNaGUg/xEbBArq/7g7lgrdmpjAdBgNVHQ4EFgQUNHjX Vei/P0DdklwoP8A3Tkq0XTYwDgYDVR0PAQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwHQYDVR0l BBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMBgGA1UdIAQRMA8wDQYLKwYBBAGyMQECAh0wPwYD VR0fBDgwNjA0oDKgMIYuaHR0cDovL2NybC50Y3MudGVyZW5hLm9yZy9URVJFTkFQZXJzb25h bENBLmNybDByBggrBgEFBQcBAQRmMGQwOgYIKwYBBQUHMAKGLmh0dHA6Ly9jcnQudGNzLnRl cmVuYS5vcmcvVEVSRU5BUGVyc29uYWxDQS5jcnQwJgYIKwYBBQUHMAGGGmh0dHA6Ly9vY3Nw LnRjcy50ZXJlbmEub3JnMB0GA1UdEQQWMBSBEmppcmkuc2xlemthQHNsdS5jejANBgkqhkiG 9w0BAQUFAAOCAQEAJy6bixJ53paigwWwnXfipRly2TTkICwf4PtXw9hOBoYC17PbPpAoGBtT Dvz6pQW4woSJ4JbkkD9JKGPlZXt0fQgZKgbfQ7sRFQ54goOhvJYm+CFJUPiSXrZ/i1CUzI40 U3kXYbWOq99yKid5aUEaIub9E6cJY6fybt7ireTV2IKVNIm/AXWjjf6jxGVavQ1QzTxmRvfE sXpQis5jgCeJjRHhZ4BhwRChkIThLYfWTSYId9rbtuj3yjLjtJipDhHJEuIckgV8sCDbjbyt xo0WNLQmfL0KUVxvpfMfdZ3McGKwn7nQiqBcpsGI3+9pfmHkMzy4+rDGZCHkeyNNxEUpLDCC BMMwggOroAMCAQICEHP+V/rfuMUIgXtmuWvwLe8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNV BAYTAlVTMQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoT FVRoZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3Qu Y29tMTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg RW1haWwwHhcNMDkwNTE4MDAwMDAwWhcNMjgxMjMxMjM1OTU5WjA7MQswCQYDVQQGEwJOTDEP MA0GA1UEChMGVEVSRU5BMRswGQYDVQQDExJURVJFTkEgUGVyc29uYWwgQ0EwggEiMA0GCSqG SIb3DQEBAQUAA4IBDwAwggEKAoIBAQDIFdn1M2ojoZANz7sFRMOrH0o1hRohhaBP+PBA4kpD m/5bsbC/tFfcdYBBS2Qa9ttPb4/QJUU1+erLSvr72tPtRYgRlDbkzKgN78U9N+0We+PClZ5Y M38i+/j/7Oa+264KZSUih9pvhItG6ECGKD+/VgjiSumDouki+y36tigfkcHDcftTwCtOpAyh bp1V7ezhJIc6COINHOTETdDLJ/qEZObRl51WJFuTuykuQ+JBaj3iSmX8ml9ahoe8h8d5gJaZ UcaQD2SRmX0Q3awsAyrheGT+zj1O9CtQEUvRWNSbA/B/9TtTsFND+8UvxAQpGjqs11Xp0Q6V 0Tsxf3hPriktAgMBAAGjggFNMIIBSTAfBgNVHSMEGDAWgBSJgmd9xJ0mcABLtFBIfN49rgRu fTAdBgNVHQ4EFgQUY01DWhlIP8RGwQK6v+4O5YK3ZqYwDgYDVR0PAQH/BAQDAgEGMBIGA1Ud EwEB/wQIMAYBAf8CAQAwGAYDVR0gBBEwDzANBgsrBgEEAbIxAQICHTBYBgNVHR8EUTBPME2g S6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVTRVJGaXJzdC1DbGllbnRBdXRo ZW50aWNhdGlvbmFuZEVtYWlsLmNybDBvBggrBgEFBQcBAQRjMGEwOAYIKwYBBQUHMAKGLGh0 dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BQUFDbGllbnRfQ0EuY3J0MCUGCCsGAQUFBzAB hhlodHRwOi8vb2NzcC51c2VydHJ1c3QuY29tMA0GCSqGSIb3DQEBBQUAA4IBAQAGK6lTLxPc XDkWzIafXkx7cvvsjVWKXpoK/1NMdvQGPVDPV/Ciz6+ZjKr+oBl2PpkDMvp1gziKu2uapQwT stQbduaULmeYWeORbAKQmpzIYEtVq8qIWo0r5WmVAwfR1A78JCIuWbFjpF/t2SNy5JzOOlxs H0+pAMkd/vp/RS22LoTdDyegWRhO1XYlRfSZJnnbb58j90O7Kw8Eo4EmLLd7Nfk9d19AIeZ/ HaWWWr3QyxY6bLthi4r9BDlECsss4cvOLhCYGtvgk+1JZGQIIJ+3o1Dwot3KtMZ8DD3nXhXc J4bkOjtSWherqQZTK50Jc2QcAcP9MNKHA2/kFQN6OV9oMYIDGjCCAxYCAQEwUDA7MQswCQYD VQQGEwJOTDEPMA0GA1UEChMGVEVSRU5BMRswGQYDVQQDExJURVJFTkEgUGVyc29uYWwgQ0EC EQC45Is/CVzH+XkioGWC4zR8MA0GCWCGSAFlAwQCAQUAoIIBmzAYBgkqhkiG9w0BCQMxCwYJ KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTEwMDcxNjU4NDFaMC8GCSqGSIb3DQEJBDEi BCAuOZDGuAhpaG1iOzoEddF5JX/N/eFfgrZshO6Iqp+94zBfBgkrBgEEAYI3EAQxUjBQMDsx CzAJBgNVBAYTAk5MMQ8wDQYDVQQKEwZURVJFTkExGzAZBgNVBAMTElRFUkVOQSBQZXJzb25h bCBDQQIRALjkiz8JXMf5eSKgZYLjNHwwYQYLKoZIhvcNAQkQAgsxUqBQMDsxCzAJBgNVBAYT Ak5MMQ8wDQYDVQQKEwZURVJFTkExGzAZBgNVBAMTElRFUkVOQSBQZXJzb25hbCBDQQIRALjk iz8JXMf5eSKgZYLjNHwwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUD BAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMC BzANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASCAQAWowTiiUZBzcYXlE9eP0ak5E6l lpFiynEKcwwuEaIuFt13UAsaBnJCZQBcOMp5nW5X3yIMj6E6fow2Y+0zte+eYUNGiLBqIuH6 uRlr2TxhlsBxjFnjZ4rgRiWhkc9jxSdDWacEeGOmXCzP9mVYKdf9WoP7kST8TnWLJ6DwwZgA x9J+4Gafdh/RFf6zehHK7bpzh76Kv4LbuW2bHD2s9oZV3zdijtzdE5i8Bdnsn9bCCwhScqND uyO15GTuPj8BeVG18tBLUl30AjZhAjjzjmFbjfUxdQoYWPNbRg9SSJ4LMqzwXsSEFCL/Sd5z 9toiUDZ6pJ6x7D6zfOlQpQICDZXEAAAAAAAA --------------ms070607010005010406080300--
On Wed, Oct 7, 2015 at 7:58 PM, Jiří Sléžka <jiri.slezka@slu.cz> wrote:
Hi,
Dne 6.10.2015 v 22:07 ccox@endlessnow.com napsal(a):
I want to correlate virtual disks back to their originating storage under ovirt. Is there any way to do this?
e.g. (made up example)
/dev/vda
maps to ovirt disk
disk1_vm serial 978e00a3-b4c9-4962-bc4f-ffc9267acdd8
In oVirt there are two storage types - filesystem based (NFS, posix, glusterfs - uses files for storing images) and block device based (FC, iSCSI - uses lvm)
If I understand correctly, you would like know where exactly is stored a virtual disk. Right?
All you know is on which storage domain is your virtual disk stored and disk uuid (imgUUID)), right?
My approach is this (I am using block device based FC stroage so my virtual disks are stored as logical volumes). Probably there is much easier way ;-) please correct me
ssh to any host
list storage domains (sdUUID)
vdsClient -s 0 getImageDomainsList
find your domain uuid by name
vdsClient -s 0 getStorageDomainInfo sdUUID
you will get also pool (spUUID)
now you can search for volume(s) the image consists of
getVolumesList sdUUID spUUID imgUUID
you will get volUUID (one or more)
now you can check volume info
getVolumeInfo sdUUID spUUID imgUUID volUUID
and also you can get volume path
getVolumePath sdUUID spUUID imgUUID volUUID
Note that getVolumePath was removed in 3.6. The only way to get this info now is via prepareImage.
you will get something like
/rhev/data-center/mnt/blockSD/088e7ed9-84c7-4fbd-a570-f37fa986a772/images/be5c56de-6a22-4d1a-8579-f0f5d501d90c/0681822f-3ac8-473b-95ce-380f8ab4de06
it is symlink which points to target block device
it looks to me that on block devices the path is
/dev/sdUUID/volUUID
btw. I am using oVirt3.5...
Cheers, Jiri
_______________________________________________ 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)
-
ccox＠endlessnow.com -
Darrell Budic -
Jiří Sléžka -
Nir Soffer -
Raz Tamir