L2 status and SQL MA

The objective is to integrate the L2 status information into the SQL MA, so that historical L2 circuit status information is provided.

First phase
1. The E2EMon MP is being extended with the E2ESync which pushes messages into the SQL MA using perfSONAR
2. The SQL MA is extended with (i) the L2 status "write" capability and (ii) the same perfSONAR interface as the E2EMon MP (except that it can provide historical information).
3. The E2E Mon access the SQL MA to retrieve status information and display historical information.
Second phase
1. To be determined: E2EMon MP becomes only an export to the SQL MA and is installed on a different machine (security - equipment access, public access on separate machines), visualisation showing historical information

to OK and MG: do we need to display historical status information on the E2EMon visualisation.
to RL: a lot is dependent on the configuration of the service (in respect with what is accepted or not). The documentation needs probalby to be updated .
to OK: what visualisation do we use for LHC for the historical display of the status information.
to MH and RL: what happens if there is a new circuit that is being added? The MP pushes the information that contains the entire update for the network, including the new circuit. Then the MA creates a new table for that new circuit and start "announcing" via its web-interface? Is it how it works?
- to RL: does the SQL MA register this new information to the LS (depending on what the LS registers).
to M&Ms: does the central server retrieve the information from the MP or from the MA?
to RL: what has to be configured on the SQL MA side?