Thanks Michael. After change the log level, there are indeed several information in the /data/logs/BE/SDC/SDC-BE/*.log files. But there are some healthcheck logs inserted, which makes it hard to analyze , is there any option to disable the healthcheck or hide related logs? Like: 2018-05-30T18:35:28.207Z|||||BE-Health-Check-Task|||SDC-BE||||||||INFO||||192.168.0.60||o.o.s.b.c.impl.CassandraHealthCheck||ActivityType=<getCassandraStatus>, Desc=<creating cluster for Cassandra for monitoring.>
Thanks Libo From: Kumar Skand Priya, Viswanath V [mailto:[email protected]] Sent: Tuesday, May 29, 2018 11:06 PM To: Lando,Michael <[email protected]>; Chris Donley <[email protected]> Cc: Zhu, Libo <[email protected]>; Huang, Haibin <[email protected]>; onap-discuss <[email protected]>; UdhayaChandran M <[email protected]> Subject: Re: [onap-discuss] [E] [sdc] [vnfsdk] CSAR can not import sdc Hi Michael / Chris Donley, Good Day! We would like to understand latest status of SOL 004 support between VNF-SDK and SDC in ONAP R2 ( latest release ). 1. From https://onap.readthedocs.io/en/latest/submodules/vnfsdk/model.git/docs/release-notes.html, it is stated that, there is a native integration between VNF-SDK and SDC. What is that integration ? * We tried generating a CSAR from VNF-SDK ( using pkgtools ) and then tried on-boarding the same in SDC and that's where we are hit with below error. So does this means, SDC is not fully integrated with VNF-SDK? 1. As per SOL 004 CSAR specification, a CSAR can contain either a TOSCA.metadata dir or can directly specify the VNFD in the root dir itself. However based on our testing, SDC is expecting TOSCA.metadata mandatorily. Does this mean that, SDC is not SOL 004 compliant ? * Also as per https://onap.readthedocs.io/en/latest/submodules/vnfsdk/model.git/docs/release-notes.html, VNF-SDK is having priliminary SOL 004 support. Is this due to SDC not being able to parse SOL 004 compliant CSAR? 1. Is complete support for SOL 004 has been scoped for R3 under both VNF SDK & SDC projects? BR, Viswa [http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]<http://www.verizon.com> Viswanath Kumar Skand Priya Architect Verizon India ( VDSI ) On Tue, May 29, 2018 at 7:43 PM, Lando,Michael <[email protected]<mailto:[email protected]>> wrote: Hi Please see my mail about the csar format. If you need to change the log lavel to debug this can be done in the docker it self by editing the log back xml file no restart is required. The docker resposible for the onboarding is the onboarding be docker. I suggest you use the sdc trabulshoting section in the wiki Sent from Email+ secured by MobileIron -------- Original Message -------- From: "Zhu, Libo" <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> Date: Tue, May 29, 2018, 15:30 To: "Kumar Skand Priya, Viswanath V" <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>>,"Huang, Haibin" <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>>,"Lando,Michael" <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> Subject: RE: [onap-discuss] [E] [sdc] CSAR can not import sdc +1. Where is the SDC log file which is triggered when user imports a CSAR file? There are some log files on the /data/logs/, but can’t find any useful info. BE docker_logs FE ONBOARD sdc-api-tests sdc-ui-tests WS BTW, setup the SDC based on https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Deploying-2BSDC-2Bon-2Ba-2BLinux-2BVM-2Bfor-2BDevelopment&d=DwIF-g&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ&m=qVufetxs5LXgkRxpOizZ5x1LWZ9ov6hclI9GdY7K-7w&s=hHIG5cRX6RUSGEkhNKC7GQSlBZlRUnnf0Pky3Kk7OF0&e=<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Deploying-2BSDC-2Bon-2Ba-2BLinux-2BVM-2Bfor-2BDevelopment&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=UHkTasNxY9W7bcdXXeCFMPGhsq8PmnZLGStj3cpsNuE&s=nWVthMsfvJvG-1OJKJDXFZiGc5RZplzFsVUIeh41WL0&e=> Thanks Libo From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Kumar Skand Priya, Viswanath V via onap-discuss Sent: Tuesday, May 29, 2018 7:37 PM To: Huang, Haibin <[email protected]<mailto:[email protected]>>; LANDO, MICHAEL <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] [E] [sdc] CSAR can not import sdc + 1 We are also getting same error. Could someone from SDC team comment here? BR, Viswa [http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.verizon.com&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=UHkTasNxY9W7bcdXXeCFMPGhsq8PmnZLGStj3cpsNuE&s=vSS2NnX39jIDRff04dFMiKbjFRi07IXakfzCIS63Iz4&e=> Viswanath Kumar Skand Priya Architect Verizon India ( VDSI ) On Wed, May 16, 2018 at 1:18 PM, Huang, Haibin <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> wrote: Hi SDC developers, We accord to SOL-004 create one CPE CSAR file. But when I import this file to SDC, we found below error. Who know why get below error? [cid:[email protected]] ------------------------------------------------------------------------------------------------------------------------------- Huang.haibin 11628530 86+18106533356 _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ&m=PJVXXvifRlG7rJ_0_NC7YOZEztufSMnrHP_zKAN3uKU&s=rf3uP0N070r_wFOn1zqzKGvcgSjuUPygyHp2CZ6pJek&e=
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
