Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-990

AUTO.json in SDC has unreachable addresses

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Highest Highest
    • Beijing Release
    • Beijing Release
    • None
    • SB-04 OOM

      /root/chef-solo/environments/AUTO.json

      "UEB":

      { "PublicKey": "iPIxkpAMI8qTcQj8", "SecretKey": "Ehq3WyT4bkif4zwgEbvshGal", "fqdn": ["dev-dmaap.onap", "dev-dmaap.onap"] }

      ,

      dev-dmaap.onap doesnt seem to be reach from SDC container.

      dev-dmaap.onap should probably be message-router.onap

      equivalent in HEAT is:
      "UEB":

      { "PublicKey": "iPIxkpAMI8qTcQj8", "SecretKey": "Ehq3WyT4bkif4zwgEbvshGal", "fqdn": ["10.0.11.1", "10.0.11.1"] }

      ,

      ~oom/kubernetes/sdc/resources/config/environments/AUTO.json has:
      "UEB": {
      "PublicKey": "iPIxkpAMI8qTcQj8",
      "SecretKey": "Ehq3WyT4bkif4zwgEbvshGal",
      "fqdn": ["{{.Release.Name}}-dmaap.{{include "common.namespace" .}}", "{{.Release.Name}}-dmaap.{{include "common.namespace" .}}"]
      },

      but kubernetes GUI shows

      message-router
      app: dmaap
      chart: message-router-2.0.0
      heritage: Tiller
      release: dev
      10.43.110.70
      message-router.onap:3904 TCP
      message-router.onap:30227 TCP
      message-router.onap:3905 TCP
      message-router.onap:30226 TCP
      -

            Unassigned Unassigned
            bdfreeman1421 bdfreeman1421
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: