)
Thank you
/michael
From: Bainbridge, David [mailto:dbain...@ciena.com]
Sent: Wednesday, January 3, 2018 19:25
To: Michael O'Brien
Cc: onap-discuss
Subject: Re: [onap-discuss] [**EXTERNAL**] Re: [integration][oom] OOM readiness
for Beijing release
Fwiw, the logs in the elastic POD show:
:onap-discuss-boun...@lists.onap.org] On Behalf Of Bainbridge, David
Sent: Wednesday, January 3, 2018 14:58
To: Alexis de Talhouët ; BRIAN D FREEMAN
Cc: GILBERT, MAZIN E ; onap-discuss
Subject: Re: [onap-discuss] [**EXTERNAL**] Re: [integration][oom] OOM readiness
for Beijing release
Just attempti
onap-discuss
Subject: Re: [onap-discuss] [**EXTERNAL**] Re: [integration][oom] OOM readiness
for Beijing release
David,
Hi, not good, will try to help you out.
The CD hourly build is running against Beijing/master, I also did a run on a
server for the amsterdam branch – not seeing these 2
, January 3, 2018 14:58
To: Alexis de Talhouët ; BRIAN D FREEMAN
Cc: GILBERT, MAZIN E ; onap-discuss
Subject: Re: [onap-discuss] [**EXTERNAL**] Re: [integration][oom] OOM readiness
for Beijing release
Just attempting to deploy via OOM. Left with 2 pods not starting correctly:
NAMESPACE
Btw, I consider it a bit of a bug that I have to add /etc/hosts entries for
portal.api.simpledemo.onap.org
sdc.api.simpledemo.onap.org
it seems like this implies there are some embedded (hard corded) host names
that are not resolving correctly when I run the UI remotely.
From: on behalf of Ale
Just attempting to deploy via OOM. Left with 2 pods not starting correctly:
NAMESPACE NAME READY
STATUS RESTARTS AGE
onap-log elasticsearch-6df4f65775-w48c90/1
CrashLoopBackOff 11
