Change Details

after creating the new debian package, we would test it over two new nodes (that could be VMs) name it as docker-registry-beta.wikimedia.org / docker-registry-beta.discovery.wmnet writing to a new swift container since we don't want to interfere with old registry normal operation. After the test, if we feel happy about results we can repush existing images to the new registry and point the DNS to the new one. Some tests that should be performed: - Prometheus can scrape metrics and we get at least push/pull metrics by an image. - a minimal stress test/ be able to pull 10 images in parallel and compare timings over production. - tearing down one docker-registry should not affect the registry service.

After creating the new debian package, we would test it over two new nodes (that could be VMs) name it as `docker-registry-beta.wikimedia.org` / `docker-registry-beta.discovery.wmnet` writing to a new Swift container since we don't want to interfere with old registry normal operation. After the test, if we feel happy about results we can repush existing images to the new registry and point the DNS to the new one. Some tests that should be performed: - Prometheus can scrape metrics and we get at least push/pull metrics by an image. - A minimal stress test/ be able to pull 10 images in parallel and compare timings over production. - Tearing down one docker-registry should not affect the registry service.

aAfter creating the new debian package, we would test it over two new nodes (that could be VMs) name it as `docker-registry-beta.wikimedia.org / org` / `docker-registry-beta.discovery.wmnet` writing to a new sSwift container since we don't want to interfere with old registry normal operation. After the test, if we feel happy about results we can repush existing images to the new registry and point the DNS to the new one. Some tests that should be performed: - Prometheus can scrape metrics and we get at least push/pull metrics by an image. - a- A minimal stress test/ be able to pull 10 images in parallel and compare timings over production. - t- Tearing down one docker-registry should not affect the registry service.