| New features suggestion [message #3499] |
Wed, 31 May 2006 14:18  |
dwebwarm
Messages: 11
Registered: February 2006
Location: Hewlett-Packard Global De...
|
Junior Member |
|
|
Hi @ll,
I was thinking about some kind of kernel/userspace extension to the
OpenVZ project. Actually the full list of processes on the hostnode is a
bit disturbing and could lead to some bad things like killing a VPS
process by accident. It's almost the same with netstat - now we see all
open ports from the hostnode and the VPSes in the same list. To avoid
such situations I suggest the following:
1. To patch the kernel in order to have the possibility to filter easy
hostnode's and VPS'es processes.
2. To patch some userspace programs, just to list the VPS related stuff.
To be clear I'll give the following example with netstat. The program
will still list the port stats, but _only_ from the hostnode. A new
program, called vnetstat will list the ports, that are handled by the
VPSes. In the mean time a new column can show the VPS ID too, just to
have the possibility to easy find the corresponding server. The same
idea can be used for ps too.
Actually there is no need to separate the things in different programs.
Let's say we'll patch the main program and include the VPS ID column in it.
What do you thing about this? Any comments and suggestions are appreciated!
Best regards,
Martin Dobrev
|
|
|
|
| Re: New features suggestion [message #3525 is a reply to message #3499] |
Thu, 01 June 2006 08:41  |
dim
Messages: 344
Registered: August 2005
|
Senior Member |
|
|
On Wednesday 31 May 2006 18:18, Martin Dobrev wrote:
> Hi @ll,
>
> I was thinking about some kind of kernel/userspace extension to the
> OpenVZ project. Actually the full list of processes on the hostnode is a
> bit disturbing and could lead to some bad things like killing a VPS
> process by accident. It's almost the same with netstat - now we see all
> open ports from the hostnode and the VPSes in the same list. To avoid
> such situations I suggest the following:
>
> 1. To patch the kernel in order to have the possibility to filter easy
> hostnode's and VPS'es processes.
> 2. To patch some userspace programs, just to list the VPS related stuff.
>
> To be clear I'll give the following example with netstat. The program
> will still list the port stats, but _only_ from the hostnode. A new
> program, called vnetstat will list the ports, that are handled by the
> VPSes. In the mean time a new column can show the VPS ID too, just to
> have the possibility to easy find the corresponding server. The same
> idea can be used for ps too.
> Actually there is no need to separate the things in different programs.
> Let's say we'll patch the main program and include the VPS ID column in it.
>
> What do you thing about this? Any comments and suggestions are appreciated!
There was similar development some time ago, check
http://download.openvz.org/contrib/
It will be great, if you'll port it to current procps version. After that,
we'll include it to standard OpenVZ package set, as well, as proposed
vnetstat.
>
> Best regards,
> Martin Dobrev
--
Thanks,
Dmitry.
|
|
|
|
|
|
| Re: New features suggestion [message #3543 is a reply to message #3499] |
Fri, 02 June 2006 10:50 |
dev
Messages: 1693
Registered: September 2005
Location: Moscow
|
Senior Member |
|
|
BTW, I also uploaded a couple of useful tools to
http://download.openvz.org/contrib/utils/ which allow to use fair CPU
scheduler or UBC separately from virtualization. For example, it is
possible to limit users.
Would be nice, if someone took a look and cleanup these tools.
Kirill
> Hi @ll,
>
> I was thinking about some kind of kernel/userspace extension to the
> OpenVZ project. Actually the full list of processes on the hostnode is a
> bit disturbing and could lead to some bad things like killing a VPS
> process by accident. It's almost the same with netstat - now we see all
> open ports from the hostnode and the VPSes in the same list. To avoid
> such situations I suggest the following:
>
> 1. To patch the kernel in order to have the possibility to filter easy
> hostnode's and VPS'es processes.
> 2. To patch some userspace programs, just to list the VPS related stuff.
>
> To be clear I'll give the following example with netstat. The program
> will still list the port stats, but _only_ from the hostnode. A new
> program, called vnetstat will list the ports, that are handled by the
> VPSes. In the mean time a new column can show the VPS ID too, just to
> have the possibility to easy find the corresponding server. The same
> idea can be used for ps too.
> Actually there is no need to separate the things in different programs.
> Let's say we'll patch the main program and include the VPS ID column in it.
>
> What do you thing about this? Any comments and suggestions are appreciated!
>
> Best regards,
> Martin Dobrev
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
