Page MenuHomePhabricator

The production server configuration is outdated
Closed, ResolvedPublic2 Estimated Story Points

Description

The production server configuration is outdated. This task encompasses the work to revise the prod config using the dev config as a guide.

Event Timeline

ovasileva triaged this task as Medium priority.Feb 13 2018, 3:44 PM
ovasileva subscribed.

Setting this as normal, but let's discuss further during grooming. Seems like we might want to expand the task description a bit.

@Niedzielski do we still need that? From my understanding SCAP will create the production yaml file by itself (https://gerrit.wikimedia.org/r/#/c/408869/).

pmiazga subscribed.

@pmiazga, I asked Petr about combining the Scap3 and prod config but it seems to be necessary to keep them distinct for Puppet Hiera. (Sorry, I don't have any additional details.)

@Pchelolo do we need to keep the production config in our repo? If we're not going to use it, only the Scap3 config I don't see a reason to keep both dev and prod configs in the repository.

@pmiazga the configs in the source repo work for example/dev/test/documentation purposes, so it's up to you - technically if you don't need it, you can delete it.

Change 412946 had a related patch set uploaded (by Pmiazga; owner: Pmiazga):
[mediawiki/services/chromium-render@master] Hygiene: Remove config.prod.yaml as it's not required

https://gerrit.wikimedia.org/r/412946

Per https://phabricator.wikimedia.org/T186338#3986075 I decied to remove the prod.config from chromium-service repository

Change 412946 merged by jenkins-bot:
[mediawiki/services/chromium-render@master] Hygiene: Remove config.prod.yaml as it's not required

https://gerrit.wikimedia.org/r/412946

Niedzielski claimed this task.

The tests still pass and there's no additional QA needed on this.