Fix ssl.yaml generating GaneshaInternal in the endpoint map

The GaneshaInternal configured in the endpoint map is used by
the Ganesha service that front-ends CephFS with Manila. It cannot be
a hostname, it must be an IP Address always. See [1]

Closes-Bug: #1824421
[1] https://github.com/nfs-ganesha/nfs-ganesha/blob/af26bf4/src/config_samples/config.txt#L43
Change-Id: I9eefa5f145ab5b17a4d93e96f4aad35d3e069382

environments/ssl/tls-everywhere-endpoints-dns.yaml

@@ -31,7 +31,7 @@ parameter_defaults:
     Ec2ApiAdmin: {protocol: 'https', port: '8788', host: 'CLOUDNAME'}
     Ec2ApiInternal: {protocol: 'https', port: '8788', host: 'CLOUDNAME'}
     Ec2ApiPublic: {protocol: 'https', port: '13788', host: 'CLOUDNAME'}
-    GaneshaInternal: {protocol: 'nfs', port: '2049', host: 'CLOUDNAME'}
+    GaneshaInternal: {protocol: 'nfs', port: '2049', host: 'IP_ADDRESS'}
     GlanceAdmin: {protocol: 'https', port: '9292', host: 'CLOUDNAME'}
     GlanceInternal: {protocol: 'https', port: '9292', host: 'CLOUDNAME'}
     GlancePublic: {protocol: 'https', port: '13292', host: 'CLOUDNAME'}

sample-env-generator/ssl.yaml

@@ -370,7 +370,7 @@ environments:
             Ec2ApiAdmin: {protocol: 'https', port: '8788', host: 'CLOUDNAME'}
             Ec2ApiInternal: {protocol: 'https', port: '8788', host: 'CLOUDNAME'}
             Ec2ApiPublic: {protocol: 'https', port: '13788', host: 'CLOUDNAME'}
-            GaneshaInternal: {protocol: 'nfs', port: '2049', host: 'CLOUDNAME'}
+            GaneshaInternal: {protocol: 'nfs', port: '2049', host: 'IP_ADDRESS'}
             GlanceAdmin: {protocol: 'https', port: '9292', host: 'CLOUDNAME'}
             GlanceInternal: {protocol: 'https', port: '9292', host: 'CLOUDNAME'}
             GlancePublic: {protocol: 'https', port: '13292', host: 'CLOUDNAME'}