Performing the first round of reconciliation between Cray-HPE and OpenCHAMI repos

[alexlovelltroy]

No description provided.

[ajgarside]

We’re actively looking at this at Cray/HPE. We’re focusing on building OCHAMI on vShasta and running associated automated tests. The data from this will guide next steps. We’ll post updates to this issue.

[rainest]

@ajgarside is vShasta available outside HPE at all? I'd very much like to have some option for a virtualized set of nodes to develop against. Our actual test hardware is normally tasked with ongoing pre-production testing, and isn't readily available for me to develop against. Virtualized dummy nodes would provide a lot more leeway to vet new (probably buggy) code before a more complete test against actual hardware.

[ajgarside]

Unfortunately, I don’t think vshasta works for what you want. It’s very tightly coupled with CSM and GCP. There’s a future vshasta effort based on vTDS that will be more flexible, but it’s not something we have today...

[alexlovelltroy]

We're publishing attested containers. Can you import those into your vShasta environment for testing and share results?

[ajgarside]

I have a meeting with the build & test team today re. OCHAMI build/install/testing. I've already added Travis' request to the agenda; I'll add attested containers as well. We're building an overall plan. I'll ping you by week's end to discuss.

[shunr-hpe]

I'm working on bringing OCHAMI's changes to SMD into CSM's version of SMD. Here is the branch where the changes are being brought in https://github.com/Cray-HPE/hms-smd/tree/ochami-sync

I will then do these things

1. Bring back my CSM changes to OCHAMI
2. Update OCHAMI to the latest CSM code (the merge base of OCHAMI and CSM is old and there have been changes since in CSM)
3. Update CSM to the latest OCHAMI code (this will probably be completed in item 1)

I plan to look into doing some of these things

1. Create a github workflow in CSM's repo that runs tests against an OCHAMI environment.
2. Get the SMD unit tests and CT tests working in an OCHAMI github workflow.

For the time being I'm not bringing any of OCHAMI's build or docker changes into CSM. However, doing tests in CSM against an OCHAMI environment may require bringing these in.

After those things are done the go code should be the same between CSM and OCHAMI, except for minor differences like the package paths due to the difference in the repositories paths.