cah-patrickthiem

After some research, see [here](https://github.com/SovereignCloudStack/standards/issues/366#issuecomment-2045429707) and below, I came to following conclusions: The GPU flavor naming should be changed in a way that is more clear what to expect and...

For the record, since I presented the current state in todays (10.07.24) IaaS call. My favorite way of gpu flavor naming looks like this: 1. do not use SMs, CUs...

> General comments: > > * I think it's an excellent idea to include the amount of VRAM that the VM will have access to. > * To get an...

> Hi Patrick, > > thanks for the very detailed analysis. > > No, performance is not linear, as it depends on the bottleneck. Sometimes memory bandwidth is the limiting...

I close this PR because we finally came to a common conclusion, see this PR https://github.com/SovereignCloudStack/standards/pull/780, which by now already was merged.

Current status of this topic & some open questions: - this standard will be a rather more general standard, with important topics directly associated with IPv4 handling and linking to...

For the record, that topic was discussed recently in a SCS IaaS meeting, initiated by kgube. One of the questions was, if we want to define all network topics in...

Just for the record. I did some research on how hyperscalers are doing the naming of GPU flavors to maybe get some inspiration or "common practices". However, neither of the...

> I'll add a longer commentary based on the outcomes of the nova operator hour of the Caracal vPTG here later and elaborate on why a different way of pursuing...

For reference, here the successful test logs of sonobuoy: cat results/plugins/scs-kaas-conformance/sonobuoy_results.yaml | yq name: scs-kaas-conformance status: passed meta: type: summary items: - name: out.json status: passed meta: file: results/global/out.json type:...