Skip to content

Instantly share code, notes, and snippets.

@flynnduism

flynnduism/snapshotting-inline.md

Last active August 29, 2015 14:08
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save flynnduism/23ce05039a24073dcb2c to your computer and use it in GitHub Desktop.
Save flynnduism/23ce05039a24073dcb2c to your computer and use it in GitHub Desktop.
Download ZIP
Raw
snapshotting-inline.md

Hey Eben, dumping my thoughts on inline snapshot info here.

Server Status

I think if we’re going to show live info on in-progress snapshots, then it should follow the activity state indicator we use for other event types...

https://hostr.co/file/S0kicp2i3fKl/status-header.png

The first line of copy on each server is meant to reflect the current state. Running / Updating / Offline, etc. I’d like to incorporate the Snapshotting info into that space.

Is there a way of we could set ‘snapshotting’ as a status/class on the server, so the status and content within can change?

Running Multiple Snaps

https://hostr.co/file/BBFFenHn9pGc/multiple.png

In terms of showing the state of multiple snapshots, I’d rather avoid listing all active snaps, and instead focus on a summary as to the most recent snapshot.

Slack is unsure of whether AWS allows concurrent snapshotting on an individual server, it may queue or return errors. He’s not sure.

https://hostr.co/file/Vv0e7GGUTf78/snapping.png

^ So something like this is what I’m thinking for the inline snapshot info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment