[osiris-devel] removing features

[Alexei_Roudnev]

I use CLI for configuration. But I _DO NOT APPROVE_ changes usually - every
group of servers sent messages to the group of 'xxx-change: ' mail list,
which includes me, our manager and solution chief engineer. And _THEY_ do
approve this changes.

They can not use CLI, not a chance.
I never use CLI for change approval (which I have 2 - 40 / day - for
example, I approved 40 changes yesterday when we removed old account from
all unix servers - local passwords. It is absolutely impossible to use CLI
for such things).

Of course, I do not bother_how_ EB and osiris interacts, but what's the
problem with http -it works, it _do not require 100% compatibility_ - you
can apply any client restrictions - because it is _technical management web
service_.

----- Original Message ----- 
From: "Spike Ilacqua" <spike at indra.com>
To: "Osiris Developers" <osiris-devel at lists.shmoo.com>
Cc: <brian at shmoo.com>
Sent: Thursday, November 11, 2004 4:07 PM
Subject: Re: [osiris-devel] removing features


> Personally I use the CLI interface, but I think Alexei does have a valid
> point, your average user is going to prefer a pretty Web interface.
>
> That said, I don't think the management console should be a Web server.
>     Let Web servers be Web servers, and Osiris be Osiris.  Create a CGI
> that can be installed on an existing Web server.  That way you don't
> have to be writting HTTP code and if the user can't get to the Web
> server, than it's a problem with the Web server, not Osiris.
>
> ->Spike
> _______________________________________________
> osiris-devel mailing list
> osiris-devel at lists.shmoo.com
> https://lists.shmoo.com/mailman/listinfo/osiris-devel
>