-
Notifications
You must be signed in to change notification settings - Fork 44
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
multiple 1click-hpc clusters with the same FSx will crash enginframe #27
Comments
yes, right. we could consider using something like /fsx/nice/{instanceID}/ instead. |
Sounds reasonable
Obțineți Outlook pentru iOS<https://aka.ms/o0ukef>
…________________________________
De la: Nicola Venuti ***@***.***>
Trimis: Thursday, July 7, 2022 4:46:54 PM
Către: aws-samples/1click-hpc ***@***.***>
Cc: Richard Vencu ***@***.***>; Author ***@***.***>
Subiect: Re: [aws-samples/1click-hpc] multiple 1click-hpc clusters with the same FSx will crash enginframe (Issue #27)
yes, right. we could consider using something like /fsx/nice/{instanceID}/ instead.
what do you think ?
—
Reply to this email directly, view it on GitHub<#27 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AACGFM3UEVCMPEP4XE4XSZLVS3NU5ANCNFSM52HNURIA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
or what about cluster name that has to be unique anyway?
|
yes this is an option because the module that install EF backup an existing EF installation. So you are fine deleting an old cluster a creating a new one with the same name mounting the same FSx. |
on the post.install.sh, line 62 and on 10.install.enginframe.headnode.sh line 60
then multiple clusters can live side by side with the enginframe portals intact |
yep! can you sent a PR specifically with this modification so I can incorporante |
Since the /fsx/nice location is not unique to the cluster, starting multiple clusters with the same fsx will overwrite the portal data for older clusters
The text was updated successfully, but these errors were encountered: