From 08b338862aae05d8e2de62124fbce27d7903d92c Mon Sep 17 00:00:00 2001 From: Adam Spiers Date: Thu, 2 Jun 2016 15:57:07 +0100 Subject: [PATCH] explain reference to the "pet model" Add a brief explanation of pets vs. cattle, and a link to a more in-depth explanation, since we use that terminology in the user story. Change-Id: I60d4ef458aebdaddc33bd9773c670e6571d0718b Signed-off-by: Adam Spiers --- user-stories/proposed/ha_vm.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/user-stories/proposed/ha_vm.rst b/user-stories/proposed/ha_vm.rst index 2bf4ddf..d4e0d1c 100644 --- a/user-stories/proposed/ha_vm.rst +++ b/user-stories/proposed/ha_vm.rst @@ -132,3 +132,11 @@ Glossary operational performance for a higher than normal period. Not to be confused with 100% availability, which is sometimes described as `fault tolerance `_. + +* `Pets and cattle + `_ - + a metaphor commonly used in the OpenStack community to describe the + difference between two service architecture models: cloud-native, + stateless, disposable instances with built-in resilience in the + application layer (cattle), vs. legacy, stateful instances with no + built-in resilience (pets).