Automate backups of initial environment
Bug #1451616 reported by
Tim Penhey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Juju has a nice backup feature. But unless users run 'juju backup' & store the
output somewhere, it is useless.
How difficult would it be to automate backup creation & storage on each unit ? I
mean, when someone 'juju deploy', the backup command could sometime be run and
the output stored on each unit.
If the juju environment becomes stale or suffer partial destruction, the output
could be fetched from any of the unit.
Revision history for this message
| James Troup (elmo) wrote | #1 |
| Changed in juju-core: | |
| importance: | Wishlist → Low |
| tags: | added: feature |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
While this is a nice idea that might work for some people, please
don't do this by default. It's not safe to assume that individual
units have the same trust as the bootstrap node(s).