search

redhat-performance / jetlag

Automation to deploy Bare-metal OpenShift leveraging the Assisted-Installer
Apache License 2.0
26 stars 41 forks source link

[RFE] du_profile var to do a full vDU profile #446

Open jtaleric opened 6 months ago

jtaleric commented 6 months ago

https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.html#ztp-sno-post-install-time-cluster-config

Right now du_profile does not apply much of the post-install-time recommendations. This resulted in me seeing SNO issues that were not vDU specific (like the registry taking 4 cores).

akrzos commented 6 months ago

@Noreen21 would you be able to chime in here on what the delta on having a single var is to have the du profile applied to an SNO would be? Is it possible with the current setup to do a connected SNO with du profile or only disconnected with du profile? From my work on ACM deploying SNOs with the du profile I believe it should be possible.

dbutenhof commented 3 months ago

Is this redundant with #451 ?? Is there additional context implied here?

akrzos commented 3 months ago

This isn't redundant, the DU profile is pretty complicated set of configuration, and on top of that it isn't standard for every set of hardware. There are two efforts, one in which ideally we have a single var to make an SNO be DU compliant, and another where the rest of the DU profile items are actually automated and installed (additional operators), both and not completed yet with no timeframe on when they will be completed, maybe @Noreen21 knows if these will be picked up eventually?

dbutenhof commented 3 months ago

For some reason, we ended up with a Jira equivalent of this issue at the top of our backlog. I've spent some time attempting to grasp both what Jetlag currently does in this area as well as the documentation link cited, and clearly, your "is pretty complicated" phrase is a massive understatement.

We can attempt to make some progress towards at least some subset of the massive and confusing territory implied by "post-install (v)DU configuration", but we need a lot more clarification and detail to get a foothold. The fact that you clearly see a difference between these two issues while I don't is probably a good capsule summary of our context. 😆

If this is something that's better left to "the grownups" at a later time, that's cool.