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.

Sign up for GitHub

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

Jump to bottom

configuring scram versions for Tier0 workflows #3257

Closed
hufnagel opened this issue Feb 14, 2012 · 0 comments
Closed

configuring scram versions for Tier0 workflows #3257

hufnagel opened this issue Feb 14, 2012 · 0 comments
Assignees
@hufnagel

Comments

@hufnagel
Copy link
Member

At the moment the scram versions are hardcoded in the specs. I could add them to the Tier0 configuration, but is this really needed ? Changing scram versions is a big deal, maybe it's enough to sync that switch with a switch of the deployed Tier0 code.

If we add them to the Tier0 configuration, at what granularity ? Adding a scram version for every cmssw version used for every stream or dataset config is the most flexible, but might be overkill...
@ghost ghost assigned hufnagel Jul 24, 2012
hufnagel added a commit to hufnagel/T0 that referenced this issue Dec 3, 2013
@hufnagel
allow configuring scram arch for everything, fixes dmwm#3257
4c3376e 
Allows to setup a default scram arch for all releases and then
overrides for specific releases. This reduces the amount of
configuration options as one specific release is only used
from a single scram arch no matter in how many places in the
Tier0 it is configured.

Express and Repack CMSSW overrides are now not stored as
overrides anymore but stored in the repack_config or
express_config database tables. Also store the optional
extra second step reco release for Express and store
scram arch for all choices separately. The reco_config
table keeps its CMSSW version and scram arch columns.

The stream cmssw association table now only has the
online CMSSW version, the override was removed as it
isn't needed anymore.

Also get rid of all PromptSkim releated code.
hufnagel added a commit to hufnagel/T0 that referenced this issue Dec 3, 2013
@hufnagel
allow configuring scram arch for everything, fixes dmwm#3257
776617f 
Allows to setup a default scram arch for all releases and then
overrides for specific releases. This reduces the amount of
configuration options as one specific release is only used
from a single scram arch no matter in how many places in the
Tier0 it is configured.

Express and Repack CMSSW overrides are now not stored as
overrides anymore but stored in the repack_config or
express_config database tables. Also store the optional
extra second step reco release for Express and store
scram arch for all choices separately. The reco_config
table keeps its CMSSW version and scram arch columns.

The stream cmssw association table now only has the
online CMSSW version, the override was removed as it
isn't needed anymore.

Also get rid of all PromptSkim releated code.
hufnagel added a commit that referenced this issue Dec 4, 2013
@hufnagel
Merge pull request #4059 from hufnagel/scramarch
5997fbd 
allow configuring scram arch for everything, fixes #3257
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hufnagel hufnagel

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hufnagel