Fetch RSE info from Rucio and save to a file

[d-ylee]

Would close #770

Currently in progress.

The script can first fetch RSE settings and attributes from Rucio. Will have to use the RSEClient to update settings with update_rse and attributes with delete_rse_attribute and then add_rse_attribute.

The json looks like this:

{
    "settings": {
        "setting1": "1",
        "setting2": "2",
    },
    "attributes": {
        "attribute1": "1",
        "attribute2": "2"
    }
}

The question is where should we store the settings file. As with consistency checker and protocols, we could also use SITECONF in the CERN Gitlab instance.

[ericvaandering]

seems like a good start for a draft PR

[ericvaandering]

res_info

usage and limits are unused, right?

[ericvaandering]

Sets

[ericvaandering]

Yes

[ericvaandering]

Settings is still coming?

[d-ylee]

@Panos512 @ericvaandering @haozturk I made some updates. Currently, I don't have permission to directly commit to a SITECONF project (currently using T2_US_Nebraska). To test the initial upload script, I forked the SITECONF project and then ran my script to commit to it. Details here: https://gitlab.cern.ch/SITECONF/T2_US_Nebraska/-/merge_requests/1

I am also updating CMSRSE.py and the setRucioFromGitlab to read from the SITECONF//rucio directory for RSE settings and attributes.

One thought I have is to include the last commit id for a config and set that as an RSE attribute:

CMSRucio/docker/rucio_client/scripts/setRucioFromGitlab

Lines 89 to 92 in f86e809

	# load rucio attributes and settings from gitlab
	f = full_project.files.get(f'rucio/{rse_name}.json', 'master')
	rucio_attrs = json.loads(base64.b64decode(f.content))
	commit_id = f.last_commit_id

We could use this to keep track of the current RSE configuration. I was also thinking we could include another attribute to keep track of which storage.json is currently applied to an RSE.

Would this be a good idea?