From: Takashi Ikebe <ikebe.takashi@lab.ntt.co.jp>
To: linux-kernel@vger.kernel.org
Subject: Carrier Grade Linux 3.0 availability draft announcement
Date: Tue, 08 Jun 2004 13:23:52 +0900 [thread overview]
Message-ID: <40C53F58.1060907@lab.ntt.co.jp> (raw)
Hello.
I wanted to let this mailing list know about the availability of an
early public draft of the Carrier Grade Linux v3.0 Availability
specification, available at
http://www.osdl.org/docs/cgl_availability_req_definition___v30.pdf
The requirements in this document are aimed at supporting
serviceability of a network element in a carrier-grade environment.
I acknowledge that the requirements in this draft are being
implemented in a variety of ways and many of the requirements in this
document exist in current implementations. I am contacting this
mailing list because I believe your projects may meet some of the
requirements and we'd like to solicit feedback.
Again, this is an early draft document of the v3.0 availability
requirements spec. Past OSDL Carrier Grade Linux technical documents
have contained all requirements in a single document. For OSDL CGL
v3.0 draft releases, we are releasing them as more granular sections,
roughly split on functional boundaries. These boundaries are
Standards, Serviceability, Clustering, Hardware, Performance,
Security, and Availability (this document).
More information on Carrier Grade Linux and the Carrier Grade Linux
Working Group can be found at
http://osdl.org/lab_activities/carrier_grade_linux/.
Feel free to direct any comments on the spec to me directly at
ikebe.takashi@lab.ntt.co.jp or to our mailing list at
cgl_discussion@osdl.org.
--
Takashi Ikebe
NTT Network Service Systems Laboratories
9-11, Midori-Cho 3-Chome Musashino-Shi,
Tokyo 180-8585 Japan
Tel : +81 422 59 4246, Fax : +81 422 60 4012
e-mail : ikebe.takashi@lab.ntt.co.jp
reply other threads:[~2004-06-08 4:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40C53F58.1060907@lab.ntt.co.jp \
--to=ikebe.takashi@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox