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

Remove usage of the Machine API in the Chedir #3967

Closed
mshaposhnik opened this issue Jan 31, 2017 · 8 comments
Closed

Remove usage of the Machine API in the Chedir #3967

mshaposhnik opened this issue Jan 31, 2017 · 8 comments
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Milestone

Comments

@mshaposhnik
Copy link
Contributor

mshaposhnik commented Jan 31, 2017

Remove usage of the Machine API in Chedir. Example: here and replace with exec's.

@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Jan 31, 2017
@skabashnyuk skabashnyuk added this to the 5.3.0 milestone Jan 31, 2017
@benoitf
Copy link
Contributor

benoitf commented Jan 31, 2017

I don't see why it's a blocker as I was not informed that it's gonna be removed and that when the code has been changed to use agent, job was not done on all parts ?

@skabashnyuk
Copy link
Contributor

Sorry we thought that we know all places where it's used. now we know what cheConf/ che dir is used it too. severity/blocker set to inform about our intent to remove Deprecated Machine API asap.

@benoitf
Copy link
Contributor

benoitf commented Jan 31, 2017

why the job of migrating machine api to agent was not including chedir ?

@skabashnyuk
Copy link
Contributor

We don't know how it works and want to delegate it to authors who knows how it works.

@JamesDrummond JamesDrummond removed this from the 5.3.0 milestone Feb 7, 2017
@JamesDrummond JamesDrummond removed the severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. label Feb 7, 2017
@skabashnyuk
Copy link
Contributor

skabashnyuk commented Feb 10, 2017

PR where we introduced exec #2163

Available API:

@benoitf Do you know where Chedir functionality is located?

@benoitf
Copy link
Contributor

benoitf commented Feb 13, 2017

@skabashnyuk
Copy link
Contributor

I see that /api/workspace is used in three places in https://github.com/eclipse/che/blob/master/dockerfiles/lib/src/internal/dir/che-dir.ts

  • checkCheIsNotRunning
  • checkCheIsRunning
  • pingCheAction

@benoitf Am I correct ?

@benoitf
Copy link
Contributor

benoitf commented Feb 13, 2017

@skabashnyuk there are other places
I think you are interested in calls to machine API which are only there:
https://github.com/eclipse/che/blob/master/dockerfiles/lib/src/api/wsmaster/machine/machine-service-client.ts

@benoitf benoitf added the status/in-progress This issue has been taken by an engineer and is under active development. label Feb 27, 2017
benoitf added a commit that referenced this issue Feb 27, 2017
Change-Id: I67e9d668516bf634c47e72653086e93ef34d5fe9
Signed-off-by: Florent BENOIT <fbenoit@codenvy.com>
@benoitf benoitf added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Feb 28, 2017
@benoitf benoitf removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Feb 28, 2017
@benoitf benoitf added this to the 5.4.0 milestone Feb 28, 2017
JPinkney pushed a commit to JPinkney/che that referenced this issue Aug 17, 2017
Change-Id: I67e9d668516bf634c47e72653086e93ef34d5fe9
Signed-off-by: Florent BENOIT <fbenoit@codenvy.com>
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

No branches or pull requests

4 participants