- 1 CGL Requirements Definition Documents - V3.2
- 2 CGL Requirements Definition Documents - V3.1
- 3 Clustering White Papers - V3.1
- 4 CGL Use Cases - V3.1
- 5 CGL Requirements Definition Documents - V3.0 (Technology Release)
- 6 CGL Requirements Definition Documents - V2.0.2
- 7 CGL Requirements Definition Documents - V1.1
CGL Requirements Definition Documents - V3.2
The CGL 3.2 Requirement Document was released on February 14, 2006. The CGL 3.2 will be available for registration starting February 27, 2006. The registration process of the CGL 3.2 will be published by February 27, 2006. Please send comments on any of these documents to the lf_carrier mailing list.
- The CGL V3.2 requirements documents define the next generation Linux for carrier grade implementations. This document gives a summary of the documents in the V3.2 document set (Availability, Serviceability, Performance, Clustering, Standards, Hardware and Security).
- Availability requirements apply to the Linux kernel, core libraries, and tools essential to a carrier-grade system. These availability requirements are related to single system availability.
- Serviceability requirements define the tools and methods used by system administrators to manage, install, maintain, upgrade, and monitor a carrier grade system.
- Performance requirements have a significant bearing on application performance. Carrier grade applications have some unique requirements, although they also share many needs with more general applications.
- Clustering requirements are aimed at supporting clustered applications in a carrier-grade environment as an effective way to achieve highly available services inside a network element.
Clustering Development Guideline An analysis of open source cluster-related projects that address CGL requirements.
- Standards requirements cover the intersections of the OSDL CGL requirements with those of "recognized" standards bodies, such as POSIX, IETF, and DMTF. This document serves as a reference for the standards referred to in the CGL 3.2 functional requirements.
- The telecommunication industry is migrating from proprietary platforms toward a commercial off the shelf (COTS) building blocks infrastructure. Important hardware building blocks for carrier grade systems and the open source software needed to support this hardware are identified in this document.
- The security objectives and requirements in this document are aimed at analyzing and mitigating threats and to improve resiliency to attacks on CGL systems.
CGL Requirements Definition Documents - V3.1
The CGL 3.1 Requirement Document was released in June 2005. It is the third major release of the CGL Requirement Document 2.0 and 1.1. Early 2005, the CGL working group has released a "Technology Release" versioned 3.0, which was just meant as a preview of the ongoing progress with the CGL requirements. Development of 3.1 defined capabilities is ongoing. The CGL 3.1 is not available for registration. Instead, you can register for CGL 3.2.
Clustering White Papers - V3.1
The Clustering White Papers are contributions from CGL participants. These white papers were used as the basis for discussions when the CGL working group was developing the CGL clustering model.
CGL Use Cases - V3.1
A use case explains the usage model of a particular requirement, in a carrier environment, as well as why it is needed in the CGL specifications.
CGL Requirements Definition Documents - V3.0 (Technology Release)
CGL Requirements Definition Documents - V2.0.2
Carrier Grade Linux Requirements Definition V2.0.2 (739K)(pdf) -- The CGL V2.0.2 requirements document defines next-generation Linux for carrier-grade implementations. The CGL 2.0.2 is available for registration.
CGL Requirements Definition Documents - V1.1
- This is early version of the CGL Requirements Definition. It is a retired document since the publication of CGL V2.0.2 and later versions.