EDA deployment and persistance

Engineering Data Base (EDA) is one of the key components of the Control System, and is required early in the development cycle to support testing, debugging, integration, commissioning, trending analysis and more.

EDA shall be deployed in all deployment environments (SKAMPI, PSIs, ITFs, Telescope).  

It should be possible to deploy EDA independently from other software subsystems, persist the content while the rest of software may be shutdown, re-deployed and restarted.  Users should be able to access EDA content at any time. 

EDA persistence is addressed by SP-1801.

PSI is not fundamentally different from other environments. 

 
Need to decide:

Is there an instance of the EDA for each facility, i.e. each cluster where MVP is deployed,  PSI,  ITF,  Telescope ?   Or is there a single distributed EDA ?  

Per Telescope (Low EDA and Mid EDA) or per observatory ?

Note: Both Low and Mid Telescope are distributed over two major locations: Central Processing Facility (CPF) - often referred to as 'site' and the SDP location.  These two locations are hundreds, if not thousands, kilometers apart.  EDA has to be deployed at both sites so that archiving can continue  when communication between the sites is cutoff.