Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Define different levels of redundancy and failure safety. #540

Closed
josephineSei opened this issue Mar 26, 2024 · 2 comments
Closed

Define different levels of redundancy and failure safety. #540

josephineSei opened this issue Mar 26, 2024 · 2 comments
Assignees
@josephineSei
Labels
duplicate This issue or pull request already exists IaaS Issues or pull requests relevant for Team1: IaaS SCS is standardized SCS is standardized SCS-VP10 Related to tender lot SCS-VP10 standards Issues / ADR / pull requests relevant for standardization & certification

Comments

@josephineSei
Copy link
Contributor

As well as for the replication of volumes as for AZs, we have to adress the question what redundancy can look like and what to expect from each mechanism.

This may be just a guide or definition as a baseline for further standards.
@josephineSei josephineSei added IaaS Issues or pull requests relevant for Team1: IaaS standards Issues / ADR / pull requests relevant for standardization & certification SCS is standardized SCS is standardized SCS-VP10 Related to tender lot SCS-VP10 labels Mar 26, 2024
@josephineSei josephineSei self-assigned this Mar 26, 2024
@mbuechse
Copy link
Contributor

I may be mistaken, but this looks like a duplicate of #527.

@josephineSei
Copy link
Contributor Author

I may be mistaken, but this looks like a duplicate of #527.

Ah yes, I'm closing this and put my thought into the other ticket.

@josephineSei josephineSei added the duplicate This issue or pull request already exists label Mar 26, 2024
cah-hbaum added a commit that referenced this issue Apr 3, 2024
@cah-hbaum
fixup! Update standard to v2 (issues/#540)
6c0e696 
Signed-off-by: Hannes Baum <[email protected]>
cah-hbaum added a commit that referenced this issue Apr 3, 2024
@cah-hbaum
fixup! Update standard to v2 (issues/#540)
b26aef9 
Signed-off-by: Hannes Baum <[email protected]>
cah-hbaum added a commit that referenced this issue Jun 4, 2024
@cah-hbaum
Update node distribution standard (issues/#540)
c0c587b 
Adds the new label topology.scs.openstack.org/host-id to the standard and extend the standard to require providers to set the labels on their managed k8s clusters.

Signed-off-by: Hannes Baum <[email protected]>
cah-hbaum added a commit that referenced this issue Jun 4, 2024
@cah-hbaum
Update standard to v2 (issues/#540)
9f60afd 
Like discussed in the SIG Standardization and Certification Meeting, the standard is updated to v2 with the changes made to it and immediately set to "Stable", since no major changes were done. This comes mainly from the rushed job we did.

Signed-off-by: Hannes Baum <[email protected]>
cah-hbaum added a commit that referenced this issue Jun 5, 2024
@cah-hbaum
Update node distribution standard (issues/#540)
237739c 
Adds the new label topology.scs.openstack.org/host-id to the standard and extend the standard to require providers to set the labels on their managed k8s clusters.

Signed-off-by: Hannes Baum <[email protected]>
cah-hbaum added a commit that referenced this issue Jun 5, 2024
@cah-hbaum
Update standard to v2 (issues/#540)
18e2dfa 
Like discussed in the SIG Standardization and Certification Meeting, the standard is updated to v2 with the changes made to it and immediately set to "Stable", since no major changes were done. This comes mainly from the rushed job we did.

Signed-off-by: Hannes Baum <[email protected]>
cah-hbaum added a commit that referenced this issue Jun 17, 2024
@cah-hbaum
Update node distribution standard (issues/#540)
6a2fcb1 
Adds the new label topology.scs.openstack.org/host-id to the standard and extend the standard to require providers to set the labels on their managed k8s clusters.

Signed-off-by: Hannes Baum <[email protected]>
cah-hbaum added a commit that referenced this issue Jun 17, 2024
@cah-hbaum
Update standard to v2 (issues/#540)
d905ecb 
Like discussed in the SIG Standardization and Certification Meeting, the standard is updated to v2 with the changes made to it and immediately set to "Stable", since no major changes were done. This comes mainly from the rushed job we did.

Signed-off-by: Hannes Baum <[email protected]>
cah-hbaum added a commit that referenced this issue Jun 17, 2024
@cah-hbaum @mbuechse
Create v2 of node distribution standard (issues/#494) (#524)
6c82357 
* Update node distribution standard (issues/#540)

Adds the new label topology.scs.openstack.org/host-id to the standard and extend the standard to require providers to set the labels on their managed k8s clusters.
Like discussed in the SIG Standardization and Certification Meeting, the standard is updated to v2 with the changes made to it and like it was discussed in the Standardization/Certification meeting, we will set this v2 to a Draft state for now.
Some small cosmetic updates fixing some problems mentioned by @martinmo.
Did some more textual updates requested by @mbuechse.

---------

Signed-off-by: Hannes Baum <[email protected]>
Co-authored-by: Matthias Büchse <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@josephineSei josephineSei

Labels
duplicate This issue or pull request already exists IaaS Issues or pull requests relevant for Team1: IaaS SCS is standardized SCS is standardized SCS-VP10 Related to tender lot SCS-VP10 standards Issues / ADR / pull requests relevant for standardization & certification
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mbuechse @josephineSei