Workspace Infrastructure SPI for v6

[gazarenkov]

Current SPI which provides machines instances is outdated.
Originally it was reworked from v3 implementation where we used it for shared builder/runner.
Then we were oriented to one machine (mostly Docker container) workspace.
As a result it is not good adopted (too stricted) to new requirements such as multi-machine (Compose described) or other nature of infrastructure (such as Kubernetes/OpenShift) and we have to spend a lot of effort for workarounds trying to adopt it.

Base idea of new SPI is that interfaces to implement should be really light, contract not that stricted and as a result the main functional loading is put to concrete Infrastructure implementation.

Pilot implementation of this concept is placed in the "spi" branch.
https://github.com/eclipse/che/tree/spi

• First draft of SPI specification First draft of SPI specification #5035
• Implement snapshotting concept in Docker SPI implementation Implement snapshotting concept in Docker SPI implementation #5101
• Rework SPI components to allow clients to get current state of Runtime while it is still starting Rework SPI components to allow clients to get current state of Runtime while it is still starting. #5092
• Create POC of Codenvy implementation of SPI Create POC of Codenvy implementation of SPI #5100
• Rework Agent installation Rework agents installation #3971
• Rework server pinging to make it more interactive and fast Rework server pinging to make it more interactive and fast #5420
• Specify IDE Application state phases and make it more clear Specify IDE Application state phases and make it more clear  #4900
• Provide all endpoints of an server as separate servers in Runtime Provide all endpoints of an server as separate servers in Runtime #5609
• Termination of workspace infrastructure Termination of workspace infrastructure #5570
• Implement mechanism for providing unique ids for json rpc clients Implement mechanism for providing unique ids for json rpc clients #5439 (Dmitrii)
• Investigate how to run IDE tooling in separate containers Investigate how to run IDE tooling in separate containers #5623
• Che master doesn't restart properly in SPI branch Che master doesn't restart properly in SPI branch #5610
• Provide links of the workspace to the client Provide links of the workspace to the client #5581
• Add server health concept into infrastructure workflow. Add server health concept into infrastructure workflow. #5093
• Run QA in SPI branch and figure out what should be done to adapt QA to SPI

In progress

TODO

Related epics & issues:

• Adapt che dashboard in the spi branch Adapt che dashboard in the spi branch #5887
• SPI 6 Docker implementation SPI 6 Docker implementation #5639
• OpenShift infrastructure implementation of SPI OpenShift infrastructure implementation of SPI #5098

[benoitf]

I would say that usually we add diagram or concepts to explain the pros/cons and explain the new vision, we don't give a pointer to a branch

[gazarenkov]

@benoitf of course there will be more details and sub-issues very soon. Actually, it is quite clear for people who feel this pain. Let me know if you have some concrete questions or want to help.

[sunix]

@gazarenkov sorry it is actually quite UNclear. Is this related to having workspace agents in their own container ?

[gorkem]

@gazarenkov @garagatyi I understand the problem you are trying to solve but it is very hard to see how you intend to fix it. I think we need some more material for communicating this with others.