Hi  Zhao,
Tried it but without any luck.
I am executing this on the onap k8s env and I have observed that one of the POD 
is down - kube2msb-registrator-1900608333-06b2p. Could that be the reason? What 
is the main function of this POD?
What are the other containers

-          msb-eag-565007981-vgnth – is this the external gateway

-          msb-iag-3532976410-8xf0c – is this the internal gateway

Is there a way to check if the service is registered in the internal gateway.

I will check once I get the registrator pod running.

Thanks,
Avdhut Kholkar
From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn]
Sent: Wednesday, November 29, 2017 1:33 PM
To: Avdhut Kholkar <avdhut.khol...@amdocs.com>
Cc: onap-discuss@lists.onap.org
Subject: Re:[onap-discuss] [msb] Cannot access Services through MSB


Hi Avdhut,



It seems like the AAI service has not been successfully registered to MSB.



Could you please try this curl command and send me the output?



curl -X POST \
-H "Content-Type: application/json" \
-d '{"serviceName": "aai", "version": "v8", "url": "/aai/v8","protocol": 
"REST", "path": "/aai/v8", "nodes": [ {"ip": "{AAI_IP}","port": "8443"}]}' \
"http://127.0.0.1:10081/api/microservices/v1/services";



Thanks,

Huabing



Original Mail
Sender:  <avdhut.khol...@amdocs.com<mailto:avdhut.khol...@amdocs.com>>;
To:  <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>;
Date: 2017/11/29 14:36
Subject: [onap-discuss] [msb] Cannot access Services through MSB
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-discuss


Hi,

I have followed instructions mentioned over page: 
https://wiki.onap.org/display/DW/MSB+Test+Environment+Setup
I have registered AAI service in MSB as mentioned in the wiki above
{
  "serviceName": "aai",
  "version": "v8",
  "url": "/aai/v11",
  "protocol": "REST",
  "visualRange": "1",
  "path":"/aai/v11",
  "nodes": [
    {
      "ip": "10.235.34.13",
      "port": "40325",
      "ttl": 0
    }
  ]
}

If I access the URL directly from AAI it works
https://<ipaddress>:<port>/aai/v8/cloud-infrastructure/cloud-regions<https://%3cipaddress%3e:%3cport%3e/aai/v8/cloud-infrastructure/cloud-regions>
Response: 200 OK
{
    "cloud-region": [
        {
            "cloud-owner": "OnapPrivateCloud",
            "cloud-region-id": "RegionOne",
            "cloud-type": "SharedNode",
            "owner-defined-type": "OwnerType",
            "cloud-region-version": "v1",
            "cloud-zone": "CloudZone",
            "resource-version": "1511873022465",
            "tenants": {
                "tenant": [
                    {
                        "tenant-id": "{{tenant_id}}",
                        "tenant-name": "onap-dev",
                        "resource-version": "1511873022533"
                    }
                ]
            }
        }
    ]
}

But If I access through MSB API, I get a ‘BAD Gateway’ error

GET 
/api/aai/v8/cloud-infrastructure/cloud-regions/cloud-region/OnapPrivateCloud/RegionOne
Host: 10.235.34.13: 40325
Content-Type: application/json
X-FromAppId: AAI
Accept: application/json

Response: 502 Bad Gateway
<html>
    <head>
        <title>502 Bad Gateway</title>
    </head>
    <body bgcolor="white">
        <center>
            <h1>502 Bad Gateway</h1>
        </center>
        <center>error message:No route found for this request!</center>
        <hr>
        <center>nginx</center>
    </body>
</html>

I also tried by registering a SO URL and have the same issue. I am able to 
access the SO URL directly but via MSB.
Note that my env did not register the services directly via ESR – this should 
not make a difference I think.

Can someone help?
Regards,
Avdhut
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement, you may review at 
https://www.amdocs.com/about/email-disclaimer
Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partner­ship with LLP Identification Number: AAI-6901 
effective 28th Feb 2017)


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement, you may review at 
https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partner­ship with LLP Identification Number: AAI-6901 
effective 28th Feb 2017)
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to