Get score specific for runtime environments available

[fridex]

Is your feature request related to a problem? Please describe.

As Thoth user, I would like to get information about the best runtime environment for my application. For this purpose, I would like to ask Thoth which runtime environment should I use for my specific set of requirements.

Describe the solution you'd like

Run multiple advisers at once, each differing in the runtime environment setup (e.g. different base image, different operating system, different Python interpreter version) but with the same requirements. Then, aggregate results of adviser runs and obtain information about the runtime environment which should be used based on the score - using map-reduce.

• create a workflow that runs multiple advise workflows based on available runtime environments
• create an aggregation task that is run once all the triggered workflows finish and aggregates score computed
• the task reports which runtime environment is the most suitable for running the given application stack
• create a flag on advise endpoint that runs the extended workflow if no runtime environment configuration is supplied
• create an integration test that verifies correctness of the workflow

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[fridex]

/remove-lifecycle stale

We can do this once the recommendations for one runtime environment stabilize. It will be just a manner of providing a workflow for this with a task that will aggregate results of multiple workflows created.

[goern]

@fridex do we have an issue to create the workflow? if not, could you please create it? thx! 🙏

[fridex]

@fridex do we have an issue to create the workflow? if not, could you please create it? thx!

This user story will deserve multiple changes - I've added a list of items that should be done not to create more issues for the same thing. I think we can split the issue items once we decide to work on this.

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[fridex]

Still relevant, see also linked issues.

/remove-lifecycle rotten

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[fridex]

/remove-lifecycle rotten
/reopen
/triage accepted

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[codificat]

/priority important-longterm
/remove-priority backlog

[goern]

@fridex is this a feature we want to push for MVP?

[fridex]

It might be a good idea to postpone it.

[codificat]

/sig stack-guidance