Date   

R: [onap-discuss] dmaap-message-router NodePort not recheable

Calamita Agostino
 

I didn’t find healthmr test but only health.

(

./ete-k8s.sh onap

Usage: ete-k8s.sh [namespace] [ health | healthdist | distribute | instantiate | instantiateVFWCL | instantiateDemoVFWCL |  | portal ] )

 

The command ./ete-k8s.sh onap health reports the list below (  Basic DMAAP Message Router Health Check = PASS )                            

In my environment there are some PODs not in Running state:

 

dev-aai-aai-data-router-5d55646cdc-cc62v                      1/2       CrashLoopBackOff   1084       4d        10.42.79.203    onapkm3   <none>

dev-appc-appc-ansible-server-76fcf9454d-8km9d                 0/1       CrashLoopBackOff   1656       6d        10.42.212.202   onapkm0   <none>

dev-oof-oof-has-api-585497f5-ktjsv                            0/1       Init:0/3           1085       8d        10.42.86.82     onapkm0   <none>

dev-oof-oof-has-controller-9469b9ff8-td4k9                    0/1       Init:1/3           945        8d        10.42.5.110     onapkm2   <none>

dev-oof-oof-has-data-d559897dc-4lmkt                          0/1       Init:1/4           1091       8d        10.42.199.220   onapkm3   <none>

dev-oof-oof-has-healthcheck-jq9xq                             0/1       Init:0/1           1092       8d        10.42.242.145   onapkm3   <none>

dev-oof-oof-has-reservation-868c7c88ff-pv79n                  0/1       Init:1/4           1081       8d        10.42.176.61    onapkm1   <none>

dev-oof-oof-has-solver-6f8bc6fdf4-tw4cj                       0/1       Init:1/4           1084       8d        10.42.29.154    onapkm0   <none>

dev-sdnc-sdnc-ansible-server-7c76f965c6-hqtzl                 0/1       CrashLoopBackOff   1844       8d        10.42.202.36    onapkm3   <none>

dev-sdnc-sdnc-ueb-listener-6d74459c6-tdqhc                    0/1       CrashLoopBackOff   542        1d        10.42.219.51    onapkm2   <none>

 

and multicloud is not deployed.

 

==============================================================================

Testsuites

==============================================================================

Testsuites.Health-Check :: Testing ecomp components are available via calls.

==============================================================================

Basic A&AI Health Check                                               | PASS |

------------------------------------------------------------------------------

Basic AAF Health Check                                                | PASS |

------------------------------------------------------------------------------

Basic AAF SMS Health Check                                            | PASS |

------------------------------------------------------------------------------

Basic APPC Health Check                                               | PASS |

------------------------------------------------------------------------------

Basic CLI Health Check                                                | PASS |

------------------------------------------------------------------------------

Basic CLAMP Health Check                                              | PASS |

------------------------------------------------------------------------------

Basic DCAE Health Check                                               [ WARN ] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f03e8102250>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /healthcheck

[ WARN ] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f03e817a8d0>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /healthcheck

[ WARN ] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f03e817a850>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /healthcheck

| FAIL |

