Zenpacks extend the capabilities of Zenoss. This port builds cleanly in Tinderbox. This port depends on the following PR: ports/156655
pkg-message tuning # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # zenpack-InterfaceGraphs # zenpack-InterfaceGraphs/files # zenpack-InterfaceGraphs/files/pkg-deinstall.in # zenpack-InterfaceGraphs/files/pkg-message.in # zenpack-InterfaceGraphs/distinfo # zenpack-InterfaceGraphs/pkg-descr # zenpack-InterfaceGraphs/pkg-plist # zenpack-InterfaceGraphs/Makefile # echo c - zenpack-InterfaceGraphs mkdir -p zenpack-InterfaceGraphs > /dev/null 2>&1 echo c - zenpack-InterfaceGraphs/files mkdir -p zenpack-InterfaceGraphs/files > /dev/null 2>&1 echo x - zenpack-InterfaceGraphs/files/pkg-deinstall.in sed 's/^X//' >zenpack-InterfaceGraphs/files/pkg-deinstall.in << 'f2036375e03022af26741883f361572f' X#!/bin/sh X Xif [ "$2" = "DEINSTALL" ]; then X echo "To de-activate this Zenpack, run the following command as the zenoss user: X X%%ZENHOME%%/bin/zenpack --remove %%ZPACKPREFIX%%%%PORTNAME%% X XIMPORTANT: De-activating a Zenpack will also remove all its associated data" X Xfi f2036375e03022af26741883f361572f echo x - zenpack-InterfaceGraphs/files/pkg-message.in sed 's/^X//' >zenpack-InterfaceGraphs/files/pkg-message.in << '5d0bbc9d56a8eef66de9354e7850022b' X XTo activate this Zenpack, run the following commands as the zenoss user: X X%%ZENHOME%%/bin/zenpack --install %%ZPACKHOME%%/%%ZPACK%% X%%ZENHOME%%/bin/zopectl restart 5d0bbc9d56a8eef66de9354e7850022b echo x - zenpack-InterfaceGraphs/distinfo sed 's/^X//' >zenpack-InterfaceGraphs/distinfo << 'cb23596854354391f2ae71c388c64333' XSHA256 (InterfaceGraphs-1.0.tar.gz) = 36c71c06eb12108599f793b683ff6365a1ababb87cdced99c54c73f4cdce2806 XSIZE (InterfaceGraphs-1.0.tar.gz) = 5202 cb23596854354391f2ae71c388c64333 echo x - zenpack-InterfaceGraphs/pkg-descr sed 's/^X//' >zenpack-InterfaceGraphs/pkg-descr << 'da86abb0da1db3e04f501ac24bb47844' XWhen troubleshooting network issues, it can be very useful to have all the Xinterface graphs for a device on the same screen. This helps with spotting Xtrends, or tracing where traffic is flowing through a switch or router. The Xonly way to natively achieve this with Zenoss is to create a graph or Xmulti-graph report for every network device manually, which can be a chore Xif you have more than a few network devices. X XThis ZenPack provides a new link on the left side of a device detail view Xcalled "Interface Graphs" - this view shows the graphs for all of the network Xinterfaces on the device in one place, allowing for fast spotting of issues Xor traffic flows. Both the interface name and the description (if any) are Xused to title the graphs to aid with identification. X XNote that with stacked switches, you can end up with a very large number of Xgraphs on the page, so tuning this slightly via the configuration properties Xbelow could be a good idea in these situations. X XWWW: http://community.zenoss.org/docs/DOC-10226 da86abb0da1db3e04f501ac24bb47844 echo x - zenpack-InterfaceGraphs/pkg-plist sed 's/^X//' >zenpack-InterfaceGraphs/pkg-plist << '610731a87d76ef06c3ae895a13f0df2c' Xzenoss/ZenPack/%%ZPACK%% X@dirrmtry zenoss/ZenPack 610731a87d76ef06c3ae895a13f0df2c echo x - zenpack-InterfaceGraphs/Makefile sed 's/^X//' >zenpack-InterfaceGraphs/Makefile << '5574151eb8ff69554ede4cad47e0d5ba' X# New ports collection makefile for: InterfaceGraphs X# Date created: 26 May 2011 X# Whom: Zenoss <zenoss@experts-exchange.com> X# X# $FreeBSD$ X# X XPORTNAME= InterfaceGraphs XPORTVERSION= 1.0 XCATEGORIES= net-mgmt XMASTER_SITES= http://www.glenbarber.us/ports/net-mgmt/${PORTDIRNAME}/ X XMAINTAINER= zenoss@experts-exchange.com XCOMMENT= Provides a link that graphs all network interfaces for a device X XBUILD_DEPENDS= zenoss>=3.1.0:${PORTSDIR}/net-mgmt/zenoss XRUN_DEPENDS= zenoss>=3.1.0:${PORTSDIR}/net-mgmt/zenoss X XFETCH_ARGS= -o - > ${DISTDIR}/${DISTFILES} XPKGNAMEPREFIX:= zenpack-community- X XZENHOME= ${LOCALBASE}/zenoss XZPACKHOME= ${LOCALBASE}/zenoss/ZenPack XZPACKPREFIX= ZenPacks.community. XZPACK= ${ZPACKPREFIX}${PORTNAME}-${PORTVERSION}-${PYTHON_VERSION:S/thon//}.egg XPLIST_SUB= ZPACK=${ZPACK} XSUB_LIST= ZENHOME=${ZENHOME} \ X ZPACK=${ZPACK} \ X ZPACKHOME=${ZPACKHOME} \ X ZPACKPREFIX=${ZPACKPREFIX} \ X PORTNAME=${PORTNAME} XSUB_FILES= pkg-message pkg-deinstall X XSHAREOWN= zenoss XSHAREGRP= zenoss X X#zenoss provides its own python 2.6 - we build against that for application compatibility XPYTHON_VERSION= python2.6 XPYTHON_CMD= ${ZENHOME}/bin/python XPYSETUP= ./setup.py X XMAKE_ENV+= ZENHOME=${ZENHOME} \ X INSTANCE_HOME=${ZENHOME} \ X PYTHONPATH=${ZENHOME}/lib/python \ X PATH=${ZENHOME}/bin:${PATH} X X.if !defined(UID) XUID!= /usr/bin/id -u X.endif X Xdo-build: X.if ${UID} != 0 && !defined(INSTALL_AS_USER) X @${ECHO_MSG} "===> Switching to root credentials for '${.TARGET}' target" X @cd ${.CURDIR} && \ X ${SU_CMD} "${MAKE} ${__softMAKEFLAGS} ${.TARGET}" X @${ECHO_MSG} "===> Returning to user credentials" X.else X cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} bdist_egg X.endif X Xdo-install: X ${MKDIR} ${ZPACKHOME} X ${INSTALL_DATA} ${WRKSRC}/dist/${ZPACK} ${ZPACKHOME} X @${CAT} ${PKGMESSAGE} X X.include <bsd.port.mk> 5574151eb8ff69554ede4cad47e0d5ba exit
updated tarball and distinfo, respectively. # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # zenpack-InterfaceGraphs # zenpack-InterfaceGraphs/files # zenpack-InterfaceGraphs/files/pkg-deinstall.in # zenpack-InterfaceGraphs/files/pkg-message.in # zenpack-InterfaceGraphs/distinfo # zenpack-InterfaceGraphs/pkg-descr # zenpack-InterfaceGraphs/pkg-plist # zenpack-InterfaceGraphs/Makefile # echo c - zenpack-InterfaceGraphs mkdir -p zenpack-InterfaceGraphs > /dev/null 2>&1 echo c - zenpack-InterfaceGraphs/files mkdir -p zenpack-InterfaceGraphs/files > /dev/null 2>&1 echo x - zenpack-InterfaceGraphs/files/pkg-deinstall.in sed 's/^X//' >zenpack-InterfaceGraphs/files/pkg-deinstall.in << 'f2036375e03022af26741883f361572f' X#!/bin/sh X Xif [ "$2" = "DEINSTALL" ]; then X echo "To de-activate this Zenpack, run the following command as the zenoss user: X X%%ZENHOME%%/bin/zenpack --remove %%ZPACKPREFIX%%%%PORTNAME%% X XIMPORTANT: De-activating a Zenpack will also remove all its associated data" X Xfi f2036375e03022af26741883f361572f echo x - zenpack-InterfaceGraphs/files/pkg-message.in sed 's/^X//' >zenpack-InterfaceGraphs/files/pkg-message.in << '5d0bbc9d56a8eef66de9354e7850022b' X XTo activate this Zenpack, run the following commands as the zenoss user: X X%%ZENHOME%%/bin/zenpack --install %%ZPACKHOME%%/%%ZPACK%% X%%ZENHOME%%/bin/zopectl restart 5d0bbc9d56a8eef66de9354e7850022b echo x - zenpack-InterfaceGraphs/distinfo sed 's/^X//' >zenpack-InterfaceGraphs/distinfo << 'cb23596854354391f2ae71c388c64333' XSHA256 (InterfaceGraphs-1.0.tar.gz) = 5acf65f06c57557bd09ba7cd8e5716e1db637b07ea00a9a276fdca82ae96705c XSIZE (InterfaceGraphs-1.0.tar.gz) = 5207 cb23596854354391f2ae71c388c64333 echo x - zenpack-InterfaceGraphs/pkg-descr sed 's/^X//' >zenpack-InterfaceGraphs/pkg-descr << 'da86abb0da1db3e04f501ac24bb47844' XWhen troubleshooting network issues, it can be very useful to have all the Xinterface graphs for a device on the same screen. This helps with spotting Xtrends, or tracing where traffic is flowing through a switch or router. The Xonly way to natively achieve this with Zenoss is to create a graph or Xmulti-graph report for every network device manually, which can be a chore Xif you have more than a few network devices. X XThis ZenPack provides a new link on the left side of a device detail view Xcalled "Interface Graphs" - this view shows the graphs for all of the network Xinterfaces on the device in one place, allowing for fast spotting of issues Xor traffic flows. Both the interface name and the description (if any) are Xused to title the graphs to aid with identification. X XNote that with stacked switches, you can end up with a very large number of Xgraphs on the page, so tuning this slightly via the configuration properties Xbelow could be a good idea in these situations. X XWWW: http://community.zenoss.org/docs/DOC-10226 da86abb0da1db3e04f501ac24bb47844 echo x - zenpack-InterfaceGraphs/pkg-plist sed 's/^X//' >zenpack-InterfaceGraphs/pkg-plist << '610731a87d76ef06c3ae895a13f0df2c' Xzenoss/ZenPack/%%ZPACK%% X@dirrmtry zenoss/ZenPack 610731a87d76ef06c3ae895a13f0df2c echo x - zenpack-InterfaceGraphs/Makefile sed 's/^X//' >zenpack-InterfaceGraphs/Makefile << '5574151eb8ff69554ede4cad47e0d5ba' X# New ports collection makefile for: InterfaceGraphs X# Date created: 26 May 2011 X# Whom: Zenoss <zenoss@experts-exchange.com> X# X# $FreeBSD$ X# X XPORTNAME= InterfaceGraphs XPORTVERSION= 1.0 XCATEGORIES= net-mgmt XMASTER_SITES= http://www.glenbarber.us/ports/net-mgmt/${PORTDIRNAME}/ X XMAINTAINER= zenoss@experts-exchange.com XCOMMENT= Provides a link that graphs all network interfaces for a device X XBUILD_DEPENDS= zenoss>=3.1.0:${PORTSDIR}/net-mgmt/zenoss XRUN_DEPENDS= zenoss>=3.1.0:${PORTSDIR}/net-mgmt/zenoss X XFETCH_ARGS= -o - > ${DISTDIR}/${DISTFILES} XPKGNAMEPREFIX:= zenpack-community- X XZENHOME= ${LOCALBASE}/zenoss XZPACKHOME= ${LOCALBASE}/zenoss/ZenPack XZPACKPREFIX= ZenPacks.community. XZPACK= ${ZPACKPREFIX}${PORTNAME}-${PORTVERSION}-${PYTHON_VERSION:S/thon//}.egg XPLIST_SUB= ZPACK=${ZPACK} XSUB_LIST= ZENHOME=${ZENHOME} \ X ZPACK=${ZPACK} \ X ZPACKHOME=${ZPACKHOME} \ X ZPACKPREFIX=${ZPACKPREFIX} \ X PORTNAME=${PORTNAME} XSUB_FILES= pkg-message pkg-deinstall X XSHAREOWN= zenoss XSHAREGRP= zenoss X X#zenoss provides its own python 2.6 - we build against that for application compatibility XPYTHON_VERSION= python2.6 XPYTHON_CMD= ${ZENHOME}/bin/python XPYSETUP= ./setup.py X XMAKE_ENV+= ZENHOME=${ZENHOME} \ X INSTANCE_HOME=${ZENHOME} \ X PYTHONPATH=${ZENHOME}/lib/python \ X PATH=${ZENHOME}/bin:${PATH} X X.if !defined(UID) XUID!= /usr/bin/id -u X.endif X Xdo-build: X.if ${UID} != 0 && !defined(INSTALL_AS_USER) X @${ECHO_MSG} "===> Switching to root credentials for '${.TARGET}' target" X @cd ${.CURDIR} && \ X ${SU_CMD} "${MAKE} ${__softMAKEFLAGS} ${.TARGET}" X @${ECHO_MSG} "===> Returning to user credentials" X.else X cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} ${PYTHON_CMD} ${PYSETUP} bdist_egg X.endif X Xdo-install: X ${MKDIR} ${ZPACKHOME} X ${INSTALL_DATA} ${WRKSRC}/dist/${ZPACK} ${ZPACKHOME} X @${CAT} ${PKGMESSAGE} X X.include <bsd.port.mk> 5574151eb8ff69554ede4cad47e0d5ba exit
Responsible Changed From-To: freebsd-ports-bugs->crees I'll take it.
State Changed From-To: open->feedback Wait for patch to use bsd.zenoss.mk
Update to use bsd.zenoss.mk -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5
State Changed From-To: feedback->open Submitter has fixed.
crees 2011-10-27 14:36:31 UTC FreeBSD ports repository Modified files: net-mgmt Makefile Added files: net-mgmt/zenpack-interfacegraphs Makefile distinfo pkg-descr pkg-plist net-mgmt/zenpack-interfacegraphs/files pkg-deinstall.in pkg-message.in Log: When troubleshooting network issues, it can be very useful to have all the interface graphs for a device on the same screen. This helps with spotting trends, or tracing where traffic is flowing through a switch or router. The only way to natively achieve this with Zenoss is to create a graph or multi-graph report for every network device manually, which can be a chore if you have more than a few network devices. This ZenPack provides a new link on the left side of a device detail view called "Interface Graphs" - this view shows the graphs for all of the network interfaces on the device in one place, allowing for fast spotting of issues or traffic flows. Both the interface name and the description (if any) are used to title the graphs to aid with identification. Note that with stacked switches, you can end up with a very large number of graphs on the page, so tuning this slightly via the configuration properties below could be a good idea in these situations. WWW: http://community.zenoss.org/docs/DOC-10226 PR: ports/157503 Submitted by: Zenoss <zenoss@experts-exchange.com> Revision Changes Path 1.264 +1 -0 ports/net-mgmt/Makefile 1.1 +21 -0 ports/net-mgmt/zenpack-interfacegraphs/Makefile (new) 1.1 +2 -0 ports/net-mgmt/zenpack-interfacegraphs/distinfo (new) 1.1 +10 -0 ports/net-mgmt/zenpack-interfacegraphs/files/pkg-deinstall.in (new) 1.1 +8 -0 ports/net-mgmt/zenpack-interfacegraphs/files/pkg-message.in (new) 1.1 +18 -0 ports/net-mgmt/zenpack-interfacegraphs/pkg-descr (new) 1.1 +2 -0 ports/net-mgmt/zenpack-interfacegraphs/pkg-plist (new) _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
State Changed From-To: open->closed New port added. Thanks!