Re: [onap-discuss] OOM kubernetes values.yaml files

2018-03-17 Thread Ahmad, Munir
Hi

When you delete a pod if the image pull policy is set to Always as you have 
observed. Then the latest image with that name and tag will be pulled.

Thanks
Munir
P.S. If you prefer you can change the image pull policty to IfNotPresent then 
deploy.


From:  on behalf of 
"abdelmuhaimen.sea...@orange.com" 
Date: Friday, March 16, 2018 at 3:35 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] OOM kubernetes values.yaml files

Hi,

In oom/kubernetes/xx/values.yaml, why do we need this line in the values.yaml 
file

PullPolicy: Always

instead of

PullPolicy: IfNotPresent

The Always option for some reason does not use the images that were pre-pulled, 
and gives pull backoff messages, and I have to repull the images manually.

And anyway, helm/kubernetes cannot pull directly the image when creating the 
pods, is my understanding correct ?

Thanks.

A. Seaudi

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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


Re: [onap-discuss] SDC distribution POL5000 error in K8S, "U-EB cluster is not available"

2018-03-17 Thread Ahmad, Munir
Hi,

It may have to do with the order your sdc containers started. Try deleting your 
pods in the following order

sdc-es
sdc-cs
sdc-kb
sdc-be
sdc-fe


Thanks
Munir
From:  on behalf of 
"abdelmuhaimen.sea...@orange.com" 
Date: Saturday, March 17, 2018 at 5:31 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] SDC distribution POL5000 error in K8S, "U-EB cluster is 
not available"

Hi,

I have a minimal ONAP Depoloyment on K8S running.

If I try to distribute a new service in SDC, I get Error code POL5000, status 
code: 500, Internal Server Error. Please try again later.

Regarding the output below, what does UEB Cluster not available mean ?

cloud@olc-k8s:~$ curl http://127.0.0.1:30205/sdc2/rest/healthCheck
{
  "sdcVersion": "1.1.0",
  "siteMode": "unknown",
  "componentsInfo": [
{
  "healthCheckComponent": "BE",
  "healthCheckStatus": "UP",
  "version": "1.1.0",
  "description": "OK"
},
{
  "healthCheckComponent": "TITAN",
  "healthCheckStatus": "UP",
  "description": "OK"
},
{
  "healthCheckComponent": "DE",
  "healthCheckStatus": "DOWN",
  "description": "U-EB cluster is not available"
},
{
  "healthCheckComponent": "CASSANDRA",
  "healthCheckStatus": "UP",
  "description": "OK"
},
{
  "healthCheckComponent": "ON_BOARDING",
  "healthCheckStatus": "UP",
  "version": "1.1.0",
  "description": "OK",
  "componentsInfo": [
{
  "healthCheckComponent": "ZU",
  "healthCheckStatus": "UP",
  "version": "0.2.0",
  "description": "OK"
},
{
  "healthCheckComponent": "BE",
  "healthCheckStatus": "UP",
  "version": "1.1.0",
  "description": "OK"
},
{
  "healthCheckComponent": "CAS",
  "healthCheckStatus": "UP",
  "version": "2.1.17",
  "description": "OK"
}
  ]
}
  ]
}
cloud@olc-k8s:~$ curl -X GET   
http://localhost:30205/sdc/v1/distributionUebCluster   -H 'Accept: 
application/json'   -H 'Content-Type: application/json'   -H 
'X-ECOMP-InstanceID: mso'   -H 'authorization: Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU='
{"uebServerList":["X.Y.Z.90","X.Y.X.90"]}  < i hide the ip address, 
both are the same ip
cloud@olc-k8s:~$
cloud@olc-k8s:~$

root@olc-k8s:~/oom/kubernetes/oneclick# watch 'free -h;echo 
===; df -h /dev/vda1; df -h /dev/vdb1; echo 
===; kubectl get pods --all-namespaces'
Every 2.0s: free -h;echo ===; df -h /dev/vda1; df -h /dev/vdb1; 
echo ===; kubectl get pods --all-namespaces 
 Sat Mar 17 09:30:32 2018

  totalusedfree  shared  buff/cache   available
Mem:61G 41G1.8G 60M 18G 19G
Swap:0B  0B  0B
===
Filesystem  Size  Used Avail Use% Mounted on
/dev/vda149G  7.4G   41G  16% /
Filesystem  Size  Used Avail Use% Mounted on
/dev/vdb1   197G   29G  159G  16% /var/lib/docker
===
NAMESPACE NAME   READY STATUS   
 RESTARTS   AGE
kube-system   heapster-4285517626-1q6rj  1/1   Running  
 0  23h
kube-system   kube-dns-638003847-xb3mc   3/3   Running  
 0  23h
kube-system   kubernetes-dashboard-716739405-s3tr3   1/1   Running  
 0  23h
kube-system   monitoring-grafana-2360823841-15ppr1/1   Running  
 0  23h
kube-system   monitoring-influxdb-2323019309-3kvn2   1/1   Running  
 0  23h
kube-system   tiller-deploy-737598192-4h8bj  1/1   Running  
 0  23h
onap-aai  aai-resources-2398553481-pfnt0 2/2   Running  
 0  18h
onap-aai  aai-service-749944520-cx9w51/1   Running  
 0  18h
onap-aai  aai-traversal-2677319478-lccqd 2/2   Running  
 0  18h
onap-aai  data-router-3700447603-3ftp1   1/1   Running  
 0  18h
onap-aai  elasticsearch-622738319-zpwx2  1/1   Running  
 0  18h
onap-aai  hbase-3471984843-zwxpj 1/1   Running  
 0  18h
onap-aai  model-loader-service-911950978-5l2bk   2/2   Running  
 0  18h
onap-aai  search-data-service-2471976899-rg1g9   2/2   Running  
 0  18h
onap-aai  sparky-be-1779663793-td3m8 2/2   Running  
 0  18h
onap-message-router   dmaap-3126594942-r3jg3 1/1   Running  
 0  18h
onap-message-router   global-kafka-3848542622-14rbs  1/1

Re: [onap-discuss] Regarding Tosca parsing of Overlay/Underlay templates for VoLTE use case

2018-03-17 Thread Singh Kalra, Mandeep
Thanks a lot Chuanyu and Ramu .

@Chunuyu :: I can see that there are some updates done to SO bpmn scripts in 
master branch for VoLTE case, is this change of parsing the overlay/underlay 
templates part already there ?

How about the modelling in SDC, will that also be changed ? PNFs etc for 
underlay ?

@Ramu :: Is there any change in SDNC’s directed graphs for this case ?


Regards
Mandeep



From: Chenchuanyu [mailto:chenchua...@huawei.com]
Sent: Wednesday, February 28, 2018 2:38 PM
To: Singh Kalra, Mandeep ; Ramu n 
; onap-discuss@lists.onap.org
Subject: [External] 答复: [onap-discuss] Regarding Tosca parsing of 
Overlay/Underlay templates for VoLTE use case

Hi, Mandeep,
  SO will do this(but in R1, this have not been implemented, all parameters 
published as user inputs).
  In R2, SO will merge both user filled parameters and template assigned 
parameters(which set in design time), and then sent all of them to SDNC.
Thanks,
Chuanyu Chen.

发件人: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] 代表 Singh Kalra, Mandeep
发送时间: 2018年2月28日 17:02
收件人: Ramu n; onap-discuss@lists.onap.org
主题: Re: [onap-discuss] Regarding Tosca parsing of Overlay/Underlay templates 
for VoLTE use case

Thanks Ramu.

I guess UUI will only take the input parameters from the users.
In case the template also holds some values, who will be parsing/providing that 
?

And can you please share the AAI - SDNC configurations for the VoLTE use case. 
Does SDNC itself holds some data apart from AAI ?


Regards
Mandeep

From: Ramu n [mailto:ram...@huawei.com]
Sent: Wednesday, February 28, 2018 2:06 PM
To: Singh Kalra, Mandeep 
>; 
onap-discuss@lists.onap.org
Subject: [External] RE: [onap-discuss] Regarding Tosca parsing of 
Overlay/Underlay templates for VoLTE use case

Hi Mandeep,

For VoLTE use case, Usecase UI will prompt for tosca inputs of Underlay/Overlay 
templates..
UUI will call SO’s e2eService API with these parameters, then SO will call 
SDNC’s network-topology-operation RPCs for underlay/overlay resource creation.

Thanks,
Ramu N

***
 This e-mail and attachments contain confidential information from 
HUAWEI, which is intended only for the person or entity whose address is listed 
above. Any use of the information contained herein in any way (including, but 
not limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient's) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Singh Kalra, Mandeep
Sent: Wednesday, February 28, 2018 1:26 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Regarding Tosca parsing of Overlay/Underlay templates 
for VoLTE use case

Hi,

  I can see from the SDNC network-topology-operation RPC that it requires 
some tosca inputs.
  I need to know which layer parses the tosca template declared in SDC and 
fetch parameters ?



Regards
Mandeep



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy.
__

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


Re: [onap-discuss] SDC distribution POL5000 error in K8S, "U-EB cluster is not available"

2018-03-17 Thread abdelmuhaimen.seaudi
Also, I see the following in SDC logs, I noticed that it's trying to use the 
public IP with port 3904, although this port is not reachable from the public 
ip.

How can i correct this ?


Line 43120: 2018-03-17T10:01:08.744Z[pool-63-thread-1]  WARN
c.att.nsa.apiClient.http.HttpClient Error executing HTTP request. 
Connect to 84.39.48.90:3904 [/84.39.48.90] failed: Connection refused 
(Connection refused); blacklisting for 2 minutes
Line 43121: 2018-03-17T10:01:08.744Z[pool-63-thread-1]  ERROR   
o.o.s.c.config.EcompErrorLogUtilalarmSeverity=MAJOR ETYPE = 
"CONNECTION_PROBLEM" ENAME = "BeUebConnectionError" ECODE = "ASDC210E" ECONTEXT 
= "getTopics" EDESC = "Connection problem towards U-EB server. Reason: 500"
Line 43121: 2018-03-17T10:01:08.744Z[pool-63-thread-1]  ERROR   
o.o.s.c.config.EcompErrorLogUtilalarmSeverity=MAJOR ETYPE = 
"CONNECTION_PROBLEM" ENAME = "BeUebConnectionError" ECODE = "ASDC210E" ECONTEXT 
= "getTopics" EDESC = "Connection problem towards U-EB server. Reason: 500"
Line 43121: 2018-03-17T10:01:08.744Z[pool-63-thread-1]  ERROR   
o.o.s.c.config.EcompErrorLogUtilalarmSeverity=MAJOR ETYPE = 
"CONNECTION_PROBLEM" ENAME = "BeUebConnectionError" ECODE = "ASDC210E" ECONTEXT 
= "getTopics" EDESC = "Connection problem towards U-EB server. Reason: 500"
Line 43122: 2018-03-17T10:01:08.744Z[pool-63-thread-1]  ERROR   
o.o.s.c.config.EcompErrorLogUtilalarmSeverity=MAJOR ETYPE = 
"SYSTEM_ERROR" ENAME = "BeUebSystemError" ECODE = "ASDC502E" ECONTEXT = 
"initDistributionEngine" EDESC = "Error occured during access to U-EB Server. 
Operation: try retrieve list of topics from U-EB server"
Line 43122: 2018-03-17T10:01:08.744Z[pool-63-thread-1]  ERROR   
o.o.s.c.config.EcompErrorLogUtilalarmSeverity=MAJOR ETYPE = 
"SYSTEM_ERROR" ENAME = "BeUebSystemError" ECODE = "ASDC502E" ECONTEXT = 
"initDistributionEngine" EDESC = "Error occured during access to U-EB Server. 
Operation: try retrieve list of topics from U-EB server"
Line 43122: 2018-03-17T10:01:08.744Z[pool-63-thread-1]  ERROR   
o.o.s.c.config.EcompErrorLogUtilalarmSeverity=MAJOR ETYPE = 
"SYSTEM_ERROR" ENAME = "BeUebSystemError" ECODE = "ASDC502E" ECONTEXT = 
"initDistributionEngine" EDESC = "Error occured during access to U-EB Server. 
Operation: try retrieve list of topics from U-EB server"
Line 43122: 2018-03-17T10:01:08.744Z[pool-63-thread-1]  ERROR   
o.o.s.c.config.EcompErrorLogUtilalarmSeverity=MAJOR ETYPE = 
"SYSTEM_ERROR" ENAME = "BeUebSystemError" ECODE = "ASDC502E" ECONTEXT = 
"initDistributionEngine" EDESC = "Error occured during access to U-EB Server. 
Operation: try retrieve list of topics from U-EB server"
Line 43122: 2018-03-17T10:01:08.744Z[pool-63-thread-1]  ERROR   
o.o.s.c.config.EcompErrorLogUtilalarmSeverity=MAJOR ETYPE = 
"SYSTEM_ERROR" ENAME = "BeUebSystemError" ECODE = "ASDC502E" ECONTEXT = 
"initDistributionEngine" EDESC = "Error occured during access to U-EB Server. 
Operation: try retrieve list of topics from U-EB server"



From: onap-discuss-boun...@lists.onap.org [onap-discuss-boun...@lists.onap.org] 
on behalf of abdelmuhaimen.sea...@orange.com [abdelmuhaimen.sea...@orange.com]
Sent: Saturday, March 17, 2018 11:31 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] SDC distribution POL5000 error in K8S, "U-EB cluster is 
not available"

Hi,

I have a minimal ONAP Depoloyment on K8S running.

If I try to distribute a new service in SDC, I get Error code POL5000, status 
code: 500, Internal Server Error. Please try again later.

Regarding the output below, what does UEB Cluster not available mean ?

cloud@olc-k8s:~$ curl http://127.0.0.1:30205/sdc2/rest/healthCheck
{
  "sdcVersion": "1.1.0",
  "siteMode": "unknown",
  "componentsInfo": [
{
  "healthCheckComponent": "BE",
  "healthCheckStatus": "UP",
  "version": "1.1.0",
  "description": "OK"
},
{
  "healthCheckComponent": "TITAN",
  "healthCheckStatus": "UP",
  "description": "OK"
},
{
  "healthCheckComponent": "DE",
  "healthCheckStatus": "DOWN",
  "description": "U-EB cluster is not available"
},
{
  "healthCheckComponent": "CASSANDRA",
  "healthCheckStatus": "UP",
  "description": "OK"
},
{
  "healthCheckComponent": "ON_BOARDING",
  "healthCheckStatus": "UP",
  "version": "1.1.0",
  "description": "OK",
  "componentsInfo": [
{
  "healthCheckComponent": "ZU",
  "healthCheckStatus": "UP",
  "version": "0.2.0",
  "description": "OK"
},
{
  "healthCheckComponent": "BE",
  "healthCheckStatus": "UP",
  "version": "1.1.0",
  "description": "OK"
},
{
  "healthCheckComponent": "CAS",