search for: listvolum

...9;__del__', '__doc__', '__init__', '__module__', 'autostart', 'build', 'connect', 'create', 'createXML', 'createXMLFrom', 'delete', 'destroy', 'info', 'isActive', 'isPersistent', 'listVolumes', 'name', 'numOfVolumes', 'refresh', 'setAutostart', 'storageVolLookupByName', 'undefine'] >>> help(libvirt.virStoragePool.createXML) Help on method createXML in module libvirt: createXML(self, xmldesc, flags) unbound libvirt.virStora...

This set of patches needed some reworking since they would not apply on top of next. They are ready for review and to be pushed.

On 04/05/16 14:07, Cole Robinson wrote: > On 05/04/2016 06:54 AM, Paul Carlton wrote: >> Hi >> >> I'm trying to create a volume in an existing storage pool using python by >> calling createXML() on the pool object. >> If the file that is the subject of the new volume exists you get and error, >> also if it doesn't exist >> >> I worked out

hi, how do i list storage pools and volumes using the python bindings? basically the python api calls for?virsh pool-list and virsh vol-list thanks

...if I create the file in another directory then create the > storage volume as follows... > Not sure if I fully follow, but if you manually create the file in the directory, outside of libvirt's APIs, just do a pool.refresh() and libvirt will notice the new volume and it will show up in listVolumes. createXML is only for telling libvirt to create an entirely new disk image (likely by invoking qemu-img), not to teach it about an existing image... that's what pool.refresh() is essentially for - Cole > def create_volume(self, vol_name, src_path): > def create_vol_xml(na...

This patch is dependant on the previously submitted storage admin patch.

This patch provides the ability to create a "dir" type storage pool, and to add and remove volumes for existing pools.

This set of patches supercedes the previous set, and has been rebased with changes from upstream.

This patch again rebases on upstream and should apply on next as of right now.

...ble_pools(self): + return self.__has_pools + + def get_storage_volume_list_page(self, screen): + '''Requires that self.__pools_list have a selected element.''' + pool = self.get_libvirt().get_storage_pool(self.get_selected_pool()) + if len(pool.listVolumes()) > 0: + self.__has_volumes = True + self.__volumes_list = Listbox(0) + for volname in pool.listVolumes(): + volume = pool.storageVolLookupByName(volname) + self.__volumes_list.append("%s (%0.2f GB)" % (volume.name(), vo...

This pair of patches provide a new storage admin interface. Then, on top of that, it refactors the domain administration pieces to now properly use storage pools and volumes when defining a new VM.

This version of the patch includes feedback from jboggs at redhat.com, including fixes to the BuildRequires and Requires in the spec file.

This patch obsoletes any previous ones. This is an upstream candidate, so I'm looking for feedback so we can push this and start using it.

This version fixes a few bugs found by jboggs. It also includes some logging facilities that need to be fleshed out more.

This patch is ready for pushing upstream.

The previous patch was missing this file. Resending.

...just looking for some feedback on the direction I'm going. The code won't get all the way to the define stage since I'm in the middle of retrofitting it to use virtinst instead of a home spun node definition.