If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Puppet module for Logstash Shipper (client)

RESOLVED WONTFIX

Status

Infrastructure & Operations
WebOps: Other
P2
normal
RESOLVED WONTFIX
5 years ago
4 years ago

People

(Reporter: phrawzty, Assigned: phrawzty)

Tracking

Details

(Whiteboard: [triaged 20130314])

(Assignee)

Description

5 years ago
Find / modify / write / otherwise implement a Puppet module for a Logstash Shipper (likely Beaver, though Lumberjack might be interesting as well).
(Assignee)

Updated

5 years ago
Assignee: server-ops → dmaher
Blocks: 829359
Group: infra → mozilla-corporation-confidential
Depends on: 832933
Priority: -- → P2
Whiteboard: [triaged 20130314]
(Assignee)

Updated

5 years ago
Component: Server Operations → Server Operations: Web Operations
QA Contact: shyam → nmaul
(Assignee)

Updated

5 years ago
Group: mozilla-corporation-confidential
(Assignee)

Updated

4 years ago
Assignee: dmaher → ezounes
We are using a lumberjack puppet module for now. It came with serveral issues, but those have been patched. These include:

* No "/etc/lumberjack" for the cert path it sets.
* It incorrectly referenced "@instance" instead of "@name" in the lumberjack template.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

4 years ago
(In reply to Eric Zounes [:zounese] from comment #1)
> We are using a lumberjack puppet module for now. It came with serveral
> issues, but those have been patched. These include:
> 
> * No "/etc/lumberjack" for the cert path it sets.
> * It incorrectly referenced "@instance" instead of "@name" in the lumberjack
> template.

Hi Eric,

As a matter of course, any changes from upstream need to be documented (at a minimum), and preferably mirrored somewhere externally, such as Github (either the entire module or a diff, in the latter case a Gist is good enough).

Please update the UPSTREAM file with your modifications.  There are numerous examples :

$ for i in `find modules/ -name 'UPSTREAM'`
do
echo "---"; echo $i; cat $i
done
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Indeed. I'll submit a pull request. Until then I can update the upstream with the hash from my latest commit on my fork of master.
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
(Assignee)

Comment 4

4 years ago
It's been an interesting year, but the Bunker project has been officially cancelled - closing this bug.
Assignee: ezounes → dmaher
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.