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

Add new uploader script to CMSSW #33479

Closed
wants to merge 5 commits into from

Conversation

Dres90
Copy link
Contributor

@Dres90 Dres90 commented Apr 20, 2021

PR description:

Include new uploader script for the V2 version of the CondDbUploader to be distributed via CMSSW

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @Dres90 (Andrés Cárdenas) for CMSSW_11_3_X.

It involves the following packages:

CondCore/Utilities

@ggovi, @cmsbuild can you please review it and eventually sign? Thanks.
@mmusich this is something you requested to watch as well.
@silviodonato, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@cmsbuild
Copy link
Contributor

Pull request #33479 was updated. @ggovi, @cmsbuild can you please check and sign again.

@ggovi
Copy link
Contributor

ggovi commented Apr 20, 2021

please test

@tvami
Copy link
Contributor

tvami commented Apr 20, 2021

Hi @Dres90 , thanks a lot for this new uploader script. If you remember at the AlCaDB meeting when you presented about this, I asked if it is possible to do Prep-To-Prod direct uploads (without having to download a local sqlite file from Prep and upload that to Prod) with the new version of the code. I'm wondering how one does that with this new script. Thanks!

@Dres90
Copy link
Contributor Author

Dres90 commented Apr 20, 2021

Hi @Dres90 , thanks a lot for this new uploader script. If you remember at the AlCaDB meeting when you presented about this, I asked if it is possible to do Prep-To-Prod direct uploads (without having to download a local sqlite file from Prep and upload that to Prod) with the new version of the code. I'm wondering how one does that with this new script. Thanks!

Hi @tvami, I do have that noted as a future improvement but currently it is not a functionality offered by the new uploader. Definitely a possibility but we want to get the stable version fully tested before beginning work in improvements.

@tvami
Copy link
Contributor

tvami commented Apr 20, 2021

Hi @Dres90 , thanks a lot for this new uploader script. If you remember at the AlCaDB meeting when you presented about this, I asked if it is possible to do Prep-To-Prod direct uploads (without having to download a local sqlite file from Prep and upload that to Prod) with the new version of the code. I'm wondering how one does that with this new script. Thanks!

Hi @tvami, I do have that noted as a future improvement but currently it is not a functionality offered by the new uploader. Definitely a possibility but we want to get the stable version fully tested before beginning work in improvements.

Ok, looking forward to it!

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-05bb4a/14356/summary.html
COMMIT: f9f3ef9
CMSSW: CMSSW_11_3_X_2021-04-20-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/33479/14356/install.sh to create a dev area with all the needed externals and cmssw changes.

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-05bb4a/14356/git-recent-commits.json
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-05bb4a/14356/git-merge-result

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 6 differences found in the comparisons
  • DQMHistoTests: Total files compared: 38
  • DQMHistoTests: Total histograms compared: 2877046
  • DQMHistoTests: Total failures: 16
  • DQMHistoTests: Total nulls: 1
  • DQMHistoTests: Total successes: 2877007
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.004 KiB( 37 files compared)
  • DQMHistoSizes: changed ( 312.0 ): 0.004 KiB MessageLogger/Warnings
  • Checked 160 log files, 37 edm output root files, 38 DQM output files
  • TriggerResults: no differences found

'\nWhich is the destination database where the tags should be exported? \nPossible choices: oracle://cms_orcon_prod/CMS_CONDITIONS (for prod) or oracle://cms_orcoff_prep/CMS_CONDITIONS (for prep) \ndestinationDatabase: '
elif ntry==1:
inputMessage = \
'\nPlease choose one of the two valid destinations: \noracle://cms_orcon_prod/CMS_CONDITIONS (for prod) or oracle://cms_orcoff_prep/CMS_CONDITIONS (for prep) \
Copy link
Contributor

@tvami tvami Apr 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be possible to simplify this and ask the user to choose between "Prep" or "Prod" instead of the full string of "oracle://cms_orcon_prod/CMS_CONDITIONS" or "oracle://cms_orcoff_prep/CMS_CONDITIONS"? Or even 0 and 1, the same way when we choose the tags? That would make the user's life a bit more convenient. Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the suggestion, it is a great idea.
I have just added that functionality and updated the PR. The suggestions to the user are oradev and orapro to keep consistency with the conddb tools, however it will also resolve to the proper destination if you input "prep" or "prod".

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, thanks!

@cmsbuild
Copy link
Contributor

Pull request #33479 was updated. @ggovi, @cmsbuild can you please check and sign again.

@Dres90
Copy link
Contributor Author

Dres90 commented Apr 21, 2021

PR has been updated with the following changes:

  • Wizard allows user to choose destination database by inputting oradev, oraprod, dev or prod, simplifying the user experience.
  • When no server is specified, the script chooses the appropriate server based on the destination database.

@ggovi
Copy link
Contributor

ggovi commented Apr 21, 2021

please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-05bb4a/14385/summary.html
COMMIT: 4b799df
CMSSW: CMSSW_11_3_X_2021-04-20-2300/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/33479/14385/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 3 differences found in the comparisons
  • DQMHistoTests: Total files compared: 38
  • DQMHistoTests: Total histograms compared: 2877046
  • DQMHistoTests: Total failures: 6
  • DQMHistoTests: Total nulls: 1
  • DQMHistoTests: Total successes: 2877017
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.004 KiB( 37 files compared)
  • DQMHistoSizes: changed ( 312.0 ): 0.004 KiB MessageLogger/Warnings
  • Checked 160 log files, 37 edm output root files, 38 DQM output files
  • TriggerResults: no differences found

@ggovi
Copy link
Contributor

ggovi commented Apr 22, 2021

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_11_3_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2)

@mmusich
Copy link
Contributor

mmusich commented Apr 22, 2021

@ggovi @Dres90 out of curiosity, are users invited to use this in lieu of the old script, once it gets distributed to cmssw?

@ggovi
Copy link
Contributor

ggovi commented Apr 22, 2021

@mmusich good point. At some point, that 'invitation' will be explicit. We are still somewhat in the introductory phase...

@qliphy
Copy link
Contributor

qliphy commented Apr 23, 2021

@Dres90 Please make a PR first to master before backporting to 11_3_X.

@Dres90
Copy link
Contributor Author

Dres90 commented Apr 23, 2021

Closing this PR as it was pointing to a prior release. Replaced by
#33511 now pointing to master branch.

@Dres90 Dres90 closed this Apr 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants