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.

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

Defining a single fault domain #13

Open
bpmooch opened this issue Oct 5, 2022 · 2 comments
Open

Defining a single fault domain #13

bpmooch opened this issue Oct 5, 2022 · 2 comments

Comments

@bpmooch
Copy link

bpmooch commented Oct 5, 2022

From GLOSSARY.md:

Aurae Node is the set of services that provide an Aurae service that exist as a single fault domain

I take the ambiguity of "single fault domain" as a conviction for auraed to work well in multiple production scenarios:

  1. Bare metal / VM pid 1
  2. Container
  3. Bare-metal / VM integrates w/ systemd to replace systemd-nspawn

Is this a correct read on the definition of an Aurae Node?

@krisnova
Copy link
Contributor

krisnova commented Oct 7, 2022

CC @taniwha3 who has a better grasp here

This language should also define "tenant" as it is referred to by the expression "multi tenant".

I believe a fault domain is different than an isolation/trust boundary.

A namespace should be a trust zone or isolation zone (or both?).

A rack in a data center with unique power is a fault domain.

@krisnova
Copy link
Contributor

krisnova commented Oct 7, 2022

Feel free to PR a change/update @bpmooch if you are interested in taking a stab at capturing all this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants