infra/tickets
24
9
Fork 1
Code Issues 80 Projects Wiki Activity Actions

RFE: Add a role for deploying through OpenShift deployment #11884

New issue
Closed
opened 2024-04-17 08:04:06 +00:00 by svashisht · 10 comments
svashisht commented 2024-04-17 08:04:06 +00:00
Copy link

Describe what you would like us to do:

OpenScanHub project on OpenShift currently does not use imagestreams. So only way to trigger a production deployment is to request an admin to delete and recreate pods. This is a manual step and should be automated through a role.

When do you need this to be done by? (YYYY/MM/DD)

asap

# Describe what you would like us to do: ---- OpenScanHub project on OpenShift currently does not use imagestreams. So only way to trigger a production deployment is to request an admin to delete and recreate pods. This is a manual step and should be automated through a role. # When do you need this to be done by? (YYYY/MM/DD) ---- asap
zlopez commented 2024-04-17 08:42:28 +00:00
Owner
Copy link

Just to clarify: The request is to add role that will allow app owners to trigger a new deployment in case they want to just restart some specific pod.

Just to clarify: The request is to add role that will allow app owners to trigger a new deployment in case they want to just restart some specific pod.
zlopez commented 2024-04-17 08:42:29 +00:00
Owner
Copy link

Metadata Update from @zlopez:

  • Issue tagged with: OpenShift, low-gain, medium-trouble
**Metadata Update from @zlopez**: - Issue tagged with: OpenShift, low-gain, medium-trouble
zlopez commented 2024-04-17 08:42:43 +00:00
Owner
Copy link

Metadata Update from @zlopez:

  • Issue priority set to: Waiting on Assignee (was: Needs Review)
**Metadata Update from @zlopez**: - Issue priority set to: Waiting on Assignee (was: Needs Review)
mizdebsk commented 2024-07-15 10:58:51 +00:00
Copy link

Maybe create a dedicated playbook to restart deployment? For example Koschei project has manual playbooks playbooks/manual/upgrade/koschei-rolling.yml and playbooks/manual/upgrade/koschei-full.yml that can be used by appowners to trigger rolling or full updates as needed.

Maybe create a dedicated playbook to restart deployment? For example Koschei project has manual playbooks `playbooks/manual/upgrade/koschei-rolling.yml` and `playbooks/manual/upgrade/koschei-full.yml` that can be used by appowners to trigger rolling or full updates as needed.
zlopez commented 2024-10-17 16:35:59 +00:00
Owner
Copy link

@mizdebsk That is not a bad idea, but doing that for each OpenShift project is not great. I assume it will be better to allow appowners to have ability to delete/create pods in their own project.

@mizdebsk That is not a bad idea, but doing that for each OpenShift project is not great. I assume it will be better to allow appowners to have ability to delete/create pods in their own project.
zlopez commented 2025-04-03 17:52:33 +00:00
Owner
Copy link

[backlog refinement]
This is still something that would be nice to have. Ideally in a way that will allow us to have something general that could be run for multiple different OpenShift projects. Allowing authorized users to rebuild, rollout project if that is needed.

[backlog refinement] This is still something that would be nice to have. Ideally in a way that will allow us to have something general that could be run for multiple different OpenShift projects. Allowing authorized users to rebuild, rollout project if that is needed.
zlopez commented 2026-01-08 17:29:47 +00:00
Owner
Copy link

[backlog refinement]
Situation is still the same. We would like to have this, but we need to find few cycles to spare.

[backlog refinement] Situation is still the same. We would like to have this, but we need to find few cycles to spare.
kevin commented 2026-04-02 16:55:15 +00:00
Owner
Copy link

So, thinking about this more... I think we can just use the pattern some of our apps already use. Have ansible tags that also have 'never' associated, so they don't normally get run, but when the specific tag is passed they do run.

So, look at the bodhi app, you can see it has a 'build' and 'rollout' tags that build and rollout a new deployment. Those only run when '-t that tag' is passed to the playbook.

We can make a 'restart deployment' tag for this too.

So, thinking about this more... I think we can just use the pattern some of our apps already use. Have ansible tags that also have 'never' associated, so they don't normally get run, but when the specific tag is passed they do run. So, look at the bodhi app, you can see it has a 'build' and 'rollout' tags that build and rollout a new deployment. Those only run when '-t that tag' is passed to the playbook. We can make a 'restart deployment' tag for this too.
smoliicek commented 2026-06-19 07:19:23 +00:00
Member
Copy link

i opened infra/ansible#3429 which adds this

i opened https://forge.fedoraproject.org/infra/ansible/pulls/3429 which adds this
kevin commented 2026-06-23 19:30:50 +00:00
Owner
Copy link

Merged it. ;)

Hopefully we are done here. Thanks Vit!

Merged it. ;) Hopefully we are done here. Thanks Vit!
kevin closed this issue 2026-06-23 19:30:51 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
announcement

Archived

  
anubis
Issues related to anubis

  
authentication
Authentication related issues

  
aws
Issues related to Amazon Web Services

  
backlog
Tasks that will take longer then ~4 hours to do

Archived

  
blocked
Issue is blocked

Archived

  
bodhi
Issues with Bodhi

  
ci
Continuous Integration

  
cloud
Items in FedoraInfraCloud or COmmunishift

  
communishift
issues/questions about os.edorainfracloud.org ( Community OpenShift)

  
copr
COPR system (run by other team)

  
database
Issues related to databases

  
day-to-day
These are small self contained tasks that are part of normal operations, but are async from sprint planning.

  
dc-move
Items related to datacenter move

Archived

  
deprecated
Tools which Infrastructure may not be able to fix

Archived

  
dev
Tasks requiring some dev work

  
discourse
outsourced tool

  
dns
Changes or problems with DNS

  
downloads
rsync,dl.fp.o,AWS,torrents

  
easyfix

Archived

  
epel
Issues relating to epel

Archived

  
firmitas

   
forgejo_migration
Request migration to the new forge

  
Gain
High
 task that gets us a lot / is important / makes many people happy

Archived

  
Gain
Low
 tasks that gets us little / isn't very important / makes only 1 person or few happy

Archived

  
Gain
Medium
 task that gets us some / is somewhat important / makes some people happy

Archived

  
gitlab

   
greenwave
Issues with greenwave

  
hardware
Problem is with Fedora Infrastructure Owned/Leased Hardware

  
help wanted

   
high-trouble
task that is complex/long/difficult

Archived

  
koji
Issues with the build system

  
koschei
Items needing Koschei team

  
lists
issues with lists

  
low-trouble
task that is easy/short

Archived

  
medium-trouble
task that is medium complex / difficult

Archived

  
mirrorlists
Way to tell systems where downloads are

  
monitoring

   
Needs investigation

   
odcs
On Demand Compose Service issues

Archived

  
OpenShift
Issues with OpenShift

  
ops
ops problem now...

Archived

  
outage

   
packager_workflow_blocker
Blocks the packager workflow

Archived

  
pagure
Issues with pagure.io

  
permissions
Items which need permissions set in outside tools

  
Priority
Needs Review
 Priority of Needs Review

Archived

  
Priority
Next Meeting
 Priority of Next Meeting

Archived

  
Priority
🔥 URGENT 🔥
 Priority of 🔥 URGENT 🔥

Archived

  
Priority
Waiting on Assignee
 Priority of Waiting on Assignee

Archived

  
Priority
Waiting on External
 Priority of Waiting on External

Archived

  
Priority
Waiting on Reporter
 Priority of Waiting on Reporter

Archived

  
rabbitmq
issues with the message broker

  
release-monitoring
release-monitoring.org (Anitya)

  
releng
For problems which should be in the releng ticket system

Archived

  
request-for-resources

   
s390x
The secondary architecture hardware and problems related with it

  
security

   
SMTP
Email issues outside of lists (DMARC, SPF, aliases)

  
sprint-0

Archived

  
sprint-1

Archived

  
src.fp.o
Issues related to src.fedoraproject.org

  
staging
Issues in staging

  
unfreeze
Patches to be applied after freeze is lifted

  
waiverdb
Issues with waiverdb

  
websites-general
General items with a website focus

  
wiki
Issues with the Wiki

  
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint ( 2026-06-15 to 2026-06-28)
Assignees
Clear assignees
No assignees
smoliicek
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
infra/tickets#11884
No description provided.