From f52ac0d10b4c5f1219a4af9fa659659d5aff5012 Mon Sep 17 00:00:00 2001 From: Scott Dodson Date: Mon, 5 Feb 2018 13:30:52 -0500 Subject: xPaaS v1.4.8 for v3.7 --- .../v3.7/xpaas-templates/amq62-persistent.json | 42 +++++++++++++++++----- 1 file changed, 34 insertions(+), 8 deletions(-) (limited to 'roles/openshift_examples/files/examples/v3.7/xpaas-templates/amq62-persistent.json') diff --git a/roles/openshift_examples/files/examples/v3.7/xpaas-templates/amq62-persistent.json b/roles/openshift_examples/files/examples/v3.7/xpaas-templates/amq62-persistent.json index 67c812fb4..bc62098ee 100644 --- a/roles/openshift_examples/files/examples/v3.7/xpaas-templates/amq62-persistent.json +++ b/roles/openshift_examples/files/examples/v3.7/xpaas-templates/amq62-persistent.json @@ -6,7 +6,7 @@ "description": "Application template for JBoss A-MQ brokers. These can be deployed as standalone and use persistent storage for saving messages, including message migration when the number of pods are reduced. This template doesn't feature SSL support.", "iconClass": "icon-amq", "tags": "messaging,amq,jboss,hidden", - "version": "1.4.7", + "version": "1.4.8", "openshift.io/display-name": "JBoss A-MQ 6.2 (no SSL)", "openshift.io/provider-display-name": "Red Hat, Inc." }, @@ -14,7 +14,7 @@ }, "labels": { "template": "amq62-persistent", - "xpaas": "1.4.7" + "xpaas": "1.4.8" }, "message": "A new persistent messaging service has been created in your project. It will handle the protocol(s) \"${MQ_PROTOCOL}\". The username/password for accessing the service is ${MQ_USERNAME}/${MQ_PASSWORD}.", "parameters": [ @@ -64,7 +64,7 @@ "displayName": "A-MQ Volume Size", "description": "Size of the volume used by A-MQ for persisting messages.", "name": "VOLUME_CAPACITY", - "value": "512Mi", + "value": "1Gi", "required": true }, { @@ -87,7 +87,7 @@ "displayName": "A-MQ Mesh Discovery Type", "description": "The discovery agent type to use for discovering mesh endpoints. 'dns' will use OpenShift's DNS service to resolve endpoints. 'kube' will use Kubernetes REST API to resolve service endpoints. If using 'kube' the service account for the pod must have the 'view' role, which can be added via 'oc policy add-role-to-user view system:serviceaccount::default' where is the project namespace.", "name": "AMQ_MESH_DISCOVERY_TYPE", - "value": "kube", + "value": "dns", "required": false }, { @@ -210,6 +210,32 @@ } } }, + { + "kind": "Service", + "apiVersion": "v1", + "spec": { + "clusterIP": "None", + "ports": [ + { + "name": "mesh", + "port": 61616 + } + ], + "selector": { + "deploymentConfig": "${APPLICATION_NAME}-amq" + } + }, + "metadata": { + "name": "${APPLICATION_NAME}-amq-mesh", + "labels": { + "application": "${APPLICATION_NAME}" + }, + "annotations": { + "service.alpha.kubernetes.io/tolerate-unready-endpoints": "true", + "description": "Supports node discovery for mesh formation." + } + } + }, { "kind": "DeploymentConfig", "apiVersion": "v1", @@ -237,7 +263,7 @@ "from": { "kind": "ImageStreamTag", "namespace": "${IMAGE_STREAM_NAMESPACE}", - "name": "jboss-amq-62:1.6" + "name": "jboss-amq-62:1.7" } } }, @@ -341,7 +367,7 @@ }, { "name": "AMQ_MESH_SERVICE_NAME", - "value": "${APPLICATION_NAME}-amq-tcp" + "value": "${APPLICATION_NAME}-amq-mesh" }, { "name": "AMQ_MESH_SERVICE_NAMESPACE", @@ -398,7 +424,7 @@ "from": { "kind": "ImageStreamTag", "namespace": "${IMAGE_STREAM_NAMESPACE}", - "name": "jboss-amq-62:1.6" + "name": "jboss-amq-62:1.7" } } }, @@ -457,7 +483,7 @@ }, { "name": "AMQ_MESH_SERVICE_NAME", - "value": "${APPLICATION_NAME}-amq-tcp" + "value": "${APPLICATION_NAME}-amq-mesh" }, { "name": "AMQ_MESH_SERVICE_NAMESPACE", -- cgit v1.2.3