Todd C. Davis
These are my opinions and absolutely not official opinions of Intel Corp.
-----Original Message-----
From: Ken McDonell [mailto:kenmcd@xxxxxxxxxxxxxxxxx]
Sent: Tuesday, October 15, 2002 2:21 PM
To: pcp@xxxxxxxxxxx
Subject: PCP QA Suite to be Open Sourced
I have arranged for the PCP QA Suite to be made available outside SGI
under some (TBD) Open Source license.
I'd like input from those who have expressed an interest in this area,
specificially to discuss (off the list, since others probably do not
care) the options for:
1. splitting the tests that apply to the open source parts of PCP from
the proprietary parts of PCP
[Todd Davis] This is a large problem that needs to be broken down into
smaller manageable units. For instance:
1. Validation of the PMAPI
a. PMDA library interfaces
b. metric value functions
c. instance domains & profiles
d. PMNS functions
c. archive logging
d. context functions
e. miscellaneous functions
2. tests for correctness of the PMDA's metrics
- contributed by PDMA developers?
3. Validate the command line utilities
a. functional breakdown similar/parallel to PMAPI validation
b. validation of command line options
c. stress or load tests
d. fault injection tests
2. gatekeeper and takeback logistics
[Todd Davis] A site like SourceForge that provides source control services
could be used in the development of these test suites so trusted
contributors can freely maintain test code.
3. the specific open source license to be used
[Todd Davis] The preferred license at Intel is BSD but this is decision that
your corporate lawyers must be comfortable with.
4. developing documentation to guide the evolution of the suite and
the creation of new tests
[Todd Davis] The Open Source Development Lab's Carrier Grade Linux
Enhancements validation site (http://developer.osdl.org/validation/) has a
validation framework paper that could be used as a starting point.
If you are interested, and willing to participate in this discussion,
please let me know.
|