Skip to Content
0
Former Member
Apr 07, 2014 at 10:17 AM

ESP Cluster Architecture

104 Views

Hello,

In our existing Aleri configuration,
we have established a group user ID as 'asap' which controls the binaries.

We have for each branch a single user
ID defined. The single user ID has access to all the models for that branch.

London
Branch Environment:

User
aspLDN

Group
asap

/home/aspLDN/LDNFX/models

/home/aspLDN/LDNFX/scripts

/home/aspLDN/LDNFX/props

/home/aspLDN/LDNFX/logs

Shanghai
Brranch Environment:

User
aspSHA

Group
asap

/home/aspSHA/SHAAlerts/models

/home/aspSHA/SHAAlerts/scripts

/home/aspSHA/SHAAlerts/props

/home/aspSHA/SHAAlerts/logs

New York Branch Environment:

User
aspNYK

Group
asap

/home/aspNYK/NYKFX/models

/home/aspNYK/NYKFX/scripts

/home/aspNYK/NYKFX/props

/home/aspNYK/NYKFX/logs

/home/aspNYK/NYKAC/models

/home/aspNYK/NYKAC/scripts

/home/aspNYK/NYKAC/props

/home/aspNYK/NYKAC/logs

Our New York branch has two models viz.
NYKAC & NYKFX for which we have a single ID on Linux as 'aspNYK' both of
the models are accessible by the single ID. New York ID doesn’t have access to
other branches models or data.

Similarly
for London we have a single ID viz 'aspLDN' which controls a single model. For
Shanghai branch it is the same procedure with a single model as well. The three
branches IDs (aspLDN, aspNYK & aspSHA) use a single set of binaries
controlled by 'asap' group user ID.

We are trying to work out how we should configure Clusters/workspaces/nodes to give us a similar arrangement as above, our concern is on ESP with having single cluster controlling multiple workspaces (i.e workspace for each branch) and within that multiple projects we risk having all the projects stopped if the single cluster crushes. To maintain some resilience under single server we would like to have a separate cluster for each branch and within that be able to have multiple workspaces/projects.

To summarise:-

  1. Each Branch should have a single id associated with it which can be used to start /stop / amend that Branches Projects
  2. Each Project can be start / stop independently
  3. Only the asap (esp) id itself can update / replace the esp binaries

Any feedback will be appreciated.