CGL

The CGL workgroup has two main functions. First, interface with network equipment providers and carriers to gather requirements and produce specifications that Linux distribution vendors can implement. Second, to take unimplemented requirements and foster development projects that will meet these requirements and assist in their upstream integration.

The Linux Community (Upstream) Documentation Strategy Requirements Gathering Governance

Registered Distributions
The list of Registered Distributions and platforms that have been reqistered against the CGL specification.

Registration
The 5.0 requirements and gaps are published as a single PDF document in the Carrier Grade Linux Specifications - Released Specifications section. Registrations can be done against the current specification, 5.0, by following the link below.

As with previous releases of the specification, the registration disclosure is a self-administered process. Linux distribution and platform vendors provide the disclosure information on their site and this public disclosure information is owned and maintained by each vendor. Registrants should make full public disclosure by filling out the registration template and mailing it to the lf_cgl_registration mailing list for review by the CGL technical board. Once approved an notification will be sent out to the lf_carrier mailing list announcing the new registration. Once completed, registrations may describe their product as "CGL Registered".

The Linux Foundation does not endorse or validate the veracity of the registration disclosure data.

Announcements
As of Wednesday, April 4, 2011 it is possible for Linux vendors to register their products for compliance with Version 5.0 of the Carrier Grade Linux (CGL) Requirements Definition. Linux vendors wishing to register should download the registration template and fill out the template based on the CGL Registration Process (.PDF). Vendors will host their registration results on their websites with the CGL workgroup placing links to them from the Registered Distributions page.

In The Press

Carrier Grade Linux 5.0 released with improved streaming media support
Stated Jim Zemlin, executive director at The Linux Foundation, "CGL today is a recognized industry standard on which the world's leading telecom companies rely to build their networks."

Carrier Grade Linux 5 Finalized
"Keep in mind, CGL is not just a specification writing entity, we also want to work with the upstream community to make sure our requirements are heard and met, that will be our focus for now," [Dan] Cauchy said.

Telecoms Networks - Carrier Grade Linux Comes of Age
The working group used the CGL 4.0 requirements as a starting point and split them into requirements that already exist in some mature open source project and requirements that do no[t] exist today.

The COTS Ecosystem - Strength in Numbers
Individually, the Linux Foundation Carrier Grade Linux Work Group is working on the next version of our specification. The goal this time around is to create a specification that will lead, over a reasonable amount of time, to actual code.
- Dan Cauchy, Chairman of Carrier Grade Linux Workgroup

Working Documents
Index Document
Satisfied Requirements Gaps Document New Gaps Submissions

Released Specifications

Mailing Lists

Conference Calls
Carrier Grade Linux conference calls are announced on the lf_carrier mailing list. For conference call information join the mailing list for next scheduled call.

Calendar
The CGL Workgroup is currently meeting in Shenzhen and Hong Kong. The next face-to-face meeting is tentatively scheduled for January 21-22, 2009. Details TBD.

Requirements

Index

Governance

General
The Governance of CGL will begin very lightweight. If contentious issues arise, we can move to a heavier-weight structure, such as that used by the LSB.

The workgroup is led by one or more chairpersons, who are appointed by the LF Executive Director with the advice of the workgroup.

Requirements Gathering

New requirements will be considered for future CGL documentation and they will come from these sources:

  • The CGL Workgroup
  • Network Equipment Providers (NEPs)
  • Carriers
  • SCOPE (an alliance of NEPs and Carriers)

CGL/SCOPE Relationship
As an alliance of Carriers, NEPs, and equipment providers, the SCOPE Alliance is a primary source of requirements for the CGL workgroup.

Documentation Strategy

Satisfied Requirements

The Linux Community (Upstream)

Upstream

The Linux community (also known as "upstream") works via collaborative, open development.

Syndicate content