Re: [onap-discuss] [OOM] inter-module instantiate dependencies

2018-01-24 Thread Alexis de Talhouët 
Ticket for the robot issue: https://jira.onap.org/browse/OOM-618

But I think it should be a Robot ticket.

> On Jan 24, 2018, at 2:20 PM, FREEMAN, BRIAN D <bf1...@att.com> wrote:
> 
> On the chrome driver.
>  
> I think I worked around it by installing an alternate chrome version in the 
> container.
> Using part of a fix that Gary has in integration – basically using the 2.32 
> version instead of the version in the container.
>  
> Brian
>  
>  
> # install chrome driver
> if [ ! -x ${ROBOT_VENV}/bin/chromedriver ]; then
> pushd ${ROBOT_VENV}/bin
> wget -N 
> http://chromedriver.storage.googleapis.com/2.32/chromedriver_linux64.zip 
> <http://chromedriver.storage.googleapis.com/2.32/chromedriver_linux64.zip>
> unzip chromedriver_linux64.zip
> chmod +x chromedriver
> popd
> fi
>  
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
> Sent: Wednesday, January 24, 2018 2:10 PM
> To: FREEMAN, BRIAN D <bf1...@att.com>
> Cc: onap-discuss <onap-discuss@lists.onap.org>
> Subject: Re: [onap-discuss] [OOM] inter-module instantiate dependencies
>  
> Thank Brian for trying OOM and helping improving it! I guess this is on 
> Amsterdam?
> I opened bugs to track this, see inline. for questions.
>  
> Thanks
> Alexis
> 
> 
> On Jan 24, 2018, at 1:50 PM, FREEMAN, BRIAN D <bf1...@att.com 
> <mailto:bf1...@att.com>> wrote:
>  
> Started to confirm functionality with OOM Amsterdam.
>  
> I think these are already being tracked but wanted to confirm with OOM team.
>  
> Model distribution from SDC fails to SO and SDNC on a fresh install.
> SO’s ASDC Adapter tries to communicate with SDC-BE before its up.
>i.  Delete 
> of the SO pod and K8 automated restart clears the problem – redistribute 
> works so it seems like a timing problem that SO should not be started till 
> SDC-BEis up.
>  
> AdT: https://jira.onap.org/browse/OOM-616 
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_OOM-2D616=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=0q6hZVTaqZ7d33E8pEaugboYHfjCjI_0rYPNo91TCCU=ltLOv2wp22VQOG-weLJjQaTkLwj7PIWg9r1vpdXkuTc=>
> 
> 
> SDNC ueb-listener tries to communicate with SDC-BE before its up.
>i.  Delete 
> of the ueb-listener pod and K8 automated restart clears the problem – 
> redistribute works so it seems like a timing problem that ueb-listener/SDNC 
> should not be started till SDC is up.
>  
> AdT: https://jira.onap.org/browse/OOM-617 
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_OOM-2D617=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=0q6hZVTaqZ7d33E8pEaugboYHfjCjI_0rYPNo91TCCU=oAqDwtrHbRogu8ZA7K1KcOSZkmdzDX9Y-4fs0x0OdX0=>
> 
> 
> Agree there should be automated retry in listeners on boot but in Amsterdam 
> that does not seem to be there.
>  
> AdT: It’s ok, we can have deterministic startup with K8S. We can check for a 
> given port to be open.
> 
> 
>  
> AAF does not come up and delays the install by 10+ minutes
> I assume we can take AAF out of the config and not try to start it.
> I would think for Amsterdam that might need to be the default
>  
> AdT: As far as I know, AAF never worked for OOM on Amsterdam. Always failed 
> with `Error: Could not find or load main class 
> org.onap.aaf.authz.service.AuthAPI`
>  
> Robot had a problem with the chrome driver when trying to instantiate (and 
> probably other flows) – is there a fix ?
> WebDriverException: Message: unknown error: an X display is required for 
> keycode conversions, consider using Xvfb (Session info: headless 
> chrome=63.0.3239.132) (Driver info: chromedriver=2.29.461571
>  
>  
> AdT: Is this specific to OOM? 
> 
> 
>  
>  
> Brian
>  
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>
> https://lists.onap.org/mailman/listinfo/onap-discuss 
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=0q6hZVTaqZ7d33E8pEaugboYHfjCjI_0rYPNo91TCCU=rHqg85CQ5FyJN75nqHsgWBLC6vcn_orisGfehj8iHJs=>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [OOM] inter-module instantiate dependencies

2018-01-24 Thread FREEMAN, BRIAN D 
On the chrome driver.

I think I worked around it by installing an alternate chrome version in the 
container.
Using part of a fix that Gary has in integration – basically using the 2.32 
version instead of the version in the container.

Brian


# install chrome driver
if [ ! -x ${ROBOT_VENV}/bin/chromedriver ]; then
pushd ${ROBOT_VENV}/bin
wget -N 
http://chromedriver.storage.googleapis.com/2.32/chromedriver_linux64.zip
unzip chromedriver_linux64.zip
chmod +x chromedriver
popd
fi

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Wednesday, January 24, 2018 2:10 PM
To: FREEMAN, BRIAN D <bf1...@att.com>
Cc: onap-discuss <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [OOM] inter-module instantiate dependencies

Thank Brian for trying OOM and helping improving it! I guess this is on 
Amsterdam?
I opened bugs to track this, see inline. for questions.

Thanks
Alexis


On Jan 24, 2018, at 1:50 PM, FREEMAN, BRIAN D 
<bf1...@att.com<mailto:bf1...@att.com>> wrote:

Started to confirm functionality with OOM Amsterdam.

I think these are already being tracked but wanted to confirm with OOM team.


  1.  Model distribution from SDC fails to SO and SDNC on a fresh install.

 *   SO’s ASDC Adapter tries to communicate with SDC-BE before its up.
   i.  Delete 
of the SO pod and K8 automated restart clears the problem – redistribute works 
so it seems like a timing problem that SO should not be started till SDC-BEis 
up.

AdT: 
https://jira.onap.org/browse/OOM-616<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_OOM-2D616=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=0q6hZVTaqZ7d33E8pEaugboYHfjCjI_0rYPNo91TCCU=ltLOv2wp22VQOG-weLJjQaTkLwj7PIWg9r1vpdXkuTc=>



 *   SDNC ueb-listener tries to communicate with SDC-BE before its up.
   i.  Delete 
of the ueb-listener pod and K8 automated restart clears the problem – 
redistribute works so it seems like a timing problem that ueb-listener/SDNC 
should not be started till SDC is up.

AdT: 
https://jira.onap.org/browse/OOM-617<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_OOM-2D617=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=0q6hZVTaqZ7d33E8pEaugboYHfjCjI_0rYPNo91TCCU=oAqDwtrHbRogu8ZA7K1KcOSZkmdzDX9Y-4fs0x0OdX0=>



 *   Agree there should be automated retry in listeners on boot but in 
Amsterdam that does not seem to be there.

AdT: It’s ok, we can have deterministic startup with K8S. We can check for a 
given port to be open.



 *

  1.  AAF does not come up and delays the install by 10+ minutes

 *   I assume we can take AAF out of the config and not try to start it.
 *   I would think for Amsterdam that might need to be the default

AdT: As far as I know, AAF never worked for OOM on Amsterdam. Always failed 
with `Error: Could not find or load main class 
org.onap.aaf.authz.service.AuthAPI`


  1.  Robot had a problem with the chrome driver when trying to instantiate 
(and probably other flows) – is there a fix ?

 *   WebDriverException: Message: unknown error: an X display is required 
for keycode conversions, consider using Xvfb (Session info: headless 
chrome=63.0.3239.132) (Driver info: chromedriver=2.29.461571


AdT: Is this specific to OOM?




Brian

___
onap-discuss mailing list
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=0q6hZVTaqZ7d33E8pEaugboYHfjCjI_0rYPNo91TCCU=rHqg85CQ5FyJN75nqHsgWBLC6vcn_orisGfehj8iHJs=>

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [OOM] inter-module instantiate dependencies

2018-01-24 Thread Alexis de Talhouët 
Thank Brian for trying OOM and helping improving it! I guess this is on 
Amsterdam?
I opened bugs to track this, see inline. for questions.

Thanks
Alexis

> On Jan 24, 2018, at 1:50 PM, FREEMAN, BRIAN D  wrote:
> 
> Started to confirm functionality with OOM Amsterdam.
>  
> I think these are already being tracked but wanted to confirm with OOM team.
>  
> Model distribution from SDC fails to SO and SDNC on a fresh install.
> SO’s ASDC Adapter tries to communicate with SDC-BE before its up.
>i.  Delete 
> of the SO pod and K8 automated restart clears the problem – redistribute 
> works so it seems like a timing problem that SO should not be started till 
> SDC-BEis up.

AdT: https://jira.onap.org/browse/OOM-616

> SDNC ueb-listener tries to communicate with SDC-BE before its up.
>i.  Delete 
> of the ueb-listener pod and K8 automated restart clears the problem – 
> redistribute works so it seems like a timing problem that ueb-listener/SDNC 
> should not be started till SDC is up.

AdT: https://jira.onap.org/browse/OOM-617

> Agree there should be automated retry in listeners on boot but in Amsterdam 
> that does not seem to be there.

AdT: It’s ok, we can have deterministic startup with K8S. We can check for a 
given port to be open.

> AAF does not come up and delays the install by 10+ minutes
> I assume we can take AAF out of the config and not try to start it.
> I would think for Amsterdam that might need to be the default

AdT: As far as I know, AAF never worked for OOM on Amsterdam. Always failed 
with `Error: Could not find or load main class 
org.onap.aaf.authz.service.AuthAPI`

> Robot had a problem with the chrome driver when trying to instantiate (and 
> probably other flows) – is there a fix ?
> WebDriverException: Message: unknown error: an X display is required for 
> keycode conversions, consider using Xvfb (Session info: headless 
> chrome=63.0.3239.132) (Driver info: chromedriver=2.29.461571
>  

AdT: Is this specific to OOM? 

>  
>  
> Brian
>  
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org 
> https://lists.onap.org/mailman/listinfo/onap-discuss 
> 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [OOM] inter-module instantiate dependencies

2018-01-24 Thread FREEMAN, BRIAN D 
Started to confirm functionality with OOM Amsterdam.

I think these are already being tracked but wanted to confirm with OOM team.


  1.  Model distribution from SDC fails to SO and SDNC on a fresh install.
 *   SO's ASDC Adapter tries to communicate with SDC-BE before its up.

   i.  Delete 
of the SO pod and K8 automated restart clears the problem - redistribute works 
so it seems like a timing problem that SO should not be started till SDC-BEis 
up.

 *   SDNC ueb-listener tries to communicate with SDC-BE before its up.

   i.  Delete 
of the ueb-listener pod and K8 automated restart clears the problem - 
redistribute works so it seems like a timing problem that ueb-listener/SDNC 
should not be started till SDC is up.

 *   Agree there should be automated retry in listeners on boot but in 
Amsterdam that does not seem to be there.
  1.  AAF does not come up and delays the install by 10+ minutes
 *   I assume we can take AAF out of the config and not try to start it.
 *   I would think for Amsterdam that might need to be the default
  2.  Robot had a problem with the chrome driver when trying to instantiate 
(and probably other flows) - is there a fix ?
 *   WebDriverException: Message: unknown error: an X display is required 
for keycode conversions, consider using Xvfb (Session info: headless 
chrome=63.0.3239.132) (Driver info: chromedriver=2.29.461571



Brian

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss