We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From GLOSSARY.md:
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:
Is this a correct read on the definition of an Aurae Node?
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
Feel free to PR a change/update @bpmooch if you are interested in taking a stab at capturing all this.
No branches or pull requests
From
GLOSSARY.md
:I take the ambiguity of "single fault domain" as a conviction for auraed to work well in multiple production scenarios:
Is this a correct read on the definition of an Aurae Node?
The text was updated successfully, but these errors were encountered: