-
Notifications
You must be signed in to change notification settings - Fork 16
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
Transition this repository as XSEDE Project Ends #11
Comments
Is the virtual cluster in current/active use on any infrastructure other than Jetstream2? |
We run a modifed version on Cornell’s Red Cloud OpenStack.
From: Chris Martin ***@***.***>
Date: Tuesday, June 21, 2022 at 1:36 PM
To: XSEDE/CRI_Jetstream_Cluster ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [XSEDE/CRI_Jetstream_Cluster] Transition this repository as XSEDE Project Ends (Issue #11)
Is the virtual cluster in current/active use on any infrastructure other than Jetstream2?
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA45CTJHHW7DC3XH7YESOSTVQH4R7ANCNFSM5ZNCFC4Q>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
In theory everything under the XSEDE Github Org was going to be transitioned to ACCESS (I think Eric Blau was leading that)... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As XSEDE projects transition to ACCESS, find a new home for Virtual Cluster Repo. For background - https://www.xsede.org/advancetoaccess
One potential place is to work with the Jetstream2 project to home it.
The goal is to nurture a community for this code base and keep the user community active.
The text was updated successfully, but these errors were encountered: