Hi,
Updated case for modules attached.
| >From the discussion so far, mod_dtrace sounds clearly Volatile given
| that it is early and experimental and expected to change quickly. On
| mod_fcgid I don't have enough info; mod_security and mod_jk are
| well-known and widely used and we probably want to encourage their use
| in OpenSolaris.
|
| Ultimately the "project team" needs to understand the upstream
| component & their delivery history enough to weight all these pros &
| cons and determine how the project team will handle version upgrades
| if upstream incompatibilities occur.
| A key point is that the stability guarantee is from the project team
| integrating into OpenSolaris, not from the upstream community. Of
| course, the practices of the upstream community are a very important
| factor to consider, but not the only one.
I am going with Uncommitted only for mod_security as they had given a
strong assurance.
As for the rest, I hope we can upgrade their stability by considering
their individual cases later (depending also on the usage patterns and
feedback from customers in solaris).
rahul
--
1. e4 _
-------------- next part --------------
Additional Apache Modules
13 December 2007
1. Summary and motivation
1.1. Introduction
This FastTrack delivers Apache modules mod_jk, mod_fcgid,
mod_security and mod_dtrace to the Apache2 in OpenSolaris.
Modules allow Apache to integrate and provide functionality
during runtime that were not available during compile time.
This project integrates the most recent stable releases of
mod_jk[1] tomcat-connectors-1.2.25, mod_fcgid[2] 2.2,
mod_security[3] 2.1.3 and mod_dtrace[4] 0.3a
This case seeks Minor Release Binding.
2. Technical issues
2.1. Key objects
/usr/apache2/2.2/libexec/mod_jk.so
/usr/apache2/2.2/libexec/mod_fcgid.so
/usr/apache2/2.2/libexec/mod_security2.so
/usr/apache2/2.2/libexec/mod_dtrace.so
/usr/apache2/2.2/libexec/${ISAINFO}/mod_jk.so
/usr/apache2/2.2/libexec/${ISAINFO}/mod_fcgid.so
/usr/apache2/2.2/libexec/${ISAINFO}/mod_security2.so
/usr/apache2/2.2/libexec/${ISAINFO}/mod_dtrace.so
2.2 Versioning
mod_jk, mod_fcgid, mod_security and mod_dtrace have a single active
release. (There was a module named mod_jk2 which was deprecated. It
was not the successor to mod_jk.)
It is not possible to query the modules to find out their
versions. The only way to do that is to look at the package
description for the package including it.
2.2 Directory Naming and Structure
This project delivers the shared libraries of 32 bit and 64 bit
into /usr/apache2/2.2/libexec and /usr/apache2/2.2/libexec/${ISAINFO}/
directories of apache. This is in keeping with the approach taken
by the Apache2 integration project for OpenSolaris (PSARC/2007/586).
3. Documentation
The modules mod_jk, mod_fcgid, mod_security and mod_dtrace do not
install documentation into apache though they come with some
documentation in their source. The recommended way to access their
documentation is to look at their websites (mod_fcgid[5] ,mod_jk[6],
mod_security[7] and mod_dtrace[8] ). A list of external apache modules
that has been added and their corresponding sites will be part of the
release document.
4. Packaging and Delivery
The modules will be delivered under the cluster SUNWCapch22m. This
cluster consists of SUNWapch22m-fcgid, SUNWapch22m-jk,
SUNWapch22m-security and SUNWapch22m-dtrace respectively.
5. Interfaces
5.1. Interface Stability
The interface stability of each component is described as Volatile
as these are controled by external organizations over which Sun
has no control. The specific researches regarding stability of
each module are captured below.
5.1.1 mod_jk
The mod_jk developers will try to keep the releases of 1.2.X
line compatible with each other. But this is not guaranteed in
case of new features that may need to be retracted due to some
bugs or vulnerabilities.
5.1.2 mod_security
The mod_security developers will keep the compatibility
between releases of the same major number. (ie 2.y.z with 2 being
the major number.) But there is no guarantee that meaning of a
rule set (configuration directive) would be exactly the same
across any two releases.
5.1.3 mod_fcgid
There were no commitments from mod_fcgid developers in this
regard. (The mod_fcgid does not seem to have broken the
configuration compatibility with any of its earlier releases
yet [9] but is in very active developement)
5.1.4 mod_dtrace
The mod_dtrace has had just two releases (0.2a and 0.3a) and
is possibly very unstable.
5.2. Imported Interfaces
These Apache modules imports interfaces from
NAME STABILITY NOTES
Apache2 Uncommitted PSARC/2007/586/
LDAP Evolving PSARC/2000/362/
PCRE Uncommitted PSARC/2007/164/
SUNWlxml Committed PSARC/2001/175/
Dtrace Uncommitted PSARC/2001/466/
5.3. Exported Interfaces
NAME STABILITY
/usr/apache2/2.2/libexec/mod_jk.so Volatile
/usr/apache2/2.2/libexec/mod_fcgid.so Volatile
/usr/apache2/2.2/libexec/mod_security.so Uncommitted
/usr/apache2/2.2/libexec/mod_dtrace.so Volatile
/usr/apache2/2.2/libexec/${ISAINFO}/mod_jk.so Volatile
/usr/apache2/2.2/libexec/${ISAINFO}/mod_fcgid.so Volatile
/usr/apache2/2.2/libexec/${ISAINFO}/mod_security.so Uncommitted
/usr/apache2/2.2/libexec/${ISAINFO}/mod_dtrace.so Volatile
6. References
1. http://fastcgi.coremail.cn/
2. http://tomcat.apache.org/connectors-doc/
3. http://www.modsecurity.org/projects/modsecurity/apache/index.html
4. http://prefetch.net/projects/apache_modtrace/index.html
5. http://fastcgi.coremail.cn/doc.htm
6. http://tomcat.apache.org/connectors-doc/generic_howto/quick.html
7. http://www.modsecurity.org/documentation/index.html
8. http://prefetch.net/projects/apache_modtrace/mod_dtrace.c
9. http://fastcgi.coremail.cn/download.htm
