Hi,
Rather than a full rename of the SE would a DNS alias work?
We’re running a couple of services behind DNS aliases (argus and xrootd, not an SRM!) without issues, we just needed special certs with the alias as a subjectAltName.
Yours,
Chris.
On 11/02/2016, 11:04, "GRIDPP2: Deployment and support of SRM and local storage management on behalf of Alastair Dewhurst" <[log in to unmask] on behalf of [log in to unmask]> wrote:
>Hi All
>
>We had a brief discussion about this at the ATLAS Cloud support meeting earlier.
>
>ATLAS jobs are failing because they were still trying to access the old SE. However this can easily be changed in AGIS and I believe I have now fixed the parameter that I forgot to update last year. Jobs will hopefully start passing soon.
>
>The other problem is that the rename has meant anyone using the LFC no longer has access to their files. There are two solutions:
>- Rename the SE back.
>- Rename the files in the LFC so those at Sussex have the correct path.
>
>If the SE is renamed, I should be able to change back the ATLAS settings quickly (15 mins). However this is some work for the site admins and Matt R-B no longer works there, so there is a loss of expertise. I know doing renames of the LFC have been done in the past, but RAL don’t particularly like doing this. I will have to investigate how much effort it would be.
>
>Any thoughts/suggestions or anything else we need to consider?
>
>Alastair
|