summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorColin Walters <walters@verbum.org>2017-10-21 10:10:34 -0400
committerAtomic Bot <atomic-devel@projectatomic.io>2017-10-21 14:12:02 +0000
commit4cda9f14fb5a0a886d9dc28955643b0a4837a154 (patch)
tree9b0e830d26f36d032d600a02ea2571c7b11a732a /docs
parent1222c2271b6a552054dcccf51199ed3314f9c66b (diff)
downloadostree-4cda9f14fb5a0a886d9dc28955643b0a4837a154.tar.gz
docs/related-projects: Add Google Usenix link
Closes: https://github.com/ostreedev/ostree/issues/1284 Closes: #1299 Approved by: cgwalters
Diffstat (limited to 'docs')
-rw-r--r--docs/manual/related-projects.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/manual/related-projects.md b/docs/manual/related-projects.md
index e58aeabb..c4f558da 100644
--- a/docs/manual/related-projects.md
+++ b/docs/manual/related-projects.md
@@ -244,6 +244,11 @@ It's relatively well thought through - however, it is a client-side
system assembly. If one wants to image servers and replicate
reliably, that'd be a different system.
+## Google servers (custom rsync-like approach, live updates)
+
+This paper talks about how Google was (at least at one point) managing
+updates for the host systems for some servers:
+[Live Upgrading Thousands of Servers from an Ancient Red Hat Distribution to 10 Year Newer Debian Based One (USENIX LISA 2013)](https://www.usenix.org/node/177348)
## Conary