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

Async PV for workspace: API between client/server #15956

Closed
Tracked by #15384
benoitf opened this issue Feb 7, 2020 · 1 comment
Closed
Tracked by #15384

Async PV for workspace: API between client/server #15956

benoitf opened this issue Feb 7, 2020 · 1 comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@benoitf
Copy link
Contributor

benoitf commented Feb 7, 2020

API between client/server

as part of #15384 there is a need to have the 'rsync' pod included in the workspace POD to 'discuss' with the data sync pod.

Describe the solution you'd like

It will consist of asking if there is something to restore or not for a given workspaceID.

And then, if there is data to restore, choose a way to do the transfer of file and grab information (like using rsync or something else, etc)

Both rsync client and rssync server need to agree on this

note:

Idea of the 'restore' mechanism could be used as well to import files from a local env (like someone connected to internet with its laptop) to a Che Workspace.

In that case, we could import files from laptop, edit from Che workspace and all changes are kept on the 'user/laptop storage'.

@benoitf benoitf added kind/task Internal things, technical debt, and to-do tasks to be performed. area/dev-experience labels Feb 7, 2020
@benoitf benoitf added this to the Backlog - Hosted Che milestone Feb 7, 2020
@benoitf benoitf changed the title Async PVC for workspace: API between client/server Async PV for workspace: API between client/server Feb 7, 2020
@che-bot
Copy link
Contributor

che-bot commented Oct 28, 2020

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 28, 2020
@che-bot che-bot closed this as completed Jan 4, 2021
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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants