openSUSE admin

Overview
Activity
Roadmap
Issues
Calendar
News
Files
Repository

Custom queries

Events of the openSUSE Heroes
my assigned stuff
obs-admin-tickets
openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QE tools team - backlog (dev)
QE tools team - backlog (ready issues)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (dev)
QE tools team - non-estimated (unblocked) issues (infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - SLO high forecast
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

tickets #154510

closed

Deploy Redis+Sidekiq for Redmine

Added by crameleon 10 months ago. Updated 10 months ago.

Status:

Resolved

Priority:

Normal

Assignee:

crameleon

Category:

Redmine

Target version:

Start date:

2024-01-30

Due date:

% Done:

Estimated time:

Description

The built-in queue thing is now warned about in https://progress.opensuse.org/admin/info:

https://progress.opensuse.org/admin/info

Which seems to be a result of https://www.redmine.org/issues/36695.

I suppose Sidekiq with a Redis database is the most common setup, and we use this combination for other services as well.
Happy to investigate other ideas though.

History
Notes
Property changes

Actions

Copy link

Updated by crameleon 10 months ago

Private changed from Yes to No

Actions

Copy link

Updated by crameleon 10 months ago

Description updated (diff)

Actions

Copy link

Updated by crameleon 10 months ago

I suppose if we deploy this we could also switch Redmine back to talk directly to relay.i.o.o without going through a local Postfix? Not that it makes big of a difference, but would be less hops.

Actions

Copy link

Updated by pjessen 10 months ago · Edited

crameleon wrote in #note-3:

I suppose if we deploy this we could also switch Redmine back to talk directly to relay.i.o.o without going through a local Postfix? Not that it makes big of a difference, but would be less hops.

My 2 cents - I wouldn't bother. Easier and simpler just letting Redmine use sendmail to drop mails into the queue.

Actions

Copy link