Date   

Re: New VL distribution fails

Aniello Paolo Malinconico
 

Hi all,
I want to design a new node type derived from the tosca.nodes.network.Network, adding some custom properties. Such node type is a Virtual Link (VL) resource type.
I onboarded such resource carrying out the steps below described but during distribution phase I got an error. I'd appreciate your help to understand if the procedure I followed is correct or not because I didn't find any documentation on that.

The attached files are:
- cord-evc.yml:  describing the new node type
- dataTypes.yml:   describing the new datatypes used in the new node type
- cord-evc.json:  node type metadata
  
To import the new dataTypes and the new node type, I have executed the following steps:
 
-  Download SDC code from gerrit (git clone https://gerrit.onap.org/r/sdc).
-  Put cord-evc.yml  and cord-evc.json  to {gerrit sdc code}/catalog-be/src/main/resources/import/tosca/normative-types/cord-evc/
-  Put dataTypes.yml file to {gerrit sdc code}/catalog-be/src/main/resources/import/tosca/data-types/
-  Add the new node type name to the script "importNormativeTypes.py" ({gerrit sdc code}/catalog-be/src/main/resources/scripts/import/tosca ) into the array normativeTypes
(E.g. - normativeTypes = [ "root", "compute", "softwareComponent", "webServer", "webApplication", "DBMS", "database", "objectStorage", "blockStorage", "containerRuntime", "containerApplication", "loadBalancer", "port", "network","cord-evc"]).
- Run: python importDataTypes.py -i {sdc-be docker IP} -p 8080
- Run: python importNormativeTypes.py -i {sdc-be docker IP} -p 8080
 
All 2 scripts return 201 OK. In fact, in the SDC GUI I have now the ECORD NET item as VL.
 
- Create a service composed by node type before imported (cord-evc) by SDC
- Distribute it
 
Distributution fails with errors from SDNC.AAI and SO. The error is captured into sdnc-ueb container :

ERROR 2019-03-12 11:34:02.445 +0000 SdcToscaParserFactory - ####################################################################################################
ERROR 2019-03-12 11:34:02.445 +0000 SdcToscaParserFactory - ToscaTemplate - verifyTemplate - 1 Parsing Critical occurred...
ERROR 2019-03-12 11:34:02.445 +0000 SdcToscaParserFactory - JTosca Exception [JE136]: InvalidTypeError: "org.onap.datatypes.ecord.evc.type" is not a valid type. CSAR name - /opt/onap/sdnc/ueb-listener/spool/incoming/svc_20190312_evc_test_3/service-Svc20190312EvcTest3-csar.csar
ERROR 2019-03-12 11:34:02.446 +0000 SdncUebCallback - Could not create SDC TOSCA Parser 
org.onap.sdc.tosca.parser.exceptions.SdcToscaParserException: Error: CSAR file bad format. Check the log for details.
at org.onap.sdc.tosca.parser.impl.SdcToscaParserFactory.throwSdcToscaParserException(SdcToscaParserFactory.java:196)
at org.onap.sdc.tosca.parser.impl.SdcToscaParserFactory.init(SdcToscaParserFactory.java:89)
at org.onap.sdc.tosca.parser.impl.SdcToscaParserFactory.getSdcCsarHelper(SdcToscaParserFactory.java:60)
at org.onap.ccsdk.sli.northbound.uebclient.SdncUebCallback.processToscaCsar(SdncUebCallback.java:682)
at org.onap.ccsdk.sli.northbound.uebclient.SdncUebCallback.handleToscaArtifact(SdncUebCallback.java:629)
at org.onap.ccsdk.sli.northbound.uebclient.SdncUebCallback.handleSuccessfulDownload(SdncUebCallback.java:548)
at org.onap.ccsdk.sli.northbound.uebclient.SdncUebCallback.handleArtifact(SdncUebCallback.java:506)
at org.onap.ccsdk.sli.northbound.uebclient.SdncUebCallback.activateCallback(SdncUebCallback.java:306)
at org.onap.sdc.impl.NotificationConsumer.run(NotificationConsumer.java:71)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
ERROR 2019-03-12 11:34:03.449 +0000 NotificationConsumer - Error exception occured when fetching with Cambria Client:null
 


By a GET request from https://xx.xx.xx.xx:30204/sdc2/rest/v1/catalog/dataTypes/I retrieve the list of datatypes and the org.onap.datatypes.ecord.evc.type exists in the list:

   "org.onap.datatypes.ecord.evc.type": {
        "derivedFrom": {
            "name": "tosca.datatypes.Root",
            "uniqueId": "tosca.datatypes.Root.datatype",
            "description": "The TOSCA root Data Type all other TOSCA base Data Types derive from",
            "creationTime": 1550597979107,
            "modificationTime": 1550597979107,
            "toscaPresentation": {}
        },
        "properties": [
            {
                "constraints": [
                    {
                        "validValues": [
                            "POINT_TO_POINT",
                            "ROOT_MULTIPOINT",
                            "MULTIPOINT_TO_MULTIPOINT"
                        ]
                    }
                ],
                "uniqueId": "org.onap.datatypes.ecord.evc.type.datatype.EVC_type",
                "type": "string",
                "required": false,
                "definition": false,
                "defaultValue": "POINT_TO_POINT",
                "description": "E-Line, E-Tree or E-LAN (POINT_TO_POINT, ROOT_MULTIPOINT, MULTIPOINT_TO_MULTIPOINT)",
                "password": false,
                "name": "EVC_type",
                "hidden": false,
                "immutable": false,
                "toscaPresentation": {}
            }
        ],
        "name": "org.onap.datatypes.ecord.evc.type",
        "uniqueId": "org.onap.datatypes.ecord.evc.type.datatype",
        "derivedFromName": "tosca.datatypes.Root",
        "description": "ECORD EVC type",
        "creationTime": 1552222556099,
        "modificationTime": 1552222556105,
        "toscaPresentation": {}
    }

I have noted that by unzipping my service.csar (downloaded by sdc GUI) , there is no file containing my custom datatypes ( data.yml file contains only  default datatypes ).
Any suggestion how to fix this issue?


Aniello Paolo Malinconico


Re: Helm > Error: trying to send message larger than max #oom #helm #casablanca #lfn #kubernetes

David Perez Caparros
 

Hi,

removing old configmaps versions and limiting the helm history to 5-10 versions did the trick for me.


Regards
David

--
David Pérez Caparrós
Senior Innovation Engineer
Swisscom (Switzerland)

On 14 Mar 2019, at 19:37, Pérez Caparrós David, INI-EAI-INO-COW <David.PerezCaparros@...> wrote:

Hi,

I am starting to get errors like the one below when deploying/undeploying with helm, branch Casablanca, running for ~70 days.

# helm undeploy dev-sniro-emulator --purge
Error: trying to send message larger than max (23353031 vs. 20971520)

# kubectl get configmap | wc -l
286

# kubectl --namespace=kube-system get cm | wc -l
708

# helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean”}

# kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.5", GitCommit:"753b2dbc622f5cc417845f0ff8a77f539a4213ea", GitTreeState:"clean", BuildDate:"2018-11-26T14:41:50Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.5-rancher1", GitCommit:"44636ddf318af0483af806e255d0be4bb6a2e3d4", GitTreeState:"clean", BuildDate:"2018-12-04T04:28:34Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64”}

# docker -v
Docker version 17.03.2-ce, build f5ec1e2

# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            3.9G     0  3.9G   0% /dev
tmpfs           799M   79M  720M  10% /run
/dev/vda1        97G   21G   77G  22% /
tmpfs           3.9G  392K  3.9G   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
none             97G   21G   77G  22% /var/lib/docker/aufs/mnt/168af35e85e3e4df3bf740d4e9540d7f38b3fd4d7d89ed18d5dce6c3a1ac555a
shm              64M     0   64M   0% /var/lib/docker/containers/4a98d330c0febe51e82a18cf9ff4076519e62a7817a8b36b4acd4b495791de78/shm
tmpfs           799M     0  799M   0% /run/user/1000

Did anyone encounter similar issues? any suggestion?

Regards
David

--
David Pérez Caparrós
Senior Innovation Engineer
Swisscom (Switzerland)



Re: [oom] arm64 docker containers deploy

Paul Vaduva
 

Hi Gary,

 

Thank you for your answer and sorry for the late reply.

Does anyone know or know where I can find about which are the ONAP projects involved in an absolute minimal deployment of ONAP?

 

Thanks,

Paul

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Gary Wu
Sent: Friday, February 15, 2019 7:58 PM
To: onap-discuss@...; Paul Vaduva <Paul.Vaduva@...>
Cc: Mike.Elliott@...
Subject: Re: [onap-discuss][oom] arm64 docker containers deploy

 

Hi Paul,

 

We use Rancher to deploy the Kubernetes cluster on OpenStack, then use helm to deploy ONAP on the k8s cluster.  If you’re able to deploy k8s on arm64 using some other tool, you don’t need to use Rancher.


Thanks,

Gary

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Paul Vaduva
Sent: Friday, February 15, 2019 8:09 AM
To: onap-discuss@...
Cc: Mike.Elliott@...
Subject: [onap-discuss][oom] arm64 docker containers deploy

 

                Hi Guys,

 

We want to try an arm64 build of ONAP docker containers minimum deployment maybe also vFW usecase necessary docker images, and we have to deploy them on an arm64 openstack deployment environment for the integration testing vFW usecase test. I am aware that on x86_64 you use rancher to deploy but rancher does not have arm64 support, so I was wondering if we could (would be acceptable) to use helm instead. Please share with me your thoughts.

 

Best Regards,

Paul Vaduva


This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.


This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.


Re: VES collector error

Kukulski, Marek (Nokia - PL/Wroclaw)
 

Hi,

 

additionalFileds is a hashMap

According to definition

"hashMap": {

      "description": "an associative array which is an array of key:value pairs",

      "type": "object",

      "additionalProperties": {

        "type": "string"

      },

      "default": {}

    }

it should be an array and you have object. This match to error you get “

[2019-03-14 12:33:11,367][WARN ][http-nio-8080-exec-5][org.onap.dcae.restapi.VesRestController] - instance type (object) does not match any allowed primitive type (allowed: ["array"])

Try changing

{"additionalFields":{"macAddress":"01:02:03:04:05:06","softwareVersion":"1.2.3}

To

{"additionalFields":{["macAddress":"01:02:03:04:05:06","softwareVersion":"1.2.3]}

 

BR,

Marek

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Michail Salichos via Lists.Onap.Org
Sent: Thursday, March 14, 2019 1:57 PM
To: onap-discuss@...
Subject: [onap-discuss] VES collector error

 

Hi,

 

I am trying to POST a VES event (details below) and getting an error (also below). It seems it is related to not conforming with the schema version but I can't spot the problem.

 

https://wiki.onap.org/display/DW/CPE+Authentication+Notification#CPEAuthenticationNotification-CPEAuthenticationVESEvent

 

CPE authentication VES message sent:

{"event":{"commonEventHeader":{"sourceId":"","startEpochMicrosec":1.413378172E15,"eventId":"ab305d54-85b4-a31b-7db2fb6b9e546015","timeZoneOffset":"","reportingEntityId":"","internalHeaderFields":{},"eventType":"applicationNf","priority":"Normal","version":7.1,"reportingEntityName":"thirdparty-sdnc-idfromesrrequest","sequence":0,"domain":"stateChange","lastEpochMicrosec":1.413378172E15,"eventName":"StateChange_cpe_authentication","vesEventListenerVersion":"","sourceName":"pnf-1"},"stateChangeFields":{"additionalFields":{"macAddress":"01:02:03:04:05:06","softwareVersion":"1.2.3"},"oldState":"outOfService","stateChangeFieldsVersion":1,"stateInterface":"","newState":"inService"}}}

              

Schema:

https://git.onap.org/dcaegen2/collectors/ves/tree/etc/CommonEventFormat_30.0.1.json

 

VES collector logs:

[2019-03-14 12:33:11,366][WARN ][http-nio-8080-exec-5][org.onap.dcae.restapi.VesRestController] - Schema validation failed for event: {"event":{"commonEventHeader":{"sourceId":"","startEpochMicrosec":1.413378172E15,"eventId":"ab305d54-85b4-a31b-7db2fb6b9e546015","timeZoneOffset":"","reportingEntityId":"","internalHeaderFields":{},"eventType":"applicationNf","priority":"Normal","version":7.1,"reportingEntityName":"thirdparty-sdnc-idfromesrrequest","sequence":0,"domain":"stateChange","lastEpochMicrosec":1.413378172E15,"eventName":"StateChange_cpe_authentication","vesEventListenerVersion":"","sourceName":"pnf-1"},"stateChangeFields":{"additionalFields":{"macAddress":"01:02:03:04:05:06","softwareVersion":"1.2.3"},"oldState":"outOfService","stateChangeFieldsVersion":1,"stateInterface":"","newState":"inService"}}}

[2019-03-14 12:33:11,367][WARN ][http-nio-8080-exec-5][org.onap.dcae.restapi.VesRestController] - instance type (object) does not match any allowed primitive type (allowed: ["array"])

 

Error:

{"requestError":{"ServiceException":{"messageId":"SVC0002","text":"Bad Parameter (JSON does not conform to schema)"}}}

 

Michail

 


Re: Project usecase-ui - Casablanca release: container uui-server fails to start

thierry.hardy@...
 

For your information, i have performed the following actions but the final result is still the same:

-       helm undeploy onap-uui –purge

-       helm deploy onap local/onap --namespace onap -f oom/casablanca/onap-overrides.yaml

 

 

Here is the pods status:

debian@control01-onap:~$ kubectl -n onap get po

NAME                                                           READY     STATUS              RESTARTS   AGE

functest-onap-core-ttgkn                                       0/1       ContainerCreating   0          1d

functest-onap-medium-647hb                                     0/1       ContainerCreating   0          1d

identity-wrapper-5956f65f8f-wwlfc                              1/1       Running             0          27d

onap-aaf-aaf-cm-84bfb49d6-m9rrz                                1/1       Running             0          27d

onap-aaf-aaf-cs-5bf4485575-tkr98                               1/1       Running             0          27d

onap-aaf-aaf-fs-6cddb946b6-6n68n                               0/1       Init:0/2            0          6d

onap-aaf-aaf-gui-78f4895b94-n97b6                              1/1       Running             0          27d

onap-aaf-aaf-hello-7c6f76fc4c-c5bm8                            1/1       Running             0          27d

onap-aaf-aaf-locate-67d8885986-9bnzl                           1/1       Running             0          27d

onap-aaf-aaf-oauth-7b674ddcd7-mv2w7                            1/1       Running             0          8d

onap-aaf-aaf-service-555c6b5d46-529hx                          1/1       Running             55         27d

onap-aaf-aaf-sms-74449c69c7-qzt9m                              1/1       Running             0          27d

onap-aaf-aaf-sms-quorumclient-0                                1/1       Running             0          27d

onap-aaf-aaf-sms-quorumclient-1                                1/1       Running             0          27d

onap-aaf-aaf-sms-quorumclient-2                                1/1       Running             0          27d

onap-aaf-aaf-sms-vault-0                                       2/2       Running             1          27d

onap-aai-aai-5b69bb699d-mws59                                  1/1       Running             0          22m

onap-aai-aai-babel-66b4c4c5d7-gmz5r                            2/2       Running             0          27d

onap-aai-aai-cassandra-0                                       1/1       Running             0          7d

onap-aai-aai-cassandra-1                                       1/1       Running             0          27d

onap-aai-aai-cassandra-2                                       1/1       Running             0          1d

onap-aai-aai-champ-68f554bbc9-wh96d                            2/2       Running             0          27d

onap-aai-aai-data-router-868db64f98-6btp5                      2/2       Running             0          27d

onap-aai-aai-elasticsearch-68f6cdd8bb-9rbrv                    1/1       Running             0          8d

onap-aai-aai-gizmo-844cd8c5cb-dstxm                            2/2       Running             0          6d

onap-aai-aai-graphadmin-657b58bd8d-cb9z6                       2/2       Running             0          27d

onap-aai-aai-modelloader-b4b588d9-9f7xb                        2/2       Running             0          27d

onap-aai-aai-resources-89c96fccf-lxx7p                         2/2       Running             0          27d

onap-aai-aai-search-data-74c957d877-2ljrf                      2/2       Running             0          3d

onap-aai-aai-sparky-be-7688ff4875-j2r46                        2/2       Running             0          10d

onap-aai-aai-spike-687b95c774-ft5cg                            2/2       Running             0          27d

onap-aai-aai-traversal-8666bdb684-6pr7v                        2/2       Running             0          27d

onap-appc-appc-0                                               2/2       Running             0          27d

onap-appc-appc-ansible-server-59679fb8dc-kpc9s                 1/1       Running             0          14d

onap-appc-appc-cdt-d974666d7-zbcgn                             1/1       Running             0          27d

onap-appc-appc-db-0                                            1/1       Running             0          27d

onap-appc-appc-db-1                                            0/1       Init:0/1            0          6d

onap-appc-appc-db-2                                            1/1       Running             0          27d

onap-appc-appc-dgbuilder-5b95665cd4-dcjql                      1/1       Running             0          27d

onap-clamp-clamp-69d497c947-ldwss                              2/2       Running             0          27d

onap-clamp-clamp-dash-es-8699f4757d-jr7qd                      1/1       Running             0          27d

onap-clamp-clamp-dash-kibana-6b6bb95cbb-jclzt                  1/1       Running             0          27d

onap-clamp-clamp-dash-logstash-755fb4fc5b-kpsqw                1/1       Running             0          27d

onap-clamp-clampdb-d9dcdf875-vkzfh                             1/1       Running             0          27d

onap-cli-cli-7dbdd79665-sknrn                                  1/1       Running             0          3d

onap-consul-consul-6dbc6fc8-qs4lp                              1/1       Running             0          27d

onap-consul-consul-server-0                                    1/1       Running             0          7d

onap-consul-consul-server-1                                    1/1       Running             0          27d

onap-consul-consul-server-2                                    1/1       Running             0          27d

onap-contrib-netbox-app-7d466c4cf9-qfbd4                       1/1       Running             0          27d

onap-contrib-netbox-nginx-7855cbbc87-c7h7x                     1/1       Running             0          6d

onap-contrib-netbox-postgres-c9959877c-vl2c9                   1/1       Running             0          8d

onap-dcaegen2-dcae-bootstrap-68c4ccff54-7nw9j                  1/1       Running             0          27d

onap-dcaegen2-dcae-cloudify-manager-77d686c5cd-sbf77           1/1       Running             0          3d

onap-dcaegen2-dcae-db-0                                        1/1       Running             0          1d

onap-dcaegen2-dcae-db-1                                        1/1       Running             0          27d

onap-dcaegen2-dcae-healthcheck-57cdc47774-pww9k                1/1       Running             0          27d

onap-dcaegen2-dcae-pgpool-5469cccc6-9r46h                      1/1       Running             0          27d

onap-dcaegen2-dcae-pgpool-5469cccc6-wnfjh                      1/1       Running             0          27d

onap-dcaegen2-dcae-redis-0                                     1/1       Running             0          27d

onap-dcaegen2-dcae-redis-1                                     1/1       Running             0          27d

onap-dcaegen2-dcae-redis-2                                     1/1       Running             0          27d

onap-dcaegen2-dcae-redis-3                                     1/1       Running             0          1d

onap-dcaegen2-dcae-redis-4                                     1/1       Running             0          27d

onap-dcaegen2-dcae-redis-5                                     1/1       Running             0          6d

onap-dmaap-dbc-pg-0                                            1/1       Running             0          7d

onap-dmaap-dbc-pg-1                                            1/1       Running             0          27d

onap-dmaap-dbc-pgpool-546dd7b4db-5dh5p                         1/1       Running             0          3d

onap-dmaap-dbc-pgpool-546dd7b4db-6wk5b                         1/1       Running             0          27d

onap-dmaap-dmaap-bus-controller-574fd76759-vq2z9               1/1       Running             0          8d

onap-dmaap-dmaap-dr-db-698b5b56f7-786kl                        1/1       Running             0          3d

onap-dmaap-dmaap-dr-node-7bb75f57b4-nmwl4                      0/1       Running             1452       3d

onap-dmaap-dmaap-dr-prov-567fd9cf99-9k2sf                      1/1       Running             0          27d

onap-dmaap-message-router-57b9ffc7c-fgz84                      1/1       Running             0          27d

onap-dmaap-message-router-kafka-7cd5bfff7c-7l8z2               1/1       Running             0          6d

onap-dmaap-message-router-zookeeper-6657494784-8nwkj           1/1       Running             0          27d

onap-esr-esr-gui-86bd6f8d9d-f54nv                              1/1       Running             0          27d

onap-esr-esr-server-68548c74c5-rb5hr                           2/2       Running             0          3d

onap-log-log-elasticsearch-7f678d995c-2dpdg                    1/1       Running             0          27d

onap-log-log-kibana-7888fc5f67-sgcc4                           1/1       Running             0          27d

onap-log-log-logstash-59b76c4944-gxlvj                         1/1       Running             0          1d

onap-log-log-logstash-59b76c4944-lklxx                         1/1       Running             0          1d

onap-log-log-logstash-59b76c4944-lkrkx                         1/1       Running             0          1d

onap-log-log-logstash-59b76c4944-pwmjz                         1/1       Running             0          1d

onap-log-log-logstash-59b76c4944-z5qts                         1/1       Running             0          1d

onap-msb-kube2msb-567f8f64db-hlxqt                             1/1       Running             0          6d

onap-msb-msb-consul-7459669ff6-4hqmz                           1/1       Running             0          6d

onap-msb-msb-discovery-856dc454c6-r5fwl                        2/2       Running             0          27d

onap-msb-msb-eag-5d786b7b47-92z2z                              2/2       Running             0          6d

onap-msb-msb-iag-6cfd77df4c-przmw                              2/2       Running             0          6d

onap-multicloud-multicloud-685b6c5bdd-kd294                    2/2       Running             0          3d

onap-multicloud-multicloud-azure-754d68b4f7-h9tmb              0/2       ContainerCreating   0          8d

onap-multicloud-multicloud-ocata-5894c7f6df-q7r7g              2/2       Running             0          27d

onap-multicloud-multicloud-pike-6b7dc7bd94-qg8lq               2/2       Running             0          27d

onap-multicloud-multicloud-vio-5b7dd7fc4d-82spt                2/2       Running             0          27d

onap-multicloud-multicloud-windriver-58db4cd95-fhll6           2/2       Running             0          27d

onap-nbi-nbi-6bc54bb4ff-2xdjb                                  1/1       Running             0          27d

onap-nbi-nbi-mariadb-787fdb4c4b-wdz9f                          1/1       Running             0          27d

onap-nbi-nbi-mongo-0                                           1/1       Running             0          27d

onap-oof-cmso-db-0                                             1/1       Running             0          7d

onap-oof-music-cassandra-0                                     1/1       Running             0          27d

onap-oof-music-cassandra-1                                     1/1       Running             0          27d

onap-oof-music-cassandra-2                                     1/1       Running             0          27d

onap-oof-music-tomcat-c77b55754-977cv                          1/1       Running             0          3d

onap-oof-music-tomcat-c77b55754-gzjfs                          1/1       Running             0          27d

onap-oof-music-tomcat-c77b55754-m9m9s                          1/1       Running             0          27d

onap-oof-oof-58888745b4-wx8vb                                  1/1       Running             0          3d

onap-oof-oof-cmso-service-c69dd6dfb-zml7l                      1/1       Running             0          6d

onap-oof-oof-has-api-6cb6b6774d-s5jjg                          1/1       Running             0          27d

onap-oof-oof-has-controller-74fb65bfb9-4w56m                   1/1       Running             0          3d

onap-oof-oof-has-data-756c4fb97-zh25l                          1/1       Running             0          27d

onap-oof-oof-has-reservation-5b5957f7c7-tvgl2                  1/1       Running             0          27d

onap-oof-oof-has-solver-6479475c76-54clp                       1/1       Running             0          27d

onap-oof-zookeeper-0                                           1/1       Running             0          27d

onap-oof-zookeeper-1                                           1/1       Running             0          27d

onap-oof-zookeeper-2                                           1/1       Running             0          1d

onap-policy-brmsgw-69bccbcb7d-46jc6                            1/1       Running             0          27d

onap-policy-drools-0                                           1/1       Running             0          27d

onap-policy-nexus-65dc5cf84d-hlcnn                             1/1       Running             0          27d

onap-policy-pap-6d88dfdf97-lml78                               2/2       Running             0          27d

onap-policy-pdp-0                                              2/2       Running             0          27d

onap-policy-policy-apex-pdp-0                                  1/1       Running             0          27d

onap-policy-policy-distribution-547584bc46-ds7wx               1/1       Running             0          27d

onap-policy-policydb-794676d674-5wwjx                          1/1       Running             0          27d

onap-pomba-pomba-aaictxbuilder-5f8fb6c7b4-55p2s                2/2       Running             0          3d

onap-pomba-pomba-contextaggregator-7d74476d49-j44sh            1/1       Running             0          27d

onap-pomba-pomba-data-router-6794b78d59-srxhj                  1/1       Running             0          27d

onap-pomba-pomba-elasticsearch-569c4cd95f-6kb5h                1/1       Running             0          27d

onap-pomba-pomba-kibana-595c775664-g7pxk                       1/1       Running             0          27d

onap-pomba-pomba-networkdiscovery-5957c56bcc-7pmcf             2/2       Running             0          27d

onap-pomba-pomba-networkdiscoveryctxbuilder-6bf8dccf8f-pvq4j   2/2       Running             0          3d

onap-pomba-pomba-sdcctxbuilder-77d67bcf7b-qvvc2                0/1       CrashLoopBackOff    3366       8d

onap-pomba-pomba-search-data-588b9bcd76-p5rzr                  2/2       Running             0          27d

onap-pomba-pomba-servicedecomposition-6855c5f96f-wjzg7         1/2       Running             2852       6d

onap-pomba-pomba-validation-service-bc7f558dc-n7pzj            1/1       Running             0          27d

onap-portal-portal-app-65df4b59ff-h8ktv                        2/2       Running             0          27d

onap-portal-portal-cassandra-5c66f77c5b-xf2c7                  1/1       Running             0          3d

onap-portal-portal-db-7b97bd54db-9r86q                         1/1       Running             0          3d

onap-portal-portal-sdk-f48dff775-6gs9t                         2/2       Running             0          27d

onap-portal-portal-widget-674cfcb567-zrvff                     0/1       Running             9671       23d

onap-portal-portal-zookeeper-6c55dcb4cc-t55sm                  1/1       Running             0          27d

onap-robot-robot-7b6d6c6796-cvthq                              1/1       Running             0          8d

onap-sdc-sdc-be-ddb4f6849-8qvqm                                2/2       Running             0          27d

onap-sdc-sdc-cs-67b94cb4cf-vkgw8                               1/1       Running             0          27d

onap-sdc-sdc-dcae-be-5f4b79dcb4-9flpk                          2/2       Running             0          27d

onap-sdc-sdc-dcae-dt-df64c6dcc-pkhd5                           2/2       Running             0          27d

onap-sdc-sdc-dcae-fe-6875c75df5-7z44z                          2/2       Running             0          27d

onap-sdc-sdc-dcae-tosca-lab-899f7d547-mvg4k                    2/2       Running             0          8d

onap-sdc-sdc-es-7b678bf896-9l74n                               1/1       Running             0          27d

onap-sdc-sdc-fe-5cb8b89b-7p4ds                                 2/2       Running             0          27d

onap-sdc-sdc-kb-669f9cc784-dt6sl                               1/1       Running             0          27d

onap-sdc-sdc-onboarding-be-6f7d9ccc9b-42fgl                    2/2       Running             0          27d

onap-sdc-sdc-wfd-be-849684d479-bnqng                           1/1       Running             0          27d

onap-sdc-sdc-wfd-fe-6b479fd4db-wwngq                           2/2       Running             0          27d

onap-sdnc-controller-blueprints-68fd86967b-grgkx               1/1       Running             0          27d

onap-sdnc-controller-blueprints-db-0                           1/1       Running             0          27d

onap-sdnc-nengdb-0                                             1/1       Running             0          27d

onap-sdnc-network-name-gen-df59754f-xr59j                      1/1       Running             0          27d

onap-sdnc-sdnc-0                                               2/2       Running             0          27d

onap-sdnc-sdnc-ansible-server-b96cdd9cc-vhlp9                  1/1       Running             0          6d

onap-sdnc-sdnc-db-0                                            2/2       Running             0          27d

onap-sdnc-sdnc-dgbuilder-55c4ccd464-rpjcs                      1/1       Running             0          8d

onap-sdnc-sdnc-dmaap-listener-bf9c8d5cb-5bz9m                  1/1       Running             0          6d

onap-sdnc-sdnc-portal-5bff95fffd-5b467                         1/1       Running             0          27d

onap-sdnc-sdnc-ueb-listener-f96c69df5-dm9rh                    1/1       Running             2          27d

onap-sniro-emulator-sniro-emulator-769fcc8cd-fhcgq             1/1       Running             0          3d

onap-so-so-bdcf9fc8b-25sdp                                     1/1       Running             0          8d

onap-so-so-bpmn-infra-79c949d54d-mm6m4                         1/1       Running             0          6d

onap-so-so-catalog-db-adapter-694c4c6665-9whsq                 1/1       Running             0          27d

onap-so-so-mariadb-6c497df4f8-swc2v                            1/1       Running             0          27d

onap-so-so-monitoring-7dbc566648-c69j8                         1/1       Running             0          27d

onap-so-so-openstack-adapter-689b79856f-bfwqg                  1/1       Running             0          14d

onap-so-so-request-db-adapter-7db869f8b5-2557f                 1/1       Running             0          3d

onap-so-so-sdc-controller-797795b49f-kbczk                     1/1       Running             0          27d

onap-so-so-sdnc-adapter-d4745f87d-67j8t                        1/1       Running             0          6d

onap-so-so-vfc-adapter-6fd676b55d-5ftdq                        1/1       Running             0          27d

onap-uui-uui-7df8dfdd65-v9c92                                  1/1       Running             0          20m

onap-uui-uui-server-64bf85dc6d-sqwld                           0/1       CrashLoopBackOff    6          20m

onap-vfc-vfc-catalog-7df87b9596-mnwgx                          2/2       Running             0          27d

onap-vfc-vfc-db-7f8f9dff4b-c7sv7                               1/1       Running             0          27d

onap-vfc-vfc-ems-driver-d587cfc4f-ln7rt                        1/1       Running             0          27d

onap-vfc-vfc-generic-vnfm-driver-89d6cf8d4-4gkql               2/2       Running             0          18h

onap-vfc-vfc-huawei-vnfm-driver-7c6d75d468-gqnt9               2/2       Running             0          27d

onap-vfc-vfc-juju-vnfm-driver-f9db59775-rdth7                  2/2       Running             0          27d

onap-vfc-vfc-multivim-proxy-7dbbd7f8c7-v92pb                   1/1       Running             0          27d

onap-vfc-vfc-nokia-v2vnfm-driver-6f7b4fdfcf-8cfhr              1/1       Running             0          27d

onap-vfc-vfc-nokia-vnfm-driver-6cfd6ccf44-7p7ld                2/2       Running             0          3d

onap-vfc-vfc-nslcm-c9c694465-45wz7                             2/2       Running             0          8d

onap-vfc-vfc-resmgr-859cd655d6-flm4h                           2/2       Running             0          27d

onap-vfc-vfc-vnflcm-7c8c49664b-h9jrb                           2/2       Running             0          27d

onap-vfc-vfc-vnfmgr-5c657666d4-tv6pr                           2/2       Running             0          27d

onap-vfc-vfc-vnfres-566cf84d9c-s5mdk                           2/2       Running             0          27d

onap-vfc-vfc-workflow-74b4d6887-4znms                          1/1       Running             0          27d

onap-vfc-vfc-workflow-engine-8f96f546c-r4nq5                   1/1       Running             0          8d

onap-vfc-vfc-zte-sdnc-driver-698585fdf-8xw64                   1/1       Running             0          27d

onap-vfc-vfc-zte-vnfm-driver-54c46bfcc5-xqxc6                  2/2       Running             0          6d

onap-vid-vid-dd46c8bf-8chxl                                    2/2       Running             0          6d

onap-vid-vid-mariadb-galera-0                                  1/1       Running             0          27d

onap-vnfsdk-vnfsdk-868b5459b7-v8qzn                            1/1       Running             0          3d

onap-vnfsdk-vnfsdk-pgpool-654fbdc7f-6w46n                      1/1       Running             0          3d

onap-vnfsdk-vnfsdk-pgpool-654fbdc7f-pjzsf                      1/1       Running             0          8d

onap-vnfsdk-vnfsdk-postgres-0                                  1/1       Running             0          27d

onap-vnfsdk-vnfsdk-postgres-1                                  1/1       Running             0          6d

debian@control01-onap:~$

 

Are there some dependencies with other pods that are not in running status?

 

Regards

Thierry

 

De : HARDY Thierry TGI/OLN
Envoyé : vendredi 15 mars 2019 09:29
À : 'shentao'; onap-discuss@...
Cc : guochuyi@...
Objet : RE: [onap-discuss] Project usecase-ui - Casablanca release: container uui-server fails to start

 

Hi,

Thank you for your answer

I use the images from Casablanca maintenance release.

debian@control01-onap:~$ kubectl -n onap get deployment -l release=onap-uui -o yaml|grep image:

          image: nexus3.onap.org:10001/onap/usecase-ui:1.2.2

          image: nexus3.onap.org:10001/onap/usecase-ui-server:1.2.1

 

What is the recommended update procedure to update these images and to clean all relevant kubernetes objects?

How to remove UUI deployment ? Helm undeploy onap-uui?

But how to reinstall it ?  

Regards

Thierry

 

De : shentao [mailto:shentao@...]
Envoyé : vendredi 15 mars 2019 01:49
À : onap-discuss@...; HARDY Thier
ry TGI/OLN
Cc : guochuyi@...
Objet :
答复: [onap-discuss] Project usecase-ui - Casablanca release: container uui-server fails to start

 

Hi Thierry

 

I suggest that you use below images or the latest images.

onap/usecase-ui                         1.2.2

onap/usecase-ui-server            1.2.1

 

Best regards,

Tao

 

 

发件人: onap-discuss@... [mailto:onap-discuss@...] 代表 thierry.hardy@...
发送时间: 2019314 22:47
收件人: onap-discuss@...
抄送: guochuyi@...
主题: Re: [onap-discuss] Project usecase-ui - Casablanca release: container uui-server fails to start

 

Hi,

I’m using Orange OpenLab that uses Casablanca release. The last upgrade on this lab was around mid February this year.

 

The uui-server is not up and so I’m not able to load any csar artifact from the gui.

debian@control01-onap:~$ kubectl -n onap get po|grep uui

onap-uui-uui-7df8dfdd65-6tb6r                                  1/1       Running             0          27m

onap-uui-uui-server-5b655bdf94-nr75g                           0/1       CrashLoopBackOff    5          23m

 

I tried to delete the uui pods, to remove and reinstall the uui deployments but I get always the same result.

May you help me indicating which logs may I inspect to identify and solve this operational problem?

 

On another onap Casablanca environment that is daily installed, the uui-server pod is up and running.

 

Regards

Thierry

Orange Network Architect

_________________________________________________________________________________________________________________________
 
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.

_________________________________________________________________________________________________________________________

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.


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

Calamita Agostino
 

Hi Brian,

I fixed this problem a few days ago. As you say, I changed dmaap zookeeper image version with

 

image: cdposs/zookeeper:3.4.9

 

and SDC and DMAAP connection now is UP.

 

But now, I have another issue during creating a new instance of a Service, when I try to “Add a node instance” from “View/Edit Service Instance” VID GUI, I get this error: “MSO failure - see log below for details”.

 

In application.log under /opt/app/vid/logs/vid directory, I found this error:

Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: https://portal-app:8443/ONAPPORTAL/auxapi/v3/getSessionSlotCheckInterval

 

As Stern Ittay wrote, a similar case is tracked in https://jira.onap.org/browse/PORTAL-530 and https://jira.onap.org/browse/VID-439

Issue should be resolved soon.

 

Thanks.

Agos

 

 

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

 

Agos,

 

Dont know if you upgraded to MR1 and finally fixed this problem.

 

3.0.1-ONAP OOM helm charts and DMaaP images should work for distribution.

We did find that in Casablanca that the zookeeper image we pull from docker.io changed and broke our distribution (it had been the same image for 2 years and we hadnt caught that it had a :latest tag).

 

https://jira.onap.org/browse/SDC-2058 has details but if you are still running the 3.0.0-ONAP helm charts then you want to change the image tag reference for zookeeper to the 3.4.9 reference (and repo)

 

If you are on 3.0.1-ONAP , the helm charts and DMaaP will use the onap/dmaap/zookeeper version so we dont run into that is in the future.

 

Hopefully you had already upgraded to 3.0.1-ONAP

 

Brian

 

 

From: Calamita Agostino <agostino.calamita@...>
Sent: Wednesday, March 06, 2019 3:50 AM
To: FREEMAN, BRIAN D <bf1936@...>; 'onap-discuss@...' <onap-discuss@...>
Subject: R: R: [onap-discuss] dmaap-message-router NodePort not recheable

 

Hi Brian,

docker manifest file I found under Casablanca release (https://github.com/onap/integration/blob/3.0.1-ONAP/version-manifest/src/main/resources/docker-manifest.csv ) for SDC and DMaaP components, has the same image version number of my environment:

 

SDC 1.3.6

dmaap/datarouter-node,1.0.3

dmaap/datarouter-prov,1.0.3

dmaap/dmaap-mr,1.1.8

 

So, which docker manifest file have I apply to get newer images ? 

 

I saw that docker manifest under master has newer dmaap image

 

dmaap/datarouter-node,2.0.1

dmaap/datarouter-prov,2.0.1

dmaap/dmaap-mr,1.1.9

 

but older SDC version 1.3.4

 

Thanks

 

Agos

 

 

 

Da: FREEMAN, BRIAN D [mailto:bf1936@...]
Inviato: martedì 5 marzo 2019 14:47
A: Calamita Agostino <agostino.calamita@...>; 'onap-discuss@...' <onap-discuss@...>
Oggetto: Re: R: [onap-discuss] dmaap-message-router NodePort not recheable

 

Make sure to apply the docker manifest update to image tags

 

 

 

Sent via the Samsung Galaxy S8, an AT&T 5G Evolution smartphone

 

 

-------- Original message --------

From: Calamita Agostino <agostino.calamita@...>

Date: 3/5/19 3:53 AM (GMT-05:00)

To: "FREEMAN, BRIAN D" <bf1936@...>, "'onap-discuss@...'" <onap-discuss@...>

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

 

Thanks Brian.

 

To use 3.0.1-ONAP can I clone oom release as in onap.readthedocs.io documentation, under “OOM Quick Start Guide”,

 

git clone -b casablanca http://gerrit.onap.org/r/oom

 

or is there another command / repository ?

 

Agos

 

Da: FREEMAN, BRIAN D [mailto:bf1936@...]
Inviato: lunedì 4 marzo 2019 15:55
A: Calamita Agostino <agostino.calamita@...>; 'onap-discuss@...' <onap-discuss@...>
Oggetto: RE: [onap-discuss] dmaap-message-router NodePort not recheable

 

Agos.,

 

Make sure you are using 3.0.1-ONAP (Maintenance release)

 

That being said – the SDC team thinks its the timing issue. DMaaP has to be up (and clean dockerdata-nfs) before SDC.

 

Brian

 

 

 

From: FREEMAN, BRIAN D
Sent: Monday, March 04, 2019 9:31 AM
To: Calamita Agostino <agostino.calamita@...>; onap-discuss@...
Subject: RE: [onap-discuss] dmaap-message-router NodePort not recheable

 

Hmm

 

Those two SDC-BE messages are for clients trying to register so I think that is expected until SDC registers with DMaaP/MR.

Is there  a SDC-BE errror on its communication with DMaaP/MR ?

 

The other thing to try is a redeploy of dev-dmaap (remove dockerdata-nfs/dev-dmaap to clean out the topic registrations)

And dev-sdc (again just to start them fresh)

 

Brian

 

 

 

From: Calamita Agostino <agostino.calamita@...>
Sent: Monday, March 04, 2019 5:21 AM
To: FREEMAN, BRIAN D <bf1936@...>; onap-discuss@...
Subject: R: [onap-discuss] dmaap-message-router NodePort not recheable

 

Hi, after redeploy of SDC, healtcheck return “Dmaap: None” in SDC health Check, and Distribution of a Service returns POL5000 error.

 

In SDC-FE error log files I see:

 

2019-03-04T09:52:38.847Z        [qtp215145189-44]       INFO    o.o.sdc.fe.servlets.FeProxyServlet      timer=12        ErrorCategory=INFO      RequestId=null ServiceName=SDC catalog serviceInstanceID=null  ErrorCode=0     uuid=599a9bb3-d3c8-4cea-a926-ea6a11762a63       userId=op0001   localAddr=10.42.236.172        remoteAddr=10.42.98.28  SC="500"

 

 

And in SDC-BE error log file I see these messages:

 

2019-03-04T10:15:21.209Z        [qtp215145189-16]       INFO    o.o.sdc.be.filters.BeServletFilter      AuditMessage=ACTION = "HttpAuthentication" URL = "v1/registerForDistribution" USER = "clamp" AUTH_STATUS = "AUTH_SUCCESS" REALM = "ASDC"       AlertSeverity=0 ElapsedTime=96  EndTimestamp=2019-03-04 10:15:21.208Z  auditOn=false   ServerFQDN=dev-sdc-sdc-be-656bd64b9b-5b89b      StatusCode=ERROR        timer=96        ServiceInstanceId=null  ClassName=org.openecomp.sdc.be.filters.BeServletFilter ResponseDescription=Internal Server Error       ResponseCode=500        InstanceUUID=clamp      RequestId=8c56c7a2-da62-4598-963d-b5ed13673fce PartnerName=Apache-HttpClient/4.5.6 (Java/1.8.0_181)    TargetEntity=registerInDistributionEngine       CustomField1=POST: https://sdc-be.onap:8443/sdc/v1/registerForDistribution     CustomField2=500        AuditBeginTimestamp=2019-03-04 10:15:21.112Z    RemoteHost=10.42.216.84        ErrorCategory=INFO      ServerIPAddress=10.42.13.89     ServiceName=/v1/registerForDistribution ErrorCode=0     POST /sdc/v1/registerForDistribution HTTP/1.1 SC="500"

 

2019-03-04T10:15:24.740Z        [qtp215145189-20]       ERROR   o.o.s.c.config.EcompErrorLogUtil        alarmSeverity=MAJOR     AuditBeginTimestamp=2019-03-04 10:15:24.690Z   AuditMessage=ACTION = "HttpAuthentication" URL = "v1/registerForDistribution" USER = "policy" AUTH_STATUS = "AUTH_SUCCESS" REALM = "ASDC"      RequestId=ab5939bb-6780-42e7-b63a-54381b74c352  ErrorCategory=ERROR     ServerIPAddress=10.42.13.89     ServiceName=/v1/registerForDistribution        ErrorCode=500   PartnerName=Apache-HttpClient/4.5.5 (Java/1.8.0_171)    auditOn=true    ServerFQDN=dev-sdc-sdc-be-656bd64b9b-5b89b    TargetEntity=registerInDistributionEngine        Error occured in Distribution Engine. Failed operation: registration validation failed

 

 

Any other check to do ?

 

Thank.

Agos.

 

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

 

I’d do a helm delete dev-sdc –purge

Delete /dockerdata-nfs/dev-so

Configm pv/pvc/pod are gone

Then

 

helm deploy dev-sdc local/onap -f /root/oom/kubernetes/onap/resources/environments/public-cloud.yaml -f /root/integration-override.yaml --namespace onap  --verbose

 

(or whatever your override files are)

 

Looks like SDC came up before dmaap and is confused.

 

There are some less intrusive things to try but you need SDC to Pass Health Check (with DMaaP Up from its perspective)

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

 

 

Brian

 

 

From: Calamita Agostino <agostino.calamita@...>
Sent: Friday, March 01, 2019 9:30 AM
To: FREEMAN, BRIAN D <bf1936@...>; onap-discuss@...
Subject: R: [onap-discuss] dmaap-message-router NodePort not recheable

 

It works.

 

curl -X POST http://138.132.168.85:30227/events/TEST_TOPIC -H 'cache-control: no-cache'   -H 'content-type: application/json'  -H 'postman-token: 1c679102-85e8-f1a2-e708-3e6d84f8ea06' -d '{ "test": "success",                "timestamp": "1/1/2020" }'

{

    "serverTimeMs": 1,

    "count": 1

 

curl -X GET 'http://138.132.168.85:30227/events/TEST_TOPIC/g1/c3?timeout=5000' -H 'accept: application/json'  -H 'cache-control: no-cache'  -H 'postman-token: 04778117-fd44-0cac-b70c-ef2a2c3024af'                       

["{\"test\":\"success\",\"timestamp\":\"1/1/2020\"}"]

 

Agos.

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

 

Casablanca.

 

OK

 

Use curl or POSTMAN to write to a TEST_TOPIC (unauthenticated topics are created on demand)

(replace 10.12.5.13 with one of your k8 host IPs) – dont need the postman-token and modify for your environment and preferences etc.

 

curl -X POST \

  http://10.12.5.13:30227/events/TEST_TOPIC \

  -H 'cache-control: no-cache' \

  -H 'content-type: application/json' \

  -H 'postman-token: 1c679102-85e8-f1a2-e708-3e6d84f8ea06' \

  -d '{ "test": "success",

               "timestamp": "1/1/2020"

}'

 

The do a GET

 

curl -X GET \

  'http://10.12.5.13:30227/events/TEST_TOPIC/g1/c3?timeout=5000' \

  -H 'accept: application/json' \

  -H 'cache-control: no-cache' \

  -H 'postman-token: 04778117-fd44-0cac-b70c-ef2a2c3024af'

 

 

You should get the test/timestamp object back on the GET (have to execute the POST/GET twice on the initial topic create)

 

This is to confirm that Mesage Router is internally talking to itself correctly.

 

 

Brian

 

From: Calamita Agostino <agostino.calamita@...>
Sent: Friday, March 01, 2019 9:13 AM
To: FREEMAN, BRIAN D <bf1936@...>; onap-discuss@...
Subject: R: [onap-discuss] dmaap-message-router NodePort not recheable

 

This is the output:

 

Executing robot tests at log level TRACE

[ ERROR ] Suite 'Testsuites' contains no tests with tag 'healthmr'.

 

Try --help for usage information.

command terminated with exit code 252

 

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

 

Please try ./ete-k8s.sh onap healthmr

 

From: Calamita Agostino <agostino.calamita@...>
Sent: Friday, March 01, 2019 9:09 AM
To: FREEMAN, BRIAN D <bf1936@...>; onap-discuss@...
Subject: R: [onap-discuss] dmaap-message-router NodePort not recheable

 

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/

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/

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: Project usecase-ui - Casablanca release: container uui-server fails to start

thierry.hardy@...
 

Hi,

Thank you for your answer

I use the images from Casablanca maintenance release.

debian@control01-onap:~$ kubectl -n onap get deployment -l release=onap-uui -o yaml|grep image:

          image: nexus3.onap.org:10001/onap/usecase-ui:1.2.2

          image: nexus3.onap.org:10001/onap/usecase-ui-server:1.2.1

 

What is the recommended update procedure to update these images and to clean all relevant kubernetes objects?

How to remove UUI deployment ? Helm undeploy onap-uui?

But how to reinstall it ?  

Regards

Thierry

 

De : shentao [mailto:shentao@...]
Envoyé : vendredi 15 mars 2019 01:49
À : onap-discuss@...; HARDY Thier
ry TGI/OLN
Cc : guochuyi@...
Objet :
答复: [onap-discuss] Project usecase-ui - Casablanca release: container uui-server fails to start

 

Hi Thierry

 

I suggest that you use below images or the latest images.

onap/usecase-ui                         1.2.2

onap/usecase-ui-server            1.2.1

 

Best regards,

Tao

 

 

发件人: onap-discuss@... [mailto:onap-discuss@...] 代表 thierry.hardy@...
发送时间: 2019314 22:47
收件人: onap-discuss@...
抄送: guochuyi@...
主题: Re: [onap-discuss] Project usecase-ui - Casablanca release: container uui-server fails to start

 

Hi,

I’m using Orange OpenLab that uses Casablanca release. The last upgrade on this lab was around mid February this year.

 

The uui-server is not up and so I’m not able to load any csar artifact from the gui.

debian@control01-onap:~$ kubectl -n onap get po|grep uui

onap-uui-uui-7df8dfdd65-6tb6r                                  1/1       Running             0          27m

onap-uui-uui-server-5b655bdf94-nr75g                           0/1       CrashLoopBackOff    5          23m

 

I tried to delete the uui pods, to remove and reinstall the uui deployments but I get always the same result.

May you help me indicating which logs may I inspect to identify and solve this operational problem?

 

On another onap Casablanca environment that is daily installed, the uui-server pod is up and running.

 

Regards

Thierry

Orange Network Architect

_________________________________________________________________________________________________________________________
 
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.

_________________________________________________________________________________________________________________________

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.


Re: 答复: #vnfrqts, #vnfsdk #CVC VNF Certification scope at ONS #vnfsdk #cvc

Gaoweitao(Victor)
 

Hi Steven,

 

                Currently, the number of VNFSDK test cases is around 30, you can find the detail here: https://wiki.onap.org/pages/viewpage.action?pageId=45297965. All of these  requirements will be implemented before ONS.

 

BR

Victor

 

发件人: WRIGHT, STEVEN A [mailto:sw3588@...]
发送时间: 2019313 23:23
收件人: Gaoweitao (Victor, Cloudify Network OSDT) <victor.gao@...>; Lincoln Lavoie <lylavoie@...>; Heather Kirksey (hkirksey@...) <hkirksey@...>
抄送: onap-discuss <onap-discuss@...>; compliance@...; HALLAHAN, RYAN <rh173x@...>; LEFEVRE, CATHERINE <catherine.lefevre@...>
主题: #vnfrqts, #vnfsdk #CVC VNF Certification scope at ONS

 

From previous discussions on VNF certification, I understand we have an intent to make some announcement about VNF Certification at ONS.

 

From VNFRQTS project, I owe an update to ONAP TSC on status of VNF certification for ONAP. I’d like to use that to get the ONAP TSC approval.

I’d like to use the attached slide as the basis for that ONAP TSC discussion.

 

Victor,

Can you provide updated numbers for the number of TOSCA related VNF requirements and tests  coming from VNFSDK that will be available then?

 

Heather/ Lincoln,

Can you provide a date as to when this program would become live from LF perspective ?

 

Any other aspects that we need to add/delete/change in the content on the slide ?

I’d like to get this to the ONAP TSC for their 3/21 meeting so we can get this out of the way before ONS.

 

Once approved by the ONAP TSC, We can get then get the slide prettier with the right logos etc and sort out the event presentation mechanics.

 

best regards
Steven Wright, MBA, PhD, JD.

Tech Integration

AT&T Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319

 


Re: 答复: [onap-discuss] Project usecase-ui - Casablanca release: container uui-server fails to start

Shen Tao <shentao@...>
 

Hi Thierry

 

I suggest that you use below images or the latest images.

onap/usecase-ui                         1.2.2

onap/usecase-ui-server            1.2.1

 

Best regards,

Tao

 

 

发件人: onap-discuss@... [mailto:onap-discuss@...] 代表 thierry.hardy@...
发送时间: 2019314 22:47
收件人: onap-discuss@...
抄送: guochuyi@...
主题: Re: [onap-discuss] Project usecase-ui - Casablanca release: container uui-server fails to start

 

Hi,

I’m using Orange OpenLab that uses Casablanca release. The last upgrade on this lab was around mid February this year.

 

The uui-server is not up and so I’m not able to load any csar artifact from the gui.

debian@control01-onap:~$ kubectl -n onap get po|grep uui

onap-uui-uui-7df8dfdd65-6tb6r                                  1/1       Running             0          27m

onap-uui-uui-server-5b655bdf94-nr75g                           0/1       CrashLoopBackOff    5          23m

 

I tried to delete the uui pods, to remove and reinstall the uui deployments but I get always the same result.

May you help me indicating which logs may I inspect to identify and solve this operational problem?

 

On another onap Casablanca environment that is daily installed, the uui-server pod is up and running.

 

Regards

Thierry

Orange Network Architect

_________________________________________________________________________________________________________________________
 
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 Helpdesk #69762] [linuxfoundation.org #69762] 答复: [onap-discuss] Ownership of UUI repo?

Kenny Paul via RT
 

Hi Sylvain



Yes, UUI project doesn’t exist that yaml file.

I will add that file and update committers this week.

As PTL of UUI project, I will assign all JIRA tasks.



Best regards,

Tao





发件人: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] 代表 Sylvain Desbureaux
发送时间: 2019年3月13日 18:03
收件人: Jessica Wagantall; Jessica Wagantall via RT
抄送: onap-discuss@lists.onap.org
主题: [onap-discuss] Ownership of UUI repo?



Hello,

In most of the repo, there’s an “INFO.yaml” file which show who’s the responsible for the repo.

In usecase-ui, there’s no such file.

So, who to assign when filling a JIRA?



Regards,



--

<http://www.orange.com/> cid:image001.png@01D33D23.D1353070



Sylvain Desbureaux

Senior Automation Architect

ORANGE/IMT/OLN/CNC/NCA/SINA



Fixe : +33 2 96 07 13 80 <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2096%2007%2013%2080>

Mobile : +33 6 71 17 25 57 <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2071%2017%2025%2057>

sylvain.desbureaux@orange.com



_________________________________________________________________________________________________________________________

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.


Re: 答复: [onap-discuss] Ownership of UUI repo?

Shen Tao <shentao@...>
 

Hi Sylvain

 

Yes, UUI project doesn’t exist that yaml file.

I will add that file and update committers this week.

As PTL of UUI project, I will assign all JIRA tasks.

 

Best regards,

Tao

 

 

发件人: onap-discuss@... [mailto:onap-discuss@...] 代表 Sylvain Desbureaux
发送时间: 2019313 18:03
收件人: Jessica Wagantall; Jessica Wagantall via RT
抄送: onap-discuss@...
主题: [onap-discuss] Ownership of UUI repo?

 

Hello,

In most of the repo, there’s an “INFO.yaml” file which show who’s the responsible for the repo.

In usecase-ui, there’s no such file.

So, who to assign when filling a JIRA?

 

Regards,

 

-- 

 

Sylvain Desbureaux

Senior Automation Architect

ORANGE/IMT/OLN/CNC/NCA/SINA

 

Fixe : +33 2 96 07 13 80

Mobile : +33 6 71 17 25 57

sylvain.desbureaux@...

 

_________________________________________________________________________________________________________________________
 
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.


Re: Unable to test schema change in AAI - Master branch #aai

Keong Lim
 

If you want to be notified of gerrit reviews, goto https://gerrit.onap.org/r/#/settings/projects and register for aai/schema-service project

 

 

From: udhayachandran.m via lists.onap.org [mailto:udhayachandran.m=verizon.com@...]
Sent: Thursday, 14 March 2019 17:07
To: Keong Lim <Keong.Lim@...>; onap-discuss@...
Subject: Re: [onap-discuss] Unable to test schema change in AAI - Master branch #aai

 

Thanks Keong for the support.

since the changes for schema-service is still ongoing, where can i keep track of the completion of the changes, So that it will  be helpful to integrate the schema addition changes in master code.

Regards,
Udhay


Re: [AAI] [portal] Problem accessing AAI GUI from ONAP Portal

Keong Lim
 

I think you are missing sparky-fe (the front end part).

 

 

From: Thiriloshini.ThoppeKrishnakumar@... [mailto:Thiriloshini.ThoppeKrishnakumar@...]
Sent: Thursday, 14 March 2019 15:11
To: onap-discuss@...; Keong Lim <Keong.Lim@...>
Cc: Ravi.Rao@...
Subject: [onap-discuss] [AAI] [portal] Problem accessing AAI GUI from ONAP Portal

 

Hi All,

 

I have a ONAP cluster (Casablanca) with components aai, aaf, dmaap, esr, msb, portal, sdnc,sdc up and running.

 

I have the below VMs spun up using openstack

 

onap-k8s-vm-2: 10.1.8.106, onap-k8s-vm-3: 10.1.8.112 , rancher-vm: 10.1.8.102

 

Used OOM kubernetes installation (Casablanca).

 

The aai and portal pods are listed below.

 

demo-aai-aai-78947bf888-phmtp                          1/1       Running            0          5h        10.42.67.242    onap-k8s-vm-2

demo-aai-aai-babel-5499b48894-z4lnh                    2/2       Running            0          5h        10.42.92.245    onap-k8s-vm-3

demo-aai-aai-cassandra-0                               1/1       Running            0          5h        10.42.4.75      onap-k8s-vm-3

demo-aai-aai-cassandra-1                               1/1       Running            1          5h        10.42.96.142    onap-k8s-vm-2

demo-aai-aai-cassandra-2                               1/1       Running            0          5h        10.42.218.142   onap-k8s-vm-3

demo-aai-aai-champ-75f5d6f664-c556b                    2/2       Running            0          5h        10.42.41.229    onap-k8s-vm-3

demo-aai-aai-data-router-94f79b78f-n75cf               2/2       Running            6          5h        10.42.64.204    onap-k8s-vm-3

demo-aai-aai-elasticsearch-f868cff98-8m4f6             1/1       Running            0          5h        10.42.25.95     onap-k8s-vm-3

demo-aai-aai-gizmo-7b6ff8f6f-w6vzr                     2/2       Running            0          5h        10.42.97.228    onap-k8s-vm-2

demo-aai-aai-graphadmin-8485cd6c85-c6q7x               2/2       Running            0          5h        10.42.218.225   onap-k8s-vm-3

demo-aai-aai-modelloader-77496bd596-xfmtw              2/2       Running            0          5h        10.42.47.168    onap-k8s-vm-2

demo-aai-aai-resources-6d8d78cb-7rzrn                  2/2       Running            0          5h        10.42.201.208   onap-k8s-vm-3

demo-aai-aai-search-data-5d7fc5cc8c-rjw4f              2/2       Running            0          5h        10.42.227.143   onap-k8s-vm-2

demo-aai-aai-sparky-be-6598bf956c-6668p                2/2       Running            0          5h        10.42.103.166   onap-k8s-vm-3

demo-aai-aai-spike-6546658f99-s2htz                    2/2       Running            0          5h        10.42.166.102   onap-k8s-vm-2

 

demo-portal-portal-app-5c8cb9cd58-plbdn                2/2       Running            0          5h        10.42.157.147   onap-k8s-vm-3

demo-portal-portal-cassandra-6f67d869d4-hnq2g          1/1       Running            0          5h        10.42.162.112   onap-k8s-vm-2

demo-portal-portal-db-7f8b57d6b9-pdrm4                 1/1       Running            0          5h        10.42.225.15    onap-k8s-vm-3

demo-portal-portal-sdk-58cd77bc98-qxkt9                2/2       Running            0          5h        10.42.145.105   onap-k8s-vm-2

demo-portal-portal-widget-79c4f84f66-4vp79             1/1       Running            0          5h        10.42.200.73    onap-k8s-vm-3

demo-portal-portal-zookeeper-88656b6b9-jrpps           1/1       Running            0          5h        10.42.8.146     onap-k8s-vm-3

 

The services of aai and portal are given below

 

aai                        NodePort       10.43.195.83    <none>                  8080:30232/TCP,8443:30233/TCP                                 5h

aai-babel                  NodePort       10.43.216.104   <none>                  9516:30279/TCP                                                5h

aai-cassandra              ClusterIP      None            <none>                  9042/TCP,9160/TCP,61621/TCP                                   5h

aai-champ                  NodePort       10.43.165.28    <none>                  9522:30278/TCP                                                5h

aai-crud-service           NodePort       10.43.27.195    <none>                  9520:30268/TCP                                                5h

aai-elasticsearch          ClusterIP      None            <none>                  9200/TCP                                                      5h

aai-graphadmin             ClusterIP      None            <none>                  8449/TCP,5005/TCP                                             5h

aai-modelloader            NodePort       10.43.251.134   <none>                  8080:30210/TCP,8443:30229/TCP                                 5h

aai-resources              ClusterIP      None            <none>                  8447/TCP,5005/TCP                                             5h

aai-search-data            ClusterIP      None            <none>                  9509/TCP                                                      5h

aai-sparky-be              NodePort       10.43.48.66     <none>                  9517:30220/TCP                                                5h

aai-spike                  NodePort       10.43.30.231    <none>                  9518:30239/TCP                                                5h

aai-traversal              ClusterIP      None            <none>                  8446/TCP,5005/TCP                                             5h

 

portal-app                 LoadBalancer   10.43.192.32    10.1.8.112              8989:30215/TCP,8006:30213/TCP,8010:30214/TCP,8443:30225/TCP   5h

portal-cassandra           ClusterIP      10.43.163.167   <none>                  9160/TCP,7000/TCP,7001/TCP,7199/TCP,9042/TCP                  5h

portal-db                  ClusterIP      10.43.131.227   <none>                  3306/TCP                                                      5h

portal-sdk                 NodePort       10.43.43.68     <none>                  8080:30212/TCP                                                5h

portal-widget              ClusterIP      10.43.107.133   <none>                  8082/TCP                                                      5h

portal-zookeeper           ClusterIP      10.43.170.249   <none>                  2181/TCP                                                      5h

 

Added the below to /etc/hosts

 

10.1.8.112 portal.api.simpledemo.onap.org

10.1.8.112 aai.api.sparky.simpledemo.onap.org

 

Accessing ONAP portal: http://10.1.8.112:8989/ONAPPORTAL/login.htm

 

When I click on AAI, It is blank and doesn’t show anything.

 

 

Using the Network option in google-chrome, I see the below information in header. But the response shows “This request has no response data available”.

 

Request URL:https://portal.api.simpledemo.onap.org:30225/ONAPPORTAL/portalApi/auditLog/store?affectedAppId=7&type=tab&comment=http://aai.api.sparky.simpledemo.onap.org:30220/services/aai/webapp/index.html?cc=1552536622817

Request Method:GET

Status Code:200 OK

Remote Address:10.1.8.112:30225

Referrer Policy:no-referrer-when-downgrade

 

Any insights on what might be going wrong ? Please let me know if I am missing something.

 

 

Thanks,

Thiriloshini


[SDC] SDC returns POL_5000 for the micro-service on CDS side I am building

prathamesh
 

Hi, 

I am trying to implement a CDS listener micro-service which acts a client to the SDC.

At the moment my code is calling SDC client and I am running SDC and DMAAP locally with the help of this documents(https://wiki.onap.org/display/DW/How+to+set+up+a+local+DMaaP+installation+in+Docker+for+testing, 

https://wiki.onap.org/display/DW/Building+and+running+SDC+using+Docker+for+OSX). Unfortunately at the registerForDistribution step I am getting 500 server error 

This is my curl request ->
curl -X POST \

  https://localhost:8443/sdc/v1/registerForDistribution \

  -H 'Accept: application/json; charset=UTF-8' \

  -H 'Authorization: Basic dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=' \

  -H 'Content-Type: application/json' \

  -H 'Postman-Token: e67d1c19-9754-4203-80a6-8ff3788b5e44' \

  -H 'X-ECOMP-InstanceID: cds-id-local' \

  -H 'X-ECOMP-RequestID: d7dd5b60-0894-421d-ad39-6565232708eb' \

  -H 'cache-control: no-cache' \

  -d '{

  "apiPublicKey": "v4avnOnjlk6JeBIb", // Received from DMAAP which is running locally

  "distrEnvName": "AUTO",   //  Same as the one I used for running SDC locally 

  "isConsumerToSdcDistrStatusTopic": false,

  "distEnvEndPoints": [

    "localhost" 

  ]

}'

 

This is the error I am getting 

 

{

    "requestError": {

        "policyException": {

            "messageId": "POL5000",

            "text": "Error: Internal Server Error. Please try again later.",

            "variables": []

        }

    }

}

 

 I checked SDC-BE health check and found this.

{

"healthCheckComponent": "ES",

      "healthCheckStatus": "DOWN",

      "version": "1.4.0-SNAPSHOT",

      "description": "ES cluster is down"

    },

    {

      "healthCheckComponent": "DE",

      "healthCheckStatus": "DOWN",

      "description": "U-EB cluster is not available"

    },

 

Is it happening because DE is down even though the container is up or something else? Please let me know 

 

Thanks,

Prathamesh Morde

 


Re: OOM: K8S deployment minimum nodes

kranthi guttikonda
 

Aai-cassandra is a statefulset.

 

So, we have to overwrite the value of replicaCount: 1 in

 

aai/charts/aai-cassandra/values.yaml

 

I generally deploy each component individually because of setup and resource constraints.

 

If you deploy individual components then override something like below

 

Below is just an example in my setup. You may want to fine tune Probe values based on resources in your setup

 

global:

  repository: xx.xx.xx.xx:5000

  pullPolicy: IfNotPresent

  flavor: unlimited

 

liveness:

  initialDelaySeconds: 120

aai-cassandra:

  replicaCount: 1

aai-data-router:

  liveness:

    initialDelaySeconds: 120

aai-sparky-be:

  liveness:

    initialDelaySeconds: 120

aai-spike:

  liveness:

    initialDelaySeconds: 120

aai-champ:

  liveness:

    initialDelaySeconds: 120

  readiness:

    initialDelaySeconds: 120

aai-resources:

  readiness:

    initialDelaySeconds: 120

 

If you are deploying all ONAP components together (using helm deploy plugin) then you may have to do something like below to override

 

global:

  repository: xx.xx.xx.xx:5000

  pullPolicy: IfNotPresent

  flavor: unlimited

 

aai:

  liveness:

    initialDelaySeconds: 120

  aai-cassandra:

    replicaCount: 1

  aai-data-router:

    liveness:

      initialDelaySeconds: 120

  aai-sparky-be:

    liveness:

      initialDelaySeconds: 120

 aai-spike:

    liveness:

      initialDelaySeconds: 120

  aai-champ:

    liveness:

      initialDelaySeconds: 120

    readiness:

      initialDelaySeconds: 120

  aai-resources:

    readiness:

      initialDelaySeconds: 120

 

Thanks,
Kranthi

 

From: DeWayne Filppi <dewayne@...>
Date: Thursday, March 14, 2019 at 4:14 PM
To: Kranthi Guttikonda <kranthi.guttikonda@...>
Cc: "onap-discuss@..." <onap-discuss@...>
Subject: Re: [onap-discuss] OOM: K8S deployment minimum nodes

 

Perhaps there is some adjustment to the Helm charts needed, because the aai-cassandra container fails claiming it needs 2 nodes.  Granted, I'm using Casablanca code.  Are you aware of any tweaks needed to the charts?

 

On Thu, Mar 14, 2019 at 1:01 PM Kranthi Guttikonda <kranthi.guttikonda@...> wrote:

Hi DeWayne,

 

I don’t think there is such requirement. You can deploy the whole ONAP in single HP or DELL gen9 v4 or above server (having 256GB RAM, 56 CPU (with hyper threading)). All you need to do is increase the --max-pods in kubelet. I did this with Rancher and kubeadm and able to deploy ONAP successfully in single server.

 

Attached the rancher POST call for reference.

 

Also I did test ONAP Casablanca with helm v2.12.3 and kubelet version 1.13.4 as well. With latest kubeadm you need to adjust the value of maxPods in “/var/lib/kubelet/config.yaml” and restart the kubelet

 

Coming to taints, affinities and nodeSelector fields unless you specify ONAP charts doesn’t have these enabled as default.

 

Thanks,
Kranthi

 

From: <onap-discuss@...> on behalf of "DeWayne Filppi via Lists.Onap.Org" <dewayne=cloudify.co@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "dewayne@..." <dewayne@...>
Date: Thursday, March 14, 2019 at 3:37 PM
To: "onap-discuss@..." <onap-discuss@...>
Subject: [onap-discuss] OOM: K8S deployment minimum nodes

 

  Has anyone established the minimum number of compute nodes that ONAP can run on (in a K8S deployment)?  Not counting Rancher or the Kubernetes master.  I know it's at least 2, but was wonder if anyone had established the minimum.  I'm not talking about resource limitations, I'm talking about actual deployments or pods having taints or affinities that require a certain number of nodes.

 

Thanks,

 

DeWayne

 


 

--

DeWayne Filppi

Director, Sr. Architect CTO Office

+972523609583cloudify.co @cloudifysource

 

        

 


Re: OOM: K8S deployment minimum nodes

DeWayne Filppi
 

Perhaps there is some adjustment to the Helm charts needed, because the aai-cassandra container fails claiming it needs 2 nodes.  Granted, I'm using Casablanca code.  Are you aware of any tweaks needed to the charts?


On Thu, Mar 14, 2019 at 1:01 PM Kranthi Guttikonda <kranthi.guttikonda@...> wrote:

Hi DeWayne,

 

I don’t think there is such requirement. You can deploy the whole ONAP in single HP or DELL gen9 v4 or above server (having 256GB RAM, 56 CPU (with hyper threading)). All you need to do is increase the --max-pods in kubelet. I did this with Rancher and kubeadm and able to deploy ONAP successfully in single server.

 

Attached the rancher POST call for reference.

 

Also I did test ONAP Casablanca with helm v2.12.3 and kubelet version 1.13.4 as well. With latest kubeadm you need to adjust the value of maxPods in “/var/lib/kubelet/config.yaml” and restart the kubelet

 

Coming to taints, affinities and nodeSelector fields unless you specify ONAP charts doesn’t have these enabled as default.

 

Thanks,
Kranthi

 

From: <onap-discuss@...> on behalf of "DeWayne Filppi via Lists.Onap.Org" <dewayne=cloudify.co@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "dewayne@..." <dewayne@...>
Date: Thursday, March 14, 2019 at 3:37 PM
To: "onap-discuss@..." <onap-discuss@...>
Subject: [onap-discuss] OOM: K8S deployment minimum nodes

 

  Has anyone established the minimum number of compute nodes that ONAP can run on (in a K8S deployment)?  Not counting Rancher or the Kubernetes master.  I know it's at least 2, but was wonder if anyone had established the minimum.  I'm not talking about resource limitations, I'm talking about actual deployments or pods having taints or affinities that require a certain number of nodes.

 

Thanks,

 

DeWayne

 



--

DeWayne Filppi

Director, Sr. Architect CTO Office

+972523609583cloudify.co @cloudifysource
        



Re: OOM: K8S deployment minimum nodes

kranthi guttikonda
 

Hi DeWayne,

 

I don’t think there is such requirement. You can deploy the whole ONAP in single HP or DELL gen9 v4 or above server (having 256GB RAM, 56 CPU (with hyper threading)). All you need to do is increase the --max-pods in kubelet. I did this with Rancher and kubeadm and able to deploy ONAP successfully in single server.

 

Attached the rancher POST call for reference.

 

Also I did test ONAP Casablanca with helm v2.12.3 and kubelet version 1.13.4 as well. With latest kubeadm you need to adjust the value of maxPods in “/var/lib/kubelet/config.yaml” and restart the kubelet

 

Coming to taints, affinities and nodeSelector fields unless you specify ONAP charts doesn’t have these enabled as default.

 

Thanks,
Kranthi

 

From: <onap-discuss@...> on behalf of "DeWayne Filppi via Lists.Onap.Org" <dewayne=cloudify.co@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "dewayne@..." <dewayne@...>
Date: Thursday, March 14, 2019 at 3:37 PM
To: "onap-discuss@..." <onap-discuss@...>
Subject: [onap-discuss] OOM: K8S deployment minimum nodes

 

  Has anyone established the minimum number of compute nodes that ONAP can run on (in a K8S deployment)?  Not counting Rancher or the Kubernetes master.  I know it's at least 2, but was wonder if anyone had established the minimum.  I'm not talking about resource limitations, I'm talking about actual deployments or pods having taints or affinities that require a certain number of nodes.

 

Thanks,

 

DeWayne

 


Re: Logging for SO

Abdelmuhaimen Seaudi
 

Hi,

I was able to enable logging of SO to ELK using the change in https://gerrit.onap.org/r/#/c/69947/https://gerrit.onap.org/r/#/c/69947/, and I can now see SO logs in Kibana.

However, I had to modify the logs folder in the deployment yaml, since the SO pods are using /app/logs, instead of /var/log/onap.

A. Seaudi


From: SEAUDI Abdelmuhaimen O-EG/HRCS
Sent: Thursday, March 14, 2019 9:06 AM
To: onap-discuss@...
Subject: RE: Logging for SO

Hi,

 

1.       I found that SO logging was removed, and it’s being re-added again in SO-1110

 

For my infom, why was logging removed ?

 

And, when is it expected to be back again for SO ?

 

Or, is there a workaround to use to enable SO, that I can do on my own ? e.g. maybe use an older SO chart and replace the new one in oom/kubernets/so ?

 

Thanks.

 

Abdelmuhaimen Seaudi

Orange Labs Egypt

Email: abdelmuhaimen.seaudi@...

Mobile: +2012 84644 733

 

From: SEAUDI Abdelmuhaimen O-EG/HRCS
Sent: Wednesday, March 13, 2019 4:26 PM
To: onap-discuss@...
Subject: Logging for SO

 

Hi,

 

I was deploying ONAP Casablanca with some components, and I noticed that Kibana does not have any logs from SO.

 

I checked the SO Pods, and it seems they don’t have the filebeat container.

 

I searched the oom/kubernetes/so and found resources/config/log/filebeat/filebeat.yml

 

What can I do to have SO send the logs to ELK ?

 

Thanks

 

Abdelmuhaimen Seaudi

Orange Labs Egypt

Email: abdelmuhaimen.seaudi@...

Mobile: +2012 84644 733

 

_________________________________________________________________________________________________________________________

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.


OOM: K8S deployment minimum nodes

DeWayne Filppi
 

  Has anyone established the minimum number of compute nodes that ONAP can run on (in a K8S deployment)?  Not counting Rancher or the Kubernetes master.  I know it's at least 2, but was wonder if anyone had established the minimum.  I'm not talking about resource limitations, I'm talking about actual deployments or pods having taints or affinities that require a certain number of nodes.

Thanks,

DeWayne


Helm > Error: trying to send message larger than max #oom #helm #casablanca #lfn #kubernetes

David Perez Caparros
 

Hi,

I am starting to get errors like the one below when deploying/undeploying with helm, branch Casablanca, running for ~70 days.

# helm undeploy dev-sniro-emulator --purge
Error: trying to send message larger than max (23353031 vs. 20971520)

# kubectl get configmap | wc -l
286

# kubectl --namespace=kube-system get cm | wc -l
708

# helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean”}

# kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.5", GitCommit:"753b2dbc622f5cc417845f0ff8a77f539a4213ea", GitTreeState:"clean", BuildDate:"2018-11-26T14:41:50Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.5-rancher1", GitCommit:"44636ddf318af0483af806e255d0be4bb6a2e3d4", GitTreeState:"clean", BuildDate:"2018-12-04T04:28:34Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64”}

# docker -v
Docker version 17.03.2-ce, build f5ec1e2

# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            3.9G     0  3.9G   0% /dev
tmpfs           799M   79M  720M  10% /run
/dev/vda1        97G   21G   77G  22% /
tmpfs           3.9G  392K  3.9G   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
none             97G   21G   77G  22% /var/lib/docker/aufs/mnt/168af35e85e3e4df3bf740d4e9540d7f38b3fd4d7d89ed18d5dce6c3a1ac555a
shm              64M     0   64M   0% /var/lib/docker/containers/4a98d330c0febe51e82a18cf9ff4076519e62a7817a8b36b4acd4b495791de78/shm
tmpfs           799M     0  799M   0% /run/user/1000

Did anyone encounter similar issues? any suggestion?

Regards
David

--
David Pérez Caparrós
Senior Innovation Engineer
Swisscom (Switzerland)

7061 - 7080 of 23112