openSUSE admin

Overview
Activity
Roadmap
Issues
Calendar
News
Files
Repository

Custom queries

Events of the openSUSE Heroes
my assigned stuff
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 (ready issues)
QE tools team - backlog (w/o infra)
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 (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
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 #121921

closed

Set up domain for minio

Added by hellcp over 1 year ago. Updated over 1 year ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

2022-12-13

Due date:

% Done:

Estimated time:

Description

So minio is now kind of working, and I think I decided on s3.opensuse-project.net as the domain for it (that's what is used in https://gitlab.infra.opensuse.org/infra/salt/-/merge_requests/595, as we want to avoid potential xss issues), we need to set things up for that domain to work properly.

We need the following:

dns setup
ssl certificate
proxy setup

History
Notes
Property changes

Actions

Copy link

Updated by pjessen over 1 year ago

Private changed from Yes to No

Just my opinion - we should really really avoid using any of the openSUSE ccTLDs, except maybe for minor/occasional testing. Some of the ccTLDs are used by national communities, e.g. opensuse.id, and I think it's best to leave it like that.

Actions

Copy link

Updated by hellcp over 1 year ago

Sure, that being said, I think if we are gonna have Turkish presence, I think we should instead have SUSE invest in opensuse.tr instead.

Actions

Copy link

Updated by hellcp over 1 year ago

After a discussion on in #opensuse-admin we are also considering s3.opensuse-project.net and s3.opensuse-project.com

Actions

Copy link

Updated by pjessen over 1 year ago

hellcp wrote:

After a discussion on in #opensuse-admin we are also considering s3.opensuse-project.net and s3.opensuse-project.com

Again, only my opinion - we really ought to stick to "opensuse.org". I think I saw Bernhard mention it on irc, why isn't it sufficient to use Content-Security-Policy ?

Actions

Copy link

Updated by hellcp over 1 year ago

CSP is per site policy, and we are both using old software that may not set those headers and we don't have access to the servers to change those headers.

Actions

Copy link