Closed
Bug 664814
Opened 14 years ago
Closed 14 years ago
mrapp-stage02 <-> elasticsearch1 access
Categories
(Infrastructure & Operations Graveyard :: NetOps, task)
Infrastructure & Operations Graveyard
NetOps
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nmaul, Assigned: arzhel)
References
Details
The Input team would like to start using the elasticsearch cluster.
Could you add an ACL for this?
mrapp-stage02 (10.2.81.29) -> elasticsearch1.webapp.phx1 (10.8.81.65) port 9200/tcp
There will also be a similar need for prod, but we can make a separate bug for that when they're ready for it. The prod cluster is already in PHX, so it won't be cross-DC like this one is. Thanks!
Assignee | ||
Updated•14 years ago
|
Assignee: network-operations → arzhel
Assignee | ||
Comment 1•14 years ago
|
||
[root@mrapp-stage02 ~]# nc -z elasticsearch1.webapp.phx1.mozilla.com 9200
Connection to elasticsearch1.webapp.phx1.mozilla.com 9200 port [tcp/wap-wsp] succeeded!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 2•14 years ago
|
||
> There will also be a similar need for prod, but we can make a separate bug
> for that when they're ready for it. The prod cluster is already in PHX, so
> it won't be cross-DC like this one is. Thanks!
Oh there will be... prod metrics ES is in SJC :( We'll get one setup later in PHX, but we'll need to cross-datacenter for now.
Updated•12 years ago
|
Product: mozilla.org → Infrastructure & Operations
Updated•2 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•