Specifications aim to improve and enhance the open-source operating system to meet the strict requirements of the telecom industry

Paul Travis, Managing Editor, InformationWeek.com

February 11, 2005

4 Min Read

Lucent Technologies Inc. and Nortel Networks Ltd., two of the leading suppliers of telecom network infrastructure, could be most threatened by the move to Linux. Those vendors, using proprietary technology and software, supply much of the central-office switching systems and operational-support systems used by most of the large U.S. phone companies. Neither company is a member of OSDL.

Lucent is evaluating several vendor offerings of CGL and is prototyping products internally, but hasn't officially revealed any products based on carrier-grade Linux. Nortel has been developing its own version of CGL and already is shipping a number of products using that operating system. It's the de facto standard for all new Nortel product development, but "it will be a number of years before it is commonplace," says Rich Wilkie, Nortel's services edge chief architect.

"There are a lot of compelling reasons why it makes sense to use CGL as a base for a lot of different telecom products," says Howard Trickey, director of the systems software research department at Bell Labs. "But there are places where it doesn't make sense." The Linux kernel is larger than some "old-school" operating systems, which may make it inappropriate for some applications where a small memory image is desired. And Linux is still maturing in terms of providing real-time control, which is important for some telecom applications.

KEY FUNCTIONS

Telecom requirements for Linux are higher than most enterprise data centers


Availability: Aiming for 99.999% availability


Serviceability: Enables remote management and monitoring


Performance: Systems must meet service deadlines; support SMP, hyperthreading, and large memory systems; and provide efficient, low-latency communication


Clusters: Can work in high-availability cluster to remove any single point of failure


Standards: Must be compliant with other standards such as the Linux Standard Base


Hardware: Works with commercial-hardware components, supports hot-swap components



Carriers may not care whether their vendors build products using CGL, Trickey and Wilkie say. What they really care about is whether their equipment vendors can ensure that their products meet the reliability and availability standards carriers require. Several leading telecom carriers declined to comment on this topic, saying only that they were monitoring CGL developments and that they would rely on their equipment suppliers to use the best software for the job.

Linux will slowly replace proprietary operating systems in telecom equipment as carriers replace old equipment with new technology, Wilkie predicts.

"The old will simply go away and it will be hidden from the user," he says. "So the speed at which you evolve to a new OS is driven by the engineering team building the product and not by the user community. The users just want to use the box as it came."

Carriers, however, take a long time to introduce new products into their networks, says Julie Giera, a VP at Forrester Research. "It is inevitable, but it will be awhile before carrier-grade Linux is introduced and begins to be stressed by the telecom carriers," she says. "The introduction of a new technology platform is always exciting, but carriers will be concerned about the cost of maintaining the code and integrating all of the individual pieces and parts together. Enhancing Linux to make it reliable enough for carriers will make it a much bigger monster to feed and care for."

It also, over time, will provide benefits for businesses. Those involved in the CGL effort are quick to say that all new features and improvements eventually will appear in the Linux kernel used for servers, desktops, and other systems. That means business-technology managers using Linux can look forward to carrier-grade availability and reliability in their own data centers.

About the Author(s)

Paul Travis

Managing Editor, InformationWeek.com

Paul Travis is Managing Editor of InformationWeek.com. Paul got his start as a newspaper reporter, putting black smudges on dead trees in the 1970s. Eventually he moved into the digital world, covering the telecommunications industry in the 1980s (when Ma Bell was broken up) and moving to writing and editing stories about computers and information technology in the 1990s (when he became a "content creator"). He was a news editor for InformationWeek magazine for more than a decade, and he also served as executive editor for Tele.Com, and editor of Byte and Switch, a storage-focused website. Once he realized this Internet thingy might catch on, he moved to the InformationWeek website, where he oversees a team of reporters that cover breaking technology news throughout the day.

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like


More Insights