Yes, the service in the VNF may not be up because of cloud init failures. Try from an external client like postman to run health check against the VNF (change the IP in the URL below):
curl -X GET \ https://10.12.5.47:8445/restconf/operational/health-vnf-onap-plugin:health-vnf-onap-plugin-state/health-check \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ -H 'Postman-Token: 1e6f9861-3238-4217-aff4-ec3de5e023db' \ -H 'cache-control: no-cache' See which error you get. Sometimes some slowness in cloud init prevents the v_lb_init.sh script to run this command, which configures the vLB with the IP address of the vDNS that is part of the base module: curl -X PUT http://localhost:8183/restconf/config/vlb-business-vnf-onap-plugin:vlb-business-vnf-onap-plugin/vdns-instances/vdns-instance/$VDNS_IPADDR -H 'Accept: application/json' -H 'Cache-Control: no-cache' -H 'Content-Type: application/json' -H 'Postman-Token: 8bfe8815-3efb-4c9b-8974-7b8d7b6da4c6' -H "Authorization: Basic YWRtaW46YWRtaW4=" -d '{"vdns-instance": [{ "ip-addr": "'$VDNS_IPADDR'", "oam-ip-addr": "'$OAM_VDNS_IP'", "enabled": true }]}' Last, and most importantly, we didn’t test the VNF APIs because they are deprecated and we are moving to GR APIs, so I’m not sure whether the use case will work with old APIs. At least, you need to change the JSON path to the SDNC object that SO uses to resolve configuration params. SO uses the selflink in the specific VF module object in AAI. Thanks, Marco From: <[email protected]> on behalf of "Gopigiri, Sirisha via Lists.Onap.Org" <[email protected]> Reply-To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Date: Thursday, December 20, 2018 at 8:29 AM To: "[email protected]" <[email protected]> Cc: Viswanath V Kumar Skand Priya <[email protected]> Subject: [E][onap-discuss] Scale-out Usecase Dear Team, I am trying to replicate the Scale-out Usecase by using the following link: https://wiki.onap.org/display/DW/Running+Scale+Out+Use+Case+for+Casablanca<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Running-2BScale-2BOut-2BUse-2BCase-2Bfor-2BCasablanca&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=KP3A7U35ZCXCpN0y-_nkCBP0g8Ce8fzbQDUZ4uoBERM&s=-D_d3rH78-iCIfpsIT_OhhsaCV88PL9Ca3yvjUHlB0A&e=> Instead of GR_APIs I am using VNF_old APIs in the VID. After the Vf-module is created, I could see no services running on 8445 port in the vLoadBalancer VM. So the health check is failing while scale out operation. And I could see only compilation errors in the cloud-init logs. Is it because of compilation errors the service is not coming up on 8445 port or am I missing any configuration? Thank you Best Regards Sirisha Gopigiri -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14665): https://lists.onap.org/g/onap-discuss/message/14665 Mute This Topic: https://lists.onap.org/mt/28811190/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
