On 04/14/2011 02:05 PM, Darryl L. Pierce wrote: > The goal of the virtlib library is to extract from Virt Manager and > Virt Manager TUI the shared business logic and package it separately > as a reusable library of code. >
Just to be clear, a reusable _private_ library of code for tools in the virt-manager umbrella. There isn't any benefit to making this library public at the moment. As far as the code is concerned I assume it shouldn't make a difference (that said I haven't looked at the code yet). - Cole > This first patch set creates the library's package structure and > defines the first shared business object: the Hypervisor model. > > A concrete implementation, KvmHypervisor, interacts with libvirt > and provides the source for information presented by both version of > Virt Manager to the user as well as enable controlling networks, > storage pools and domains. > > Future enhancements will provide the means for retrieving physical > storage details and other information needed by Virt Manager. > > _______________________________________________ > virt-tools-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/virt-tools-list _______________________________________________ virt-tools-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-tools-list
