On Wed, Jul 11, 2012 at 05:28:07PM -0700, Ata Bohra wrote: > > > > > Hi All, > > I am interested in extending libvirt APIs to support iSCSI operations such > as: add/remove targets, list targets, list remote LUNs, rescan luns etc. The > intention is to provide an interface that external programs can hook to > manage iSCSI storage devices on a given hypervisor(I would be adding > interfaces for ESX first). Looking at the libvirt.c interface for storage > driver I'm unable find routines that can be overridden for specific > hypervisor. Googling lead to a nice blog presentation that provisions VMs on > remote LUN(s) for KVM but uses virish. (http://berrange.com/tags/iscsi/). > > My question is; is this as per design not to expose iSCSI related APIs? Will > an extention to libvirt.c (_virStorageDriver) so that every hypervisor can > implement it is acceptable? Please correct me if I am missing something > serious here.
The libvirt model is to *not* expose iSCSI specific APIs. We expose a general purpose storage API, which (for KVM, UML, LXC & Xen) already supports ISCSI target connections. This existing API can be implemented for VMWare or other hypervisors as needed. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
