x/development-proposals
Code Issues Proposed changes

explain reference to the "pet model"

Browse Source 
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 <aspiers@suse.com>
This commit is contained in:
Adam Spiers
2016-06-02 15:57:07 +01:00
parent 0dd880d0ec
commit 08b338862a
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
user-stories/proposed/ha_vm.rst
View File

@@ -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 <https://en.wikipedia.org/wiki/Fault_tolerance>`_.
* `Pets and cattle
<http://www.theregister.co.uk/2013/03/18/servers_pets_or_cattle_cern/>`_ -
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).