Experimental Physics and
Industrial Control System

"Phillip A. Sorensen via Tech-talk" <tech-talk at aps.anl.gov> · Thu, 1 Oct 2020 10:26:02 -0400

I sounds like you are on the right track. We have setup with 3 AA that

can run on the same machine (The setup is a 2 node pacemaker cluster).

What we did was

1. A tomcat setup for each AA

2. setup the appliance.xml with a single appliance0 entry that uses an

IP address of the subnet/NIC it should listen on.

3. Set the EPICS_CA_AUTO_ADDR_LIST to NO and EPICS_CA_ADDR_LIST to the

proper broadcast for the network for each tomcat.

Hope that helps.

Phil Sorensen
CHESS

On 9/19/20 12:33 PM, Daniel Cuneo via Tech-talk wrote:

We are setting up a new host with enough resources to run 3 AA instances.
It makes sense to use more than a single NIC to handle a large network load.

The idea is to separate the AA instances and NICs, to cover different

subnets with some overlap.

I'd rather not use a container like Singularity right off the bat,

although that might end up beieng the  best practice after all.

In the appliances.xml file I know that I set the appliance id and inet

which points to

directories in Tomcat.

Can I use a FQND like, appliance01.als.lbl.gov:17665

<http://appliance01.als.lbl.gov:17665/> and another

entry, appliance02.als.lbl.gov:17665

<http://appliance02.als.lbl.gov:17665/>  and do forth ? Where the

appliance ID is also the IP address.

Of course "appliance01" would have to match the Tomcat context directory

as well, where  all the WAR files are deployed.

Or, do I just multihome the host and the Linux kernel handles it ? Then

use different port ranges for each instance in the appliances.xml file.

Not really sure how to ask this question, thanks in advance for your

patience.

--
Daniel Cuneo
ALS Accelerator Controls
BLD 46-172G
desk: 510-486-5439
cell:   415-871-1909

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System