This is a bit rough, I have not had time to make it better or add the other
less common use cases or HA but should give a more decent explanation
https://docs.google.com/a/canonical.com/document/d/1AtAo-uxED5TvXahJNytF-PIswRv9T0lewcyu699Rpyk/edit?usp=sharing

On Wed, Mar 25, 2015 at 3:44 PM, Eric Snow <eric.s...@canonical.com> wrote:

> On Tue, Mar 24, 2015 at 9:25 PM, Tim Penhey <tim.pen...@canonical.com>
> wrote:
> > I'm seriously not in favour of calling it "recover", and not just
> > because it has a particular meaning in Go.
>
> I'm glad you said so then. :)
>
> >
> > Perhaps "rebuild" or "recreate", but "recover" feels wrong.
>
> Got it.  I'm not married to "recover".  It was just the first
> reasonable (to me) alternative that popped into my head.
>
> "rebuild" and "recreate" could work, though they don't seem quite
> right either.  Perhaps something more like "replace" or "reset"?  So
> far it's all re* names, so maybe "wipe"? :)  The catch is that it will
> be a subcommand of "juju backups" so it also needs to be something
> that implies applying a backup rather than affecting a backup.  Hmm.
> "apply"?
>
> -eric
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Reply via email to