Enterprise FOSS Adoption Beyond Linux Servers?

An anonymous reader writes "I am working with a couple of large companies that are purchasing web and collaboration software stacks from Microsoft, IBM and others. These are for thousands of end users and are (supposedly) ready for multiple data center deployment and other big-corp requirements. I have suggested some open source alternatives such as Liferay and Drupal, and the technical people are interested but management types are not. They have given a few reasons, such as concerns over supportability and enterprise-readiness, but my feeling is that they are being won over by FUD from large vendors and the fact that most corps do not have significant deployments of FOSS technologies beyond Linux yet. All this seems to be in line with a survey on Web-app servers by OpenLogic. So my questions are: How have you persuaded larger enterprises to adopt server-side OSS, beyond server-room Linux and a couple of demo JBoss boxes under someone's desk? And which products are truly ready for enterprise-scale deployment?"

Comments

-Enterprise

[MrEricSir]

Could someone re-write this story without the buzzword "enterprise" substituting for the actual requirements?

Until then, I will have to mod this down.

Re:-Enterprise

[JWSmythe]

    You just got out of Microsoft school, didn't you?

    In the real world, the majority of servers are *nix based, with the majority of those being Linux. You'll find them all over the place.

    Yes, you'll need to learn the CLI to do it right. Playing point and click just doesn't cut it in the higher levels. Even in the higher levels of Microsoft stuff, you'll need to know how to use their CLI, except it's not well documented, and a quick Google search won't tell you all the answers.

    Wait until you have to start programming. Don't worry, if you get beyond help desk support for your local ISP, telling people how to renew their DHCP lease, you'll have to (oh my gosh) actually type things. Since you're probably unaware, the nifty point and click programs were actually written out and compiled. They didn't just start life as pretty interfaces. When you start scripting (batch, VB, Perl, PHP, or whatever) you'll live in the CLI. That is, unless you live on crutches provided to you by others.

    I'm a *nix/Linux admin. I get pulled into the Windows arena on occasion. Because I'm really good at what I do, it's assumed I'm good at anything. The truth is, I'll figure it out faster than most people, which is why they call me. Once I had to add several hundred new sites to an IIS web server. They were pointing and clicking, and wondering why the occasional one didn't work (you missed a click). I wiped out the 10 sites that they had done by hand, and scripted the whole thing. My script took less than 20 minutes to write, and less than a minute to execute. It would have taken them days to get all the sites entered and fixed, and even still, customers would have called complaining because particular check boxes weren't clicked when they should have been.

    Linux and open source are in the enterprise, and they're going to stay. They are the future, and Microsoft is struggling to keep up. But hey, MS is all you know, it's what you learned in your tech school, so you could get your MSCE, and now you hang it proudly in your cube at your call center. Congratulations. If you want to succeed, pick up some more skills. Linux, Solaris, and AIX are a start. MySQL, and Oracle, Apache are good too. Pick up Perl, PHP, shell scripting, and maybe get some decent exposure to C*. Go get your Cisco cert too. Once you're there, then you're allowed to play with the big boys. Until then, sush up and answer your support calls from housewives who can't figure out what the mouse is. Don't forget those winning Microsoft skills you picked up. Once you've shown that you are great at what you do, you'll still be asked to fix office computers because they have malware or some mysterious crashing problem.

Use the big vendors to assist

[xzvf]

I work for IBM, but don't speak for them in an official capacity. Open source is customer driven and not vendor driven. There is little incentive for anyone outside your company to push open source software because it reduces their profit. Ask your vendors to come up with solutions that use open alternatives, otherwise they are just going to push what makes them money. Software margins are high and ISV's are bribed to push it. I think MS gives 6% kickback to vendors that sells a license, which is a revenue stream lost when open source is used. Ask your vendors to present an open alternative alongside their proprietary ones. Same support that management demands, but less risk.

Re:IBM is adopting

[cp.tar]

So open format standards are more important than overall software quality? Not sure I really agree with that.

I would.

It does seem counter-intuitive, but an open standard at least guarantees that your documents will be readable if you conclude the software you are using does not meet your needs. You simply get a new program and leave the documents be.

An open standard means a more level playing field. And that means some evolution can occur.

Re:You know--"Enterprise", "Enterprisy", ...

[jrumney]

You forgot to mention that the salesman is paying for lunch after we finish the 18th hole, have you ever seen open source that does that?. -- the Management team