search

okd-project / okd

The self-managing, auto-upgrading, Kubernetes distribution for everyone
https://okd.io
Apache License 2.0
1.72k stars 295 forks source link

Community testing #1959

Closed JaimeMagiera closed 2 months ago

JaimeMagiera commented 3 months ago

Per discussion on the Community Development meeting, here is an initial pass at a pre-release testing info document. Feedback very much welcome.

bernhardloos commented 3 months ago

I admit I'm not really sure how useful the discussion category approach is for collection test feedback. In general there are two goals for this pre-release testing:

  1. Getting a release signal, i.e. how well does the release work and did anybody even test it. I suspect it will be pretty hard to extract some solid metrics from from free from discussion entries. Something like the system from Jenkins would probably be much more useful here, maybe also in connection with some weekly release channel. But I admit somebody would have to sit down and build such a system first.
  2. Finding bugs. Those should e reported as actual bugs and some information where to do this would be useful. The OKD GitHub? The component GitHub? Redhat JIRA? I don't know for sure myself. Also, this is only useful if somebody actually sits down to triage and fix those bugs. I guess this comes down to the question of how much resources the OKD project actually has and if RedHat engineers are willing to investigate OKD bugs (which are probably also Openshift bugs).
JaimeMagiera commented 3 months ago

@bernhardloos Thanks for the questions. They are connected: The discussion threads are just a temporary way to gather information until we have more time and resources, and a greater understanding of what is possible, to do something more substantial. The Red Hat employees working on the project have Jira. However, new issues cannot currently be created by the general public and we don't have a bug submissions front end yet.

The initial Enhance Request which started this process earlier in the year notes that bugs can be submitted by the community and taken up by Red Hat engineers. The goal is to eventually move the build process to infrastructure that would allow more direct community involvement. That's down the road though.

We need some way to get basic feedback on these initial pre-releases while we work out those bigger picture details.

Does that provide some context?

titou10titou10 commented 3 months ago

It seems that all UPI "pre-release" install/tests are excluded by this procedure as "./openshift-install create cluster"only allows IPI install

Is there another "procedure" for testing UPI installed clusters ?

Thx

JaimeMagiera commented 3 months ago

That's actually a copy-paste typo. You can use any of the usual methods to install, including UPI. I'll update the text later today.