Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes required for adoption of the cmsweb-preprod cluster #12067

Open
amaltaro opened this issue Aug 6, 2024 · 0 comments
Open

Changes required for adoption of the cmsweb-preprod cluster #12067

amaltaro opened this issue Aug 6, 2024 · 0 comments

Comments

@amaltaro
Copy link
Contributor

amaltaro commented Aug 6, 2024

Impact of the new feature
WMCore in general

Is your feature request related to a problem? Please describe.
We have recently decided to have a 3rd cluster for integration tests, called cmsweb-preprod. A short summary is:
0) cmsweb-testX clusters: a developer's playground environment to test, patch, change, and do whatever we need when developing for central services.

  1. cmsweb-testbed is a level up from the testX clusters. Meant for initial integration tests with more stable code
  2. cmsweb-preprod is yet another level up from testbed cluster. Meant for pre-production code, so code that we are actually preparing to push to production. It is meant to be stable!
  3. cmsweb-prod/cmsweb is the production environment.

Having said that, we are moving towards the adoption of cmsweb-preprod in CMS (and WM). So this ticket is meant to track all the relevant changes that we need to either a) revise or b) update the codebase for.

Note that some cmsweb-preprod details are still under discussion, e.g. dbs url to be used and separation of CouchDB (and MongoDB) backends.

Describe the solution you'd like

  1. https://github.com/dmwm/WMCore/blob/2748054/src/python/WMCore/WorkQueue/DataLocationMapper.py and
    pileUpinstance = '-testbed' if 'cmsweb-testbed' in dbsUrl else '-prod'
    using a code like:
                pileupInstance = '-testbed' if 'cmsweb-testbed' in dbsUrl else '-prod'
  1. Create new MongoDB cluster (or database under cmsweb-testbed)

  2. Create new CouchDB cluster

  3. Considerations for the data stored in the database? I would suggest moving cmsweb-testbed data over to cmsweb-preprod and start with a fresh database in cmsweb-testbed

  4. testbed agents will have to move to cmsweb-preprod

In terms of WMCore codebase, I don't think there is anything else to consider. We might want to revisit the workflow json templates though.

Describe alternatives you've considered
None

Additional context
None

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant