Skip to content
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.

Implement compatibility with the new automatic multicast discovery in plugin broker #1354

Closed
davidfestal opened this issue Apr 10, 2019 · 10 comments
Assignees

Comments

@davidfestal
Copy link
Collaborator

davidfestal commented Apr 10, 2019

Placeholder for eclipse-che/che#13272

@davidfestal davidfestal self-assigned this Apr 10, 2019
@ibuziuk ibuziuk added this to the Sprint #165 (Che OSIO) milestone Apr 10, 2019
@ibuziuk
Copy link
Member

ibuziuk commented May 2, 2019

Related to the Future Improvement comment in the merge meta.yaml / plugin.yaml change -eclipse-che/che#12908 (comment)

@ibuziuk ibuziuk modified the milestones: Sprint #165 (Che OSIO), Sprint #166 (Che OSIO) May 2, 2019
@tsmaeder
Copy link
Contributor

tsmaeder commented May 3, 2019

It is important that we do not break self hosting as described in https://docs.google.com/document/d/1V292nYN655ekPPZvzdg7zbLpwVXW5uFjmffgoN2CmpM/edit#bookmark=id.kw179rb9gjl6
If we do break that approach, we need to come up with an alternative.

@davidfestal
Copy link
Collaborator Author

@benoitf any idea about whether it might break self-hosting ?

@benoitf
Copy link
Contributor

benoitf commented May 14, 2019

@davidfestal why it should break self-hosting ?

@davidfestal
Copy link
Collaborator Author

@benoitf no idea, but my purpose was to let you confirm to @tsmaeder that it doesn't break it :-)

@tsmaeder
Copy link
Contributor

tsmaeder commented May 14, 2019

@benoitf https://docs.google.com/document/d/1V292nYN655ekPPZvzdg7zbLpwVXW5uFjmffgoN2CmpM/edit#heading=h.mu558mvq9pl4 suggests running the ide and plugin containers "by hand" in a workspace: if we can't tell the ide container where the plugin host is, how do we separate the outer editor (the one we're using to develop) from the inner (the one being developed)?

@benoitf
Copy link
Contributor

benoitf commented May 14, 2019

@davidfestal @tsmaeder
it should not break self-hosting

in fact multiple containers is still compliant with discovery (as we share the network). Moreover, there are custom ENV variables allowing to specify the discovery host/port if you need to opt-out
Also, we can still use previous ENV variables to declare remote endpoint for any plugin.

@tsmaeder
Copy link
Contributor

@benoitf can we please try this work flow and document it in the referenced document before we turn on discovery as the default mechanism? IMO, we need to continuously improve developer experience and we should make sure at the very least that we don't break documented work flows.

@ibuziuk
Copy link
Member

ibuziuk commented May 21, 2019

@davidfestal, as I understand once the docs are updated we can close this issue, right?

@ibuziuk
Copy link
Member

ibuziuk commented May 22, 2019

Moving to Done. since it is merged to plugin-broker-master. Should be closed once plugin broker v0.17.2 and rh-che is updated to Che 7 CR1 version

@ibuziuk ibuziuk closed this as completed Jun 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants