Re: [onap-discuss] OOM Robot Distribute

sday, January 11, 2018 4:29 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 > > It’s the same IP address in the HEAT deployment

Re: [onap-discuss] OOM Robot Distribute

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:ade

Re: [onap-discuss] OOM Robot Distribute

_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

Re: [onap-discuss] OOM Robot Distribute

;bf1...@att.com> Cc: 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

Re: [onap-discuss] OOM Robot Distribute

> On Jan 11, 2018, at 4:00 PM, Alexis de Talhouët > 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

Re: [onap-discuss] OOM Robot Distribute

Brian, For some reason, we had to fork asdc_interface.robot script, that’s why it’s not up-to-date, please create a ticket for this and assign it to me. The reasons are hostname resolution are different from HEAT and OOM. Robot can point to HEAT’s VM IP, whereas robot point to the service

[onap-discuss] OOM Robot Distribute

Alexis, Michael, I was using robot ete-k8s.sh from amsterdam release and the version of asdc_interface.robot in dockerdata-nfs was out of date. I cant seem to find where it got loaded from since the asdc_interface.robot wasn't compatible with the robot testsuite (the return parameter list from