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.

Sign up for GitHub

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

Jump to bottom

create a job to aid in multi-arch builder access #803

Closed
dustymabe opened this issue Jan 19, 2023 · 2 comments
Closed

create a job to aid in multi-arch builder access #803

dustymabe opened this issue Jan 19, 2023 · 2 comments
Assignees
@aaradhak
Labels
jira For syncing to JIRA

Comments

@dustymabe
Copy link
Member

We recently discussed our limited access to multi-arch for most of our team members. We have our multi-arch builders, but managing access can be complicated. We could just use the pipeline itself to spawn a remote session on a builder and the user can then grab a shell via OpenShift to do testing. The remote sessions would be auto-garbage collected after a period of time.
@aaradhak
Copy link
Member

@dustymabe
Summarizing the requirements as discussed in the meeting. Kindly review if there are any missing points in the requirements.

Requirements:

  • pod name includes the name of the person who ran the job
    - i.e. user-devpod-2023101abc
  • pod/job times out after X hours (configurable?)
  • starts remote session on multi-arch builder and does a few convenience things
    - runs tmux (so that the session can be connected to by the user)
    - user uses openshift webui or CLI to connect to pod and re-attach to tmux
    - tmux window offers two panes
    - one where the remote session is already set up.
    - running cosa just works in tmux.
  • Run cosa init

@aaradhak aaradhak added the jira For syncing to JIRA label Feb 13, 2023
@aaradhak aaradhak self-assigned this Feb 13, 2023
@aaradhak aaradhak mentioned this issue Mar 24, 2023
Closed
aaradhak added a commit to aaradhak/coreos-assembler that referenced this issue Mar 24, 2023
@aaradhak
Add tmux to cosa
62a994e 
The user can use tmux via OpenShift to do testing

Ref: coreos/fedora-coreos-pipeline#803
@aaradhak aaradhak mentioned this issue Mar 24, 2023
Merged
aaradhak added a commit to aaradhak/coreos-assembler that referenced this issue Mar 24, 2023
@aaradhak
Add tmux to cosa
b5885e7 
The user can use tmux via OpenShift to do testing

Ref: coreos/fedora-coreos-pipeline#803
aaradhak added a commit to aaradhak/coreos-assembler that referenced this issue Mar 24, 2023
@aaradhak
Add tmux to cosa
4d7841e 
We can use tmux to create terminal sessions that can be attached to later

Ref: coreos/fedora-coreos-pipeline#803
aaradhak added a commit to aaradhak/coreos-assembler that referenced this issue Mar 24, 2023
@aaradhak
Add tmux to cosa
b9ff841 
We can use tmux to create terminal sessions that can be attached to later

Ref: coreos/fedora-coreos-pipeline#803
dustymabe pushed a commit to coreos/coreos-assembler that referenced this issue Mar 24, 2023
@aaradhak @dustymabe
Add tmux to cosa
9583c90 
We can use tmux to create terminal sessions that can be attached to later

Ref: coreos/fedora-coreos-pipeline#803
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Mar 24, 2023
@aaradhak
jobs:debug-pod to aid in multi-arch builder access
b24c485 
In order to resolve the limited access to multi-arch for most of our
team members,we have the multi-arch builders where we could just use
the pipeline itself to spawn a remote session on a builder and the
user can then grab a shell via OpenShift to do testing. cosa-init &
sleep stages are added as part of creating a job for multi-arch
builder access.

Ref: coreos#803
@aaradhak aaradhak mentioned this issue Mar 24, 2023
Closed
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Mar 24, 2023
@aaradhak
jobs:debug-pod to aid in multi-arch builder access
5c69439 
In order to resolve the limited access to multi-arch for most of our
team members,we have the multi-arch builders where we could just use
the pipeline itself to spawn a remote session on a builder and the
user can then grab a shell via OpenShift to do testing. cosa-init &
sleep stages are added as part of creating a job for multi-arch
builder access.

Ref: coreos#803
@aaradhak aaradhak mentioned this issue May 22, 2023
Merged
aaradhak added a commit to aaradhak/coreos-ci-lib that referenced this issue Jun 15, 2023
@aaradhak
pod: add username from jenkins for debug-pod job
622d645 
The debug-pod for multi-arch builders will carry a username when a pod
is created which would make it easier to track the pods when a job is
triggered. The pod would also carry the arch name of the build.

Ref: coreos/fedora-coreos-pipeline#803
@aaradhak aaradhak mentioned this issue Jun 15, 2023
Merged
aaradhak added a commit to aaradhak/coreos-ci-lib that referenced this issue Jun 15, 2023
@aaradhak
pod: add logged in username from jenkins
380818c 
The debug-pod for multi-arch builders will carry a username when a pod
is created which would make it easier to track the pods when a job is
triggered. The pod would also carry the arch name of the build.

Ref: coreos/fedora-coreos-pipeline#803
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jun 16, 2023
@aaradhak @dustymabe
jobs:debug-pod for multi-arch builder access
460f6aa 
In order to resolve the limited access to multi-arch for most of our
team members,we have the multi-arch builders where we could just use
the pipeline itself to spawn a remote session on a builder and the user
can then grab a shell via OpenShift to do testing. cosa-init & sleep
stages are added as part of creating a job for multi-arch builder access.

Co-authored-by: Dusty Mabe <dusty@dustymabe.com>
Red: coreos#803
aaradhak added a commit to aaradhak/coreos-ci-lib that referenced this issue Jun 16, 2023
@aaradhak
pod: add logged in username from jenkins
1d6f124 
The debug-pod for multi-arch builders will carry a username when a pod
is created which would make it easier to track the pods when a job is
triggered. The pod would also carry the arch name of the build.

Ref: coreos/fedora-coreos-pipeline#803
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jun 16, 2023
@aaradhak @dustymabe
jobs:debug-pod for multi-arch builder access
ca1199e 
In order to resolve the limited access to multi-arch for most of our
team members,we have the multi-arch builders where we could just use
the pipeline itself to spawn a remote session on a builder and the user
can then grab a shell via OpenShift to do testing. cosa-init & sleep
stages are added as part of creating a job for multi-arch builder access.

Co-authored-by: Dusty Mabe <dusty@dustymabe.com>
Red: coreos#803
dustymabe added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jun 16, 2023
@aaradhak @dustymabe
jobs:debug-pod for multi-arch builder access
b9c27ec 
In order to resolve the limited access to multi-arch for most of our
team members,we have the multi-arch builders where we could just use
the pipeline itself to spawn a remote session on a builder and the user
can then grab a shell via OpenShift to do testing. cosa-init & sleep
stages are added as part of creating a job for multi-arch builder access.

Co-authored-by: Dusty Mabe <dusty@dustymabe.com>
Red: coreos#803
aaradhak added a commit to aaradhak/coreos-ci-lib that referenced this issue Jun 16, 2023
@aaradhak
pod: Allow caller to specify name of pod
3d63649 
Allowing the caller to specify the pod name would make it easier to
identify what pods were created for what purpose.

We are planning to use this in the debug pod pipeline job to allow
users to identify which debug pods they own.

Ref: coreos/fedora-coreos-pipeline#803
dustymabe pushed a commit to coreos/coreos-ci-lib that referenced this issue Jun 16, 2023
@aaradhak @dustymabe
pod: Allow caller to specify name of pod
4591c8e 
Allowing the caller to specify the pod name would make it easier to
identify what pods were created for what purpose.

We are planning to use this in the debug pod pipeline job to allow
users to identify which debug pods they own.

Ref: coreos/fedora-coreos-pipeline#803
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jun 16, 2023
@aaradhak @dustymabe
jobs:debug-pod for multi-arch builder access
58de3e4 
In order to resolve the limited access to multi-arch for most of our
team members,we have the multi-arch builders where we could just use
the pipeline itself to spawn a remote session on a builder and the user
can then grab a shell via OpenShift to do testing. cosa-init & sleep
stages are added as part of creating a job for multi-arch builder access.

