Changed aaiEndpoint to point to new server name 51/20451/1
authorJim Hahn <jrh3@att.com>
Tue, 24 Oct 2017 21:44:13 +0000 (17:44 -0400)
committerJim Hahn <jrh3@att.com>
Tue, 24 Oct 2017 21:46:44 +0000 (17:46 -0400)
aaiEndpoint was pointing to the vm1 server which is aliased to the new
server.  However, as the new server's certificate does not include the
alias as one of its alternate names, things were unable to connect. The
endpoint has now been changed to match the new server name, thus the SSL
ceritifcate should match now. Note: for this to work, the new server
name must be found in DNS (or /etc/hosts).

Change-Id: I1d148ebc69ddf91edead45a4ad075c167a88fc33
Issue-Id: SO-249
Signed-off-by: Jim Hahn <jrh3@att.com>
volumes/mso/chef-config/mso-docker.json

index b864b6a..9b20fca 100644 (file)
       "mso.sniro.endpoint": "/optimizationInstance/V1/create",
       "mso.sniro.callback": "/adapters/rest/SDNCNotify/SNIROResponse",
       "mso.infra.customer.id": "21014aa2-526b-11e6-beb8-9e71128cae77",
-      "aaiEndpoint": "https://c1.vm1.aai.simpledemo.openecomp.org:8443",
+      "aaiEndpoint": "https://aai.api.simpledemo.openecomp.org:8443",
       "aaiAuth": "2630606608347B7124C244AB0FE34F6F",
       "adaptersNamespace": "http://org.openecomp.mso",
       "adaptersCompletemsoprocessEndpoint": "http://mso:8080/CompleteMsoProcess",