[I've Cc'd back to the wider list, as this is a heas up on the QA
stuff and addresses a broader issue]
On Thu, 24 Oct 2002, Alan Hoyt wrote:
> Ken,
>
> Finally got to the QA scripts - I scanned the scripts and noticed
> platform related conditionals (i.e. the $PCP_PLATFORM checks) and other
> platform specifics (chkconfig, etc.). This brings me to the crux of my
> question:
>
> We're porting PCP to Solaris which basically means writing the OS
> specific /proc stuff. I know this constitutes "reinventing the wheel"
> since SGI already ported PCP to Solaris (among other operating systems).
We did not port PCP to Solaris ... some other folks outside SGI have been
working on this on and off for some time.
> Do you want:
>
> * Solaris specific PCP patches (it runs but as stated above, /proc needs
> serious work)
We'd like to keep the common PCP code generic and building on all
platforms, so patches for any platform that touch the libraries, the
utilities, etc. should be candidates for inclusion back in the common
code base ... we already have avested interest in continuing to release
products from this code base that must work on
- 32-bit and 64-bit IRIX on MIPS
- Linux on ia32
- Linux on ia64
So the infrastructure in the code and the build environment is already
in place to support multiple platforms.
Since this code is also used to make the IRIX proprietary version,
we'd need copyright assignment for patches in this area, but I don't
expect the changes to be substantial.
For the PMDA for another host O/S, like Solaris, I'd be happy to include
the code in the open source version of PCP on oss.sgi.com, but would be
looking for someone else to take on the effective gatekeeper role. We'd
avoid forking the code base, and align the gatekeeper load more
closely to those with vested interests.
> * Solaris specific QA suite patches
The QA suite is almost ready to go ... I've separated all the components
into an open source bucket and a proprietary bucket ... just need to throw
some instructions together and this will appear in the download area on
oss.sgi.com as a tarball.
The QA suite includes 2 conditional mechanisms ...
- each test belongs to one or more groups, and you can include or
exclude whole groups from the set of tests to be run at any one
time
- there is a "not run" protocol, and each test retains the right to
sniff out the environment and decide that this is not a good place
to even try to run this test.
I'd strongly recommend using both schemes ... and then there is no
problem with platform-specific QA tests being added to the mix.
> It's not clear to me how this would impact code management/tree
> management/gatekeeper, etc.. from your perspective. We want/need to
> feed these changes back to the community so any feedback is greatly
> appreciated.
Hope this addresses your issues.
|