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

Allow running multiple parallel Dev sessions on the same platform type #6809

Open
2 tasks
valaparthvi opened this issue May 10, 2023 · 7 comments
Open
2 tasks
Labels
kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.

Comments

@valaparthvi
Copy link
Contributor

valaparthvi commented May 10, 2023

/kind user-story

User Story

As an odo user, I want to be able to run 2 parallel Dev session on different clusters (or on podman and docker for e.g.), So that I can simultaneously check my application/cluster's behavior instead of having to restart the Dev sessions and moving back and forth between the clusters/Container runtimes.

Acceptance Criteria

  • It should allow to run multiple dev sessions on different clusters.
  • It should allow to run multiple dev sessions on podman and docker or 2 different versions of container runtimes.

Current Behavior:

$ KUBECONFIG=some_config odo dev
  __
 /  \__     Developing using the "springboot" Devfile
 \__/  \    Platform: cluster
 /  \__/    odo version: v3.10.0
 \__/

↪ Running on podman in Dev mode
 ✗  unable to save state file: a session with PID 21535 is already running on platform "cluster"
$ PODMAN_CMD=docker odo dev
  __
 /  \__     Developing using the "springboot" Devfile
 \__/  \    Platform: podman
 /  \__/    odo version: v3.10.0
 \__/

↪ Running on podman in Dev mode
 ✗  unable to save state file: a session with PID 22552 is already running on platform "podman"

Links

  • Related Epic (mandatory):

/kind user-story

Notes

Currently the validation relies on checking for platform in the .odo/devstate.*.json path. This could be fixed by also storing the KUBECONFIG and PODMAN_CMD in the file and additionally relying on their values to determine if the user is trying to run a duplicate session.

@openshift-ci openshift-ci bot added the kind/user-story An issue of user-story kind label May 10, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label May 10, 2023
@valaparthvi valaparthvi changed the title odo dev does not allow to run multiple parallel Dev sessions on different clusters odo dev does not allow to run multiple parallel Dev sessions on on the same platform May 10, 2023
@valaparthvi valaparthvi changed the title odo dev does not allow to run multiple parallel Dev sessions on on the same platform odo dev does not allow to run multiple parallel Dev sessions on the same platform type May 10, 2023
@feloy feloy added needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. and removed needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. labels May 11, 2023
@feloy
Copy link
Contributor

feloy commented May 11, 2023

Grooming (2023-05-11)

We could consider adding a DOT_ODO_DIRECTORY environment variable to change the directory on which devstate files are stored.

@rm3l rm3l removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Jun 15, 2023
@github-actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 14, 2023
@valaparthvi
Copy link
Contributor Author

@rm3l is this still relevant? I see it's pointed, so it was relevant at some point.

@rm3l
Copy link
Member

rm3l commented Sep 14, 2023

is this still relevant? I see it's pointed, so it was relevant at some point.

Makes sense to keep it open, indeed, as it had been pointed and prioritized.
Thanks for commenting out.

/remove-lifecycle stale
/lifecycle frozen

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 14, 2023
@rm3l
Copy link
Member

rm3l commented Sep 14, 2023

Changing the title to make it clear that this is a new feature, not a bug.

/retitle Allow running multiple parallel Dev sessions on the same platform type
/remove-lifecycle frozen

@openshift-ci openshift-ci bot removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Sep 14, 2023
@openshift-ci openshift-ci bot changed the title odo dev does not allow to run multiple parallel Dev sessions on the same platform type Allow running multiple parallel Dev sessions on the same platform type Sep 14, 2023
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 14, 2023
@rm3l
Copy link
Member

rm3l commented Dec 14, 2023

/remove-lifecycle stale
/lifecycle frozen

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
Projects
Status: No status
Development

No branches or pull requests

3 participants