Dear Huabing and Michael, CLI has dependency on the MSB to discover the service before issuing the commands to that service. I believe this OOM and MSB integration will compliment CLI and thank you. And I have a question related to it, kindly help:
When OOM register the service in to MSB, what the is the format of Service URL followed ? For example, every service has URL in the form of <http(s)>://<service-dns>:<port>/<REST API URI> In this format, when OOM register the service, what portion of this service URL will be used? Here, CLI would look for the <http(s)>://<service-dns>:<port> from MSB as base path. Thanks Kanagaraj M *************************************************************************************** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！************************************************************************************** *************************************************************************************** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *************************************************************************************** From: [email protected] [mailto:[email protected]] On Behalf Of Michael O'Brien Sent: Monday, September 04, 2017 8:00 PM To: [email protected] Cc: [email protected] Subject: Re: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integration finished Huabing, Very nice work, I personally would be interested in seeing how other services communicate to AAI via V11 calls for example. Bringing up the new 4 onap-msb containers for a look now (I see we need to add them to the root of the dependency tree) – before the other 44. Looking forward to the demo at the OOM meeting on Wed at 2300h CST / 1100h EDT /michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Sunday, September 3, 2017 21:26 To: [email protected]<mailto:[email protected]>; Mike Elliott <[email protected]<mailto:[email protected]>>; Roger Maitland <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integration finished Hi David and OOM Team, I'm glad to let you know that oom registrator has been successfully deployed in k8s cluster which filled the last part of map. Now every ONAP microservices deployed by OOM will be automatically registered to MSB by oom registrator, and microservices can leverage MSB SDK or API Gateway to communicate with each other easily. I could show the demo in this week's meeting if we have time, it will cost about 5 minutes. I'd also like to discuss some minor issues like how to start MSB and registrator first in the OOM script so they're ready when other onap Microservices are spun up by OOM. Cheers, Huabing 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
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
