I'm not sure I understand the distinction, Curtis. Backing up the state data in an HA environment is what I was talking about for large environments.
On Wed, Jun 4, 2014 at 4:12 PM, Curtis Hovey-Canonical <cur...@canonical.com > wrote: > On Wed, Jun 4, 2014 at 3:58 PM, Nate Finch <nate.fi...@canonical.com> > wrote: > ... > > Then the only case that is really a problem is large environments which > are > > not using HA, which should be something we discourage, and uninterrupted > > backup can be a way to show the benefits of HA. > > There is one other scenario. A backup and restore of a HA env. We > support this as a final fallback for cases where disaster strikes all > state-servers. We test that his can always be done. CI does see the > downtime. I think this is acceptable since a human chooses to bring > down state-server and none of the other services running in the > environment are affected. > > In the future, when charms can report the health of services, > consumers of health data may have some sense of downtime. > > > -- > Curtis Hovey > Canonical Cloud Development and Operations > http://launchpad.net/~sinzui > > -- > 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