[libvirt] XenAPI remote storage - target path
Hi, I'm trying to write a Remote Storage driver for XenAPI. I see that target-path is used for both storage pools and volumes. In the case of XenAPI remote storage, the storage is not mounted on the local host where libvirt is running. Storage is maintained in a remote location only. In this case how do I specify target-path and how do I go about creating a VM with storage using libvirt APIs with virsh and virt-manager. Virt-manager expects me to give an absolute path for target-path. But In my case I don't have an absolute path. Can I have a target path like this for a particular storage volume "/storage pool uuid/storage-vol uuid"? This will help me identify which storage pool is Libvirt talking about and which volume in it. Using this information I can fetch data from The remote location and give it back to libvirt. Is this approach ok or does libvirt support my specific remote storage case in some way. Could someone clarify please? Regards, Sharadha
On Mon, Mar 15, 2010 at 05:57:57PM +0000, Sharadha Prabhakar (3P) wrote:
Hi, I'm trying to write a Remote Storage driver for XenAPI.
For XAPI (used in XenServer and XCP), or for the old XenAPI used in the traditional Xen/xend? -- Pasi
I see that target-path is used for both storage pools and volumes. In the case of XenAPI remote storage, the storage is not mounted on the local host where libvirt is running. Storage is maintained in a remote location only. In this case how do I specify target-path and how do I go about creating a VM with storage using libvirt APIs with virsh and virt-manager. Virt-manager expects me to give an absolute path for target-path. But In my case I don't have an absolute path. Can I have a target path like this for a particular storage volume "/storage pool uuid/storage-vol uuid"? This will help me identify which storage pool is Libvirt talking about and which volume in it. Using this information I can fetch data from The remote location and give it back to libvirt. Is this approach ok or does libvirt support my specific remote storage case in some way. Could someone clarify please?
On Tue, Mar 23, 2010 at 02:22:24PM +0200, Pasi K?rkk?inen wrote:
On Mon, Mar 15, 2010 at 05:57:57PM +0000, Sharadha Prabhakar (3P) wrote:
Hi, I'm trying to write a Remote Storage driver for XenAPI.
For XAPI (used in XenServer and XCP), or for the old XenAPI used in the traditional Xen/xend?
They're the same aren't they - at least that was the point of the XenAPI RPC specification. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
On Tue, Mar 23, 2010 at 12:27:46PM +0000, Daniel P. Berrange wrote:
On Tue, Mar 23, 2010 at 02:22:24PM +0200, Pasi K?rkk?inen wrote:
On Mon, Mar 15, 2010 at 05:57:57PM +0000, Sharadha Prabhakar (3P) wrote:
Hi, I'm trying to write a Remote Storage driver for XenAPI.
For XAPI (used in XenServer and XCP), or for the old XenAPI used in the traditional Xen/xend?
They're the same aren't they - at least that was the point of the XenAPI RPC specification.
Hmm.. yeah, that makes sense. My bad. I was confused about that. -- Pasi
On Tue, Mar 23, 2010 at 02:22:24PM +0200, Pasi Kärkkäinen wrote:
On Mon, Mar 15, 2010 at 05:57:57PM +0000, Sharadha Prabhakar (3P) wrote:
Hi, I'm trying to write a Remote Storage driver for XenAPI.
For XAPI (used in XenServer and XCP), or for the old XenAPI used in the traditional Xen/xend?
Never mind, I was reading the virt-tools list before reading libvirt-list :) -- Pasi
I see that target-path is used for both storage pools and volumes. In the case of XenAPI remote storage, the storage is not mounted on the local host where libvirt is running. Storage is maintained in a remote location only. In this case how do I specify target-path and how do I go about creating a VM with storage using libvirt APIs with virsh and virt-manager. Virt-manager expects me to give an absolute path for target-path. But In my case I don't have an absolute path. Can I have a target path like this for a particular storage volume "/storage pool uuid/storage-vol uuid"? This will help me identify which storage pool is Libvirt talking about and which volume in it. Using this information I can fetch data from The remote location and give it back to libvirt. Is this approach ok or does libvirt support my specific remote storage case in some way. Could someone clarify please?
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
participants (3)
-
Daniel P. Berrange -
Pasi Kärkkäinen -
Sharadha Prabhakar (3P)