Re: [onap-discuss] SDNC - oam clone issue

2017-07-03 Thread Sanchita Pathak
Hi, Not to worry about sdnc/oam folder, I could build sdnc core and sdnc rootpom without cloning oam. Regards, Sanchita From: Arun Arora (c) [mailto:aroraa...@vmware.com] Sent: Monday, July 3, 2017 03:44 PM To: Sanchita Pathak <sanch...@techmahindra.com>; onap-discuss@lists.onap.org S

[onap-discuss] SDNC - oam clone issue

2017-07-03 Thread Sanchita Pathak
Hi All, While cloning SDNC -oam project every time it gets stuck at 93% , please refer below screenshot. [cid:image001.png@01D2F40F.91A78F50] I never had this issue before while cloning APPC code and SDNC other projects i.e. adapters, core, northbound and plugins. Issue is only with

Re: [onap-discuss] SDNC - oam clone issue

2017-07-03 Thread Sanchita Pathak
Thanks for quick reply Arun. I kept it for more than 2 hrs but no change in the status (And tried it couple of times.). Usually it don't take so much time. Regards, Sanchita From: Arun Arora (c) [mailto:aroraa...@vmware.com] Sent: Monday, July 3, 2017 03:38 PM To: Sanchita Pathak <sa

Re: [onap-discuss] SDNC - oam clone issue - add -Djava.net.preferIPv4Stack=true to MAVEN_OPTS

2017-07-06 Thread Sanchita Pathak
linux" -Djava.net<http://java.net/>.preferIPv4Stack=true /michael From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Sanchita Pathak Sent: Monday, July 3, 2017 06:35 To: Arun Arora (c) &

[onap-discuss] [so] SO API version

2018-09-07 Thread Sanchita Pathak
Hi, We have setup ONAP Beijing release using heat based installation. While using VID, it is invoking SO API with version v6. But SO seems to have APIs available with version v4 (confirmed by manually invoking API). Can someone confirm if we are using correct SO image ? We have pulled

Re: [onap-discuss] [so] SO API version

2018-09-10 Thread Sanchita Pathak
Hi Seshu, API we are trying is POST http://:8080/ecomp/mso/infra/serviceInstances/v6 with payload. We are getting 404 Not Found back. Same API works with v4. VID is also trying to invoke SO API with v6 and it is also getting error 404. Btw, when service is distributed from SDC, we are getting

Re: [onap-discuss] [so] SO API version

2018-09-09 Thread Sanchita Pathak
Hi Steve, We are using CreateServiceInstance API manually. Able to call the API with v4 but not with v6. We are not able to create service instance using VID, as it is calling this API with v6. Thanks, Sanchita

Re: [onap-discuss] [so] SO API version

2018-09-11 Thread Sanchita Pathak
The issue was due to using incorrect SO Docker image (may be Amstersam one ! ). With pulling SO image again, this issue has gone. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12379): https://lists.onap.org/g/onap-discuss/message/12379 Mute This