letsencrypt
/
boulder
mirror of https://github.com/letsencrypt/boulder.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: remove stale multi-va feat. flag info (#4670)

This commit is contained in:
Daniel McCarney 2020-02-04 19:34:36 -05:00 committed by GitHub
parent c658b5cd77
commit e352227e46
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/multi-va.md
View File

@ -38,14 +38,13 @@ and
as their config files.
There are two feature flags that control whether multi-VA takes effect:
MultiVAFullResults and EnforceMultiVA. If MultiVAFullResults is enabled (the
current setting in prod and staging), then each primary validation will also
send out remote validation requests, and wait for all the results to come in, so
we can log the results for analysis. If EnforceMultiVA is enabled, we require
that almost all remote validation requests succeed. The primary VA's
"maxRemoteValidationFailures" config field specifies how many remote VAs can
fail before the primary VA considers overall validation a failure. It should be
strictly less than the number of remote VAs.
MultiVAFullResults and EnforceMultiVA. If MultiVAFullResults is enabled
then each primary validation will also send out remote validation requests, and
wait for all the results to come in, so we can log the results for analysis. If
EnforceMultiVA is enabled, we require that almost all remote validation requests
succeed. The primary VA's "maxRemoteValidationFailures" config field specifies
how many remote VAs can fail before the primary VA considers overall validation
a failure. It should be strictly less than the number of remote VAs.
Validation is also controlled by the "multiVAPolicyFile" config field on the
primary VA. This specifies a file that can contain temporary overrides for