| Supervisor VPS [message #9191] |
Thu, 21 December 2006 14:13  |
dagr
Messages: 83
Registered: February 2006
|
Member |
|
|
I wonder is there is possibility to make a kind of supervisor VPS. Imagine you have bunch of VPSs. You need to monitor,make updates, for development ,etc . Better to do it from 1 place. Also if you migrate them from time to time to another HNs - you might want to place all this stuff into some kind of superVPS which could run commands outside itself just like as it was HN. Advantage - is easy migration , no need to sync all this stuff across all HNs. Also if you have several HNs - you need to know which HN is "master" now - so every time you connect to another ip. In case of VPS - ip stays the same , which makes VPS environment migration - transparent for users, useful for developer team for instance.
Or may be smth like that there is in Virtuozzo?
|
|
|
|
| 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
|
|
|
|
|
|
|
|
| Re: Supervisor VPS [message #9413 is a reply to message #9387] |
Mon, 01 January 2007 18:17 |
dagr
Messages: 83
Registered: February 2006
|
Member |
|
|
About possible solution.
Say you have built monitoring/management center for OpenVZ. It gathers data about services/VPSs across different hosts,(or may be nodes/VPSs just upload data to it by ssh). It has some db backend and apache/php as frontend , may be some custom/exotic things. Php must be compiled to support db , etc. And you might want that all this stuff was able to move to another HN easy and fast. Best solution - to place it to another VPS, in addition this will keep same ip during move for uploading data, so move will be absolutely transparent for other parts of system. At the same time this monitoring/management center should be able to change other VPSs runtime parameters, like kmemsize,oomguarpages, so on. This tool also should be able to migrate other VPSs.
Its possible to place all this stuff into 1 special directory on HN and start apache/db on special ports, in case another HN could already have custom apache/db/php.Well, guess yes. But it will not work if you need to move it to another distro.
Actually there is no any need in some special service VE.Cause its possible to run all commands on HN from inside common VPS via ssh (if you place public/private keys). Especially cause in case of several HNs you'll have to use ssh anyway.
I wasnt able to find overwhelming advantages of placing such stuff into VPS. Though here are some:
1. doesnt depend on HNs distro,
2.keeps ip
3. dont need to think about keeping such things like placing services in startup,smtp mta settings (you could have special ones, and its harder to place 2 mtas (especially different) on 1 HN as many senders (cron,php,etc) use 25 port anyway),syncing cronjobs,home dirs, other trivial details.
Just makes you mind free of what does it require for work when suddenly need to migrate. Especially if it wasnt you who built this system.
|
|
|
|
| Re: Supervisor VPS [message #9525 is a reply to message #9191] |
Tue, 09 January 2007 06:14 |
Vasily Tarasov
Messages: 1345
Registered: January 2006
|
Senior Member |
|
|
I just want to note, that for each VE you can set so called "capabilities"
(more information at vzctl man-page). Some of these capabilites are ve_admin,
setveid, sys_resource, sys_admin, ...
I suppose that by playing with capabilities you'll be able to create something like "supervisor" VE, you need.
But remember, you'll be the first one on this way, so you can meet
unexpected problems.
HTH,
Vasily.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
