Closed Bug 851116 Opened 11 years ago Closed 10 years ago

Puppet module for Logstash Shipper (client)

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task, P2)

All
Other

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: dmaher, Assigned: dmaher)

References

Details

(Whiteboard: [triaged 20130314])

Find / modify / write / otherwise implement a Puppet module for a Logstash Shipper (likely Beaver, though Lumberjack might be interesting as well).
Assignee: server-ops → dmaher
Blocks: 829359
Group: infra → mozilla-corporation-confidential
Depends on: 832933
Priority: -- → P2
Whiteboard: [triaged 20130314]
Component: Server Operations → Server Operations: Web Operations
QA Contact: shyam → nmaul
Group: mozilla-corporation-confidential
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
Closed: 11 years ago
Resolution: --- → FIXED
(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
It's been an interesting year, but the Bunker project has been officially cancelled - closing this bug.
Assignee: ezounes → dmaher
Status: REOPENED → RESOLVED
Closed: 11 years ago10 years ago
Resolution: --- → WONTFIX
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.