Implement supporting of compose based recipes by OpenShift infrastructure

[sleshchenko]

Description

Implement supporting of compose based recipes by OpenShift infrastructure.

[dmytro-ndp]

It makes it impossible to create workspace of Java-MySQL types

[garagatyi]

@dmytro-ndp yes, it is expected for the time being.

[skabashnyuk]

@l0rd @ibuziuk is there any plans for this issue?

[l0rd]

I think we can leave without it until Che 7 (ws.next). @slemeur what do you think?

[slemeur]

agreed for the time being.

[garagatyi]

In case someone wants to contribute it here are a couple of tips:
Here is an example of a converter that converts one environment into another https://github.com/eclipse/che/blob/master/infrastructures/kubernetes/src/main/java/org/eclipse/che/workspace/infrastructure/kubernetes/environment/convert/DockerImageEnvironmentConverter.java
This is a very simple one, a converter of compose would be more complex because compose recipe contains a lot of syntax constructs.
Here is an example of a compose converter https://github.com/eclipse/che/blob/master/infrastructures/docker/infrastructure/src/main/java/org/eclipse/che/workspace/infrastructure/docker/environment/convert/ComposeEnvironmentConverter.java
It shows pretty well how it can be implemented on the k8s infra.
After implementing such a converter it is needed to apply it, so here is a place and an example where/how to do it https://github.com/eclipse/che/blob/master/infrastructures/kubernetes/src/main/java/org/eclipse/che/workspace/infrastructure/kubernetes/KubernetesInfrastructure.java#L76

This is it. I hope it would be enough to implement such a feature. If not, do not hesitate to ask me for more details.

[tgrall]

agreed for the time being.

If this is not working why not hiding this option until it works?

[garagatyi]

We can hide it. But not sure which part should do that. API can avoid returning is, but I'm not sure we need this behavior. The client can skip it. Or client can ask for only supported ones from the API.
On the other hand, stacks might not make sense in Che 7, so we can avoid investing in that.

[skabashnyuk]

@l0rd is this issue still relevant for Che7?

[l0rd]

I guess this is still relevant. @slemeur?

[ibuziuk]

@gorkem @slemeur any plans to invest into this or can we close this one?

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.