1 files changed, 63 insertions, 0 deletions
diff --git a/reference_templates/pgaas-database.yaml-template b/reference_templates/pgaas-database.yaml-template
new file mode 100644
index 0000000..a89d638
--- /dev/null
+++ b/reference_templates/pgaas-database.yaml-template
@@ -0,0 +1,63 @@
+# -*- indent-tabs-mode: nil -*- # vi: set expandtab:
+#
+# ============LICENSE_START====================================================
+# org.onap.dcae
+# =============================================================================
+# Copyright (c) 2017 AT&T Intellectual Property. All rights reserved.
+# =============================================================================
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+# 
+#      http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+# ============LICENSE_END======================================================
+
+tosca_definitions_version: cloudify_dsl_1_3
+
+description: |-
+  This blueprint is used to install and to uninstall a persistent database into the central postgres as a platform service.
+  This blueprint depends upon the deployment of the pgaas_plugin, the PGaaS Cinder volume, the PGaaS service, and Consul.
+  This blueprint is part of a suite of three blueprints that allow a PGaaS
+  cluster to be created that has persistent databases stored in Cinder.
+  pgaas-disk allocates the cinder volumes. It must be run first.
+  pgaas-cluster creates the PG service and attaches the cinder volumes. It must be run second.
+  pgaas-database creates a database. It must be run third, for each persistent database.
+  If the cluster is uninstalled, the persistent databases are unaffected.
+  If a database blueprint is uninstalled, the persistent database goes away.
+  If the disk blueprint is uninstalled, all persistent databases go away, along with the server instance.
+
+imports:
+  - http://www.getcloudify.org/spec/cloudify/3.4/types.yaml
+
+  - "{{ ONAPTEMPLATE_RAWREPOURL_org_onap_ccsdk_platform_plugins_releases }}/type_files/pgaas/1.1.0/pgaas_types.yaml"
+
+inputs:
+  blueprint_version:
+    type: string
+    default: '2018-03-29T14:28:59+0000'
+
+  # pgaas-specific info
+  pgaas_cluster_name:
+    type: string
+    default: pgcl
+  database_description:
+    type: string
+    default: 'This is a sample database'
+  database_name:
+    type: string
+    default: sample
+
+{{ ONAPTEMPLATE_STANDARD_INPUTS_TYPES }}
+
+node_templates:
+  pgaasdbtest:
+    type: dcae.nodes.pgaas.database
+    properties:
+      writerfqdn: { concat: [ { get_input: location_prefix }, '-', { get_input: pgaas_cluster_name }, '-write.', { get_input: location_domain } ] }
+      name: { get_input: database_name }