Option-C (http://www.option-c.com) has been working on a Xen (http://www.xensource.com) Administration tool called, cleverly enough, the XenAdmin Toolset. It's currently advanced far enough that we are making the following screenshots available for viewing. If you have any comments, please send them to email@example.com.
XenAdmin is made up of a server and a client, allowing the client to be run on any machine on the network, or even on a remote network (this includes a DomU running under the Dom0 if you so desire). In addition, multiple servers may be connected to the client, allowing a single client machine to be used to control multiple Dom0 servers.
XenAdmin uses XML to pass requests and responses between the client and server. This allows us to write a client in any language that supports sockets. To date we have written a C/C++ GUI, several C/C++ console tools, and two PHP clients - one using AJAX.
The server and console tools do not make very pretty screenshots, so they're not shown.
(Click on the thumbnails to see the full-size images; click "Back" to return to this page.)
The first set of screenshots are of the GNOME-based GUI. It is being written with wxWidgets (http://www.wxwidgets.org), so it should be possible to recompile it for Windows or Mac OS X.
||This first screenshot shows the GUI connected to three separate Dom0 servers. We primarily test the servers locally,
though we have managed to run the system over the Internet. In general we would use SSH tunnelling or some sort of
encryption to accomplish this. The machines on the second server (XenTest2) are in varying states:
- Active - running as normal
- Suspended - saved to disk
- Inactive - not running
- Paused - running, but not being allocated any system time
You can see the high-level details for each machine on the right side of the window, and the tree showing all
available DomUs on the left. The icons for each DomU in the tree also represent the state of the machine.
| The second screenshot shows some information about the Dom0, such as its load, memory usage, and so forth. By selecting this tab, or the Dom0 DMesg tab (third screenshot), the administrator can get some vital information about the current state of their systems.
||By selecting a DomU, the administrator is able to begin working with the virtual machines themselves. The first tab shows information about the DomU - the domain name, its state, CPU, memory, etc. Currently this is information that matches that taken from the "xm list" command, although we are also hoping to show the IP address (even if it's obtained via DHCP), and other more detailed information.
| The final screenshot for the GUI shows the assorted actions that can be performed on a selected DomU. The available actions depend on the current state of the machine -- it doesn't make sense to shutdown an inactive machine, for example. Most of the actions can be accessed from the tree, via a right-click menu. (Note: As of the current version, we have not enabled the "Migrate" or the "Console" actions.)
We also have two screenshots of a PHP-based admin tool. This is our AJAX-version, which currently only shows
drill-down information about the machines and the DMesg for the Dom0. We may make a version of this available
on the Internet for people to play with in the near future.
The XenAdmin Toolset is very much a work in progress, as such any information might be wildly inaccurate (although we can guarantee it will be definitively so).