HyperShift demo for NERC

[joachimweyl]

Motivation

Demo what we have working for Hypershift and how it can be used by the NERC team.

Completion Criteria

A demo that demonstrates Hypershift and how it can be used in the NERC.

Description

• Create a Demo
• Record any parts that need processing time so we can speed them up or cut the processing time
• Schedule a Demo
• Sign off from NERC team

Completion dates

Desired - 2024-12-06
Required - 2024-12-20

[larsks]

Because of the issues I ran into adding esi nodes to the existing hypershift cluster, I'm redeploying it entirely on ESI nodes. This should be something I can complete today, now that the NESE ACL has been updated. I'll return to this issue as soon as that's complete.

[joachimweyl]

@larsks what are the next steps for hypershift?

[hpdempsey]

On Tue, Jan 7, 2025 at 8:26 AM Joachim Weyl ***@***.***> wrote: @larsks <https://github.com/larsks> what are the next steps for hypershift?

First we need feedback from the MOC engineers who were not able to view the demo (it was recorded). This will help make clear what are the next steps to being able to support this a production-ready way to manage project deployments. At the end of the demo, the Red Hat engineers indicated that we plan to go ahead and use HyperShift immediately to create new projects that can not use the production NERC infrastructure for various reasons (e.g. need a newer version of OCP that what is in production). We are already supporting these projects outside of production, so that is a straightforward next step for us. But there may well be more things that the NERC engineers to consider doing this for production-level project support.

…

— Reply to this email directly, view it on GitHub <#860 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMGMIEK5NZHDPY6E4ESBF5D2JPIYTAVCNFSM6AAAAABTLKZ6ZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZVGI4TGOJSHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>