-
Notifications
You must be signed in to change notification settings - Fork 31
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
Enhancement: Action needed before upgrading to Rucio 34.1 with tokens #767
Comments
I believe we need an update to FTS. But as we are not using tokens currently, we should be OK. @dynamic-entropy @KatyEllis |
Conversation with Steve Murray on the Rucio Mattermost channel ‘tokens’:
Katy Ellis
4:52 PM<https://mattermost.web.cern.ch/rucio/pl/6du6jedoxjd99b6wbpiurnxfie>
hi @steven Murray , should we do anything for CMS? Do we need to request/wait for an FTS upgrade? CMS are currently not using tokens in Rucio, everything has been reverted to certs for the time being. I believe we are waiting for a change from IAM. And we are always a step behind ATLAS on Rucio upgrades
[smurray profile image]
Steven Murray
5:03 PM<https://mattermost.web.cern.ch/rucio/pl/wtfqufhaibg75m13jnbmzpbp8y>
?????
We have not emphasized this but ...
Token support is on for fts3-cms.cern.ch
We have optimised the SQL used in the current "poll the database for near-to-expire tokens" solution.
We will now stay is this "situation" where the fts3-atlas.cern.ch, fts3-cms.cern.ch, fts3-lhcb.cern.ch and fts3-pilot.cern.ch instances at CERN support tokens but there is no official release.
On request we will allow "crazy" token tests to be carried out on fts3-pilot.cern.ch. Nothing "crazy" should be carried out on fts3-atlas.cern.ch, fts3-cms.cern.ch or fts3-lhcb.cern.ch.
[kellis profile image]
Katy Ellis
5:14 PM<https://mattermost.web.cern.ch/rucio/pl/imzakkambbnf7ga3nh535ni4rh>
ok, 'crazy' being 3 tokens per transfer, for example?
i didn't realise you made some improvements already. Should we expect more in the next couple of months or is token development relatively stable now?
[smurray profile image]
Steven Murray
5:17 PM<https://mattermost.web.cern.ch/rucio/pl/4m6k8oq5eigi7yhfdy6wby1ear>
Yes, by "crazy" I mean the number of tokens is a function of the number of file transfers.
3 tokens per file for example.
The development of token-support for our production instances has now stopped. The "poll the database for near-to-expire tokens" solution is where we stop for now, but ...
Mihai will start to work on "official release" token support. This will take a different approach to what we have now and it is still difficult to give a timeline.
[kellis profile image]
Katy Ellis
5:22 PM<https://mattermost.web.cern.ch/rucio/pl/ig79sttu3tyydce5iqc9hicwnc>
ok thanks. Let us know when things become a bit clearer with Mihai's development
From: Eric Vaandering ***@***.***>
Date: Thursday, 4 April 2024 at 16:21
To: dmwm/CMSRucio ***@***.***>
Cc: Ellis, Katy (STFC,RAL,PPD) ***@***.***>, Assign ***@***.***>
Subject: Re: [dmwm/CMSRucio] Enhancement: Action needed before upgrading to Rucio 34.1 with tokens (Issue #767)
Assigned #767<#767> to @KatyEllis<https://github.com/KatyEllis>.
—
Reply to this email directly, view it on GitHub<#767 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKJUGQP55GJ2K5N4G4MYAD3Y3VVW5AVCNFSM6AAAAABFXHZJMSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGM3DAMJZGY4TIOA>.
You are receiving this because you were assigned.Message ID: ***@***.***>
|
That doesn't seem to say anything, one way or the other, about the audience changing for FTS, which I gather is the point of that patch. In any case, I don't see a reason to hold up upgrading Rucio to this release since the token change is a no-op right now. |
Yup, by the time we enable tokens, we shall have a new FTS version. |
Enhancement Description
Follow rucio/rucio#6590 and our FTS installations
Use Case
TBD
Possible Solution
No response
Related Issues
No response
The text was updated successfully, but these errors were encountered: