If you’re planning on using librenms I would suggest using Oxidized as you can integrate it into librenms.
On Apr 14, 2019, at 8:00 AM, fsg-public-request@lists.keekles.org wrote:
Send FSG-public mailing list submissions to fsg-public@lists.keekles.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.keekles.org/cgi-bin/mailman/listinfo/fsg-public or, via email, send a message with subject or body 'help' to fsg-public-request@lists.keekles.org
You can reach the person managing the list at fsg-public-owner@lists.keekles.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of FSG-public digest..."
Today's Topics:
1. Re: Hamwan logging/monitoring/projects (Bryan Fields) 2. Slack (Bryan Fields) 3. Re: Slack (Steve Siesel) 4. Re: Hamwan logging/monitoring/projects (John Pugh) 5. Re: Slack (John Pugh)
----------------------------------------------------------------------
Message: 1 Date: Sat, 13 Apr 2019 17:08:02 -0400 From: Bryan Fields <bryan@flscg.org> To: Florida Simulcast Group Public <fsg-public@lists.keekles.org> Subject: Re: [FSG-public] Hamwan logging/monitoring/projects Message-ID: <9ef1d4d4-8268-2e5e-5885-714e0a36cc8c@flscg.org> Content-Type: text/plain; charset=utf-8
On 4/11/19 8:03 AM, Peter Canada wrote:
Do we need hardware to run it on or is there already infrastructure in place to run those services?
I would be interested in supporting the community by assisting with these.
On 4/11/19 8:06 AM, John Pugh wrote:
And while i'm not as active as I'd like to be in this project overall, I would definitely lend a hand with grafana and the config management side even if it's with ansible ;)
Peter/John
I/we have a colo box with several VM's on it already, and I can spin up another for this. Was thinking like 3-4 cores, 16gb ram and 500g of disk should run libreNMS, greylog and grafana nicely. We can use it as a staging/config management server too (ala rancid).
I think most of this can likely run in containers too which would simplify things. Are you guys familiar with Docker?
The hamwan.org guys have some examples of what they run, and we can steal some of their ideas. Really almost anything is better than what we have now :)
73's -- Bryan Fields, W9CR Florida Simulcast Group, Inc.
------------------------------
Message: 2 Date: Sat, 13 Apr 2019 17:08:53 -0400 From: Bryan Fields <bryan@flscg.org> To: Florida Simulcast Group Public <FSG-public@lists.keekles.org> Subject: [FSG-public] Slack Message-ID: <fc47045a-e0ca-de30-d7f3-f1aca77f3588@flscg.org> Content-Type: text/plain; charset=utf-8
BTW we just got a slack for FSG/HamWAN setup. Let me know you want to be added and I'll send you an invite.
73's -- Bryan Fields, W9CR Florida Simulcast Group, Inc.
------------------------------
Message: 3 Date: Sat, 13 Apr 2019 17:09:51 -0400 From: "Steve Siesel" <steve@siesel.net> To: "'Florida Simulcast Group Public'" <fsg-public@lists.keekles.org> Subject: Re: [FSG-public] Slack Message-ID: <12ff01d4f23d$3c5669d0$b5033d70$@siesel.net> Content-Type: text/plain; charset="us-ascii"
Please do!!
Steve
-----Original Message----- From: FSG-public <fsg-public-bounces@lists.keekles.org> On Behalf Of Bryan Fields Sent: Saturday, April 13, 2019 5:09 PM To: Florida Simulcast Group Public <FSG-public@lists.keekles.org> Subject: [FSG-public] Slack
BTW we just got a slack for FSG/HamWAN setup. Let me know you want to be added and I'll send you an invite.
73's -- Bryan Fields, W9CR Florida Simulcast Group, Inc. _______________________________________________ FSG-public mailing list FSG-public@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/fsg-public
------------------------------
Message: 4 Date: Sun, 14 Apr 2019 06:53:39 -0400 From: John Pugh <pepelepugh@gmail.com> To: Florida Simulcast Group Public <fsg-public@lists.keekles.org> Subject: Re: [FSG-public] Hamwan logging/monitoring/projects Message-ID: <CAEVPj93W00ReioaHi+HAVnd_U14pxvabPw0ij8rCwOj1SbH6og@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
On Sat, Apr 13, 2019 at 5:08 PM Bryan Fields <bryan@flscg.org> wrote:
On 4/11/19 8:03 AM, Peter Canada wrote:
Do we need hardware to run it on or is there already infrastructure in place to run those services?
I would be interested in supporting the community by assisting with these.
On 4/11/19 8:06 AM, John Pugh wrote:
And while i'm not as active as I'd like to be in this project overall, I would definitely lend a hand with grafana and the config management side even if it's with ansible ;)
Peter/John
I/we have a colo box with several VM's on it already, and I can spin up another for this. Was thinking like 3-4 cores, 16gb ram and 500g of disk should run libreNMS, greylog and grafana nicely. We can use it as a staging/config management server too (ala rancid).
I think most of this can likely run in containers too which would simplify things. Are you guys familiar with Docker?
The hamwan.org guys have some examples of what they run, and we can steal some of their ideas. Really almost anything is better than what we have now :)
Hey Bryan, I'd probably want to lay out the config to ensure those specs will work, but it *should* be ok. Very familiar with container technologies (docker, cri-o, k8s, etc). All of the required apps (librenms, graylog, elasticsearch, mongo) have docker images available (all with different OS bases, unfortunately). Not sure if you have config in a VCS, but I setup https://github.com/zoopster/flscg-observe for this project in my personal github account. It's empty at present, but feel free to submit a pull request. I'll start working on a terraform config based on what I know, the easiest way to share detail would be through issues in github if you're so inclined.
JP