You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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: ***@***.***>
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: