Re: [onap-discuss] SDC deployment on heat and OOM

[PLATANIA, MARCO (MARCO)]

Michael,

The issue with the Heat deployment is that connection to Gerrit timed out, so 
the SDC repo hasn’t been cloned:

fatal: unable to access 'http://gerrit.onap.org/r/sdc.git/': Failed to connect 
to gerrit.onap.org port 80: Connection timed out

As a consequence, sdc_vm_init.sh couldn’t find deploy.sh. I just cloned it 
manually and redeployed SDC. Yesterday, we experienced network instability. 
Consider that the clone operation this morning succeeded after a few failed 
attempts. I’m not sure whether the network has healed completely.

Marco

From: "LANDO, MICHAEL" 
Date: Thursday, May 3, 2018 at 5:55 AM
To: 'Yunxia Chen' , Gary Wu , 
"OBRIEN, FRANK MICHAEL" , "PLATANIA, MARCO (MARCO)" 
, Mike Elliott , 'Roger 
Maitland' 
Cc: BRIAN FREEMAN , "NACHMIAS, LIOR" , 
"'onap-discuss@lists.onap.org'" , "RATZ, YAKI" 
, "FUSS, ARELI" 
Subject: SDC deployment on heat and OOM

Hi,

After Gary explained to me how I can login into the external labs I started 
checking our deployment there.

Heat:

It looks like on the last heat deployment execution 
https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-heat-deploy/259/consoleFull

The SDC was not even started I logged into the VM that was assigned to SDC 
10.12.5.83 and our docker startup script was not even executed as far as I can 
see since :
root@onap-sdc:~# docker ps -a
CONTAINER IDIMAGE   COMMAND CREATED 
STATUS  PORTS   NAMES
root@onap-sdc:~#

as a result our health check is shown as failing which is not the case.
What is the cause? What failed?

OOM:

https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/339/console

from what I see the job and the health check was completed at 8:30 utc when I 
logged into the Machin I can see that it took SDC started successful with no 
intervention (Thank you OOM team) and that last docker came up at 09:14:09 utc.
As a result our health check is marked as failed which is not the case since I 
was able to log into the sdc fe docker and validate the health check is passing.

How can this be addressed can we prolong the job execution or the number of 
retries for the health check? I am more than sure the SDC is not the only 
application that fails because of this.

Side note:
I tried executing the health check from out side the docker but probably I am 
missing something in connection to the K8 networking since I was unable to 
connect.
I tried curl http://sdc-fe.onap:8181/sdc1/rest/healthCheck as the health check 
does.













BR,

[ichael Lando]

AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com

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

[onap-discuss] SDC deployment on heat and OOM

[Lando,Michael]

Hi,

After Gary explained to me how I can login into the external labs I started 
checking our deployment there.

Heat:

It looks like on the last heat deployment execution 
https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-heat-deploy/259/consoleFull

The SDC was not even started I logged into the VM that was assigned to SDC 
10.12.5.83 and our docker startup script was not even executed as far as I can 
see since :
root@onap-sdc:~# docker ps -a
CONTAINER IDIMAGE   COMMAND CREATED 
STATUS  PORTS   NAMES
root@onap-sdc:~#

as a result our health check is shown as failing which is not the case.
What is the cause? What failed?

OOM:

https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/339/console

from what I see the job and the health check was completed at 8:30 utc when I 
logged into the Machin I can see that it took SDC started successful with no 
intervention (Thank you OOM team) and that last docker came up at 09:14:09 utc.
As a result our health check is marked as failed which is not the case since I 
was able to log into the sdc fe docker and validate the health check is passing.

How can this be addressed can we prolong the job execution or the number of 
retries for the health check? I am more than sure the SDC is not the only 
application that fails because of this.

Side note:
I tried executing the health check from out side the docker but probably I am 
missing something in connection to the K8 networking since I was unable to 
connect.
I tried curl http://sdc-fe.onap:8181/sdc1/rest/healthCheck as the health check 
does.













BR,

[Michael Lando]

AT Network Application Development * NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
***
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com

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