- I tend to agree with Mike Austin..
- but Steve Cavrak has some good points,
- they both represent our leading IT unit,
- debate is good,
- debate is going on since Novell arrived in Campus,
- debate grew even more when NT arrived in Campus,
- and now Linux?
- CIT invests lots of money in IBM's flavor of Unix (AIX) and Unix based applications and services,
- departments invest lots of money in Linux, NT, Novell and their share of services and applications,
- my manager wants something on his table ASAP,
- my manager wants something reliable which I will be responsible for,
- I need to make a decision,
- debate is still going on,
- Mike wants me in, Steve says be careful,
- other administrators are in the same boat,
- should I hire a consultant (C2 maybe?),
- or should I follow the University Requirements published at ????
>>> [log in to unmask] Tuesday, 13 March, 2001 11:00:29 AM >>>
On Tue, 13 Mar 2001, Steve Cavrak wrote:
> - zoo may not be able to run particular
> applications at all.
Agreed, however it depends on what applications they need. For file and
web services, Zoo very well may fit the bill.
> - zoo may be able to run the application
> but for policy reasons does not
There aren't many policy reasons that I'm aware of that would make us not
run a certain application. We try to be accomodating and allow people to
run applications that are will run in our environment if they want.
> - zoo may be able to run the application but
> at a less than desired service level
Our uptime has been extremely high since we implimented the new mail and
> - zoo may be able to do it, but at the cost
> of outsourcing a stragic resource to the
The cost of running and maintaining your own servers is usually very high.
Dealing with upgrades, security issues, and hardware failures can be
extremely costly for departments. If the services they need are offered
centrally, it seems like a waste of UVM's limited resources to duplicate
those efforts. If they have specific needs that we can't meet, then we
should talk about those needs to see if they can be met. If not, then
they should "roll their own" servers, but not without considering
centrally run options.
> It's that old "all the eggs in one basket" delimmma.
Exactly, which is why departmental servers so often have problems. They
put all their data on one or two machines. Then they don't back it up
effectively, and don't use redundant hardware.