Put PS recommendations into a proposal / ADR

[JuanPTM]

SovereignCloudStack/issues#317

[garloff]

I feel like we have to document what we mean with "domain admin group" ...
Customers have at least two roles:

• "Domain admins" can do things like creating projects, creating users and granting users access to some projects (within the domain of course)
• "Users" can create and view resources within the projects that they have been granted access to by the "domain admin"
  The thus defined terms then can be matched against PS recommendations.

[garloff]

"These are not related in any way with OpenStack." (note the corrected spelling)
I don't understand this statement though.
Later on we execute commands openstack group create gd000001-member and
openstack role add --group gd000001-member --project p000001-scs_dev_project $role; openstack role add --group gp000001-scs_dev_project-member --project p000001-scs_dev_project $role
so the "domain admin group" and "project admin group" concepts seems to correspond to OpenStack concepts ...

[JuanPTM]

Ok, this is a misunderstanding from the notes .

In the notes it says:

hint: “domain admin” and “project admin” are from a customers point of view, they are NOT in anyway related to the openstack admin role

[frosty-geek]

LGTM

[reqa]

I've made a proposal to address Kurts' comments.

[reqa]

Proposals to make the github markdown linter happy.

[reqa]

Duplicate line

[frosty-geek]

this still looks good to me... @garloff i guess this only needs a number assigned to it or is there anything else left to do here?

[JuanPTM]

Added block with federation information

[garloff]

Number 0301 would seem appropriate (track IAM, next free number).
This is a (draft) standard -- and we should have an good discussion whether or not we can make this certification agreement or whether it is a recommendation (and thus optional) only, I guess.

[fkr]

One point that I also emphasized in a few calls: By releasing recommendations we have a very good way of moving CSPs towards adopting good/better practices BEFORE we than (once they've been more and more adopted) move it from recommendation to mandatory.
So releasing something as a recommendation is a very good stepping stone without placing the burden of a mandatory item on everyone from the beginning.

[garloff]

Sidenote: No need to fork the repository. Please create a branch.
Feature branches would have names like feat/add-naming-convention, so you'd do

git checkout main
git pull
git checkout -b feat/add-naming-convention
[...]

to create the branch and work on it.
Next time ...