ConnectionError: HTTPConnectionPool(host='dcae-healthcheck.onap', port=80): Max retries exceeded with url: /healthcheck (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f03e817a5d0>: Failed to establish a new connection: [Errno -2] Name or service not known',))

------------------------------------------------------------------------------

Basic DMAAP Data Router Health Check                                  | PASS |

------------------------------------------------------------------------------

Basic DMAAP Message Router Health Check                               | PASS |

------------------------------------------------------------------------------

Basic External API NBI Health Check                                   [ WARN ] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f03e80d6c50>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /nbi/api/v3/status

[ WARN ] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f03e80c4e10>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /nbi/api/v3/status

[ WARN ] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f03e8199f50>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /nbi/api/v3/status

| FAIL |

ConnectionError: HTTPConnectionPool(host='nbi.onap', port=8080): Max retries exceeded with url: /nbi/api/v3/status (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f03e80e5410>: Failed to establish a new connection: [Errno -2] Name or service not known',))

------------------------------------------------------------------------------

Basic Log Elasticsearch Health Check                                  | PASS |

------------------------------------------------------------------------------

Basic Log Kibana Health Check                                         | PASS |

------------------------------------------------------------------------------

Basic Log Logstash Health Check                                       | PASS |

------------------------------------------------------------------------------

Basic Microservice Bus Health Check                                   | PASS |

------------------------------------------------------------------------------

Basic Multicloud API Health Check                                     | FAIL |

502 != 200

------------------------------------------------------------------------------

Basic Multicloud-ocata API Health Check                               | FAIL |

502 != 200

------------------------------------------------------------------------------

Basic Multicloud-pike API Health Check                                | FAIL |

502 != 200

------------------------------------------------------------------------------

Basic Multicloud-titanium_cloud API Health Check                      | FAIL |

502 != 200

------------------------------------------------------------------------------

Basic Multicloud-vio API Health Check                                 | FAIL |

502 != 200

------------------------------------------------------------------------------

Basic OOF-Homing Health Check                                         | FAIL |

Test timeout 10 seconds exceeded.

------------------------------------------------------------------------------

Basic OOF-SNIRO Health Check                                          | PASS |

------------------------------------------------------------------------------

Basic OOF-CMSO Health Check                                           | PASS |

------------------------------------------------------------------------------

Basic Policy Health Check                                             | PASS |

------------------------------------------------------------------------------

Basic Pomba AAI-context-builder Health Check                          | PASS |

------------------------------------------------------------------------------

Basic Pomba SDC-context-builder Health Check                          | PASS |

------------------------------------------------------------------------------

Basic Pomba Network-discovery-context-builder Health Check            | PASS |

------------------------------------------------------------------------------

Basic Portal Health Check                                             | PASS |

------------------------------------------------------------------------------

Basic SDC Health Check                                                (DMaaP:None)| PASS |

------------------------------------------------------------------------------

Basic SDNC Health Check                                               | PASS |

------------------------------------------------------------------------------

Basic SO Health Check                                                 | PASS |

------------------------------------------------------------------------------

Basic UseCaseUI API Health Check                                      | PASS |

------------------------------------------------------------------------------

Basic VFC catalog API Health Check                                    | PASS |

------------------------------------------------------------------------------

Basic VFC emsdriver API Health Check                                  | PASS |

------------------------------------------------------------------------------

Basic VFC gvnfmdriver API Health Check                                | PASS |

------------------------------------------------------------------------------

Basic VFC huaweivnfmdriver API Health Check                           | PASS |

------------------------------------------------------------------------------

Basic VFC jujuvnfmdriver API Health Check                             | PASS |

------------------------------------------------------------------------------

Basic VFC multivimproxy API Health Check                              | PASS |

------------------------------------------------------------------------------

Basic VFC nokiavnfmdriver API Health Check                            | PASS |

------------------------------------------------------------------------------

Basic VFC nokiav2driver API Health Check                              | PASS |

------------------------------------------------------------------------------

Basic VFC nslcm API Health Check                                      | PASS |

------------------------------------------------------------------------------

Basic VFC resmgr API Health Check                                     | PASS |

------------------------------------------------------------------------------

Basic VFC vnflcm API Health Check                                     | PASS |

------------------------------------------------------------------------------

Basic VFC vnfmgr API Health Check                                     | PASS |

------------------------------------------------------------------------------

Basic VFC vnfres API Health Check                                     | PASS |

------------------------------------------------------------------------------

Basic VFC workflow API Health Check                                   | PASS |

------------------------------------------------------------------------------

Basic VFC ztesdncdriver API Health Check                              | PASS |

------------------------------------------------------------------------------

Basic VFC ztevnfmdriver API Health Check                              | PASS |

------------------------------------------------------------------------------

Basic VID Health Check                                                | PASS |

------------------------------------------------------------------------------

Basic VNFSDK Health Check                                             | PASS |

------------------------------------------------------------------------------

Basic Holmes Rule Management API Health Check                         | FAIL |

502 != 200

------------------------------------------------------------------------------

Basic Holmes Engine Management API Health Check                       | FAIL |

502 != 200

------------------------------------------------------------------------------

Testsuites.Health-Check :: Testing ecomp components are available ... | FAIL |

51 critical tests, 41 passed, 10 failed

51 tests total, 41 passed, 10 failed

==============================================================================

Testsuites                                                            | FAIL |

51 critical tests, 41 passed, 10 failed

51 tests total, 41 passed, 10 failed

==============================================================================

Output:  /share/logs/0001_ete_health/output.xml

Log:     /share/logs/0001_ete_health/log.html

Report:  /share/logs/0001_ete_health/report.html

command terminated with exit code 10

 

 

 

Da: FREEMAN, BRIAN D [mailto:bf1936@...]
Inviato: venerdì 1 marzo 2019 14:49
A: onap-discuss@...; Calamita Agostino <agostino.calamita@...>
Oggetto: RE: [onap-discuss] dmaap-message-router NodePort not recheable

 

Try a POST to make sure you can write to message router.

I doubt its connectivity.

 

If you are on master branch – try ./ete-k8s.sh onap healthmr to test a write/read to a test topic.

 

(do it twice since the first time it creates a test topic and kafka doesnt forward the message till both the publisher and the subscriber have connected)

 

Brian

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Calamita Agostino
Sent: Friday, March 01, 2019 4:30 AM
To: onap-discuss@...
Subject: R: [onap-discuss] dmaap-message-router NodePort not recheable

 

I tried to execute a wget command from sdc-be POD to message-router REST API and I see that dmaap-message-router is reacheable from sdc-be.

 

This is the result:

 

# kubectl exec -it  dev-sdc-sdc-be-656bd64b9b-jh57x  -n onap -- /bin/bash

 

bash-4.4# wget "http://message-router:3904/topics"

Connecting to message-router:3904 (10.43.1.20:3904)

topics               100% |*******************************|   131   0:00:00 ETA

bash-4.4# cat topics

{"topics": [

    "__consumer_offsets",

    "champRawEvents",

    "SDC-DISTR-NOTIF-TOPIC-AUTO",

    "org.onap.dmaap.mr.PNF_READY"

]}bash-4.4#

 

But audit.log of sdc-be, after “Distribution Service” action from Portal , says:

 

2019-03-01T08:32:07.986Z        [qtp215145189-323354]   INFO    o.o.sdc.be.filters.BeServletFilter     

ResponseCode=500        InstanceUUID=null       RequestId=d2f65e19-b07b-4266-8be2-f170aba42fb1  AlertSeverity=0 ElapsedTime=3  

EndTimestamp=2019-03-01 08:32:07.986Z   PartnerName=op0001      auditOn=true    ServerFQDN=dev-sdc-sdc-be-656bd64b9b-jh57x      

StatusCode=ERROR        TargetEntity=Distribution Engine is DOWN       

CustomField1=POST: http://sdc-be.onap:8080/sdc2/rest/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate       

timer=3 CustomField2=500        AuditBeginTimestamp=2019-03-01 08:32:07.983Z    RemoteHost=10.42.194.84 ErrorCategory=ERROR    

ServerIPAddress=10.42.179.134   ServiceName=/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate      

ServiceInstanceId=null   ClassName=org.openecomp.sdc.be.filters.BeServletFilter  ResponseDescription=Internal Server Error      

ErrorCode=500   null

 

 

In the same log file I found a lot of messages like this one:

 

2019-03-01T09:21:31.850Z        [qtp215145189-399996]   INFO    o.o.sdc.be.filters.BeServletFilter      AuditMessage=ACTION = "HttpAuthentication" URL = "v1/registerForDistribution" USER = "aai" AUTH_STATUS = "AUTH_SUCCESS" REALM = "ASDC"  ResponseCode=500        InstanceUUID=aai-ml     RequestId=7f01a5b2-ee38-42c9-b7a4-330f020a4134 AlertSeverity=0  ElapsedTime=169 EndTimestamp=2019-03-01 09:21:31.850Z   PartnerName=Apache-HttpClient/4.5.6 (Java/1.8.0_171)    auditOn=true    ServerFQDN=dev-sdc-sdc-be-656bd64b9b-jh57x      StatusCode=ERROR        TargetEntity=registerInDistributionEngine       CustomField1=POST: https://sdc-be.onap:8443/sdc/v1/registerForDistribution      timer=169       CustomField2=500        AuditBeginTimestamp=2019-03-01 09:21:31.681Z    RemoteHost=10.42.209.109        ErrorCategory=ERROR     ServerIPAddress=10.42.179.134   ServiceName=/v1/registerForDistribution ServiceInstanceId=null  ClassName=org.openecomp.sdc.be.filters.BeServletFilter  ResponseDescription=Internal Server Error       ErrorCode=500   ACTION = "HttpAuthentication" URL = "v1/registerForDistribution" USER = "aai" AUTH_STATUS = "AUTH_SUCCESS" REALM = "ASDC"

 

Thanks.

 

Da: onap-discuss@... [mailto:onap-discuss@...] Per conto di Calamita Agostino
Inviato: giovedì 28 febbraio 2019 16:13
A: onap-discuss@...
Oggetto: [onap-discuss] dmaap-message-router NodePort not recheable

 

Hi all,

I have an issue releted to connectivity from sdc-be pod and dmaap-message-router.

My installation is Casablanca 3.0.0 on 7 kubernetes VM cluster.

 

All dmaap pods are up and running:

 

dev-dmaap-dbc-pg-0                                            1/1       Running            0          1d        10.42.173.158   onapkm5   <none>

dev-dmaap-dbc-pg-1                                            1/1       Running            0          1d        10.42.188.140   onapkm2   <none>

dev-dmaap-dbc-pgpool-7b748d5894-mr2m9                         1/1       Running            0          1d        10.42.237.193   onapkm3   <none>

dev-dmaap-dbc-pgpool-7b748d5894-n6dks                         1/1       Running            0          1d        10.42.192.244   onapkm2   <none>

dev-dmaap-dmaap-bus-controller-6757c4c86-8rq5p                1/1       Running            0          1d        10.42.185.132   onapkm1   <none>

dev-dmaap-dmaap-dr-db-bb4c67cfd-tm7td                         1/1       Running            0          1d        10.42.152.59    onapkm1   <none>

dev-dmaap-dmaap-dr-node-66c8749959-tpdtf                      1/1       Running            0          1d        10.42.216.13    onapkm2   <none>

dev-dmaap-dmaap-dr-prov-5c766b8d69-qzqn2                      1/1       Running            0          1d        10.42.115.247   onapkm6   <none>

dev-dmaap-message-router-fb9f4bc7d-5z52j                      1/1       Running            0          6h        10.42.138.31    onapkm3   <none>

dev-dmaap-message-router-kafka-5fbc897f48-4bpb6               1/1       Running            0          1d        10.42.78.141    onapkm4   <none>

dev-dmaap-message-router-zookeeper-557954854-8d6p9            1/1       Running            0          1d        10.42.169.205   onapkm1   <none>

 

but when I try to distribute a service, from SDC Portal, I got “Internal Server Error”.

 

SDC-BE log file traces:

 

2019-02-28T08:50:35.318Z        [qtp215145189-159837]   INFO    o.o.sdc.be.filters.BeServletFilter      ResponseCode=500       

InstanceUUID=null RequestId=dab0fd50-b06e-4a65-b4a8-7d7edeae3e01   AlertSeverity=0 ElapsedTime=99  EndTimestamp=2019-02-28 08:50:35.318Z PartnerName=op0001      auditOn=true       ServerFQDN=dev-sdc-sdc-be-656bd64b9b-jh57x      StatusCode=ERROR       

TargetEntity=Distribution Engine is DOWN       

CustomField1=POST: http://sdc-be.onap:8080/sdc2/rest/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate  

timer=99        CustomField2=500   AuditBeginTimestamp=2019-02-28 08:50:35.219Z    RemoteHost=10.42.194.84 ErrorCategory=ERROR    

ServerIPAddress=10.42.179.134   ServiceName=/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate  

ServiceInstanceId=null  ClassName=org.openecomp.sdc.be.filters.BeServletFilter     ResponseDescription=Internal Server Error      

ErrorCode=500   null

 

Also SDC healthcheck reports that U-EB Cluster is DOWN.

 

Inside SDC-BE POD, I tried to make a traceroute to “message-router-zookeeper” and to “message-router”.

 

This is the result ( the first is OK, the second one NOT OK ):

 

bash-4.4# traceroute  message-router-zookeeper

traceroute to message-router-zookeeper (10.42.169.205), 30 hops max, 46 byte packets

1  10.42.7.46 (10.42.7.46)  0.213 ms  0.005 ms  0.005 ms

2  10.42.190.179 (10.42.190.179)  0.194 ms  0.145 ms  0.135 ms

3  10.42.169.205 (10.42.169.205)  0.461 ms  0.160 ms  0.134 ms

 

bash-4.4# traceroute  message-router

traceroute to message-router (10.43.1.20), 30 hops max, 46 byte packets

1  10.42.0.1 (10.42.0.1)  0.009 ms  0.005 ms  0.005 ms

2  itpat1ng505.palermo.italtel.it (138.132.168.173)  0.344 ms  2.211 ms  1.910 ms     ß 138.132.168.X  is VM public network

 3  138.132.169.2 (138.132.169.2)  5.063 ms  3.859 ms  3.934 ms

4  *  *  *

5  *  *  *

6  *  *  *

 

traceroute to message-router-kafka (10.43.148.154), 30 hops max, 46 byte packets

1  10.42.0.1 (10.42.0.1)  0.006 ms  0.005 ms  0.004 ms

2  itpat1ng505.palermo.italtel.it (138.132.168.173)  0.391 ms  0.337 ms  0.314 ms

3  138.132.169.2 (138.132.169.2)  0.803 ms  0.748 ms  0.807 ms

4  *  *  *

5  *  *  *

6  *  *  *

 

It seems that I cannot reach NodePort or ClusterIP inside a POD. This is routing table inside POD:

 

bash-4.4# netstat -rn

Kernel IP routing table

Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface

0.0.0.0         10.42.0.1       0.0.0.0         UG        0 0          0 eth0

10.42.0.0       0.0.0.0         255.255.0.0     U         0 0          0 eth0

 

What can I check on Kubernetes Cluster ?

 

Thanks.

Agostino.

 

Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/

Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/

Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/


Re: dmaap-message-router NodePort not recheable

Brian Freeman
 

Try a POST to make sure you can write to message router.

I doubt its connectivity.

 

If you are on master branch – try ./ete-k8s.sh onap healthmr to test a write/read to a test topic.

 

(do it twice since the first time it creates a test topic and kafka doesnt forward the message till both the publisher and the subscriber have connected)

 

Brian

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Calamita Agostino
Sent: Friday, March 01, 2019 4:30 AM
To: onap-discuss@...
Subject: R: [onap-discuss] dmaap-message-router NodePort not recheable

 

I tried to execute a wget command from sdc-be POD to message-router REST API and I see that dmaap-message-router is reacheable from sdc-be.

 

This is the result:

 

# kubectl exec -it  dev-sdc-sdc-be-656bd64b9b-jh57x  -n onap -- /bin/bash

 

bash-4.4# wget "http://message-router:3904/topics"

Connecting to message-router:3904 (10.43.1.20:3904)

topics               100% |*******************************|   131   0:00:00 ETA

bash-4.4# cat topics

{"topics": [

    "__consumer_offsets",

    "champRawEvents",

    "SDC-DISTR-NOTIF-TOPIC-AUTO",

    "org.onap.dmaap.mr.PNF_READY"

]}bash-4.4#

 

But audit.log of sdc-be, after “Distribution Service” action from Portal , says:

 

2019-03-01T08:32:07.986Z        [qtp215145189-323354]   INFO    o.o.sdc.be.filters.BeServletFilter     

ResponseCode=500        InstanceUUID=null       RequestId=d2f65e19-b07b-4266-8be2-f170aba42fb1  AlertSeverity=0 ElapsedTime=3  

EndTimestamp=2019-03-01 08:32:07.986Z   PartnerName=op0001      auditOn=true    ServerFQDN=dev-sdc-sdc-be-656bd64b9b-jh57x      

StatusCode=ERROR        TargetEntity=Distribution Engine is DOWN       

CustomField1=POST: http://sdc-be.onap:8080/sdc2/rest/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate       

timer=3 CustomField2=500        AuditBeginTimestamp=2019-03-01 08:32:07.983Z    RemoteHost=10.42.194.84 ErrorCategory=ERROR    

ServerIPAddress=10.42.179.134   ServiceName=/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate      

ServiceInstanceId=null   ClassName=org.openecomp.sdc.be.filters.BeServletFilter  ResponseDescription=Internal Server Error      

ErrorCode=500   null

 

 

In the same log file I found a lot of messages like this one:

 

2019-03-01T09:21:31.850Z        [qtp215145189-399996]   INFO    o.o.sdc.be.filters.BeServletFilter      AuditMessage=ACTION = "HttpAuthentication" URL = "v1/registerForDistribution" USER = "aai" AUTH_STATUS = "AUTH_SUCCESS" REALM = "ASDC"  ResponseCode=500        InstanceUUID=aai-ml     RequestId=7f01a5b2-ee38-42c9-b7a4-330f020a4134 AlertSeverity=0  ElapsedTime=169 EndTimestamp=2019-03-01 09:21:31.850Z   PartnerName=Apache-HttpClient/4.5.6 (Java/1.8.0_171)    auditOn=true    ServerFQDN=dev-sdc-sdc-be-656bd64b9b-jh57x      StatusCode=ERROR        TargetEntity=registerInDistributionEngine       CustomField1=POST: https://sdc-be.onap:8443/sdc/v1/registerForDistribution      timer=169       CustomField2=500        AuditBeginTimestamp=2019-03-01 09:21:31.681Z    RemoteHost=10.42.209.109        ErrorCategory=ERROR     ServerIPAddress=10.42.179.134   ServiceName=/v1/registerForDistribution ServiceInstanceId=null  ClassName=org.openecomp.sdc.be.filters.BeServletFilter  ResponseDescription=Internal Server Error       ErrorCode=500   ACTION = "HttpAuthentication" URL = "v1/registerForDistribution" USER = "aai" AUTH_STATUS = "AUTH_SUCCESS" REALM = "ASDC"

 

Thanks.

 

Da: onap-discuss@... [mailto:onap-discuss@...] Per conto di Calamita Agostino
Inviato: giovedì 28 febbraio 2019 16:13
A: onap-discuss@...
Oggetto: [onap-discuss] dmaap-message-router NodePort not recheable

 

Hi all,

I have an issue releted to connectivity from sdc-be pod and dmaap-message-router.

My installation is Casablanca 3.0.0 on 7 kubernetes VM cluster.

 

All dmaap pods are up and running:

 

dev-dmaap-dbc-pg-0                                            1/1       Running            0          1d        10.42.173.158   onapkm5   <none>

dev-dmaap-dbc-pg-1                                            1/1       Running            0          1d        10.42.188.140   onapkm2   <none>

dev-dmaap-dbc-pgpool-7b748d5894-mr2m9                         1/1       Running            0          1d        10.42.237.193   onapkm3   <none>

dev-dmaap-dbc-pgpool-7b748d5894-n6dks                         1/1       Running            0          1d        10.42.192.244   onapkm2   <none>

dev-dmaap-dmaap-bus-controller-6757c4c86-8rq5p                1/1       Running            0          1d        10.42.185.132   onapkm1   <none>

dev-dmaap-dmaap-dr-db-bb4c67cfd-tm7td                         1/1       Running            0          1d        10.42.152.59    onapkm1   <none>

dev-dmaap-dmaap-dr-node-66c8749959-tpdtf                      1/1       Running            0          1d        10.42.216.13    onapkm2   <none>

dev-dmaap-dmaap-dr-prov-5c766b8d69-qzqn2                      1/1       Running            0          1d        10.42.115.247   onapkm6   <none>

dev-dmaap-message-router-fb9f4bc7d-5z52j                      1/1       Running            0          6h        10.42.138.31    onapkm3   <none>

dev-dmaap-message-router-kafka-5fbc897f48-4bpb6               1/1       Running            0          1d        10.42.78.141    onapkm4   <none>

dev-dmaap-message-router-zookeeper-557954854-8d6p9            1/1       Running            0          1d        10.42.169.205   onapkm1   <none>

 

but when I try to distribute a service, from SDC Portal, I got “Internal Server Error”.

 

SDC-BE log file traces:

 

2019-02-28T08:50:35.318Z        [qtp215145189-159837]   INFO    o.o.sdc.be.filters.BeServletFilter      ResponseCode=500       

InstanceUUID=null RequestId=dab0fd50-b06e-4a65-b4a8-7d7edeae3e01   AlertSeverity=0 ElapsedTime=99  EndTimestamp=2019-02-28 08:50:35.318Z PartnerName=op0001      auditOn=true       ServerFQDN=dev-sdc-sdc-be-656bd64b9b-jh57x      StatusCode=ERROR       

TargetEntity=Distribution Engine is DOWN       

CustomField1=POST: http://sdc-be.onap:8080/sdc2/rest/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate  

timer=99        CustomField2=500   AuditBeginTimestamp=2019-02-28 08:50:35.219Z    RemoteHost=10.42.194.84 ErrorCategory=ERROR    

ServerIPAddress=10.42.179.134   ServiceName=/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate  

ServiceInstanceId=null  ClassName=org.openecomp.sdc.be.filters.BeServletFilter     ResponseDescription=Internal Server Error      

ErrorCode=500   null

 

Also SDC healthcheck reports that U-EB Cluster is DOWN.

 

Inside SDC-BE POD, I tried to make a traceroute to “message-router-zookeeper” and to “message-router”.

 

This is the result ( the first is OK, the second one NOT OK ):

 

bash-4.4# traceroute  message-router-zookeeper

traceroute to message-router-zookeeper (10.42.169.205), 30 hops max, 46 byte packets

1  10.42.7.46 (10.42.7.46)  0.213 ms  0.005 ms  0.005 ms

2  10.42.190.179 (10.42.190.179)  0.194 ms  0.145 ms  0.135 ms

3  10.42.169.205 (10.42.169.205)  0.461 ms  0.160 ms  0.134 ms

 

bash-4.4# traceroute  message-router

traceroute to message-router (10.43.1.20), 30 hops max, 46 byte packets

1  10.42.0.1 (10.42.0.1)  0.009 ms  0.005 ms  0.005 ms

2  itpat1ng505.palermo.italtel.it (138.132.168.173)  0.344 ms  2.211 ms  1.910 ms     ß 138.132.168.X  is VM public network

 3  138.132.169.2 (138.132.169.2)  5.063 ms  3.859 ms  3.934 ms

4  *  *  *

5  *  *  *

6  *  *  *

 

traceroute to message-router-kafka (10.43.148.154), 30 hops max, 46 byte packets

1  10.42.0.1 (10.42.0.1)  0.006 ms  0.005 ms  0.004 ms

2  itpat1ng505.palermo.italtel.it (138.132.168.173)  0.391 ms  0.337 ms  0.314 ms

3  138.132.169.2 (138.132.169.2)  0.803 ms  0.748 ms  0.807 ms

4  *  *  *

5  *  *  *

6  *  *  *

 

It seems that I cannot reach NodePort or ClusterIP inside a POD. This is routing table inside POD:

 

bash-4.4# netstat -rn

Kernel IP routing table

Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface

0.0.0.0         10.42.0.1       0.0.0.0         UG        0 0          0 eth0

10.42.0.0       0.0.0.0         255.255.0.0     U         0 0          0 eth0

 

What can I check on Kubernetes Cluster ?

 

Thanks.

Agostino.

 

Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/

Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/


Re: SDC-FE catalog API call for setting GenericNeutronNet "network_role" attribute #sdc

Brian Freeman
 

Look in the asdc_interface.robot files for examples of setting GenericNeutronNet network_role.

 

Brian

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Andreas Geissler
Sent: Friday, March 01, 2019 6:47 AM
To: onap-discuss@...
Subject: [onap-discuss] SDC-FE catalog API call for setting GenericNeutronNet "network_role" attribute #sdc

 

Hi,
I am trying to instantiate in SDC via API calls a Service and added a GenericNeutronNet VL to it.
Now I would like to configure the property "network _role" via POST command, which I found in the SDC-FE logs, but without success.
Post command:
{{url-sdc2}}/sdc1/feProxy/rest/v1/catalog/services/{{auto_service_unique_id}}/resourceInstance/{{auto_vl_instance_uniqueid}}/properties

How do I need to pass the attribute in the body of the command.
Do you have any idea ?

Best regards
Andreas


Re: Demo Use Case MWC 2019 - MEC with ONAP and OAI

Marco Platania
 

Thanks Xoan, well done!

 

Marco

 

From: <onap-discuss@...> on behalf of jkzcristiano <jkzcristiano@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "jkzcristiano@..." <jkzcristiano@...>
Date: Friday, March 1, 2019 at 7:00 AM
To: jkzcristiano <jkzcristiano@...>, "onap-discuss@..." <onap-discuss@...>
Subject: Re: [onap-discuss] Demo Use Case MWC 2019 - MEC with ONAP and OAI

 

This demo is part of Veo5G project led by Cellnex and in collaboration with Optare Solutions and the GTI group at University of Vigo.

Contact:

jgrois@...

Personal acknowledgements:

I would personally like to thank Marco Platania from AT&T for his very kind comments, help and support in working with ONAP platform. You are great Marco!


Re: dmaap-message-router NodePort not recheable

Marco Platania
 

Agostino,

 

Please use nexus3.onap.org:10001:onap/dmaap/zookeeper:2.0.0

 

docker.io/wurstmeister/zookeeper:latest has been lately updated to a version that gave us some troubles…

 

Marco

 

 

From: <onap-discuss@...> on behalf of Calamita Agostino <agostino.calamita@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "agostino.calamita@..." <agostino.calamita@...>
Date: Friday, March 1, 2019 at 3:00 AM
To: "SAWANT, MANDAR" <ms5838@...>, "onap-discuss@..." <onap-discuss@...>
Subject: R: [onap-discuss] dmaap-message-router NodePort not recheable

 

Zookeeper image is:

 

Image:   docker.io/wurstmeister/zookeeper:latest

 

Dmaap message-router-kafka is running and connected to zookeeper.

 

Da: Mandar Sawant [mailto:ms5838@...]
Inviato: giovedì 28 febbraio 2019 23:12

A: Calamita Agostino <agostino.calamita@...>; onap-discuss@...
Oggetto: Re: [onap-discuss] dmaap-message-router NodePort not recheable

 

Can you please tell whats the DMaaP Zookeeper image that's installed in the environment?

Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/


Re: Demo Use Case MWC 2019 - MEC with ONAP and OAI

jkzcristiano
 

This demo is part of Veo5G project led by Cellnex and in collaboration with Optare Solutions and the GTI group at University of Vigo.

Contact:

jgrois@...

Personal acknowledgements:

I would personally like to thank Marco Platania from AT&T for his very kind comments, help and support in working with ONAP platform. You are great Marco!


SDC-FE catalog API call for setting GenericNeutronNet "network_role" attribute #sdc

Andreas Geissler
 

Hi,
I am trying to instantiate in SDC via API calls a Service and added a GenericNeutronNet VL to it.
Now I would like to configure the property "network _role" via POST command, which I found in the SDC-FE logs, but without success.
Post command:
{{url-sdc2}}/sdc1/feProxy/rest/v1/catalog/services/{{auto_service_unique_id}}/resourceInstance/{{auto_vl_instance_uniqueid}}/properties

How do I need to pass the attribute in the body of the command.
Do you have any idea ?

Best regards
Andreas


[doc] CORRECTION - Update the Creative commons license header

Sofia Wallin
 

Correction!

Please don’t change the date in the copy right headers.

The doc team have already updated the license published at the bottom of docs.onap.org.

 

However, please check that published documents that has the date at the bottom of the page is updated to 2019. It shouldn’t be any issues since we are using submodules.  

 

Sorry for the confusion.  

 

Best regards,

Sofia

 

From: Sofia Wallin <sofia.wallin@...>
Date: Wednesday, 13 February 2019 at 13:11
To: "onap-discuss@..." <onap-discuss@...>
Subject: [onap-discuss] [doc] Update the Creative commons license header

 

Hello ONAP community,

This is a reminder that we need to update the year in the licence header in each document.

Please make sure that is done in all files intended for the Dublin release.

 

Thanks!

 

Best regards,

Sofia

 

Example,

 

.. This work is licensed under a Creative Commons Attribution 4.0

   International License. http://creativecommons.org/licenses/by/4.0

   Copyright 2019 <company> All rights reserved.

 

 


R: [onap-discuss] dmaap-message-router NodePort not recheable

Calamita Agostino
 

I tried to execute a wget command from sdc-be POD to message-router REST API and I see that dmaap-message-router is reacheable from sdc-be.

This is the result:

 

# kubectl exec -it  dev-sdc-sdc-be-656bd64b9b-jh57x  -n onap -- /bin/bash

 

bash-4.4# wget "http://message-router:3904/topics"

Connecting to message-router:3904 (10.43.1.20:3904)

topics               100% |*******************************|   131   0:00:00 ETA

bash-4.4# cat topics

{"topics": [

    "__consumer_offsets",

    "champRawEvents",

    "SDC-DISTR-NOTIF-TOPIC-AUTO",

    "org.onap.dmaap.mr.PNF_READY"

]}bash-4.4#

 

But audit.log of sdc-be, after “Distribution Service” action from Portal , says:

 

2019-03-01T08:32:07.986Z        [qtp215145189-323354]   INFO    o.o.sdc.be.filters.BeServletFilter     

ResponseCode=500        InstanceUUID=null       RequestId=d2f65e19-b07b-4266-8be2-f170aba42fb1  AlertSeverity=0 ElapsedTime=3  

EndTimestamp=2019-03-01 08:32:07.986Z   PartnerName=op0001      auditOn=true    ServerFQDN=dev-sdc-sdc-be-656bd64b9b-jh57x      

StatusCode=ERROR        TargetEntity=Distribution Engine is DOWN       

CustomField1=POST: http://sdc-be.onap:8080/sdc2/rest/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate       

timer=3 CustomField2=500        AuditBeginTimestamp=2019-03-01 08:32:07.983Z    RemoteHost=10.42.194.84 ErrorCategory=ERROR    

ServerIPAddress=10.42.179.134   ServiceName=/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate      

ServiceInstanceId=null   ClassName=org.openecomp.sdc.be.filters.BeServletFilter  ResponseDescription=Internal Server Error      

ErrorCode=500   null

 

 

In the same log file I found a lot of messages like this one:

 

2019-03-01T09:21:31.850Z        [qtp215145189-399996]   INFO    o.o.sdc.be.filters.BeServletFilter      AuditMessage=ACTION = "HttpAuthentication" URL = "v1/registerForDistribution" USER = "aai" AUTH_STATUS = "AUTH_SUCCESS" REALM = "ASDC"  ResponseCode=500        InstanceUUID=aai-ml     RequestId=7f01a5b2-ee38-42c9-b7a4-330f020a4134 AlertSeverity=0  ElapsedTime=169 EndTimestamp=2019-03-01 09:21:31.850Z   PartnerName=Apache-HttpClient/4.5.6 (Java/1.8.0_171)    auditOn=true    ServerFQDN=dev-sdc-sdc-be-656bd64b9b-jh57x      StatusCode=ERROR        TargetEntity=registerInDistributionEngine       CustomField1=POST: https://sdc-be.onap:8443/sdc/v1/registerForDistribution      timer=169       CustomField2=500        AuditBeginTimestamp=2019-03-01 09:21:31.681Z    RemoteHost=10.42.209.109        ErrorCategory=ERROR     ServerIPAddress=10.42.179.134   ServiceName=/v1/registerForDistribution ServiceInstanceId=null  ClassName=org.openecomp.sdc.be.filters.BeServletFilter  ResponseDescription=Internal Server Error       ErrorCode=500   ACTION = "HttpAuthentication" URL = "v1/registerForDistribution" USER = "aai" AUTH_STATUS = "AUTH_SUCCESS" REALM = "ASDC"

 

Thanks.

 

Da: onap-discuss@... [mailto:onap-discuss@...] Per conto di Calamita Agostino
Inviato: giovedì 28 febbraio 2019 16:13
A: onap-discuss@...
Oggetto: [onap-discuss] dmaap-message-router NodePort not recheable

 

Hi all,

I have an issue releted to connectivity from sdc-be pod and dmaap-message-router.

My installation is Casablanca 3.0.0 on 7 kubernetes VM cluster.

 

All dmaap pods are up and running:

 

dev-dmaap-dbc-pg-0                                            1/1       Running            0          1d        10.42.173.158   onapkm5   <none>

dev-dmaap-dbc-pg-1                                            1/1       Running            0          1d        10.42.188.140   onapkm2   <none>

dev-dmaap-dbc-pgpool-7b748d5894-mr2m9                         1/1       Running            0          1d        10.42.237.193   onapkm3   <none>

dev-dmaap-dbc-pgpool-7b748d5894-n6dks                         1/1       Running            0          1d        10.42.192.244   onapkm2   <none>

dev-dmaap-dmaap-bus-controller-6757c4c86-8rq5p                1/1       Running            0          1d        10.42.185.132   onapkm1   <none>

dev-dmaap-dmaap-dr-db-bb4c67cfd-tm7td                         1/1       Running            0          1d        10.42.152.59    onapkm1   <none>

dev-dmaap-dmaap-dr-node-66c8749959-tpdtf                      1/1       Running            0          1d        10.42.216.13    onapkm2   <none>

dev-dmaap-dmaap-dr-prov-5c766b8d69-qzqn2                      1/1       Running            0          1d        10.42.115.247   onapkm6   <none>

dev-dmaap-message-router-fb9f4bc7d-5z52j                      1/1       Running            0          6h        10.42.138.31    onapkm3   <none>

dev-dmaap-message-router-kafka-5fbc897f48-4bpb6               1/1       Running            0          1d        10.42.78.141    onapkm4   <none>

dev-dmaap-message-router-zookeeper-557954854-8d6p9            1/1       Running            0          1d        10.42.169.205   onapkm1   <none>

 

but when I try to distribute a service, from SDC Portal, I got “Internal Server Error”.

 

SDC-BE log file traces:

 

2019-02-28T08:50:35.318Z        [qtp215145189-159837]   INFO    o.o.sdc.be.filters.BeServletFilter      ResponseCode=500       

InstanceUUID=null RequestId=dab0fd50-b06e-4a65-b4a8-7d7edeae3e01   AlertSeverity=0 ElapsedTime=99  EndTimestamp=2019-02-28 08:50:35.318Z PartnerName=op0001      auditOn=true       ServerFQDN=dev-sdc-sdc-be-656bd64b9b-jh57x      StatusCode=ERROR       

TargetEntity=Distribution Engine is DOWN       

CustomField1=POST: http://sdc-be.onap:8080/sdc2/rest/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate  

timer=99        CustomField2=500   AuditBeginTimestamp=2019-02-28 08:50:35.219Z    RemoteHost=10.42.194.84 ErrorCategory=ERROR    

ServerIPAddress=10.42.179.134   ServiceName=/v1/catalog/services/02e0c5a4-be65-4d09-9f1e-49a2dab0f865/distribution/PROD/activate  

ServiceInstanceId=null  ClassName=org.openecomp.sdc.be.filters.BeServletFilter     ResponseDescription=Internal Server Error      

ErrorCode=500   null

 

Also SDC healthcheck reports that U-EB Cluster is DOWN.

 

Inside SDC-BE POD, I tried to make a traceroute to “message-router-zookeeper” and to “message-router”.

 

This is the result ( the first is OK, the second one NOT OK ):

 

bash-4.4# traceroute  message-router-zookeeper

traceroute to message-router-zookeeper (10.42.169.205), 30 hops max, 46 byte packets

1  10.42.7.46 (10.42.7.46)  0.213 ms  0.005 ms  0.005 ms

2  10.42.190.179 (10.42.190.179)  0.194 ms  0.145 ms  0.135 ms

3  10.42.169.205 (10.42.169.205)  0.461 ms  0.160 ms  0.134 ms

 

bash-4.4# traceroute  message-router

traceroute to message-router (10.43.1.20), 30 hops max, 46 byte packets

1  10.42.0.1 (10.42.0.1)  0.009 ms  0.005 ms  0.005 ms

2  itpat1ng505.palermo.italtel.it (138.132.168.173)  0.344 ms  2.211 ms  1.910 ms     ß 138.132.168.X  is VM public network

 3  138.132.169.2 (138.132.169.2)  5.063 ms  3.859 ms  3.934 ms

4  *  *  *

5  *  *  *

6  *  *  *

 

traceroute to message-router-kafka (10.43.148.154), 30 hops max, 46 byte packets

1  10.42.0.1 (10.42.0.1)  0.006 ms  0.005 ms  0.004 ms

2  itpat1ng505.palermo.italtel.it (138.132.168.173)  0.391 ms  0.337 ms  0.314 ms

3  138.132.169.2 (138.132.169.2)  0.803 ms  0.748 ms  0.807 ms

4  *  *  *

5  *  *  *

6  *  *  *

 

It seems that I cannot reach NodePort or ClusterIP inside a POD. This is routing table inside POD:

 

bash-4.4# netstat -rn

Kernel IP routing table

Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface

0.0.0.0         10.42.0.1       0.0.0.0         UG        0 0          0 eth0

10.42.0.0       0.0.0.0         255.255.0.0     U         0 0          0 eth0

 

What can I check on Kubernetes Cluster ?

 

Thanks.

Agostino.

 

Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/

Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/


Re: [aai] Sync and bulk migration in AAI

Keong Lim
 

Hi Chandra,

If you search the wiki for "data restore", you can find the related pages for AAI in various ONAP releases:

https://wiki.onap.org/dosearchsite.action?queryString=data+restore


Keong


R: [onap-discuss] dmaap-message-router NodePort not recheable

Calamita Agostino
 

Zookeeper image is:

 

Image:   docker.io/wurstmeister/zookeeper:latest

 

Dmaap message-router-kafka is running and connected to zookeeper.

 

Da: Mandar Sawant [mailto:ms5838@...]
Inviato: giovedì 28 febbraio 2019 23:12
A: Calamita Agostino <agostino.calamita@...>; onap-discuss@...
Oggetto: Re: [onap-discuss] dmaap-message-router NodePort not recheable

 

Can you please tell whats the DMaaP Zookeeper image that's installed in the environment?

Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/


Register for ONS North America -- Schedule Now Live!

Brandon Wick
 

LFN Project Communities:

ONS North America, to be held April 3-5 in San Jose, CA, brings together enterprises, telecom companies, and cloud providers to advance collaboration and innovation across the entire open source networking ecosystem. ONS 2019 tracks include: Carrier and Cloud DevOps, Cloud Native Networking, Enterprise IT & Operations, The New Edge, and World of Open Innovation and Impact to Networking.

The full lineup of sessions can be viewed here, and features speakers from AT&T, China Mobile, Ericsson, Google, Huawei, Intel, KPMG, Nokia, Red Hat, Target, and more.

In addition to the program, LF Networking will have a strong presence at the event with an 10 community-driven demos in the LFN Booth, and an LFN Unconference Track each day in room LL21A & LL21B for project meetings, impromptu meetups, and hacking.

LF Member companies can register with a discount of 20% using this code: LFMEM20. What's more, Day Passes are available for $675 and Hall Passes for $275. Note: The Hall Pass includes access to Keynote Sessions, Sponsor Showcase, Unconference Track, Attendee Onsite Reception, Wednesday Morning Tutorials, and daily conference breakfast/breaks. It does not include access to any ONS conference sessions or offsite evening events. Get materials to help make the case for your attendance here

We hope that you will take advantage of this opportunity to engage with the LFN community at our flagship event in North America. We encourage you to register early and book your travel and accommodations. Please direct any questions you may have to events@.... Thank you!

Best, 

Brandon Wick
Senior Integrated Marketing Manager
The Linux Foundation
+1.917.282.0960



[cia] Weekly meeting reminder

Adolfo Perez-Duran
 

Team,

A gentle reminder of our weekly meeting.

Details are as follows:

Day: Friday
Time: 6h PT/ 7h MT/ 9h ET/ 14h UTC / 22h Beijing Time

LF is updating the meeting, we might get a new meeting ID. For this Friday, please use the following meeting link

Join Zoom Meeting
https://us04web.zoom.us/j/9891284512

One tap mobile
+14086380968,,9891284512# US (San Jose)
+16465588656,,9891284512# US (New York)

Dial by your location
        +1 408 638 0968 US (San Jose)
        +1 646 558 8656 US (New York)
Meeting ID: 989 128 4512
Find your local number: https://us04web.zoom.us/u/fVP7jn1wE




Re: [aai] Sync and bulk migration in AAI

Chandra
 

Hi Keong,

Is there any documentation available for this tool to facilitate backup and restore of AAI db?

Regards
Chandrashekhar Thakare

-----Original Message-----
From: Keong Lim [mailto:keong.lim@huawei.com]
Sent: 01 March 2019 06:25
To: Chandrashekhar Thakare <CT00548828@TechMahindra.com>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [aai] Sync and bulk migration in AAI

Hi Chandra,

AAI itself does not provide general-purpose sync utilities, but other ONAP projects (as clients of AAI) manage their own flows of data in/out of many different external systems.

There is a special-purpose tool which captures AAI data in graphson format for the purposes of backup/restore of the underlying JanusGraph db and there are other efforts underway for doing bulk data migrations, e.g. from Amsterdam release to Casablanca release.

There is a Bulk API for AAI. The updated documentation is here:

https://onap.readthedocs.io/en/casablanca/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/AAIRESTAPI_CASABLANCA.html#bulk-apis


Keong
============================================================================================================================

Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra.

============================================================================================================================


Re: [aai] Sync and bulk migration in AAI

Keong Lim
 

Hi Chandra,

AAI itself does not provide general-purpose sync utilities, but other ONAP projects (as clients of AAI) manage their own flows of data in/out of many different external systems.

There is a special-purpose tool which captures AAI data in graphson format for the purposes of backup/restore of the underlying JanusGraph db and there are other efforts underway for doing bulk data migrations, e.g. from Amsterdam release to Casablanca release.

There is a Bulk API for AAI. The updated documentation is here:

https://onap.readthedocs.io/en/casablanca/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/AAIRESTAPI_CASABLANCA.html#bulk-apis


Keong


Re: [SO] Ingestion of PNF model data to the catalog DB

Steve Smokowski
 

Develop from the start.

 

Thanks

 

-Steve

 

 

From: <onap-discuss@...> on behalf of Oskar Malm <oskar.malm@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "oskar.malm@..." <oskar.malm@...>
Date: Thursday, February 28, 2019 at 5:09 PM
To: Seshu m <seshu.kumar.m@...>, "onap-discuss@..." <onap-discuss@...>
Cc: "MALAKOV, YURIY" <ym9479@...>, Henry Xie <henry.xie@...>
Subject: [onap-discuss] [SO] Ingestion of PNF model data to the catalog DB

 

Hi Seshu,

 

As part of E2E automation effort for the Dublin release, optional configuration steps are being added to service instantiation workflows for both VNFs and PNFs. In order to have all the necessary parameters for the configuration step,  some additional information from the service model distributed from SDC must be extracted and stored in the SO catalog. This may require some updates to model ingestion code as well as the catalog DB schema.

 

For VNFs SO is already populating the catalog with various types of model information. But for PNFs we have not yet found anything similar. Can you confirm whether SO today has any support for PNF model ingestion or if this would have to be developed from start?

 

BR,

Oskar


Re: dmaap-message-router NodePort not recheable

Mandar Sawant <ms5838@...>
 

Can you please tell whats the DMaaP Zookeeper image that's installed in the environment?


[SO] Ingestion of PNF model data to the catalog DB

Oskar Malm
 

Hi Seshu,

 

As part of E2E automation effort for the Dublin release, optional configuration steps are being added to service instantiation workflows for both VNFs and PNFs. In order to have all the necessary parameters for the configuration step,  some additional information from the service model distributed from SDC must be extracted and stored in the SO catalog. This may require some updates to model ingestion code as well as the catalog DB schema.

 

For VNFs SO is already populating the catalog with various types of model information. But for PNFs we have not yet found anything similar. Can you confirm whether SO today has any support for PNF model ingestion or if this would have to be developed from start?

 

BR,

Oskar


[aai] Sync and bulk migration in AAI

Chandra
 

Hi ,

Do we have any utility in ONAP which provides the sync framework between the relational inventory db and AAI? Do we have any                tools to assist this? Also are there any tools for bulk migration?

 

 

Regards

Chandrashekhar Thakare

 

 

============================================================================================================================

Disclaimer:  This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.

============================================================================================================================


Re: SO High availability environment deployment

Srini
 

Thanks Piyush.

 

For load balancing and pod selection (among replicas), we are planning to rely on Kubernetes services.”

 

SRINI> I was only trying to find out what K8S projects are you using to do load balancing among the SO services.  Is it ISTIO or something else?

 

Thanks

Srini

 

 

From: Piyush Garg [mailto:Piyush.Garg1@...]
Sent: Thursday, February 28, 2019 1:23 AM
To: Addepalli, Srinivasa R <srinivasa.r.addepalli@...>; onap-discuss@...
Subject: RE: [onap-discuss] SO High availability environment deployment

 

Hi Srini,

 

Currently we are not planning to do the performance benchmarking.

For load balancing and pod selection (among replicas), we are planning to rely on Kubernetes services.

 

Regards,

Piyush

 

From: Addepalli, Srinivasa R <srinivasa.r.addepalli@...>
Sent: Wednesday, February 27, 2019 8:28 PM
To: onap-discuss@...; Piyush Garg <Piyush.Garg1@...>
Subject: RE: [onap-discuss] SO High availability environment deployment

 

Hi Piyush,

 

Yes, if the intention is to share the load across multiple instances.  I am curious to understand on whether there is any effort to do performance benchmarking. What is the type of input load?  What metrics are you collecting -  Number of SO service instantiations/hour?

 

Other reason you had given is to reduce the amount of time the service is down.  Yes, yet times, container restart can take minutes.  Good point.

 

When you have multiple instances of a micro-service, then the consuming micro-services need to have a way to figure out the running instances and then figure out the right instance within them to talk to.  In K8S world, service meshes (e.g ISTIO) are used for this purpose. Are you using any service mesh to experiment the scenario you described?

 

Thanks

Srini

 

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Piyush Garg
Sent: Wednesday, February 27, 2019 2:15 AM
To: Piyush Garg <piyush.garg1@...>; onap-discuss@...
Subject: Re: [onap-discuss] SO High availability environment deployment

 

Hi Srini,

 

Yes, for now we are not planning to handle the failure during in-flight requests.

With replica count of 2 or more (on different nodes), we want to achieve load sharing as well as we want to avoid a single point of failure in case a k8s node goes down. K8s can bring up the container in case of failure, but having more than 1 pods will keep system available while failed pod comes back.


Regards,
Piyush

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service

7541 - 7560 of 23354