{"resourceId":"nerc-service-suspension-openshift-ai-research-cloud-faq","versions":[{"version":"external-2b5695e6d7c6d3ec839d6cac5bd1318f71861d3cfc0cc0cb97f6aebd3d038535","resource":{"id":"nerc-service-suspension-openshift-ai-research-cloud-faq","title":"NERC service suspension and data preservation FAQ: regional research cloud with OpenShift AI paused while MOC 2.0 is built","organization":"New England Research Cloud (NERC) / Mass Open Cloud","sector":"Higher education research computing (regional academic cloud)","geography":"New England / Massachusetts, U.S.","publishedAt":"NERC/MOC FAQ page (undated; retrieved Oct. 29, 2026)","publicationDate":null,"eventDate":"2026-07-31","sourceName":"Mass Open Cloud","sourceLabel":"NERC Service Suspension and Data Preservation FAQ","sourceUrl":"https://massopen.cloud/faq/","evidenceClass":"public-sector-association","outcomeClass":"cautionary","topics":["infrastructure","operating-model","governance-procurement"],"finding":"The New England Research Cloud said its current services, including OpenStack, OpenShift and OpenShift AI (RHOAI) workbenches and model serving, would be suspended on July 31, 2026, because it lacks resources to maintain them while building a new platform under the MOC name. That platform is intended to support NIST 800-171 and HIPAA workloads. NERC said it would not migrate projects. Users had to export and verify data, notebooks, models and configurations themselves. The suspension was expected to last several months. MOC 2.0 timelines, quotas, GPUs, onboarding and approvals are not yet set, and endpoints, quotas and GPUs are not guaranteed to return.","sledRelevance":"A rare public account of a shared academic OpenShift AI platform pausing service. It is directly relevant to universities and state research consortia that host shared AI platforms for faculty and courses. It shows that platform continuity, export responsibility and regulated-data readiness are operating-model risks separate from the technology itself.","evidence":"Read the full FAQ page. The page is undated; the July 31, 2026 suspension date is stated in the text. It is an operator notice to users, not an evaluation. It gives no figures on affected users, projects or costs, and does not explain the funding or staffing situation beyond lacking resources to run both platforms.","architectureImplications":"Projects on shared OpenShift AI need portable artifacts: manifests, images, model checkpoints, data connections and endpoint configuration documented so they can move. Endpoints and routes should be parameterized.","governanceImplications":"PIs and project leadership carry export and retention responsibility. Funder and data-management obligations continue through platform changes, and agencies may need notification.","securityPrivacyImplications":"Current NERC services are not approved for regulated data. Planned NIST 800-171 and HIPAA support was a driver for the rebuild. Secrets must be documented and rotated, not exported insecurely.","caveats":"The page is undated, so the publication date is unknown. It is an operator FAQ with no quantitative impact data. The Red Hat product role is inferred from listed services (OpenShift, RHOAI).","streamIds":["red-hat"],"roles":{"sales":"Sales framing: handle this one carefully. It is a customer-side continuity failure, not a product failure, but it shows the risk for shared university AI platforms. For research consortia and university systems, the opening is continuity planning: supported subscriptions, managed operations or partner capacity so a platform rebuild does not mean a service pause. Avoid exploiting the situation publicly. Use it to ask how the customer would keep services running while modernizing.","engineering":"Engineering framing: NERC's checklist is effectively a portability spec for OpenShift AI projects. That means exporting workbench storage, notebooks, pipelines, model-serving configuration, data connections and environment definitions, and verifying that models load elsewhere. For any shared platform, design for portability from the start with GitOps manifests, image build sources, externalized endpoints and documented secrets references. Plan regulated-data enclaves (NIST 800-171, HIPAA) as separate, accredited environments.","delivery":"Delivery framing: shared AI platforms need a continuity and transition plan before launch. That covers funding for parallel running, migration support, export tooling and user communication. Assign export responsibility to PIs explicitly, as NERC did, but also provide verification checklists. For instructors, require reproducible course environments. Budget the staff time that a platform transition consumes, which is what NERC said it lacked."},"roleDetails":{"sales":{"customerProblem":"Shared academic AI platforms can lack the funding and staff to operate existing services while building successors.","stakeholders":["Research computing director","Consortium governance board","University CIOs","Research administration offices"],"discoveryQuestions":["How would you keep current AI services running during a platform rebuild?","Do projects have documented, portable artifacts?","Which projects need NIST 800-171 or HIPAA environments?"],"valueHypothesis":"Managed operations or partner capacity during transitions could avoid service pauses for researchers and courses.","potentialEngagement":"Platform continuity and portability assessment for a shared research OpenShift AI environment.","unsupportedClaims":["That the pause was caused by Red Hat software","Any number of affected users or projects","Timeline for MOC 2.0"]},"engineering":{"fit":"Applies to multi-tenant research OpenShift AI platforms serving many institutions.","architectureIntegration":"GitOps-managed manifests, image build pipelines, externalized endpoints, S3-compatible storage with export paths, separate regulated-data enclaves.","prerequisites":["Inventory of tenant projects and storage","Export tooling (Globus, rclone, etc.)","Documented environment definitions"],"constraints":["Undated source with no impact metrics","Future platform details not finalized","Users responsible for their own exports"],"security":"Do not store regulated data on unapproved platforms. Document and rotate secrets during migration.","proofOfValue":["Restore a sample project's notebooks and model on another cluster","Verify checksums for exported datasets","Confirm endpoints can be reconfigured without code changes"]},"delivery":{"work":"Create continuity, export and migration plans for shared AI research platforms.","dependencies":["Consortium funding decisions","Staff capacity","Destination storage"],"ownership":"Platform operator for tooling and communication; PIs for project exports.","skillsAdoption":"Train project teams on export, verification and reproducible environments.","governanceCheckpoints":["Transition plan approved before announcing changes","Funder notification review","Post-export verification sign-off"],"acceptanceCriteria":["Proposed: every active project has a verified export or migration path","Proposed: course environments reproducible on another platform","Proposed: regulated-data projects routed to approved environments"],"risks":["Research data loss","Course disruption","Prolonged gap before successor platform"]}},"retrievedAt":"2026-10-30T03:18:38Z","enrichedAt":"2026-10-30T03:21:15Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Students, instructors and courses that depended on RHOAI workbenches lose access during the pause. Courses must be made reproducible elsewhere.","procurementImplications":"Institutions relying on consortium platforms should check service-level terms; the NERC EULA lets the provider modify, suspend or discontinue services.","operatingModelImplications":"Running a shared AI platform while building its successor required more resources than were available, forcing a pause. Consortia need funding and staffing for parallel operation during transitions.","sourceVerification":{"openedUrl":"https://massopen.cloud/faq/","referenceExcerpt":"We expect this suspension to last for several months while the new platform is built, tested, and prepared for onboarding.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}