Page MenuHomePhabricator

Deploy striker on labtestweb2001
Closed, ResolvedPublic


We should do whatever puppet monkeying we need to get striker running on Labtest. I suspect this will prove useful in the long run, and it's always nice to test our production-ish deployment process on labtest after a merge.

Event Timeline

The big trick here will be figuring out how to separate from scap3 for the deploy step. The existing Puppet setup uses service::uwsgi which automatically sets up scap3 deployment. It looks like that can be turned off by passing deployment => 'anything_but_scap3' to the service::uwsgi define. Its a bit hacky but it should work. Doing that would likely mean converting the Puppet config to the newly defined profiles and roles layout and introducing more hiera config that could be overloaded in a role::striker::web_test class.

bd808 triaged this task as Low priority.Dec 19 2017, 5:34 PM
bd808 removed bd808 as the assignee of this task.Mar 19 2018, 9:39 PM

Change 421702 had a related patch set uploaded (by Andrew Bogott; owner: Andrew Bogott):
[operations/puppet@production] labweb oauth: use labtestwikitech, not prod wikitech

Change 421702 merged by Andrew Bogott:
[operations/puppet@production] labweb oauth: use labtestwikitech, not prod wikitech

Andrew claimed this task.

striker is now running at It shouldn't get deployed automatically from tin but rather via a local 'scap pull'. It also uses 'labtestandrew' to talk to wikitech rather than a service account but it should be good enough for test/dev purposes.