[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Control Panel For Xen



I'm not your target auddience, but I'll give my comments.

On Mon, Feb 13, 2006 at 03:03:36PM -0600, Linn Boyd wrote:
:Hello All,
:
:       We have developed an in-house control panel for Xen. I would like
:to know what kind of interest there is for this panel and the answer to
:the question of what we should do with it. This is not vaporware, but it
:is operational at this point. It runs on the LAMP platform and is managing
:our farm.
:
:Current Features
:
:       1. Traffic monitoring for each domU(inbound/outbound).
:       2. CPU monitoring for each dom0.
These are pretty easy with current monitoring tools, I can just roll
the monitoring I have for physical sytems.

:       3. Location service for each domU if you have multiple dom0's.
This I find interesting

:       4. Rapid build of dom0's from with gfs. (I don't know if this will
:ever be released as we have proprietary information in this feature)

This too is relatively simple from shared storage (gfs, clvm, nfs),
boot to an NFS root untar and  run grub, or you can use a heavier
weight system like FAI http://www.informatik.uni-koeln.de/fai/ if
there's to be much variation amoung your DomU's.

Again much like provisioning a physical system.


:       5. Support for live migration from webpage.
:       6. Support for provisioning of new domU's from web interface. We
:are currently expanding this feature and it will allow selection of os
:images and configuration of the domU's.

Not my cup of tea but I bet it will be popular.

:       7. Growing of domU's file systems on GFS from a web interface.

Why are you implementing the VBD's as fiel sin GFS instead of just
exposing logical volumes from CLVM?  I don't mean to say it's wrong,
it just seems like having an aditional filesyustem layer would impact
performance for no gain.  I could well be wrong as I've not tested
this...


:       8. Health monitor of the farm, you can see what is running on each
:dom0.

Nice.


:       9. This is targeted for a hosting company, but can be targeted for
:almost any application.

For reference I work in a research lab supporting about 800+ users and
look to Xen for computational work loads and possibly virtualization
of cor services like email, web, database, etc. in the future.

:       10. Support for restarting, starting and destroying domU's.

Handy

:Questions
:
:       1. Is there any interest in this, and if so what level of
:interest?
:       2. I am considering if I should open source these or if they
:should be left closed source and maybe on a subscription basis only. The
:investment in time and money has been great, and the competition would use
:this software as well.

There is no possibility we would use such software if it were not
opensource.  

:       3. How should it be marketed and if it is what would be a fair
:price?
:       4. Should I develop a Xen in a box type of system? We have done
:this and can bring a stable Xen/GFS farm online in about three hours. 
:       5. What other features does everyone want on this?

If you're going for a long term fancy product perhaps automating live
migration among Dom0's.  There's alot to look at CPU, Memory, I/O so
getting those balanced the right way would be tricky. 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.