So why not submit a change to testsuite so they split it into two IP’s and modify the robot_vm_install.sh to ocpy the input into the two variable so that we can use the same asdc_interface.robot for either HEAT or OOM ?
Testsuite will be adding to the asdc_interface.robot over time (as in this case) . I’m sure you dont want to maintain these files in OOM long term. Brian From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] Sent: Thursday, January 11, 2018 4:29 PM To: FREEMAN, BRIAN D <bf1...@att.com> Cc: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] OOM Robot Distribute It’s the same IP address in the HEAT deployment. In OOM it’s not the same. sdc-fe.onap-sdc for frontend —> GLOBAL_INJECTED_SDC_FE_IP_ADDR sdc-be.onap-sdc for backend —> GLOBAL_INJECTED_SDC_BE_IP_ADDR Alexis On Jan 11, 2018, at 4:07 PM, FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>> wrote: The front end and back of SDC are the same IP address so its not clear to me why you had to change anything in the asdc_interface.robot ? Brian root@onapoom3:/dockerdata-nfs/onap/robot/robot/resources# diff asdc_interface.robot asdc_interface.robot.old 47,48c47,48 < ${ASDC_FE_ENDPOINT} ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_IP_ADDR}:${GLOBAL_ASDC_FE_PORT} < ${ASDC_BE_ENDPOINT} ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_IP_ADDR}:${GLOBAL_ASDC_BE_PORT} --- > ${ASDC_FE_ENDPOINT} > ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_FE_IP_ADDR}:${GLOBAL_ASDC_FE_PORT} > ${ASDC_BE_ENDPOINT} > ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_BE_IP_ADDR}:${GLOBAL_ASDC_BE_PORT} 56d55 < ${catalog_resources}= Create Dictionary 62d60 < \ Set To Dictionary ${catalog_resources} ${loop_catalog_resource_id}=${loop_catalog_resource_resp} 74,75c72,73 < [Return] ${catalog_service_resp['name']} ${loop_catalog_resource_resp['name']} ${vf_module} ${catalog_resource_ids} ${catalog_service_id} ${catalog_resources} < --- > [Return] ${catalog_service_resp['name']} > ${loop_catalog_resource_resp['name']} ${vf_module} > ${catalog_resource_ids} ${catalog_service_id} > 297,298c295,296 < [Documentation] Creates an asdc Software Product and returns its id < [Arguments] ${software_product_id} ${file_path} ${version_id}=0.1 --- > [Documentation] Creates an asdc Software Product and returns its id > [Arguments] ${software_product_id} ${file_path} ${version_id}=0.1 301,302c299,300 < ${resp}= Run ASDC Post Files Request ${ASDC_VENDOR_SOFTWARE_PRODUCT_PATH}/${software_product_id}/versions/${version_id}${ASDC_VENDOR_SOFTWARE_UPLOAD_PATH} ${files} ${ASDC_DESIGNER_USER_ID} < Should Be Equal As Strings ${resp.status_code} 200 --- > ${resp}= Run ASDC Post Files Request > ${ASDC_VENDOR_SOFTWARE_PRODUCT_PATH}/${software_product_id}/versions/${version_id}${ASDC_VENDOR_SOFTWARE_UPLOAD_PATH} > ${files} ${ASDC_DESIGNER_USER_ID} > Should Be Equal As Strings ${resp.status_code} 200 From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] Sent: Thursday, January 11, 2018 4:01 PM To: FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: Re: [onap-discuss] OOM Robot Distribute On Jan 11, 2018, at 4:00 PM, Alexis de Talhouët <adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>> wrote: Robot can point to HEAT’s VM IP, whereas robot point to the service directly.. Not clear. In the HEAT setup, robot points to the SDC VM IP for that resources, whereas for the OOM setup, we point directly to the frontend or backend service.
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
