AAF Charts

-PS3-MK
 -renaming charts to remove hyphen
 -refactoring service name configuration.  It wasn't quite correct
  the way it was.  It was taking the chart name as the service name
  and not using the values.yaml from the top level chart as intended.
 -Jonathan asked to name the main app service "aaf-service and cassandra
  to "aaf-cass" as this is what is in the cert
 -squashed https://gerrit.onap.org/r/#/c/45923/1 into this commit.
 -updated robot to the latest settings
 Robot tests are failing but all pods come up.  I think this can be merged
 and the AAF team investigate the robot health issue in a running system

-PS4-MK
 -reverting sms changes and taking the latest from master
 -removing repository from the global section of the aaf values.
  -this was causing all images to be pulled from nexus3.onap.org
   which was failing to pull images that come from docker hub.
   There is supposed to be a proxy through nexus3 to dockerhub but maybe
   we are missing something.

-PS5-MK
 -removing nodeports from non gui related charts.  There are conflicts

-PS6-Kiran
 -Adding imagepullsecrets for aaf-sms-vault subchart
 -updated image repository to pull from nexus3
 -tested and works now and should fix the pull errors

-PS7-Kiran
 -Previous patch picked up a couple of unintended changes
 -Reverting them

-PS8-MK
  -removing names from identities
  -using https for robot test

Issue-ID: OOM-930

Change-Id: I98f40ef5af03dda73aebf12f6fa48d928915ab34
Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>

Add Beijing CQLs into OOM

Issue-ID: AAF-114
Change-Id: I2c2d46738ba0885c41f710997d4b212b6ce4d2de
Signed-off-by: Instrumental <jonathan.gathman@att.com>
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>

1 files changed, 19 insertions, 0 deletions

diff --git a/charts/aaf-cm/templates/NOTES.txt b/charts/aaf-cm/templates/NOTES.txt
new file mode 100644
index 0000000..c60c745
--- /dev/null
+++ b/charts/aaf-cm/templates/NOTES.txt
@@ -0,0 +1,19 @@
+1. Get the application URL by running these commands:
+{{- if .Values.ingress.enabled }}
+{{- range .Values.ingress.hosts }}
+  http://{{ . }}
+{{- end }}
+{{- else if contains "NodePort" .Values.service.type }}
+  export NODE_PORT=$(kubectl get --namespace {{ include "common.namespace" . }} -o jsonpath="{.spec.ports[0].nodePort}" services {{ include "common.name" . }})
+  export NODE_IP=$(kubectl get nodes --namespace {{ include "common.namespace" . }} -o jsonpath="{.items[0].status.addresses[0].address}")
+  echo http://$NODE_IP:$NODE_PORT
+{{- else if contains "LoadBalancer" .Values.service.type }}
+     NOTE: It may take a few minutes for the LoadBalancer IP to be available.
+           You can watch the status of by running 'kubectl get svc -w {{ include "common.name" . }}'
+  export SERVICE_IP=$(kubectl get svc --namespace {{ include "common.namespace" . }} {{ include "common.name" . }} -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
+  echo http://$SERVICE_IP:{{ .Values.service.externalPort }}
+{{- else if contains "ClusterIP" .Values.service.type }}
+  export POD_NAME=$(kubectl get pods --namespace {{ include "common.namespace" . }} -l "app={{ include "common.name" . }},release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}")
+  echo "Visit http://127.0.0.1:8080 to use your application"
+  kubectl port-forward $POD_NAME 8080:{{ .Values.service.internalPort }}
+{{- end }}