Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delivering of ChePlugins binaries to the editor container #10561

Closed
3 tasks
garagatyi opened this issue Jul 27, 2018 · 2 comments · Fixed by #10740
Closed
3 tasks

Delivering of ChePlugins binaries to the editor container #10561

garagatyi opened this issue Jul 27, 2018 · 2 comments · Fixed by #10740
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.

Comments

@garagatyi
Copy link

garagatyi commented Jul 27, 2018

Description

Walking skeleton epic describes that we need an ability to deliver ChePlugins binaries to a che editor sidecar container. This would allow us, for example, to have a dynamic pluggability in Che Theia.
There might be different ways to deliver those binaries, so we need to investigate options and implement at least one of them for the walking skeleton POC.
Delivering options:

  1. Usage of data containers that don't run any process but pulled from a registry and mount some folder to another container (editor container)
  2. Download binaries from a marketplace (for now it is just an Apache server)
  3. Usage of init container in kubernetes

We might also think about ChePlugins owners being able to use different mechanisms (described here or others) depending on their needs but this is not needed for a POC and it might complicate the flow, so having just one mechanism seems more natural for me for the time being.

Subtasks:

  • Investigate delivering of Theia plugins with data containers Investigate delivering of Theia plugins with data containers #10369
  • Add a plugin downloader component in wsmaster that
    • Get as input the workspace config list of plugins and editor
    • Downloads the plugins and editor files (*.tar.gz and *.theia) from the plugin registry
    • Extract the tar.gz in che-plugins and che-editor folders
    • Copies *.theia files in a theia-plugins folder
    • Returns the local paths to the che-plugin.yml and che-editor.yml files
  • Add an editor plugin injector component in wsmaster that copies the content of editor plugins folder (theia-plugins) in the volume that will be mounted in the theia container
@garagatyi garagatyi added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Jul 27, 2018
@l0rd l0rd mentioned this issue Jul 27, 2018
24 tasks
@l0rd
Copy link
Contributor

l0rd commented Aug 3, 2018

I have created this document to discuss this issue implentation and introduce the concept of Che Plugin Broker.

@garagatyi garagatyi self-assigned this Aug 19, 2018
@garagatyi
Copy link
Author

garagatyi commented Aug 22, 2018

Work was done in a branch but there were technical difficulties.
The plan is to:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants