Preparing Upgrade WFs in RunTheMatrix

[boudoul]

This PR is adding the upgrade workflows in RunTheMatrix
While large software developments are still needed to make the upgrade geometries working in 74X, runTheMatrix is now ready for the different configurations as it was defined in 62XSLHC and will also help developers to get recipe when developing the ugrade software
This change is not impacting any of the standard workflows used in IBs or during the injection of the relvals.
The upgrade workflows can only be called with the --what upgrade option and therefore are not run in IBs. (until we have something really running)
@mark-grimes : FYI

[cmsbuild]

A new Pull Request was created by @boudoul (boudoul) for CMSSW_7_4_X.

Preparing Upgrade WFs in RunTheMatrix

It involves the following packages:

Configuration/PyReleaseValidation

@cmsbuild, @srimanob, @nclopezo, @boudoul, @franzoni can you please review it and eventually sign? Thanks.
@ghellwig, @Martin-Grunewald this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.

[ghost]

@cmsbuild please test

[cmsbuild]

The tests are being triggered in jenkins.

[franzoni]

+1

HI @boudoul , what you propose is all fine. A few tests revealed no problems.
Two comments, which are for us PdmV ( @srimanob ) and offline more in general

• handling "epochs" / "eras" in a systematic way which is not only top-level dictionaries is the organic way of managing multiple versions of the CMS experiment co-existing in the same release; besides relval, also production sequences (e.g. : recent need of different L1 emulation sequences for 50ns, 25ns ) could be handled more cleanly that way.
  @davidlange6 we spoke about this a year ago or os, you said at the time there was development ongoing, can we try anything out ?
• more relval -specific: we could forward-think and figure out if / which commonality do we expect to have between the runII- and upgrade-specific dictionary/tuples . Better merging all options in the same file or splitting ? "relval_upgrade.py " and upgradeWorkflowComponents.py could merge in one.

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs unless changes or unless it breaks tests.

[davidlange6]

There is a pull request implementing eras in 74x since a while. (Thanks to @mark-grimes ) - it needs some attention from me.

[cmsbuild]

+1
Tested at: d3b4c14
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7313/2050/summary.html

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs unless changes (tests are also fine). This pull request will be automatically merged.

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7313/2050/summary.html

[franzoni]

thanks @davidlange6 @mark-grimes good news about eras!
Can you let us PdmV know @boudoul @srimanob know when we can take a look, and understand implications for production and relvals ? Tks.

[franzoni]

@davidlange6 @mark-grimes, which one is the PR in question ?
@boudoul @srimanob

[davidlange6]

#6784
which can be found via the github search (or the 74x PR list)
https://github.com/cms-sw/cmssw/search?q=era&type=Issues&utf8=✓