The Operator Controller can provide Deppy with a set of constraints and return a solution set consisting of entity IDs.

[awgreene]

User Story:

• As a Deppy user, I would like to provide Deppy a list of constraints and Entity Sources and be returned a solution set consisting of entity IDs.

Acceptance Criteria:

• If a solution set is found, the list of entity IDs are returned.
• If no solution set is found, an error explaining why the constraints could not be met is returned.
• The operator CR's status is updated to reflect that an entity satisfying it's constraints have been found.

[joelanford]

Is this issue in the correct repository?

[awgreene]

@joelanford this Issue focuses on the Operator Controller using the Deppy Library to to find the entity IDs so it's in the correct repository. Probably warrants a better description though.

[varshaprasad96]

This is an attempt to break down the issue and understand the implementation required to integrate with Deppy. Please correct me if I'm wrong. Also, I have a few follow up questions which would be helpful in understanding the next steps.

The process involved here is to provide Deppy with entity sources and constraint generators so that we can call the "DeppySolver" (https://github.com/operator-framework/deppy/blob/36fa82370999fb0fa8c6a04f9fff228e58e5bc3b/pkg/deppy/solver/solver.go#L26).

1. Entity Source - This in my mind are the list of packages which need to be installed. It includes the dependencies - for ex., prometheus-0.0.1, requires x-0.0.2, y-0.1.0 etc.
2. Constraint generator - The constraint generator needs a variable source . These are basically the OLM constraints as introduced by OLM constraints deppy#55.

The questions which I have are:

• How does the Operator Controller get the inputs for (1) and (2), given the Operator API spec only has the package name. Do we query the bundleDeployments available (installed by rukpak provisioner) on the cluster?
• Are the constraint generator values from FBC / Venners (https://olm.operatorframework.io/docs/reference/file-based-catalogs/#specification) and does "relatedImages" reflect the dependencies. If so, it doesn't seem like operator api has access to bundle. What is the entry point or how can the operator controller get the required inputs.

[perdasilva]

I think #101 closes this