Keeping Up with Carrier Grade
Welcome to Ottawa!
A few weeks ago, I had the great opportunity to present at the Ottawa Linux Symposium (OLS). For those unfamiliar with OLS, it is a yearly Linux technology event, begun in 1999, during which software designers and developers working on the Linux kernel get together to present their activities, to discuss features and projects and, of course, to have a beer or two. This year's event was among my favorites. It was filled with rich sessions and lively discussions, and many topics that were covered. Over 600 attendees turned out for this year's event, making it the place to be.
As a presenter, I chose to cover one of the current technology trends we are witnessing in the telecom sector. Open and standardized platforms that use software and hardware component building blocks are, where suitable, complementing our existing telecom solutions. The Linux kernel as an operating system is a good example. The presentation was based on a submitted paper titled "Towards Linux-based Open Telecommunication Platforms".
In my opinion, I think this trend is good news for the Linux community. After all, the Linux kernel can be deployed as an operating system, running side-by-side with other operating systems. Some features and mechanisms still are needed in Linux, however, to support this transition.
I also wanted to present to the community some of these enhancements that are essential in a telecom environment needed by carrier grade platforms that have strict requirements in areas of performance, soft real time, availability, security and reliability. To be specific, the enhancements I presented are contributions from Ericsson, which open-sourced these technologies to enrich the Linux kernel with features needed on server nodes operating in mission-critical environments.
The contributions fall in the areas of cluster communication protocol (TIPC) and cluster security (DigSig). They also cover networking to improve route lookup and to support a multiple forwarding information basis, as well as a low-level kernel mechanism (AEM) for improved reliability and soft real-time performance.
The presentation went well, and I have received a lot of questions since then, mostly regarding the projects and the implementations. In addition, that same day, the Ericsson Linux Web site, received a lot of traffic, thanks to the availability of a wireless connection in the conference venue.
During the first ten minutes of the presentation, I felt that there wasn't much interest in the technology trend. This can be interpreted as the audience is a special audience that lacks interest in technology trends, which also can be considered to be an indicator of their own priorities. However, when I started to talk about technical contributions, open-source projects--their status and plans--people started to ask a lot of questions. What was most interesting is that people attending the presentation were answering many of the questions asked by others. I took this as a good sign that these contributions are being noticed--some people already are aware of them and know enough about them to answer questions.
Why am I talking about this? Well, my point is, within this community, source code is king.
When talking about Linux in telecom, people often think of the ongoing activity in the Open Source Development Labs: Carrier Grade Linux (CGL). OSDL has a working group, CGL WG, that was established in January 2002 with the goal of accelerating the adoption of Linux in the telecommunication sector. Since then, the working group has produced the CGL 1.0, 1.1, 2.0 and, most recently, the 3.0 requirements definition document, the later being a public draft. A lot of work has been invested in this working group by many devoted and hard-working people from different companies, all of whom believe that Linux is the operating system that could be running on many pieces of telecom platforms.
The CGL WG at OSDL also has a sub-group called the PoC WG, Proof-of-Concept. In my opinion, the PoC WG is an important aspect of the CGL work, because it is responsible for driving the implementation and integration of carrier grade enhancements to Linux, as identified and prioritized by the requirements document. The PoC WG also is responsible for establishing and leading an open-source umbrella project to coordinate implementation and integration activities for carrier grade Linux enhancements. That is a challenging and interesting mission, and having enough resources in this WG is a necessary prerequisite for the CGL technology to be adopted. However, resources always are an issue.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Three More Lessons
- Django Models and Migrations
- August 2015 Issue of Linux Journal: Programming
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Shashlik - a Tasty New Android Simulator
- Huge Package Overhaul for Debian and Ubuntu
- General Relativity in Python
- Embed Linux in Monitoring and Control Systems