You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
cmsweb-testbed is a level up from the testX clusters. Meant for initial integration tests with more stable code
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!
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.
pileupInstance = '-testbed' if 'cmsweb-testbed' in dbsUrl else '-prod'
Create new MongoDB cluster (or database under cmsweb-testbed)
Create new CouchDB cluster
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
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
The text was updated successfully, but these errors were encountered:
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.
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
WMCore/src/python/WMCore/WorkQueue/Policy/Start/StartPolicyInterface.py
Line 285 in 2748054
Create new MongoDB cluster (or database under cmsweb-testbed)
Create new CouchDB cluster
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
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
The text was updated successfully, but these errors were encountered: