diff options
| -rw-r--r-- | docs/sections/blueprints/PGaaS.rst | 24 | ||||
| -rw-r--r-- | docs/sections/blueprints/index.rst | 11 |
2 files changed, 35 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 diff --git a/docs/sections/blueprints/index.rst b/docs/sections/blueprints/index.rst new file mode 100644 index 00000000..ae267b74 --- /dev/null +++ b/docs/sections/blueprints/index.rst @@ -0,0 +1,11 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 + + +Data Collection, Analytics, and Events (DCAE) blueprints +======================= + +.. toctree:: + :maxdepth: 1 + + ./PGaaS.rst |