Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
TPA
Wiki Replica
Commits
b98cd0fb
Verified
Commit
b98cd0fb
authored
4 years ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
puppet: disaster recovery docs
parent
584208e8
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
howto/puppet.md
+16
-5
16 additions, 5 deletions
howto/puppet.md
with
16 additions
and
5 deletions
howto/puppet.md
+
16
−
5
View file @
b98cd0fb
...
...
@@ -768,11 +768,22 @@ role account instead.
## Disaster recovery
<!-- what to do if all goes to hell. e.g. restore from backups? -->
<!-- rebuild from scratch? not necessarily those procedures (e.g. see -->
<!-- "Installation" below but some pointers. -->
TODO.
Ideally, the main Puppet server would be deployable from Puppet
bootstrap code and the
[
main installer
](
new-machine
)
. But in practice, much of
its configuration was done manually over the years and it MUST be
restored from
[
backups
](
backup
)
in case of failure.
This probably includes a restore of the
[
PostgreSQL
](
postgresql
)
database
backing the PuppetDB server as well. It's
*possible*
this step
*could*
be skipped in an emergency, because most of the information in
PuppetDB is a cache of exported resources, reports and facts. But it
could also break hosts and make converging the infrastructure
impossible, as there might be dependency loops in exported resources
(for example, the Puppet server needs access to the LDAP server, and
that is configured in Puppet).
So it is strongly encouraged to restore the PuppetDB server database
as well in case of disaster.
# Reference
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment