summaryrefslogtreecommitdiffstats
path: root/docs/sections
diff options
context:
space:
mode:
authorTony Hansen <tony@att.com>2017-10-25 11:53:09 +0000
committerTony Hansen <tony@att.com>2017-10-25 11:53:17 +0000
commitb32a0b6ebcaf7a0735806f39a3b91b0f830c79c7 (patch)
tree54a231259fdf90df39347cc2465f0bc42e32d61f /docs/sections
parent6ff9936cbe3146ffd4d393251db052fc949280ea (diff)
add some testing info
expand on the section on testing connections Change-Id: Icc412a6a8944ded3e4f5c25cdde77d2878771adc Signed-off-by: Tony Hansen <tony@att.com> Issue-ID: DCAEGEN2-128
Diffstat (limited to 'docs/sections')
-rw-r--r--docs/sections/blueprints/PGaaS.rst9
1 files changed, 7 insertions, 2 deletions
diff --git a/docs/sections/blueprints/PGaaS.rst b/docs/sections/blueprints/PGaaS.rst
index 47e234e0..a5508a19 100644
--- a/docs/sections/blueprints/PGaaS.rst
+++ b/docs/sections/blueprints/PGaaS.rst
@@ -119,10 +119,15 @@ volume size.)
You can verify that the cluster is up and running by connecting to the PostgreSQL service
-on port 5432:
+on port 5432. To verify that all of the DNS names were created properly and that PostgreSQL is
+answering on port 5432, you can use something like this:
::
- telnet ${LOCATIONPREFIX}-${CLUSTER}-write.${LOCATIONDOMAIN} 5432
+ sleep 1 | nc -v ${LOCATIONPREFIX}${CLUSTER}00.${LOCATIONDOMAIN} 5432
+ sleep 1 | nc -v ${LOCATIONPREFIX}${CLUSTER}01.${LOCATIONDOMAIN} 5432
+ sleep 1 | nc -v ${LOCATIONPREFIX}-${CLUSTER}-write.${LOCATIONDOMAIN} 5432
+ sleep 1 | nc -v ${LOCATIONPREFIX}-${CLUSTER}.${LOCATIONDOMAIN} 5432
+
Once you have the cluster created, you can then allocate databases. An application that
wants a persistent database not tied to the lifetime of the application blueprint can