Skip to content

Rework remote support to account for more scenarios #10435

@rchiodo

Description

@rchiodo

Remote support is confusing:

Using this issue to describe the use cases.

Use Cases

  1. (web) User opens a notebook and wants to run a cell so they can see the output of a cell
  2. (web) User is in a notebook and wants to run a cell in the browser so they don't have to pay for/setup a remote compute
  3. (web) User is in a notebook and wants to run a cell on their local machine so they don't have to pay for/setup a remote compute
  4. (web) User is in a notebook and wants to run a cell on a different remote server because this one is more expensive
  5. (desktop) User opens a notebook and wants to run a cell without entering anything so they can see the output
  6. (desktop) User opens a notebook and wants to run it on their own compute so they can use the GPU/CPU on that machine
  7. (desktop) User wants to specify their own compute for all notebooks so they don't have to keep picking a server
  8. (desktop) User wants to run some cells on local and some cells on remote (need to check telemetry for this)
  9. (codespaces) User wants to run a cell and not have to specify anything except clicking the run button.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions