From the Red Hat edition of October 29, 2026
NERC service suspension and data preservation FAQ: regional research cloud with OpenShift AI paused while MOC 2.0 is built
New England Research Cloud (NERC) / Mass Open Cloud · Higher education research computing (regional academic cloud) · New England / Massachusetts, U.S.
- Publisher
- Mass Open Cloud
- Original publication
- NERC/MOC FAQ page (undated; retrieved Oct. 29, 2026)
- Source retrieved
- 2026-10-30
- Event date
- 2026-07-31
What happened
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.
Why it matters
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 and measured results
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.
Limitations and uncertainty
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).
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- 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
- Discovery questions
- 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?
- Value hypothesis
- Managed operations or partner capacity during transitions could avoid service pauses for researchers and courses.
- Potential engagement
- Platform continuity and portability assessment for a shared research OpenShift AI environment.
- Unsupported claims
- That the pause was caused by Red Hat software
- Any number of affected users or projects
- Timeline for MOC 2.0
Pre-sales engineering
Role takeaway
- Fit
- Applies to multi-tenant research OpenShift AI platforms serving many institutions.
- Architecture and integration
- 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.
- Proof of value
- 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
Role takeaway
- 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.
- Skills and adoption
- Train project teams on export, verification and reproducible environments.
- Governance checkpoints
- Transition plan approved before announcing changes
- Funder notification review
- Post-export verification sign-off
- Acceptance criteria
- 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
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
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.
Governance
Who approves, reviews and stays accountable for outcomes?
PIs and project leadership carry export and retention responsibility. Funder and data-management obligations continue through platform changes, and agencies may need notification.
Security and privacy
What data, permissions and controls need testing?
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.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Students, instructors and courses that depended on RHOAI workbenches lose access during the pause. Courses must be made reproducible elsewhere.
Procurement
What should contracts, pricing and exit terms secure?
Institutions relying on consortium platforms should check service-level terms; the NERC EULA lets the provider modify, suspend or discontinue services.
Operating model
Which teams own the service once it runs?
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.
Publication history
- 2026-10-29Red Hat · Issue 018 resources
Stable resource ID: nerc-service-suspension-openshift-ai-research-cloud-faq