Co-authored-by: Dusty Mabe <dusty@dustymabe.com>
Red: coreos#803
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jun 16, 2023
@aaradhak @dustymabe
jobs:debug-pod for multi-arch builder access
fd14a4e 
In order to resolve the limited access to multi-arch for most of our
team members,we have the multi-arch builders where we could just use
the pipeline itself to spawn a remote session on a builder and the user
can then grab a shell via OpenShift to do testing. cosa-init & sleep
stages are added as part of creating a job for multi-arch builder access.

Co-authored-by: Dusty Mabe <dusty@dustymabe.com>
Ref: coreos#803
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jun 16, 2023
@aaradhak @dustymabe
jobs:debug-pod for multi-arch builder access
c4e1306 
In order to resolve the limited access to multi-arch for most of our
team members,we have the multi-arch builders where we could just use
the pipeline itself to spawn a remote session on a builder and the user
can then grab a shell via OpenShift to do testing. cosa-init & sleep
stages are added as part of creating a job for multi-arch builder access.

Co-authored-by: Dusty Mabe <dusty@dustymabe.com>
Ref: coreos#803
dustymabe added a commit that referenced this issue Jun 16, 2023
@aaradhak @dustymabe
jobs:debug-pod for multi-arch builder access
bb06547 
In order to resolve the limited access to multi-arch for most of our
team members,we have the multi-arch builders where we could just use
the pipeline itself to spawn a remote session on a builder and the user
can then grab a shell via OpenShift to do testing. cosa-init & sleep
stages are added as part of creating a job for multi-arch builder access.

Co-authored-by: Dusty Mabe <dusty@dustymabe.com>
Ref: #803
Adam0Brien pushed a commit to Adam0Brien/fedora-coreos-pipeline that referenced this issue Jul 6, 2023
@aaradhak @dustymabe @Adam0Brien
jobs:debug-pod for multi-arch builder access
a18ac90 
In order to resolve the limited access to multi-arch for most of our
team members,we have the multi-arch builders where we could just use
the pipeline itself to spawn a remote session on a builder and the user
can then grab a shell via OpenShift to do testing. cosa-init & sleep
stages are added as part of creating a job for multi-arch builder access.

Co-authored-by: Dusty Mabe <dusty@dustymabe.com>
Ref: coreos#803
@aaradhak aaradhak closed this as completed Jul 6, 2023
@aaradhak
Copy link
Member

aaradhak commented Jul 6, 2023

Completed the task of adding debug pod job .

aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jul 12, 2023
@aaradhak
docs: Documentation on steps to access debug-pod
6d8c343 
This document provides the background information and the steps to
access a debug pod for multi-arch builder access.
Ref: coreos#803
@aaradhak aaradhak mentioned this issue Jul 12, 2023
Merged
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jul 12, 2023
@aaradhak
docs: Documentation on steps to access debug-pod
15d1193 
This document provides the background information and the steps to
access a debug pod for multi-arch builder access.
Ref: coreos#803
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jul 12, 2023
@aaradhak
docs: Documentation on steps to access debug-pod
ee5290b 
This document provides the background information and the steps to
access a debug pod for multi-arch builder access.
Ref: coreos#803
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jul 12, 2023
@aaradhak
docs: Documentation on steps to access debug-pod
97f63d5 
This document provides the background information and the steps to
access a debug pod for multi-arch builder access.
Ref: coreos#803
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jul 12, 2023
@aaradhak
docs: Documentation on steps to access debug-pod
a19166c 
This document provides the background information and the steps to
access a debug pod for multi-arch builder access.
Ref: coreos#803
aaradhak added a commit to aaradhak/fedora-coreos-pipeline that referenced this issue Jul 12, 2023
@aaradhak
docs: Documentation on steps to access debug-pod
26cb443 
This document provides the background information and the steps to
access a debug pod for multi-arch builder access.
Ref: coreos#803
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aaradhak aaradhak

Labels
jira For syncing to JIRA
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dustymabe @aaradhak