Closed Bug 910310 Opened 12 years ago Closed 12 years ago

[bunker] re-assign roles to better use the hardware

Categories

(Infrastructure & Operations :: IT-Managed Tools, task, P4)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dmaher, Assigned: ezounes)

Details

As discussed in the Bunker meeting today, we should re-assign some roles in order to better use the hardware profiles : * shift nodes 50 & 51 (currently "indexer") -> nodes 48 & 49 (formerly "balancer", now unused) * re-purpose nodes 50 & 51 as "log_new" Don't forget to update the Mana page when this is done. :)
The nodes have been shifted. I moved node46,47 to replace node50,51. I've added node50,51 to the log_new role. The Mana page has been updated. Bigdesk confirms that they have joined the cluster.
I noticed we have node52 and 53 if we want to add EVEN more log_new nodes. They aren't in use at the moment.
(In reply to Eric Zounes [:zounese] from comment #1) > The nodes have been shifted. I moved node46,47 to replace node50,51. I've > added node50,51 to the log_new role. So has the front_end role (formerly nodes 46 & 47) been removed entirely, or is Kibana still being hosted from nodes 50 & 51 (along with log_new on said nodes) ? Or something else entirely ?
Assignee: server-ops-webops → ezounes
Flags: needinfo?(ezounes)
(In reply to Daniel Maher [:phrawzty] from comment #3) > (In reply to Eric Zounes [:zounese] from comment #1) > > The nodes have been shifted. I moved node46,47 to replace node50,51. I've > > added node50,51 to the log_new role. > > So has the front_end role (formerly nodes 46 & 47) been removed entirely, or > is Kibana still being hosted from nodes 50 & 51 (along with log_new on said > nodes) ? Or something else entirely ? Kibana 3 is/has been hosted from the log_int nodes.(node62,63) The literal front_end role is no longer in use. The roles section on the Mana page is now consistent with the current state of Bunker.
Flags: needinfo?(ezounes)
r+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.