Using Linux to Tame the Big Hairy Beast
Pages: 1, 2
Linux @ Morgan, Stanley, Dean-Witter
Next up was Phil Moore from Morgan, Stanley, Dean-Witter. Part of his responsibility there was building up their AFS filesystem.
The "big hairy challenges" they face in the enterprise industry can be summed up as the three C's:
- Configuration management
- Change control
- Capacity planning
Providing a more traditional look and feel is what a lot of companies are looking for when they're trying to find a technology solution. In the enterprise, the main challenge they had to overcome was the support issue. The 800 number makes people feel good, even though it doesn't really work. The other support issue was the ability to get changes and fixes from vendors for software products.
Provide the traditional interface that medium- to small-sized companies are used to seeing. They want to know that there's someone there to help and support them.
Instead of trying to provide critical support internally, Phil felt it was better to team up with people to offer critical solutions, such as kernel extensions, etc., so small companies don't have to ramp up and hire kernel experts. It's better for small companies if they can go to someone and say, "we need this," contract for it, and then be able to get that solution.
Linux @ BMC Software
And finally, came Carl Coken of BMC Software. About 20 years ago when the company started, BMC Software had three products, and now they have nearly 700 programs and 7,000 employees worldwide. About 70-90% of their time is spent in supporting people. They have a mix of systems in-house, and for their sales force, so the challenge is to be able to provide support for their staff and customers.
One of the reasons why they've migrated to Linux and open source is that they needed to move to a more cost-effective model, so moving away from proprietary systems made sense for their business needs. For example, they're running out of floor space in their computer rooms, so when they look at infrastructure costs, things like the cost of power to run all of the machines can be tremendous. One solution was to shrink the number of racks of boxes down from 27 to 1, resulting in a great savings in operating and support costs.
Like MSDW, if BMC Software needs support, their solution is to go to another vendor, such as Red Hat, or to contract outside developers to help them solve and support the technology problems they encounter.
Now on to the panel discussion. Some of the points raised were:
Managing change is a big issue for companies who are trying to move to an open source solution for their business.
What is the right way for the open source community to solve the needs of traditional businesses? At PDI/DreamWorks, they extended the capabilities of the GIMP to support 16-bit graphics (the GIMP only supports 8-bit graphics). With traditional software, they wouldn't have been able to do this. But having the source available to them was very important; you can take the existing source and tailor it for your own particular needs.
It's important for both sides to be sensitive to how the OS community is viewed during the development process. Users can become developers by having the source code there. If they need to make a particular change, and if they have the technical skills to make the change, they can. And if they don't have the programming skills, there are thousands of developers out there who they can contract with to get the job done.
For BMC Software, they were finding that their customers were asking for them to move their products over to Linux.
MSDW looks to a lot of different people to provide support to their customers. "Heteregeniety is a necessary evil." Their feeling is that it's better to standardize on a single Linux distribution internally so things work better.
And that concludes my report from this morning's keynote presentation. For me, it was really interesting to hear how Linux and open source/free software are making their way into mainstream business practices. Having the source available is critical, as emphasized by Ed Leonard from PDI/DreamWorks and their "expansion" of the GIMP, or how they and BMC Software were able to reduce their operating costs by standardizing on Linux as the operating system for server and rendering farms.
One thing that really wasn't addressed in the keynote or in any of the follow-up questions from the audience was how these companies are "giving back" to the open source/free software community. Yes, they're using Linux and other GNU tools, such as the GIMP, and hiring developers to maintain these systems, but it would be really great to have the improvements PDI/DreamWorks made to the GIMP for 16-bit graphics contributed back to the project.
So maybe the beast has been tamed, but I think it's getting a little hungry.
Chuck Toporek is a Mac technology geek and a senior acquisitions editor with Addison-Wesley, a division of Pearson Education. He is the author of three Mac books and one medical book, and he has written for MacAddict and Macworld magazines.
Return to the Linux DevCenter.