Jyri Virkki wrote:
> 2. Technical issues
>
> 2.1. Key objects
>
> /usr/collectd4/lib/collectd
> From collectd's man page:
> collectd is a daemon that receives system statistics and makes
> them available in a number of ways. The main daemon itself
> doesn't have any real functionality apart from loading,
> querying and submitting to plugins.
Is collectd really that huge and important that it deserves its own
place under /usr ? Do Linux distros do this (I doubt it because the FHS
and LSB both very much frown on the new dirs in /usr).
Can this be:
/usr/lib/collectd4 instead ?
> /etc/collectd4/collectd.conf
> The default collectd configuration file.
That seems a reasonable place.
> Do note that this project won't deliver collectdmon. This
> wrapper will not be required since SMF will take care of
> starting and monitoring the collectd daemon.
Seems reasonable but is it worth delivering it anyway incase someone
needs to start it outside of SMF for some reason ?
> * ZFS ARC
What ZFS interfaces are consumed to gather this information ?
> 2.4 Directory Naming and Structure
>
> The proposed directory layout for collectd is:
>
> /usr/collectd4
> /lib
> /man
> /share
Hidding the man pages away outside of /usr/share/man isn't good, man
pages should always be in /usr/share/man unless there are multiple
incompatible versions of something installed at the same time.
Do we know we will have collectd4 and collectd5 both installed ? If not
I highly recommend the man pages go in /usr/share/man, the shared stuff
for collectd would go in /usr/share/collectd4 and the lib stuff in
/usr/lib/collectd4
> 2.6 Log File
>
> The log File will be located in /var/collectd4/logs and will
> be named collectd.log. The default log level is info and can
> be changed by modifying the main configuration file.
What uid/gid owns the logs directory ?
> 4. Packaging and Delivery
>
> We propose to package collectd under the following packages:
>
> SUNWcollectd4u - [usr] Server package (including collectd
> daemon, loadable plugins, man pages)
> SUNWcollectd4r - [root] (config files, smf files)
As I've said in other cases lets stop pretending we need split usr and
root packages unless the project is going to be delivered in Solaris 10
as well as OpenSolaris.
> 5.3. Exported Interfaces
>
> NAME STABILITY NOTES
>
> -----------------------------------------------------------------------
> SUNWcollectd4r Committed package
> SUNWcollectd4u Committed package
These need to be Volatile as they are going to change before Solaris
Next delivers and even on OpenSolaris 2010.03 there will be a single
SUNWcollectd4 package.
> /lib/svc/method/collectd4-svc Project Private SMF svc method
> svc:/application/monitoring/collectd4:default
> Committed FMRI
> /var/svc/manifest/application/monitoring/collectd4.xml
> Project Private SMF Manifest
Glad to see a case that listed all these out correctly.
--
Darren J Moffat
