Closed Bug 751175 Opened 13 years ago Closed 12 years ago

ES puppet refactoring / package changes

Categories

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

x86
macOS
task
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cshields, Assigned: dmaher)

References

Details

we need to change from deploying the ES tarball to building an RPM for ES for cleaner installations and updates. Also, this module might need a bit of fixing up to allow for cross-datacenter connectivity (ie: not using autodiscovery) re: https://mana.mozilla.org/wiki/display/websites/Elastic+Search#ElasticSearch-UpdatePushprocedure and puppet/trunk/modules/it-elasticsearch
Severity: normal → minor
See Also: → 751171
I've started work on a module that is named "newlasticsearch" (which, of course, will probably require a more sane name in the future). It exists in Puppet now and is currently being used to manage the 8 test nodes noted in bug 751171. Along with this module there is a "newlastic" class definition and a "newlasticsearch" node definition. These are all WIP and I will fully describe and document them once they begin to stabilise fully.
Status: NEW → ASSIGNED
Note to self: newlasticsearch should deploy (at least) elasticsead-head to the nodes. consider also bigdesk and paramedic.
Packaged and inserted 'elasticsearch-plugin-site-head' into the Mozilla repo. It is installed via the package resource of Class newlasticsearch (as declared in the node definition).
Packaged and inserted 'elasticsearch-plugin-site-bigdesk' and 'elasticsearch-plugin-site-paramedic' into the Mozilla repo. They are installed via (node) Class newlasticsearch (as above).
Version 1 of the module is feature-complete and tested. Just need to document it. See bug 779177.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.