Page MenuHomeFreeBSD

databases/opentsdb: add port
ClosedPublic

Authored by feld on Nov 5 2015, 12:47 AM.

Details

Summary

Add version 2.1.1 for the time being, until 2.2.0 is out

OpenTSDB is a distributed, scalable Time Series Database (TSDB) written on
top of HBase.  OpenTSDB was written to address a common need: store, index
and serve metrics collected from computer systems (network gear, operating
systems, applications) at a large scale, and make this data easily accessible
and graphable.

Thanks to HBase's scalability, OpenTSDB allows you to collect thousands of
metrics from tens of thousands of hosts and applications,  at a high rate
(every few seconds). OpenTSDB will never delete or downsample data and can
easily store hundreds of billions of data points.

OpenTSDB is free software and is available under both LGPLv2.1+ and GPLv3+.
Find more about OpenTSDB at http://opentsdb.net

WWW: http://www.opentsdb.net
Test Plan

poudriere bulk ok
poudriere testport complains about /root/.java being touched
portlint gives some nonsensical warnings

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

xmj retitled this revision from to databases/opentsdb: add port.
xmj updated this object.
xmj edited the test plan for this revision. (Show Details)
xmj added reviewers: swills, feld.

Kill most of the files/opentsdb.in rc.d script

feld edited reviewers, added: xmj; removed: feld.

comandeering per xmj

This revision was automatically updated to reflect the committed changes.

this fails to stage, was this committed without any testing?

ughhhh xmj you said this was in production :)

Also missing UIDs and GIDs changes

As for the stage issue with /root/.java, I've done a ton of googling and it seems we should possibly try to force -Djava.util.prefs.userRoot and -Djava.util.prefs.systemRoot into JAVA_ARGS

Ok I have the stage violation fixed. I'm just waiting for xmj to confirm the UID/GID entries this port actually needs since this is in production somewhere

Looks like UID/GID somehow got lost in the later revs, check out the first diff.

This revision was automatically updated to reflect the committed changes.