Need init script for DAS analytics web about das HOT 5 CLOSED

metson: Could it run in the same webserver (I assume you're using cherrypy/WMCore.Webtools) as the rest of the DAS pages? Why would you want it as a separate instance?

from das.

valya: It can, but rather I want this separation. I don't want to expose DAS analytics to end-users. I want to have separation for maintenance and scheduling. I want to put DAS analytics to different node eventually.

from das.

metson: Hmmm, ok. How does that work in the clustered environment that you're targeting? Surely this is something you should protect with authorisation, rather than running on another port (which will still require the auth.)?

from das.

valya: We need to pick up a node where we will run analytics. Since it has scheduler, it means we can assign as many tasks as we want to the analytics server. Therefore the node will be pretty busy. The clustered environment still works, since I made DAS core transparent to connection pooling. Analytics invokes DAS core, which by itself can connect to Mongo URIs (routers in case of shards or master in case of replica pairs) which redirects requests to shards/replicas pairs.

Regarding ports. Right now we have DAS web server on port 8212, the DAS cache server on port 8211 and we will have DAS analytics server on port 8213. Such separation allows to assign different nodes for every server it is required, I consider this flexibility as benefit rather complication.

The DAS cache server is not visible to end-users at all, since there is no redirect apache rules for it.
The DAS web server is visible to all users and it talks to DAS cache server. Right now I want to hide analytics too from end-users, but make it visible to CERN operators. Here we have two options. Either CERN operator connect to dedicated DAS analytics node via host:port, or we set group authorization to allow certain people to access it via cmsweb. As you well know the group authorization will require OpenID stuff, which as far as I know is not yet in place. So we left with first option so far.

This certainly needs to be reviewed/adjusted as time goes by, but during commissioning phase I opted with non-visible DAS analytics running on specified host/port.

from das.

valya: This is done and accepted by HTTP group.

from das.