| Re: Supervisor VPS [message #9192 is a reply to message #9191] |
Thu, 21 December 2006 15:26   |
rickb
Messages: 368
Registered: October 2006
|
Senior Member |
|
|
Can you be more specific about the solutions this could offer? ie, how would this make updates or development easier. I also don't see how this would effect VE migration from HN to HN. Wouldnt the HN's IP stay the same?
It sounds like a common directory on your HNs which hold scripts, utilities (for monitoring, diagnostic, migration), and reporting tools would be simpler and still do what you need.
Commercial VZ has a service VE, VE1. It is used for port redirection and houses the VZPP application. If you want an interface for managing the HN/VEs, a service VE is a good idea. OVZ currently has no application to make this useful. I started working on one, I posted about it in the discussions forum. Several other people have written management applications but from what I have seen, it runs on the HN.
I think your idea is intriguing and could benefit ovz if we can see how it would be useful.
-------------
Common Terms I post with: http://wiki.openvz.org/Category:Definitions
UBC. Learn it, love it, live it: http://wiki.openvz.org/Proc/user_beancounters
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
