The steps to follow for deploying are documented here: https://wikitech.wikimedia.org/wiki/Services/FirstDeployment
I'm going to go through this and create the appropriate subtasks for tracking visibility
@mobrovac I've captured the steps of https://wikitech.wikimedia.org/wiki/Services/FirstDeployment in subtasks of T165760; is there anything else that should be captured in productionizing the service?
It is my understanding that the subtasks as they exist now capture the scope of work to get the service into the beta cluster (from Research's perspective).
I have created via https://horizon.wikimedia.org/project/proxy/ a Web proxy for:
That does not seem to work though (nothing reach the instance), I don't even know whether the other proxies are working.
Workaround for now:
$ ssh -N -L 9632:127.0.0.1:9632 deployment-sca01.deployment-prep.eqiad.wmflabs
And in another terminal:
$ curl http://127.0.0.1:9632/
That is because we have no more security groups available in the deployment-prep project, so that port cannot be exposed to the outside world. I will try to fiddle with the existing groups and get it in.
There is a quota per project. That can surely be bumped by cloud team. Anyway, deployment-sca02 and deployment-sca04 have the sca security group applied and rules can simply be added to it :]
Mentioned in SAL (#wikimedia-releng) [2017-07-07T14:53:23Z] <hashar> deployment-prep: add port 9632 to security group "sca" https://horizon.wikimedia.org/project/access_and_security/security_groups/593/ - T148129