From sacadmin Thu Feb 21 10:34:23 2008 Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1LIYNY4021622; Thu, 21 Feb 2008 10:34:23 -0800 (PST) Received: (from johnf@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id m1LIYNJV021618; Thu, 21 Feb 2008 10:34:23 -0800 (PST) Date: Thu, 21 Feb 2008 10:34:23 -0800 (PST) From: John Fischer Message-Id: <200802211834.m1LIYNJV021618@sac.sfbay.sun.com> To: LSARC-record@sac.sfbay.sun.com Subject: RRDTool [LSARC/2008/129 FastTrack timeout 02/28/2008] Status: RO Content-Length: 554 Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: RRDTool 1.2. Name of Document Author/Supplier: Author: Stephen Brown 1.3 Date of This Document: 21 February, 2008 4. Technical Description See the case directory for more detail 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: JDS - Gnome 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From John.Fischer@sun.com Thu Feb 21 11:02:35 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1LJ2Ymh023069 for ; Thu, 21 Feb 2008 11:02:35 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m1LJ2NOE012782 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Fri, 22 Feb 2008 03:02:33 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JWL0070BRK8CU00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 21 Feb 2008 12:02:32 -0700 (MST) Received: from brmea-mail-3.sun.com ([192.18.98.34]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JWL001XERK7GX40@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 21 Feb 2008 12:02:31 -0700 (MST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m1LJ2V84019560 for ; Thu, 21 Feb 2008 19:02:31 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JWL00901RBY0200@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 21 Feb 2008 12:02:31 -0700 (MST) Received: from 129.145.154.84 ([129.145.154.84]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JWL00EVTRJWTC10@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 21 Feb 2008 12:02:21 -0700 (MST) Date: Thu, 21 Feb 2008 11:02:20 -0800 From: John Fischer Subject: LSARC/2008/129 - RRDTool Sender: John.Fischer@sun.com To: lsarc-ext@sun.com Cc: John Fischer , Stephen Browne Reply-to: John.Fischer@sun.com Message-id: <1203620539.63061.357.camel@sr1-umpk-34> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301c Content-type: multipart/mixed; boundary="Boundary_(ID_1Nl/2/OFEmb7LDcZVQB8NQ)" X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 7332 --Boundary_(ID_1Nl/2/OFEmb7LDcZVQB8NQ) Content-type: text/plain; charset=ASCII Content-transfer-encoding: 7BIT LSARC, I am sponsoring this fast track for Stephen Brown of the JDS - Gnome team in Dublin, Ireland. I have set the timer for Thursday, February 21st, 2008. The case directory contains this proposal as well as various documentation and the header file. This project integrates the Open Source project known as RRDTool into a Minor release of Solaris. RRDTool lets you log and analyze the data you gather from all kinds of data-sources and quickly generate graphical representations of the data definable over a time period. Thanks, John --Boundary_(ID_1Nl/2/OFEmb7LDcZVQB8NQ) Content-type: text/plain; charset=ASCII; name=proposal.txt Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=proposal.txt 1. Introduction 1.1. Project/Component Working Name: RRDTool 1.2. Name of Document Author/Supplier: Stephen Browne 1.3. Date of This Document: 02/15/08 1.3.1. Date this project was conceived: 1999 - community inception 2/2008 - Sun inception 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: robert.odea@sun.com 1.4.4. The name of your business unit: OPG / OpenSource. 1.5. Email Aliases: 1.5.1. Responsible Manager: leo.binchy@sun.com 1.5.2. Responsible Engineer: stephen.browne@sun.com 1.5.3. Marketing Manager: dan.roberts@sun.com 1.5.4. Interest List: desktop-discuss@opensolaris.org 4. Technical Description: 4.1. Details: It is pretty easy to gather status information from all sorts of things, ranging from the temperature in your office to the number of octets which have passed through the FDDI interface of your router. But it is not so trivial to store this data in an efficient and systematic manner. This is where RRDtool comes in handy. It lets you log and analyze the data you gather from all kinds of data-sources. The data analysis part of RRDtool is based on the ability to quickly generate graphical representations of the data values collected over a definable time period. So RRDtool is a database but there are distinct differences between RRDtool databases and other databases as listed below: * RRDtool stores data; that makes it a back-end tool. The RRDtool command set allows the creation of graphs; that makes it a front-end tool as well. Other databases just store data and can not create graphs. * In case of linear databases, new data gets appended at the bottom of the database table. Thus its size keeps on increasing, whereas the size of an RRDtool database is determined at creation time. Imagine an RRDtool database as the perimeter of a circle. Data is added along the perimeter. When new data reaches the starting point, it overwrites existing data. This way, the size of an RRDtool database always remains constant. The name "Round Robin" stems from this behavior. * Other databases store the values as supplied. RRDtool can be configured to calculate the rate of change from the previous to the current value and store this information instead. * Other databases get updated when values are supplied. The RRDtool database is structured in such a way that it needs data at predefined time intervals. If it does not get a new value during the interval, it stores an UNKNOWN value for that interval. So, when using the RRDtool database, it is imperative to use scripts that run at regular intervals to ensure a constant data flow to update the RRDtool database. RRDtool is designed to store time series of data. With every data update, an associated time stamp is stored. Time is always expressed in seconds passed since epoch (01-01-1970). It comes with a command set to carry out various operations on RRD databases. The version being integrated is 1.2.19 4.2. Bug/RFE Number(s): None. 4.3. In Scope: See above. 4.4. Out of Scope: See above. 4.5. Interfaces: -------------------------------------------------------------------- Exported Stability Comments -------------------------------------------------------------------- rrdtool Uncommitted main binary with many create subcommand subcommands/functions dump subcommand documented in rrd*.1 fetch subcommand manpages, installed graph subcommand in /usr/bin, note the info subcommand subcommands are internal last subcommand to rrdtool (i.e., no lastupdate subcommand additional bits installed). resize subcommand restore subcommand tune subcommand xport subcommand rrdcgi Uncommitted web cgi script interpreter parsing for tags documented in rrdcgi.1 man page, installed in /usr/bin rrdupdate Uncommitted convenience binary for rrdtool update, installed in /usr/bin librrd.so.2.0.9 Uncommitted lib implementation of RRD, installed in /usr/lib librrd.so Uncommitted Link target=librrd.so.2.0.9 librrd.so.2 Uncommitted Link target=librrd.so.2.0.9 librrd_th.so.2.0.8 Uncommitted Thread safe API for above, installed in /usr/lib librrd_th.so Uncommitted Link target=librrd_th.so.2.0.8 librrd_th.so.2 Uncommitted Link target=librrd_th.so.2.0.8 tclrrd1.2.19.so Uncommitted TCL bindings for RRD, installed in /usr/lib rrd.h Uncommitted header file, installed in /usr/include SUNWrrdtool Uncommitted SVr4 Package -------------------------------------------------------------------- Imported Stability Comments -------------------------------------------------------------------- /usr/lib/libpng12.so.0 Uncommitted LSARC/2003/085 /usr/lib/libz.so.1 Committed PSARC/2006/537 /usr/lib/libart_lgpl_2.so.2 Volatile LSARC/2006/202 /usr/sfw/lib/libfreetype.so.6 Volatile LSARC/2002/291 /usr/sfw/lib/libgcc_s.so.1 Volatile PSARC/2004/742 4.6. Doc Impact: Man pages are provided that both detail the rrdtool functions and provide tutorials for their use. 4.7. Admin/Config Impact: None. 4.8. HA Impact: None. 4.9. I18N/L10N Impact: The JDS team and the G11N are working together to evaluation and provide I18N/L10N support 4.10. Packaging & Delivery: Adds new package, SUNWrrdtool, approx 2.2 MB. Package will go into SUNWCall, SUNWCXall and SUNWCprog clusters. 4.11. Security Impact: None. 4.12. Dependencies: None. 5. Reference Documents: http://oss.oetiker.ch/rrdtool/ --Boundary_(ID_1Nl/2/OFEmb7LDcZVQB8NQ)-- From Lloyd.Chambers@sun.com Fri Feb 22 11:01:08 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1MJ17S0010387 for ; Fri, 22 Feb 2008 11:01:08 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m1MJ0veJ004331 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Fri, 22 Feb 2008 19:01:06 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JWN00C3BM5SG500@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 22 Feb 2008 11:01:05 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JWN001ICM5K85C0@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 22 Feb 2008 11:00:56 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1MJ0uGu007577 for ; Fri, 22 Feb 2008 11:00:56 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JWN00L01LJXNT00@fe-sfbay-09.sun.com> (original mail from Lloyd.Chambers@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 22 Feb 2008 11:00:56 -0800 (PST) Received: from [192.168.1.8] ([129.150.18.151]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JWN00IOXM5ANX10@fe-sfbay-09.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 22 Feb 2008 11:00:48 -0800 (PST) Date: Fri, 22 Feb 2008 11:00:46 -0800 From: Lloyd L Chambers Subject: Re: LSARC/2008/129 - RRDTool In-reply-to: <1203620539.63061.357.camel@sr1-umpk-34> Sender: Lloyd.Chambers@sun.com To: John.Fischer@sun.com Cc: lsarc-ext@sun.com, Stephen Browne Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.919.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <1203620539.63061.357.camel@sr1-umpk-34> Status: RO Content-Length: 7381 John, llc-01 Are the CLI interfaces CLIP compliant? The interface table says they're in man pages, I'm not sure where to find those (though I don't necessarily need to). llc02 Are there any security issues with rrdcgi? llc03 Who would use rrd.h? End users? Lloyd ---------------- 1. Introduction 1.1. Project/Component Working Name: RRDTool 1.2. Name of Document Author/Supplier: Stephen Browne 1.3. Date of This Document: 02/15/08 1.3.1. Date this project was conceived: 1999 - community inception 2/2008 - Sun inception 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: robert.odea@sun.com 1.4.4. The name of your business unit: OPG / OpenSource. 1.5. Email Aliases: 1.5.1. Responsible Manager: leo.binchy@sun.com 1.5.2. Responsible Engineer: stephen.browne@sun.com 1.5.3. Marketing Manager: dan.roberts@sun.com 1.5.4. Interest List: desktop-discuss@opensolaris.org 4. Technical Description: 4.1. Details: It is pretty easy to gather status information from all sorts of things, ranging from the temperature in your office to the number of octets which have passed through the FDDI interface of your router. But it is not so trivial to store this data in an efficient and systematic manner. This is where RRDtool comes in handy. It lets you log and analyze the data you gather from all kinds of data-sources. The data analysis part of RRDtool is based on the ability to quickly generate graphical representations of the data values collected over a definable time period. So RRDtool is a database but there are distinct differences between RRDtool databases and other databases as listed below: * RRDtool stores data; that makes it a back-end tool. The RRDtool command set allows the creation of graphs; that makes it a front-end tool as well. Other databases just store data and can not create graphs. * In case of linear databases, new data gets appended at the bottom of the database table. Thus its size keeps on increasing, whereas the size of an RRDtool database is determined at creation time. Imagine an RRDtool database as the perimeter of a circle. Data is added along the perimeter. When new data reaches the starting point, it overwrites existing data. This way, the size of an RRDtool database always remains constant. The name "Round Robin" stems from this behavior. * Other databases store the values as supplied. RRDtool can be configured to calculate the rate of change from the previous to the current value and store this information instead. * Other databases get updated when values are supplied. The RRDtool database is structured in such a way that it needs data at predefined time intervals. If it does not get a new value during the interval, it stores an UNKNOWN value for that interval. So, when using the RRDtool database, it is imperative to use scripts that run at regular intervals to ensure a constant data flow to update the RRDtool database. RRDtool is designed to store time series of data. With every data update, an associated time stamp is stored. Time is always expressed in seconds passed since epoch (01-01-1970). It comes with a command set to carry out various operations on RRD databases. The version being integrated is 1.2.19 4.2. Bug/RFE Number(s): None. 4.3. In Scope: See above. 4.4. Out of Scope: See above. 4.5. Interfaces: -------------------------------------------------------------------- Exported Stability Comments -------------------------------------------------------------------- rrdtool Uncommitted main binary with many create subcommand subcommands/functions dump subcommand documented in rrd*.1 fetch subcommand manpages, installed graph subcommand in /usr/bin, note the info subcommand subcommands are internal last subcommand to rrdtool (i.e., no lastupdate subcommand additional bits installed). resize subcommand restore subcommand tune subcommand xport subcommand rrdcgi Uncommitted web cgi script interpreter parsing for tags documented in rrdcgi.1 man page, installed in /usr/bin rrdupdate Uncommitted convenience binary for rrdtool update, installed in /usr/bin librrd.so.2.0.9 Uncommitted lib implementation of RRD, installed in /usr/lib librrd.so Uncommitted Link target=librrd.so.2.0.9 librrd.so.2 Uncommitted Link target=librrd.so.2.0.9 librrd_th.so.2.0.8 Uncommitted Thread safe API for above, installed in /usr/lib librrd_th.so Uncommitted Link target=librrd_th.so.2.0.8 librrd_th.so.2 Uncommitted Link target=librrd_th.so.2.0.8 tclrrd1.2.19.so Uncommitted TCL bindings for RRD, installed in /usr/lib rrd.h Uncommitted header file, installed in /usr/include SUNWrrdtool Uncommitted SVr4 Package -------------------------------------------------------------------- Imported Stability Comments -------------------------------------------------------------------- /usr/lib/libpng12.so.0 Uncommitted LSARC/2003/085 /usr/lib/libz.so.1 Committed PSARC/2006/537 /usr/lib/libart_lgpl_2.so.2 Volatile LSARC/2006/202 /usr/sfw/lib/libfreetype.so.6 Volatile LSARC/2002/291 /usr/sfw/lib/libgcc_s.so.1 Volatile PSARC/2004/742 4.6. Doc Impact: Man pages are provided that both detail the rrdtool functions and provide tutorials for their use. 4.7. Admin/Config Impact: None. 4.8. HA Impact: None. 4.9. I18N/L10N Impact: The JDS team and the G11N are working together to evaluation and provide I18N/L10N support 4.10. Packaging & Delivery: Adds new package, SUNWrrdtool, approx 2.2 MB. Package will go into SUNWCall, SUNWCXall and SUNWCprog clusters. 4.11. Security Impact: None. 4.12. Dependencies: None. 5. Reference Documents: http://oss.oetiker.ch/rrdtool/ On Feb 21, 2008, at 11:02 AM, John Fischer wrote: > LSARC, > > I am sponsoring this fast track for Stephen Brown of > the JDS - Gnome team in Dublin, Ireland. I have set > the timer for Thursday, February 21st, 2008. The > case directory contains this proposal as well as various > documentation and the header file. > > This project integrates the Open Source project known > as RRDTool into a Minor release of Solaris. RRDTool > lets you log and analyze the data you gather from all > kinds of data-sources and quickly generate graphical > representations of the data definable over a time > period. > > Thanks, > > John > > --- Lloyd L Chambers lloyd.chambers@sun.com Sun Microsystems, Inc From Alan.Coopersmith@sun.com Fri Feb 22 11:29:56 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1MJTtZo011212 for ; Fri, 22 Feb 2008 11:29:55 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m1MJTXZG028495 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Sat, 23 Feb 2008 03:29:54 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JWN0070DNHSZE00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 22 Feb 2008 12:29:52 -0700 (MST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JWN00734NHRUV00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 22 Feb 2008 12:29:51 -0700 (MST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1MJTpQ2004459 for ; Fri, 22 Feb 2008 11:29:51 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JWN00901NG4XB00@fe-sfbay-10.sun.com> (original mail from Alan.Coopersmith@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 22 Feb 2008 11:29:51 -0800 (PST) Received: from [129.146.108.211] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JWN00GHZNHQH0E0@fe-sfbay-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 22 Feb 2008 11:29:50 -0800 (PST) Date: Fri, 22 Feb 2008 11:29:50 -0800 From: Alan Coopersmith Subject: Re: LSARC/2008/129 - RRDTool In-reply-to: Sender: Alan.Coopersmith@sun.com To: John.Fischer@sun.com, lsarc-ext@sun.com Cc: Stephen Browne Message-id: <47BF22AE.30704@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 X-Enigmail-Version: 0.95.1 References: <1203620539.63061.357.camel@sr1-umpk-34> User-Agent: Thunderbird 2.0.0.6 (X11/20071203) Status: RO Content-Length: 393 > /usr/sfw/lib/libfreetype.so.6 Volatile LSARC/2002/291 Just for the record, the stability of /usr/sfw/lib/libfreetype.so.6 is now Obsolete. The pathname /usr/lib/libfreetype.so.6 is Uncommitted, the API's provided in it are still Volatile. (See LSARC 2007/662.) -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - X Window System Engineering From John.Fischer@sun.com Mon Feb 25 11:55:51 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1PJtpOs022422 for ; Mon, 25 Feb 2008 11:55:51 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1PJto7r003974 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Mon, 25 Feb 2008 11:55:51 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JWT0050R8P1FX00@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 25 Feb 2008 11:55:49 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JWT00KVW8OZZ4D0@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 25 Feb 2008 11:55:47 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1PJtldg006619 for ; Mon, 25 Feb 2008 11:55:47 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JWT00C01868WY00@fe-sfbay-09.sun.com> (original mail from John.Fischer@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 25 Feb 2008 11:55:47 -0800 (PST) Received: from [192.168.10.6] ([24.10.86.139]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JWT00LEI8OYYKC0@fe-sfbay-09.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 25 Feb 2008 11:55:47 -0800 (PST) Date: Mon, 25 Feb 2008 11:55:36 -0800 From: John Fischer Subject: Re: LSARC/2008/129 - RRDTool In-reply-to: Sender: John.Fischer@sun.com To: Lloyd L Chambers Cc: lsarc-ext@sun.com, Stephen Browne Reply-to: John.Fischer@sun.com Message-id: <47C31D38.1080407@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <1203620539.63061.357.camel@sr1-umpk-34> User-Agent: Thunderbird 2.0.0.4 (X11/20070622) Status: RO Content-Length: 10193 Lloyd, Stephen can correct me on these answers as he is far more familiar with the project. John Lloyd L Chambers wrote: > John, > > llc-01 Are the CLI interfaces CLIP compliant? The interface table says > they're in man pages, I'm not sure where to find those (though I don't > necessarily need to). The man page is available via the case directory materials/docs which were converted to html files. I believe that they are CLIP compliant. The 'create' subcommand looks like: rrdtool create filename [--start|-b start time] [--step|-s step] \ [DS:ds-name:DST:dst arguments] [RRA:CF:cf arguments] The 'fetch' subcommand looks like: rrdtool fetch filename CF [--resolution|-r resolution] [--start|-s \ start] [--end|-e end] Thus it consistently fits into the rrdtool CLI environment. It also provides for both short and long CLIs. > llc02 Are there any security issues with rrdcgi? From the man page: rrdcgi is a sort of very limited script interpreter. Its purpose is to run as a cgi-program and parse a web page template containing special llc03 Who would use rrd.h? End users? rrd.h is for developers to use when creating an application. A very simple example follows: #include "rrd.h" int main (int argc,char** argv) { int i=rrd_update(argc,argv); return 0; } > Lloyd > > ---------------- > > 1. Introduction > 1.1. Project/Component Working Name: > > RRDTool > > 1.2. Name of Document Author/Supplier: > > Stephen Browne > > 1.3. Date of This Document: > > 02/15/08 > > 1.3.1. Date this project was conceived: > > 1999 - community inception > 2/2008 - Sun inception > > 1.4. Name of Major Document Customer(s)/Consumer(s): > > 1.4.1. The PAC or CPT you expect to review your project: > > Solaris PAC > > 1.4.2. The ARC(s) you expect to review your project: > > LSARC > > 1.4.3. The Director/VP who is "Sponsoring" this project: > > robert.odea@sun.com > > 1.4.4. The name of your business unit: > > OPG / OpenSource. > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: > > leo.binchy@sun.com > > 1.5.2. Responsible Engineer: > > stephen.browne@sun.com > > 1.5.3. Marketing Manager: > > dan.roberts@sun.com > > 1.5.4. Interest List: > > desktop-discuss@opensolaris.org > > 4. Technical Description: > 4.1. Details: > > It is pretty easy to gather status information from all sorts > of things, ranging from the temperature in your office to the > number of octets which have passed through the FDDI interface > of your router. But it is not so trivial to store this data in > an efficient and systematic manner. This is where RRDtool comes > in handy. It lets you log and analyze the data you gather from > all kinds of data-sources. The data analysis part of RRDtool is > based on the ability to quickly generate graphical representations > of the data values collected over a definable time period. > > So RRDtool is a database but there are distinct differences > between RRDtool databases and other databases as listed below: > > * RRDtool stores data; that makes it a back-end tool. > The RRDtool command set allows the creation of graphs; that > makes it a front-end tool as well. Other databases just store > data and can not create graphs. > * In case of linear databases, new data gets appended at the bottom > of the database table. Thus its size keeps on increasing, whereas > the size of an RRDtool database is determined at creation time. > Imagine an RRDtool database as the perimeter of a circle. Data is > added along the perimeter. When new data reaches the starting point, > it overwrites existing data. This way, the size of an RRDtool > database always remains constant. The name "Round Robin" stems > from this behavior. > * Other databases store the values as supplied. RRDtool can be > configured to calculate the rate of change from the previous to the > current value and store this information instead. > * Other databases get updated when values are supplied. The RRDtool > database is structured in such a way that it needs data at predefined > time intervals. If it does not get a new value during the interval, > it stores an UNKNOWN value for that interval. So, when using the > RRDtool database, it is imperative to use scripts that run at regular > intervals to ensure a constant data flow to update the RRDtool > database. > > RRDtool is designed to store time series of data. With every data > update, > an associated time stamp is stored. Time is always expressed in seconds > passed since epoch (01-01-1970). It comes with a command set to carry > out various operations on RRD databases. > > The version being integrated is 1.2.19 > > 4.2. Bug/RFE Number(s): > > None. > > 4.3. In Scope: > > See above. > > 4.4. Out of Scope: > > See above. > > 4.5. Interfaces: > > > -------------------------------------------------------------------- > Exported Stability Comments > > -------------------------------------------------------------------- > rrdtool Uncommitted main binary with many > create subcommand subcommands/functions > dump subcommand documented in rrd*.1 > fetch subcommand manpages, installed > graph subcommand in /usr/bin, note the > info subcommand subcommands are internal > last subcommand to rrdtool (i.e., no > lastupdate subcommand additional bits installed). > resize subcommand > restore subcommand > tune subcommand > xport subcommand > > rrdcgi Uncommitted web cgi script interpreter > parsing for tags documented > in rrdcgi.1 man page, > installed in /usr/bin > > rrdupdate Uncommitted convenience binary for > rrdtool update, installed > in /usr/bin > > librrd.so.2.0.9 Uncommitted lib implementation of > RRD, > installed in /usr/lib > > librrd.so Uncommitted Link target=librrd.so.2.0.9 > > librrd.so.2 Uncommitted Link target=librrd.so.2.0.9 > > librrd_th.so.2.0.8 Uncommitted Thread safe API for above, > installed in /usr/lib > > librrd_th.so Uncommitted Link > target=librrd_th.so.2.0.8 > > librrd_th.so.2 Uncommitted Link > target=librrd_th.so.2.0.8 > > tclrrd1.2.19.so Uncommitted TCL bindings for RRD, > installed in /usr/lib > > rrd.h Uncommitted header file, installed in > /usr/include > > SUNWrrdtool Uncommitted SVr4 Package > > > -------------------------------------------------------------------- > Imported Stability Comments > > -------------------------------------------------------------------- > /usr/lib/libpng12.so.0 Uncommitted LSARC/2003/085 > > /usr/lib/libz.so.1 Committed PSARC/2006/537 > > /usr/lib/libart_lgpl_2.so.2 Volatile LSARC/2006/202 > > /usr/sfw/lib/libfreetype.so.6 Volatile LSARC/2002/291 > > /usr/sfw/lib/libgcc_s.so.1 Volatile PSARC/2004/742 > > 4.6. Doc Impact: > > Man pages are provided that both detail the rrdtool functions > and provide > tutorials for their use. > > 4.7. Admin/Config Impact: > > None. > > 4.8. HA Impact: > > None. > > 4.9. I18N/L10N Impact: > > The JDS team and the G11N are working together to evaluation > and provide I18N/L10N support > > 4.10. Packaging & Delivery: > > Adds new package, SUNWrrdtool, approx 2.2 MB. > Package will go into SUNWCall, SUNWCXall and SUNWCprog clusters. > > 4.11. Security Impact: > > None. > > 4.12. Dependencies: > > None. > > 5. Reference Documents: > > http://oss.oetiker.ch/rrdtool/ > > > > On Feb 21, 2008, at 11:02 AM, John Fischer wrote: > >> LSARC, >> >> I am sponsoring this fast track for Stephen Brown of >> the JDS - Gnome team in Dublin, Ireland. I have set >> the timer for Thursday, February 21st, 2008. The >> case directory contains this proposal as well as various >> documentation and the header file. >> >> This project integrates the Open Source project known >> as RRDTool into a Minor release of Solaris. RRDTool >> lets you log and analyze the data you gather from all >> kinds of data-sources and quickly generate graphical >> representations of the data definable over a time >> period. >> >> Thanks, >> >> John >> >> > > --- > Lloyd L Chambers > lloyd.chambers@sun.com > Sun Microsystems, Inc > > > From John.Fischer@sun.com Tue Feb 26 10:30:41 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1QIUeCv009001 for ; Tue, 26 Feb 2008 10:30:40 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m1QIUcc4013230 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 26 Feb 2008 18:30:38 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JWU00107ZF2TR00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 26 Feb 2008 10:30:38 -0800 (PST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JWU00L2WZF1S030@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 26 Feb 2008 10:30:37 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m1QIUbhg028446 for ; Tue, 26 Feb 2008 18:30:37 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JWU00101Z4OIX00@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 26 Feb 2008 11:30:37 -0700 (MST) Received: from 129.145.154.84 ([129.145.154.84]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JWU00BMFZETI740@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 26 Feb 2008 11:30:30 -0700 (MST) Date: Tue, 26 Feb 2008 10:30:29 -0800 From: John Fischer Subject: Re: LSARC/2008/129 - RRDTool In-reply-to: <47C31D38.1080407@sun.com> Sender: John.Fischer@sun.com To: Stephen Browne Cc: lsarc-ext@sun.com Reply-to: John.Fischer@sun.com Message-id: <1204050629.27968.17.camel@sr1-umpk-34> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301c Content-type: text/plain Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <1203620539.63061.357.camel@sr1-umpk-34> <47C31D38.1080407@sun.com> Status: RO Content-Length: 10947 Stephen, This case was approved during ARC business today. Thanks, John On Mon, 2008-02-25 at 11:55, John Fischer wrote: > Lloyd, > > Stephen can correct me on these answers as he is far more familiar > with the project. > > John > > > Lloyd L Chambers wrote: > > John, > > > > llc-01 Are the CLI interfaces CLIP compliant? The interface table says > > they're in man pages, I'm not sure where to find those (though I don't > > necessarily need to). > > The man page is available via the case directory > materials/docs which were converted to html files. > I believe that they are CLIP compliant. The 'create' > subcommand looks like: > > rrdtool create filename [--start|-b start time] [--step|-s step] \ > [DS:ds-name:DST:dst arguments] [RRA:CF:cf arguments] > > The 'fetch' subcommand looks like: > > rrdtool fetch filename CF [--resolution|-r resolution] [--start|-s \ > start] [--end|-e end] > > Thus it consistently fits into the rrdtool CLI environment. It also > provides for both short and long CLIs. > > > llc02 Are there any security issues with rrdcgi? > > From the man page: > > rrdcgi is a sort of very limited script interpreter. Its purpose is to > run as a cgi-program and parse a web page template containing special > In the end it will printout a web page including the necessary CGI > headers. > > The man page is available via the case directory > materials/docs/rrdcgi.html. From your own FORM it shouldn't be a > problem but that does not prevent someone from connecting directly > to the cgi script. Thus as with any cgi scripts one must always > check the inputs for crazy values. So no additional security > issues other then what is already available via other cgi scripts. > > > llc03 Who would use rrd.h? End users? > > rrd.h is for developers to use when creating an application. > A very simple example follows: > > #include "rrd.h" > > int main (int argc,char** argv) > { > int i=rrd_update(argc,argv); > return 0; > } > > > Lloyd > > > > ---------------- > > > > 1. Introduction > > 1.1. Project/Component Working Name: > > > > RRDTool > > > > 1.2. Name of Document Author/Supplier: > > > > Stephen Browne > > > > 1.3. Date of This Document: > > > > 02/15/08 > > > > 1.3.1. Date this project was conceived: > > > > 1999 - community inception > > 2/2008 - Sun inception > > > > 1.4. Name of Major Document Customer(s)/Consumer(s): > > > > 1.4.1. The PAC or CPT you expect to review your project: > > > > Solaris PAC > > > > 1.4.2. The ARC(s) you expect to review your project: > > > > LSARC > > > > 1.4.3. The Director/VP who is "Sponsoring" this project: > > > > robert.odea@sun.com > > > > 1.4.4. The name of your business unit: > > > > OPG / OpenSource. > > > > 1.5. Email Aliases: > > 1.5.1. Responsible Manager: > > > > leo.binchy@sun.com > > > > 1.5.2. Responsible Engineer: > > > > stephen.browne@sun.com > > > > 1.5.3. Marketing Manager: > > > > dan.roberts@sun.com > > > > 1.5.4. Interest List: > > > > desktop-discuss@opensolaris.org > > > > 4. Technical Description: > > 4.1. Details: > > > > It is pretty easy to gather status information from all sorts > > of things, ranging from the temperature in your office to the > > number of octets which have passed through the FDDI interface > > of your router. But it is not so trivial to store this data in > > an efficient and systematic manner. This is where RRDtool comes > > in handy. It lets you log and analyze the data you gather from > > all kinds of data-sources. The data analysis part of RRDtool is > > based on the ability to quickly generate graphical representations > > of the data values collected over a definable time period. > > > > So RRDtool is a database but there are distinct differences > > between RRDtool databases and other databases as listed below: > > > > * RRDtool stores data; that makes it a back-end tool. > > The RRDtool command set allows the creation of graphs; that > > makes it a front-end tool as well. Other databases just store > > data and can not create graphs. > > * In case of linear databases, new data gets appended at the bottom > > of the database table. Thus its size keeps on increasing, whereas > > the size of an RRDtool database is determined at creation time. > > Imagine an RRDtool database as the perimeter of a circle. Data is > > added along the perimeter. When new data reaches the starting point, > > it overwrites existing data. This way, the size of an RRDtool > > database always remains constant. The name "Round Robin" stems > > from this behavior. > > * Other databases store the values as supplied. RRDtool can be > > configured to calculate the rate of change from the previous to the > > current value and store this information instead. > > * Other databases get updated when values are supplied. The RRDtool > > database is structured in such a way that it needs data at predefined > > time intervals. If it does not get a new value during the interval, > > it stores an UNKNOWN value for that interval. So, when using the > > RRDtool database, it is imperative to use scripts that run at regular > > intervals to ensure a constant data flow to update the RRDtool > > database. > > > > RRDtool is designed to store time series of data. With every data > > update, > > an associated time stamp is stored. Time is always expressed in seconds > > passed since epoch (01-01-1970). It comes with a command set to carry > > out various operations on RRD databases. > > > > The version being integrated is 1.2.19 > > > > 4.2. Bug/RFE Number(s): > > > > None. > > > > 4.3. In Scope: > > > > See above. > > > > 4.4. Out of Scope: > > > > See above. > > > > 4.5. Interfaces: > > > > > > -------------------------------------------------------------------- > > Exported Stability Comments > > > > -------------------------------------------------------------------- > > rrdtool Uncommitted main binary with many > > create subcommand subcommands/functions > > dump subcommand documented in rrd*.1 > > fetch subcommand manpages, installed > > graph subcommand in /usr/bin, note the > > info subcommand subcommands are internal > > last subcommand to rrdtool (i.e., no > > lastupdate subcommand additional bits installed). > > resize subcommand > > restore subcommand > > tune subcommand > > xport subcommand > > > > rrdcgi Uncommitted web cgi script interpreter > > parsing for tags documented > > in rrdcgi.1 man page, > > installed in /usr/bin > > > > rrdupdate Uncommitted convenience binary for > > rrdtool update, installed > > in /usr/bin > > > > librrd.so.2.0.9 Uncommitted lib implementation of > > RRD, > > installed in /usr/lib > > > > librrd.so Uncommitted Link target=librrd.so.2.0.9 > > > > librrd.so.2 Uncommitted Link target=librrd.so.2.0.9 > > > > librrd_th.so.2.0.8 Uncommitted Thread safe API for above, > > installed in /usr/lib > > > > librrd_th.so Uncommitted Link > > target=librrd_th.so.2.0.8 > > > > librrd_th.so.2 Uncommitted Link > > target=librrd_th.so.2.0.8 > > > > tclrrd1.2.19.so Uncommitted TCL bindings for RRD, > > installed in /usr/lib > > > > rrd.h Uncommitted header file, installed in > > /usr/include > > > > SUNWrrdtool Uncommitted SVr4 Package > > > > > > -------------------------------------------------------------------- > > Imported Stability Comments > > > > -------------------------------------------------------------------- > > /usr/lib/libpng12.so.0 Uncommitted LSARC/2003/085 > > > > /usr/lib/libz.so.1 Committed PSARC/2006/537 > > > > /usr/lib/libart_lgpl_2.so.2 Volatile LSARC/2006/202 > > > > /usr/sfw/lib/libfreetype.so.6 Volatile LSARC/2002/291 > > > > /usr/sfw/lib/libgcc_s.so.1 Volatile PSARC/2004/742 > > > > 4.6. Doc Impact: > > > > Man pages are provided that both detail the rrdtool functions > > and provide > > tutorials for their use. > > > > 4.7. Admin/Config Impact: > > > > None. > > > > 4.8. HA Impact: > > > > None. > > > > 4.9. I18N/L10N Impact: > > > > The JDS team and the G11N are working together to evaluation > > and provide I18N/L10N support > > > > 4.10. Packaging & Delivery: > > > > Adds new package, SUNWrrdtool, approx 2.2 MB. > > Package will go into SUNWCall, SUNWCXall and SUNWCprog clusters. > > > > 4.11. Security Impact: > > > > None. > > > > 4.12. Dependencies: > > > > None. > > > > 5. Reference Documents: > > > > http://oss.oetiker.ch/rrdtool/ > > > > > > > > On Feb 21, 2008, at 11:02 AM, John Fischer wrote: > > > >> LSARC, > >> > >> I am sponsoring this fast track for Stephen Brown of > >> the JDS - Gnome team in Dublin, Ireland. I have set > >> the timer for Thursday, February 21st, 2008. The > >> case directory contains this proposal as well as various > >> documentation and the header file. > >> > >> This project integrates the Open Source project known > >> as RRDTool into a Minor release of Solaris. RRDTool > >> lets you log and analyze the data you gather from all > >> kinds of data-sources and quickly generate graphical > >> representations of the data definable over a time > >> period. > >> > >> Thanks, > >> > >> John > >> > >> > > > > --- > > Lloyd L Chambers > > lloyd.chambers@sun.com > > Sun Microsystems, Inc > > > > > >