WebVirt status update
February 23, 2009 9:08 pmAs you can probably guess, I’ve been rather busy.
WebVirt has become a very exciting project, so I’ve been spending almost all of my computing time coding. I have posted some screenshots but I have to admit that they’re already a bit dated with some of the new features I’ve implemented.
Current WebVirt can connect to remote libvirt nodes, however only with zero authentication. What this mean is that you’re limited to using a connection string like this:
qemu+tcp://192.168.1.2/?name=qemu:///session
That being said, I’m planning on using the Redhat package python-nss for key creation and management. So that should follow “hopefully” shortly.
Once connected, you can start and destroy (stop) both virtual networks and domains that are currently defined on a remote physical node. I should point out that there is still a bug in libvirt that “may” undefine a network on the remote machine when you destroy it. Undefining is removing the config from the remote node. This does not effect domains, however.
You can also push network and domain configurations created in WebVirt to your remote nodes.
You can toggle whether or not each virtual domain and network is to autostart. This means that when the libvirt daemon is started/restarted on the remote node, these virtuals domains and networks will automatically start.
Lastly, importing previously defined virtual domains and networks from remote nodes. The elaborate on this feature, let’s say you’re like me. You’re so excited about libvirt, that you’re already using it to manage virtual domains and networks, and you just can’t wait for a full release of WebVirt.
Fear not! Currently WebVirt can only import the very basic virtual networks and the import of virtuals domains is all but a place holder (only the name and UUID are read as a proof of concept as up CVS check-in 14), this feature is of utmost importance to the project and will be fully implemented in time.
