Daniel P. Berrange wrote: >> The general workflow is as follows: >> >> ========================================= >> import virtinst.Storage.StoragePool as sp >> >> # This gives the appropriate class for the specified pool type >> pool_class = sp.get_pool_class(sp.TYPE_FOO) >> >> # Only required params are a conn/uri and name. Default formats >> # and target paths have default values, but source paths/ >> # devices and hostnames obviously have no sensible default, but >> # they still aren't required for object instantiation >> pool = pool_class(name="foo", uri="xen:///") > > Should proably allow a existing connection to be passed in, otherwise > this class has to deal with authentication issues too. > I didn't show it in the example, but passing a connection is allowed. On a side note, we should add support for openAuth in virtinst, everything is just hardcoded to use libvirt.open at the moment. - Cole _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
