Preserve WM images, Python packages and their dependencies after WM freeze

[vkuznet]

Impact of the new feature
To be able to reproduce WM and all its dependent services at any time on k8s/docker infrastructure

Is your feature request related to a problem? Please describe.
Currently we supply -stable suffix to push stable images to CERN registry. But the CERN registry has its own retention policy, e.g. 1 year for stable images. If we will freeze WM system we should also freeze and preserve images which are required for WM services to operate, like CouchDB. Otherwise we may end-up with non reproducible behavior where CouchDB or any other images will no longer be available.

Describe the solution you'd like
We should preserve in a safe place all images we use in current WM system before its freeze, including all dependent images like CouchDB, MariaDB, etc., as well as full set of Python packages used by WM services (to avoid their potential disappearance from PyPi repository). This can be accomplished in different ways, e.g.

• copy all used images and Python packages to safe location, like EOS and make proper backup
• negotiate with CMSWEB/CERN IT how to preserve images using registry or their infrastructure
• copy all images and Python packages to tape

NOTE: The full list of images and packages along with archival script can be found in this gist

Describe alternatives you've considered
The only alternative we have so far is to rely on CERN registry repository and push all our stable images over there and extend their lifetime.

Additional context
This task can be delegated and accomplished by CMSWEB team.

[amaltaro]

Hi @vkuznet as a follow up of today's meeting, is it okay if we add the PyPi packages to the scope of this ticket? If so, then we need to slightly update the issue description and title.

[vkuznet]

I created corresponding Jira ticket: https://its.cern.ch/jira/browse/CMSKUBERNETES-302 to track steps during preservation.