openvds-clients
[Top][All Lists]
Advanced

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

[Openvds-clients] Re: [Openvds-devel] Webmin Control Panels


From: Marcos Rubinstein
Subject: [Openvds-clients] Re: [Openvds-devel] Webmin Control Panels
Date: Tue, 11 Dec 2001 16:03:11 -0800 (PST)

I'm replying *only* to de openvds-clients ;)

in any case... a few points:

On Tue, 11 Dec 2001, Clint Nelissen wrote:
-------------------8<snip,snip,snip>8-------------------
> 1 - An end-user version of webmin - This would be a dumbed down version
> of webmin.. taking out all of the root and non-vds specific stuff from
> webmin, such as the hard-disk modules and the network configuration
> modules. This would also run as the admin-pseudo user rather than root.
> This way it executes commands in the same exact manner as the admin user
> would through telnet, and no added security risks. Also whether this
> runs as an apache version or the webmin.pl version is of no security
> consequence. If it is to be a stand-alone, it should run on a different
> port than the standard webmin install.. so that for the network
> recognition features of webmin... it will not find every single VDS
> running the control panel. We don't want our customers to be able to see
> how many customers we have and where they are on the network. Even if we
> axe this all together from the client version, that would be best. But
> at the server admin version.. it would not find every VDS version.
> 

actually, eventhoug now I'm running webmin in different port
for each vs, there is not need to do so!... webmin can bind
not only to a specific port, but to specific ip also :)

I already "dumb down" one webmin... took out al "sanity
checks" at install (rem all references to check if the usr
has uid=0), and could installit with no problems ;)... I'm
only waiting for our test server with the latest freevsd or
openvds version installed to try different webmin
modules! (make no sense to start working in the freevsd
1.4.5 that we have on the production server!).

in any case I agree with you :).... a module that will need
some "tweaking" is the "users and groups" in such a way that
also reads/writes to /etc/vsd/priv!. Some modifications to
the sendmail module would be beneficial... webmin asumes
that sendmail is started as daemon and not call from
xinetd... and I'm sure we can look closely at all other
modules ;)

> 2 - The server version. This would be a standard webmin install.. all
> features intact. From here the network recognition could take place as
> normal.. allowing a network admin to locate and administer every VDS
> server (physical server) on the network.
> 

yup.. but here is where some development/coding would be
needed... we need to create de "openVds" module that would
allow the "main administrator" (the root of the
"host" server) to setup/edit the diferent vds. 

"pie in the sky" would be the abilitie to automte the
instalation of diferent packages in diferent vs's.

> 3 - A webmin VDS module. The network recognition here would only find
> the VDS version control panels for the server they are logged in on.
> (basically the same method only searching for webmin on the other port).
> >From there the admin could administer all of the VDS's under that
> server, such as add/remove/edit VDS's/users/software.
> 


mmmmm... need to think about it ;)

> Any thoughts on that?
> 

I think the "module" we should start working asap is the one
you state on 1 (the one that runs in each vs as admin)...

Cheers!
Marcos

> Clint Nelissen - Technician
> Digital Internet Services Corporation
> Phone - 760-776-0800 x 300
> Fax - 760-776-0076
> http://www.dis.net
>  
> 
> _______________________________________________
> Openvds-devel mailing list
> address@hidden
> http://mail.freesoftware.fsf.org/mailman/listinfo/openvds-devel
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]