Re[2]: [Openvds-devel] Control Panel for OpenVDS-2

[Eje Gustafsson]

Yes I see that now when OpenVDS 2 been explained little further in
detail that with that basically any more standard Linux control applet
can be used in a normal fashion.

Just take a normal webmin install and dump out of it what you don't
need such as hardware control and nic interface control since you
can't affect that.
Can't wait to see what Dave got cooked up. Wish I could do more to
contribute. Guess for now I will just fix up webadmin so I have an
more automated way of adding users/domains to control and fix a few
things in there until OpenVDS 2 is ready.. Only PITA is that when he
put it out and it's ready to use I will have to do another rotation of
servers.. :( I'm not done with this last one yet. Well now I'm
basically consolidating all the domains I have on different Linux
boxes onto my FreeVSD 1.4.10 box. Hopefully it will be lot easier to
do the switch to OpeVDS (just tar their vs skel and put on the new
machine).

Monday, January 14, 2002, 22:27:23 PM, you wrote:

JC> Eje Gustafsson wrote:

>> Not sure how I should uhm take your comments. Obviously your not found
>> of php ...


JC> No, I'm not fond of PHP (then again, maybe I should give it more of a 
JC> chance...I used to find Perl ugly too).  But that is irrelevant, and I 
JC> should have been more restrained in my comments.  Language holy wars are 
JC> irrelevant.


>> But this is all of little concern. Webmin is written in perl and from
>> the already prewritten config tools webmin seems the best option.
>> We have webmin, linuxconf and WebAdmin (freevsd's).
>> Webadmin isn't as modular as webmin but there we already have a lot of
>> the basic features running to deal with openvds.
>> Linuxconf someone said apparently messes with all config files and
>> rewrites them etc which might not be that a good thing.
>> webmin has a good modular configuration and a lot of premade features
>> for a lot of things that might be useful. But to do what we want it to
>> (at least from what I seen) we would need quite a few modules a few of
>> them one could probably take preexisting and rewrite them to fit our
>> needs.

JC> Dave's vision of OpenVDS-2 ends the problem of needing VDS specific 
JC> Webmin modules, generally.  We will still need a generic virtual server 
JC> manager for within the virst, and a VDS setup module.  But the first is 
JC> already underway in a few places (my mojo project being one of them), 
JC> and the latter should be an easy to implement frontend to the command 
JC> line tools.  I can probably do the latter in a couple of days of 
JC> development, once the tools are defined and working.

JC> More complex tasks, like Virt migration and replication (who doesn't 
JC> like the ability to offer high availability and 'live' backup servers, 
JC> and such to their clients?) and backups, etc. will need to be 
JC> implemented from scratch, but that is true in all cases--there is no 
JC> such tool available.

JC> The cool thing about what Dave has been describing is that we don't need 
JC> special admin tools within the virts anymore.  Apache will be a regular 
JC> old Apache...a default config file would even work!  This will be the 
JC> way to salvation on the administration front.

JC> So, anyway, forget I ever said anything disparaging about PHP (I just 
JC> had to fix a bug in a PHP script recently, and it wasn't pleasant for 
JC> me--code intermingled with HTML, CSS, and special tags made for a 
JC> harrowing experience).  I'm sure that PHP code can be made cleaner and 
JC> easier to read than what I've spent time with.  All that said, I'll be 
JC> writing my VDS tools as Webmin modules in Perl.



Best regards,
 Eje Gustafsson                       mailto:address@hidden
---
The Family Entertainment Network      http://www.fament.com
Phone : 620-231-7777                  Fax   : 620-231-4066
eBay UserID : macahan
          - Your fulltime professionals -