stl: StationLite localconfig

[damb]

Using the configuration variable EIDA_NODES from settings.py while initializing the StationLite database by means of eida-stationlite-db-init is error-prone.

Instead, eida-stationlite-harvest should receive a list of URLs for eidaws-routing localconfig configuration files to be parsed to fill/update the internal SQLite database. Hence, service endpoint URLs are managed dynamically.

[damb]

Also, remove EIDA node specific information from the StationLite SQLite DB.

[damb]

When truncating the DB remove also endpoint information not referenced anymore.

[damb]

Fetch fdsnws-station information from eidaws-routing localconfig configuration files, too.

[damb]

Hoi @kaestli,

when fetching the fdsnws-station information (i.e. URL) from eidaws-routing localconfig configuration files directly how to deal with:

1. the fact that there might occur ambiguities due to multiple different fdsnws-station URLs for different route-epochs?
2. missing fdsnws-station service elements for a certain route?

Thx, Daniel

[damb]

Hoi Philipp (@kaestli),

missing fdsnws-station service elements for a certain route?

Such routes must be considered as invalid, right?

[damb]

Mostly implemented with c0fd56f.

[damb]

When truncating the DB remove also endpoint information not referenced anymore.

Currently not possible since orm.Endpoint does not come along with a lastseen field.