Change Details

The WMCS project `gitlab-test` hosts a instance called `gitlab-ansible-test`, which was used for pre-production testing of GitLab configuration changes. The instance was setup before the migration from Ansible to Puppet (see T283076). The project `gitlab-test` also contains a dedicated puppet host and a `gitlab-puppet-test` machine which was mostly used to test changes for the pupptisation of Ansible code (see T283076). This instance is out of date and has no public ip (because of quota limits). We have to decide if a dedicated puppet host is needed and if needed, how we want to manage this. The old instances and the puppet host should be replace by a new instance, which uses the same code as production GitLab (and if needed, a fresh puppet host) So I see the following steps here: [ ] cleanup old instances [ ] `gitlab-ansible-test` [x] `gitlab-puppet-test-7` [x] `puppet-jelto-6` [x] ~~decide if a dedicated puppet host is needed~~ not needed [x] create new `gitlab-test` instance (gitlab-prod-1001 in devtools project) [] review and adapt hiera data for `gitlab` role for WMCS ([754063](https://gerrit.wikimedia.org/r/c/operations/puppet/+/754063/)) (this one is done but some follow-ups, in progress) [ ] setup `gitlab-test` using puppet [ ] [document everything](https://wikitech.wikimedia.org/wiki/GitLab/Test_Instance)

The WMCS project `gitlab-test` hosts a instance called `gitlab-ansible-test`, which was used for pre-production testing of GitLab configuration changes. The instance was setup before the migration from Ansible to Puppet (see T283076). The project `gitlab-test` also contains a dedicated puppet host and a `gitlab-puppet-test` machine which was mostly used to test changes for the pupptisation of Ansible code (see T283076). This instance is out of date and has no public ip (because of quota limits). We have to decide if a dedicated puppet host is needed and if needed, how we want to manage this. The old instances and the puppet host should be replace by a new instance, which uses the same code as production GitLab (and if needed, a fresh puppet host) So I see the following steps here: [ ] cleanup old instances [ ] `gitlab-ansible-test` [x] `gitlab-puppet-test-7` [x] `puppet-jelto-6` [x] ~~decide if a dedicated puppet host is needed~~ not needed [x] create new `gitlab-test` instance (gitlab-prod-1001 in devtools project) [x] review and adapt hiera data for `gitlab` role for WMCS ([754063](https://gerrit.wikimedia.org/r/c/operations/puppet/+/754063/)) (this one is done but some follow-ups, in progress) [ ] setup `gitlab-test` using puppet (in progress) [ ] [document everything](https://wikitech.wikimedia.org/wiki/GitLab/Test_Instance)

The WMCS project `gitlab-test` hosts a instance called `gitlab-ansible-test`, which was used for pre-production testing of GitLab configuration changes. The instance was setup before the migration from Ansible to Puppet (see T283076). The project `gitlab-test` also contains a dedicated puppet host and a `gitlab-puppet-test` machine which was mostly used to test changes for the pupptisation of Ansible code (see T283076). This instance is out of date and has no public ip (because of quota limits). We have to decide if a dedicated puppet host is needed and if needed, how we want to manage this. The old instances and the puppet host should be replace by a new instance, which uses the same code as production GitLab (and if needed, a fresh puppet host) So I see the following steps here: [ ] cleanup old instances [ ] `gitlab-ansible-test` [x] `gitlab-puppet-test-7` [x] `puppet-jelto-6` [x] ~~decide if a dedicated puppet host is needed~~ not needed [x] create new `gitlab-test` instance (gitlab-prod-1001 in devtools project) [x] review and adapt hiera data for `gitlab` role for WMCS ([754063](https://gerrit.wikimedia.org/r/c/operations/puppet/+/754063/)) (this one is done but some follow-ups, in progress) [ ] setup `gitlab-test` using puppet (in progress) [ ] [document everything](https://wikitech.wikimedia.org/wiki/GitLab/Test_Instance)