diff options
author | 2017-10-13 14:34:46 +0000 | |
---|---|---|
committer | 2017-10-13 14:34:59 +0000 | |
commit | 30c453e3bfa40414c1c1951fef2b97dc52ee7dae (patch) | |
tree | 15fa28e39f931371f116ce249f94381ae893fba1 /docs/sections/blueprints/PGaaS.rst | |
parent | 6553a13f948ffbf48c3bf5ec723372df137a085c (diff) |
add initial blueprint docs
add PGaaS.rst, with "MORE TO BE ADDED"
Change-Id: I4e9349a72bd4228c50a7ef11cff9df9c96a9faa4
Signed-off-by: Tony Hansen <tony@att.com>
Issue-ID: DCAEGEN2-128
Diffstat (limited to 'docs/sections/blueprints/PGaaS.rst')
-rw-r--r-- | docs/sections/blueprints/PGaaS.rst | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/docs/sections/blueprints/PGaaS.rst b/docs/sections/blueprints/PGaaS.rst new file mode 100644 index 00000000..5599c63e --- /dev/null +++ b/docs/sections/blueprints/PGaaS.rst @@ -0,0 +1,24 @@ += PostgreSQL as a Service + +PostgreSQL as a Service comes in two flavors: all-in-one blueprint, and +separate disk/cluster/database blueprints to separate the management of +the lifetime of those constituent parts. Both are provided for use. + +== Why Two Flavors? + +The reason there are two flavors of blueprints lays in the difference in +lifetime management of the constituent parts. + +For example, a database usually needs to have persistent storage, which +in these blueprints comes from Cinder storage volumes. The primitives +used in these blueprints assume that the lifetime of the Cinder storage +volumes matches the lifetime of the blueprint deployment. So when the +blueprint goes away, any Cinder storage volume allocated in the +blueprint also goes away. + +Similarly, a database's lifetime should have its + +The all-in-one blueprint assumes that everything can be allocated and +deallocated together. + +MORE TO BE ADDED |