SovereignCloudStack / SovereignCloudStack/standards

Discontinue Domain Manager standard once OpenStack 2024.2 lands in SCS

Open
#723 1 comment 0 reactions 1 assignee View on GitHub

@depressiveRobot is already working on this.

Since Feb 19, 2026.

IaaS question
Dominant language
Python
Stars
47
Forks
38
Avg merge
1d 16h
Merged PRs (30d)
8

Description

Current State
Desired State

Once SCS incorporates OpenStack 2024.2 or later, where the Domain Manager functionality is available natively in OpenStack, the following things need to happen:

  1. The SCS Domain Manager standard needs to be deprecated. It needs to either be removed or replaced by a v2 that omits any of the SCS-specific policy configuration, as it will not be necessary anymore and conflict with the native implementation. Explanations about is_domain_managed_role and an Octavia role integration could be remaining parts of a v2 although I think it would better fit in the Role Standard. I see little reason for keeping the standard at all. Update: #586 now differentiates between pre- and post-2024.2 versions of Keystone. As such, the standard can live on for the time being. In the future, all the pre-2024.2 parts can be removed.
  2. The docs page at docs/05-iam/domain-manager-setup-and-usage.md needs to be updated and reference to the Domain Manager standard be removed or replaced in a way that omits the SCS-specific policy configurations. Only the part about adjusting the is_domain_managed_role rule should stay as this will still be valid and required for the Octavia LBaaS role integration.
  3. SCS operators need to be notified to remove the Keystone policy extensions of the Domain Manager standard when upgrading to the SCS release that incorporates OpenStack 2024.2 or later.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.