Date   

Posting an event to VES collector #dcaegen2

jeanmichel.cornily@...
 

Hi,

I hope you can help me on the following: When a xNF sends an event to the VES Collector, which resource is the POST message sent out to (according to the resource structure copied below)?

1.     a) eventListener, or

b) eventbatch ?

 

I don’t see what eventbatch brings, compared to eventListener.

 

Would any of you have an example of such a HTTP POST message (including the header)?

 


 

Many thanks in advance if you can help.
Best regards.
Jean-Michel
Orange


#clamp #policy Reminder Joint Project meeting is on Clamp team's bridge #policy #clamp

Pamela Dragosh <pdragosh@...>
 

https://zoom.us/j/985787133

 

thanks!

 

Pam


#ccsdk New bridge for weekly CCSDK project meeting #ccsdk

Dan Timoney
 

CCSDK team,

 

As I mentioned on last week’s call, there has been a change to ONAP calendar scheduling – we’re now using groups.io to manage our meeting requests.   As part of that change,  the bridge has changed for our weekly CCSDK project meeting (Friday mornings at 11:00 EDT),  We’ll now be using the following bridge:

 

https://zoom.us/j/330824945

 

This meeting appears in the onap-sdnc calendar (there is no separate group for CCSDK in groups.io), so if you already subscribe to that calendar, the entry there has the correct bridge (it better – that’s where I copied that link above from 😉 ..).    If you don’t already subscribe to that calendar, a link to the calendar in groups.io:

 

https://lists.onap.org/g/onap-sdnc/calendar

 

Near the button of that page is a button “Subscribe to Calendar” that will let you copy the URL you’d need to add to your desktop calendar to subscribe.

 

Dan

 

 

 

Dan Timoney

Principal Technical Staff Member

AT&T

Email : dtimoney@...

Office : +1 (732) 420-3226

Mobile : +1 (201) 960-1211

200 S Laurel Ave, Rm E2-2A03

Middletown, NJ 08873


Re: 答复: The Open Lab Subcommittee Meeting is going on

Yan Yang
 

RESENDING

 

 

Best Regards,

Yan

发件人: Yan Yang [mailto:yangyanyj@...]
发送时间: 2019320 19:03
收件人: 'onap-openlabsub@...'; 'onap-discuss@...'
主题: The Open Lab Subcommittee Meeting is going on

 

Hi all,

 

The Open Lab Subcommittee meeting is going on in the bridge https://zoom.us/j/621738721, welcome to join the meeting.

 

 

 

Best Regards,

Yan Yang


The Open Lab Subcommittee Meeting is going on

Yan Yang
 

Hi all,

 

The Open Lab Subcommittee meeting is going on in the bridge https://zoom.us/j/621738721, welcome to join the meeting.

 

 

 

Best Regards,

Yan Yang


Re: OOM offline deployment - Casablanca

Ambica
 

Hi Samuli,


 Could you please let me know if any documentation for making changes in schema of OOM offline deployment of Casablanca is provided.


Regards,

Ambica


From: onap-discuss@... <onap-discuss@...> on behalf of Sangeeth G <sg00542754@...>
Sent: Monday, March 18, 2019 1:24:46 PM
To: Samuli Silvius; onap-discuss@...
Subject: Re: [onap-discuss] OOM offline deployment - Casablanca
 

Thanks Samuli.

 

Best Regards,

Sangeeth G

 

From: Samuli Silvius <s.silvius@...>
Sent: Monday, March 18, 2019 1:22 PM
To: onap-discuss@...; Sangeeth G <SG00542754@...>
Subject: RE: [onap-discuss] OOM offline deployment - Casablanca

 

Hi Sangeeth,

 

Offline installer docs are at the moment only in master:

https://onap.readthedocs.io/en/latest/submodules/oom/offline-installer.git/docs/index.html

 

That’s because we have not yet created Casablanca branch to oom/offline-installer git repository as we are still working on to fully support Casablanca. Ones branch will be created the documentation should be available under Casablanca in readthedocs.

 

Br

-Samuli

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Sangeeth G
Sent: maanantai 18. maaliskuuta 2019 9.21
To: onap-discuss@...
Subject: [onap-discuss] OOM offline deployment - Casablanca

 

Hi,

 

Could you please let me know the documentation of OOM offline deployment of Casablanca. The wiki page of Casablanca offline deployment does not have any content or steps to try the same.

 

Best Regards,

Sangeeth G

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

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

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

 

 

  


[Integration] [Casablanca] ete-k8s.sh onap instance ERROR

Liu Chenglong
 

Hi, Yang:
      When we running ete-k8s.sh onap instance on C release ONAP, we appear this error for openstack keystone.  



We modify /home/ubuntu/oom/kubernetes/robot/values.yaml and reinstall robot docker more times, but this error happened again.
     we reinstall robot docker by use commnd : helm install local/robot --name dev-robot --namespace onap -f /home/ubuntu/oom/kubernetes/robot/values.yaml
    and this is the result for command :
NAME:   dev-robot
LAST DEPLOYED: Mon Mar  4 07:32:53 2019
NAMESPACE: onap
STATUS: DEPLOYED

RESOURCES:
==> v1/ConfigMap
NAME                                DATA  AGE
dev-robot-robot-eteshare-configmap  3     1s

==> v1/PersistentVolume
NAME             CAPACITY  ACCESS MODES  RECLAIM POLICY  STATUS  CLAIM                 STORAGECLASS  REASON  AGE
dev-robot-robot  2Gi       RWX           Retain          Bound   onap/dev-robot-robot  1s

==> v1/PersistentVolumeClaim
NAME             STATUS  VOLUME           CAPACITY  ACCESS MODES  STORAGECLASS  AGE
dev-robot-robot  Bound   dev-robot-robot  2Gi       RWX           1s

==> v1/Service
NAME   TYPE      CLUSTER-IP    EXTERNAL-IP  PORT(S)       AGE
robot  NodePort  10.43.78.242  <none>       88:30209/TCP  1s

==> v1beta1/Deployment
NAME             DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
dev-robot-robot  1        1        1           0          1s

==> v1/Pod(related)
NAME                              READY  STATUS             RESTARTS  AGE
dev-robot-robot-787dcdc979-xvvjs  0/1    ContainerCreating  0         1s


NOTES:
# Copyright © 2018 Amdocs, Bell Canada
#
# This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE
#

1. Get the application URL by running these commands:
  export NODE_PORT=$(kubectl get --namespace onap -o jsonpath="{.spec.ports[0].nodePort}" services robot)
  export NODE_IP=$(kubectl get nodes --namespace onap -o jsonpath="{.items[0].status.addresses[0].address}")



Please help us for this error. 




----------------------------------------------
Regards,
Liu Chenglong




Updated Event: Openlab subcommittee meeting (UTC) #cal-invite

onap-discuss@lists.onap.org Calendar <onap-discuss@...>
 

Openlab subcommittee meeting (UTC)

When:
Wednesday, 20 March 2019
11:00am to 12:00pm
(GMT+00:00) Africa/Monrovia
Repeats: Weekly on Wednesday

Where:
https://zoom.us/j/621738721

Organizer:
yangyanyj@... ONAP6

Description:
Openlab subcommittee meeting
https://zoom.us/j/621738721


Event: Openlab subcommittee meeting #cal-invite

onap-discuss@lists.onap.org Calendar <onap-discuss@...>
 

Openlab subcommittee meeting

When:
Wednesday, 20 March 2019
11:00am to 12:00pm
(GMT+00:00) Africa/Monrovia
Repeats: Weekly on Wednesday

Organizer:
yangyanyj@...

Description:
Openlab subcommittee meeting


Trialling countdown clock widgets for meetings

Keong Lim
 

Hi everybody,

There is a PoC design for countdown clocks to help people attend the weekly meetings at the right time!
You can find them on the wiki here:

- https://wiki.onap.org/display/DW/PTL+Weekly+ONAP12%2C+Mon+UTC+13%3A00
- https://wiki.onap.org/display/DW/%5Baai%5D+Team+ONAP10%2C+Wed%2C+Eastern%3A+09%3A00
- https://wiki.onap.org/display/DW/%5Baai%5D+Dev+ONAP10%2C+Thurs%2C+Eastern%3A+08%3A00

Please let me know what you think.

If it's worth keeping, I can write up a tutorial on using it.
It is easy to copy and customise for other meetings as well.


Thanks,
Keong


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

Thiriloshini.ThoppeKrishnakumar@us.fujitsu.com
 

Arul, David,

 

When I open the AAI UI in a separate browser using http://aai.api.sparky.simpledemo.onap.org:30220/services/aai/webapp/index.html , it works fine now.

 

Thanks for your inputs.

 

Thanks,

Thiriloshini

 

From: Arul Nambi <Arul.Nambi@...>
Sent: Monday, March 18, 2019 7:59 AM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>; David.PerezCaparros@...
Cc: Keong.Lim@...; Rao, Ravi <Ravi.Rao@...>
Subject: RE: [onap-discuss] [AAI] [portal] Problem accessing AAI GUI from ONAP Portal

 

Hi Thiriloshni,

The part you have highlighted is not important.

What error did you see in the browser when you tried to open “http://aai.api.sparky.simpledemo.onap.org:30220/services/aai/webapp/index.html

Regards

Arul

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Thiriloshini.ThoppeKrishnakumar@...
Sent: Friday, March 15, 2019 12:24 PM
To: David.PerezCaparros@...; onap-discuss@...
Cc: Keong.Lim@...; Ravi.Rao@...
Subject: Re: [onap-discuss] [AAI] [portal] Problem accessing AAI GUI from ONAP Portal

 

David,

 

Thanks for your input.

 

I have tried http://aai.api.sparky.simpledemo.onap.org:30220/services/aai/webapp/index.html in new tab and it dint work.

 

Looks like I had missed the highlighted part http://aai.api.sparky.simpledemo.onap.org:30220/services/aai/webapp/index.html?cc=1552536622817.

 

I had to tear down the set up. I’ll try this once I have it back up.

 

Thanks,

Thiriloshini

 

From: David.PerezCaparros@... <David.PerezCaparros@...>
Sent: Friday, March 15, 2019 10:59 AM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Keong.Lim@...; Rao, Ravi <Ravi.Rao@...>
Subject: Re: [onap-discuss] [AAI] [portal] Problem accessing AAI GUI from ONAP Portal

 

I think sparky-be is enough, I don’t see sparky-fe in my deployment and the AAI UI works fine, with the caveat of having to open it outside portal, as explained in my previous mail.

 

# kubectl get svc -n onap -o wide | grep aai

aai                                NodePort       10.43.201.68    <none>                                 8080:30232/TCP,8443:30233/TCP                                 9d        app=aai

aai-babel                          NodePort       10.43.251.95    <none>                                 9516:30279/TCP                                                9d        app=aai-babel,release=dev-aai

aai-cassandra                      ClusterIP      None            <none>                                 9042/TCP,9160/TCP,61621/TCP                                   9d        app=aai-cassandra,release=dev-aai

aai-champ                          NodePort       10.43.192.104   <none>                                 9522:30278/TCP                                                9d        app=aai-champ,release=dev-aai

aai-crud-service                   NodePort       10.43.5.103     <none>                                 9520:30268/TCP                                                9d        app=aai-gizmo,release=dev-aai

aai-elasticsearch                  ClusterIP      None            <none>                                 9200/TCP                                                      9d        app=aai-elasticsearch,release=dev-aai

aai-graphadmin                     ClusterIP      None            <none>                                 8449/TCP,5005/TCP                                             9d        app=aai-graphadmin,release=dev-aai

aai-modelloader                    NodePort       10.43.250.153   <none>                                 8080:30210/TCP,8443:30229/TCP                                 9d        app=aai-modelloader,release=dev-aai

aai-resources                      ClusterIP      None            <none>                                 8447/TCP,5005/TCP                                             9d        app=aai-resources,release=dev-aai

aai-search-data                    ClusterIP      None            <none>                                 9509/TCP                                                      9d        app=aai-search-data,release=dev-aai

aai-sparky-be                      NodePort       10.43.76.32     <none>                                 9517:30220/TCP                                                9d        app=aai-sparky-be,release=dev-aai

aai-spike                          NodePort       10.43.73.3      <none>                                 9518:30239/TCP                                                9d        app=aai-spike,release=dev-aai

aai-traversal                      ClusterIP      None            <none>                                 8446/TCP,5005/TCP                                             9d        app=aai-traversal,release=dev-aai

 

 

 

David,

 

Is sparky-be sufficient for the AAI GUI to show up in OOM kubernetes installation (Casablanca) ?

Do we need sparky-fe in place for the front end ?

 

 

Thanks,

Thiriloshini

 

From: David.PerezCaparros@... <David.PerezCaparros@...> 
Sent: Friday, March 15, 2019 10:46 AM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Keong.Lim@...; Rao, Ravi <Ravi.Rao@...>
Subject: Re: [onap-discuss] [AAI] [portal] Problem accessing AAI GUI from ONAP Portal

 

Hi Thiriloshini, 

 

try to copy&paste the URL you see in network tools in a new tab, e.g. http://aai.api.sparky.simpledemo.onap.org:30220/services/aai/webapp/index.html?cc=1552536622817

aai.api.sparky.simpledemo.onap.org should point to the host where sparky-be is

 

Regards

David

 

 

Keong,

 

The sparky-fe chart isn’t available there under charts in AAI Casablanca. Should I manually add it ?

 

ubuntu@onap-rancher-vm:~/onap/Casablanca/oom/kubernetes/aai/charts$ ls

aai-babel  aai-cassandra  aai-champ  aai-data-router  aai-elasticsearch  aai-gizmo  aai-graphadmin  aai-modelloader  aai-resources  aai-search-data  aai-sparky-be  aai-spike  aai-traversal  common-3.0.0.tgz

ubuntu@onap-rancher-vm:~/onap/Casablanca/oom/kubernetes/aai/charts$

 

Thanks,

Thiriloshini

 

 

 

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

 

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

 

 

 

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

 

<image002.jpg>

 

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

 

 

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


Re: [AAI] Changing dbedgerules in onap deployment environment

Thiriloshini.ThoppeKrishnakumar@us.fujitsu.com
 

David,

 

I was able to resolve the graphadmin issue by removing old docker containers and images and re-deploying onap.

 

And for the dbedgerules, restarting the docker containers after the edgerule update as you had suggested solved the problem.

 

Thanks for the pointer and appreciate your time.

 

Thanks,

Thiriloshini

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Thiriloshini.ThoppeKrishnakumar@...
Sent: Tuesday, March 19, 2019 1:24 PM
To: David.PerezCaparros@...; onap-discuss@...
Cc: Keong.Lim@...; jf2512@...; Rao, Ravi <Ravi.Rao@...>
Subject: Re: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

David,

 

Can you please let me know where does the JanusGraph reside if you are aware of so that I can check the status of JanusGraph.

 

Thanks,

Thiriloshini

 

From: David.PerezCaparros@... <David.PerezCaparros@...>
Sent: Tuesday, March 19, 2019 12:45 PM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Keong.Lim@...; jf2512@...; Rao, Ravi <Ravi.Rao@...>
Subject: Re: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

did you also deleted the persistent volume claims before redeploying?

# kubectl get pvc -n onap | grep aai

 

 

David/ Keong,

 

Thanks for your response.

 

In the process of bringing the set up back up, I am facing exception in aai-aai-graphadmin-create-db-schema job and aai pods would not start.

 

I did a fresh helm deploy (sudo helm deploy demo ./onap --namespace onap) using new rancher. Cleared the /dockerdata-nfs. So it doesn’t have any stale entries.

I am using Casablanca oom kubernetes deployment environment. The same thing was working fine earlier and I haven’t changed anything.

 

Please find the exception attached.  It fails to instantiate Graph.  I also see same exception when I try to execute the command sh createDBSchema.sh inside the container with aaiadmin user.

 

Please find the aai pods below.

aaiadmin@demo-aai-aai-graphadmin-create-db-schema-mh4l9:/opt/app/aai-graphadmin/bin$ sh createDBSchema.sh

 

 

demo-aai-aai-75b9c64998-tdkrc                          0/1       Init:0/1           2          25m

demo-aai-aai-babel-5499b48894-f8qf2                    2/2       Running            0          25m

demo-aai-aai-cassandra-0                               1/1       Running            0          25m

demo-aai-aai-cassandra-1                               1/1       Running            1          22m

demo-aai-aai-cassandra-2                               1/1       Running            0          21m

demo-aai-aai-champ-75f5d6f664-26295                    1/2       Running            0          25m

demo-aai-aai-data-router-94f79b78f-dqp8l               2/2       Running            0          25m

demo-aai-aai-elasticsearch-f868cff98-p4grb             1/1       Running            0          25m

demo-aai-aai-gizmo-7b6ff8f6f-lkxwf                     2/2       Running            0          25m

demo-aai-aai-graphadmin-8485cd6c85-bls7f               0/2       Init:0/1           2          25m

demo-aai-aai-graphadmin-create-db-schema-mh4l9         1/1       Running            0          51s

demo-aai-aai-modelloader-77496bd596-wr9tp              2/2       Running            0          25m

demo-aai-aai-resources-6d8d78cb-jlsjf                  0/2       Init:0/1           2          25m

demo-aai-aai-search-data-5d7fc5cc8c-hcrl9              2/2       Running            0          25m

demo-aai-aai-sparky-be-6598bf956c-6nc28                0/2       Init:0/1           0          25m

demo-aai-aai-spike-6546658f99-2bwr9                    2/2       Running            0          25m

demo-aai-aai-traversal-5d8df67875-srngg                0/2       Init:0/1           2          25m

demo-aai-aai-traversal-update-query-data-xdf2w         0/1       Init:0/1           2          25m

 

This issue is blocking me from proceeding further. Any pointer is much appreciated.

 

Thanks,

Thiriloshini

 

From: David.PerezCaparros@... <David.PerezCaparros@...> 
Sent: Tuesday, March 19, 2019 7:58 AM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Keong.Lim@...; jf2512@...; Rao, Ravi <Ravi.Rao@...>
Subject: Re: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

Hi Thiriloshini, 

 

in case it helps, regarding making new edgerules work in a running deployment of Casablanca, this is what I did:

- add new edgerules in aai-resources, aai-traversal, aai-graphadmin, under v14 folder /opt/app/…/resources/schema/onap/dbedgerules/v14/

- run in aai-graphadmin as aaiadmin user the createDBSchema.sh script under /opt/app/aai-graphadmin/bin/

- restart docker containers (not deleting the pod) aai-resources, aai-traversal, aai-graphadmin

 

Regards

David



 

Keong,

 

I changed the EdgeRules in development environment by following the tutorial and things work as expected.

-        Changed the EdgeRule

-        Build aai-common,  resource, traversal, graphadmin.

-        Started resource and traversal microservices as suggested in the tutorial.

-        Deleting esr-thirdparty-sdnc deleted the associated pnfs.

 

I build the docker images – traversal, resource, graphadmin from the source code and used those images to run the container in

Deployment environment. 

The dev-aai-graphadmin-create-db-schema fails. When I try to execute the docker-entrypoint.sh and createDBSchema.sh manually inside the dev-aai-graphadmin-create-db-schema container I see the below error

aaiadmin@dev-aai-graphadmin-create-db-schema-bh2b2:/opt/app/aai-graphadmin/scripts$ sh createDBSchema.sh

 

Tue Mar 19 02:54:55 UTC 2019    Starting createDBSchema.sh

    ---- NOTE --- about to open graph (takes a little while)--------;

-- Loading new schema elements into JanusGraph --

Failed to run the tool createDBSchema.sh successfully

 

I do not any errors in error.log under logs/createDBSchema

 

I also tried the below:

 

Instead of using the imaged build from development environment, used the same images that comes with the Casablanca deployment environment. Changed the edgerules in resource, traversal, graphadmin and run the createDBSchema.sh in graphadmin. The edgerules change doesn’t take effect. I understand that this method isn’t persistent.

 

Any pointer would be useful.

 

Thanks,

Thiriloshini

 

From: Keong Lim <Keong.Lim@...> 
Sent: Sunday, March 17, 2019 7:24 PM
To: Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>; onap-discuss@...; FORSYTH, JAMES <jf2512@...>
Cc: Rao, Ravi <Ravi.Rao@...>
Subject: RE: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

Hi Thiriloshini,

 

Yes, the EdgeRules can be changed in a running OOM-based system, however the aai-traversal is not enough.

As per the wiki Tutorial, the change also needs to be in schema-service, graphadmin and aai-resources, and you need to run create-db-schema script to apply it to the database.

 

However, the method you are using has not been documented, because it is not a recommended method and it isn’t persistent when the pods are re-deployed.

 

If you can do it, please build new containers and deploy them into your OOM-based system.

 

 

Keong

 

 

From: Thiriloshini.ThoppeKrishnakumar@... [mailto:Thiriloshini.ThoppeKrishnakumar@...] 
Sent: Saturday, 16 March 2019 18:10
To: onap-discuss@...; Keong Lim <Keong.Lim@...>; FORSYTH, JAMES <jf2512@...>
Cc: Ravi.Rao@...
Subject: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

 

Please find my questions below

 

1.      Can the DbEdgeRules be changed in a deployment environment ?

2.      If it can be done, am I changing in the right place ? 

3.      Please let me know if I am missing something here.

 

Any pointer is much appreciated.

 

Thanks,

Thiriloshini

 

<Job_aai-graphadmin-create-db-schema_exception.txt>

 


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

Shen Tao <shentao@...>
 

Hi Thierry

 

I think you’d better modify k8s deployment of uui to image 1.2.2/1.2.2.

UUI components will be reinstalled automatically.

 

Best regards,

Tao

 

 

发件人: thierry.hardy@... [mailto:thierry.hardy@...]
发送时间: 2019315 17:15
收件人: shentao; onap-discuss@...
抄送: guochuyi@...
主题: RE: [onap-discuss] Project usecase-ui - Casablanca release: container uui-server fails to start

 

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.


Re: [AAI] Changing dbedgerules in onap deployment environment

Thiriloshini.ThoppeKrishnakumar@us.fujitsu.com
 

David,

 

Can you please let me know where does the JanusGraph reside if you are aware of so that I can check the status of JanusGraph.

 

Thanks,

Thiriloshini

 

From: David.PerezCaparros@... <David.PerezCaparros@...>
Sent: Tuesday, March 19, 2019 12:45 PM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Keong.Lim@...; jf2512@...; Rao, Ravi <Ravi.Rao@...>
Subject: Re: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

did you also deleted the persistent volume claims before redeploying?

# kubectl get pvc -n onap | grep aai



 

David/ Keong,

 

Thanks for your response.

 

In the process of bringing the set up back up, I am facing exception in aai-aai-graphadmin-create-db-schema job and aai pods would not start.

 

I did a fresh helm deploy (sudo helm deploy demo ./onap --namespace onap) using new rancher. Cleared the /dockerdata-nfs. So it doesn’t have any stale entries.

I am using Casablanca oom kubernetes deployment environment. The same thing was working fine earlier and I haven’t changed anything.

 

Please find the exception attached.  It fails to instantiate Graph.  I also see same exception when I try to execute the command sh createDBSchema.sh inside the container with aaiadmin user.

 

Please find the aai pods below.

aaiadmin@demo-aai-aai-graphadmin-create-db-schema-mh4l9:/opt/app/aai-graphadmin/bin$ sh createDBSchema.sh

 

 

demo-aai-aai-75b9c64998-tdkrc                          0/1       Init:0/1           2          25m

demo-aai-aai-babel-5499b48894-f8qf2                    2/2       Running            0          25m

demo-aai-aai-cassandra-0                               1/1       Running            0          25m

demo-aai-aai-cassandra-1                               1/1       Running            1          22m

demo-aai-aai-cassandra-2                               1/1       Running            0          21m

demo-aai-aai-champ-75f5d6f664-26295                    1/2       Running            0          25m

demo-aai-aai-data-router-94f79b78f-dqp8l               2/2       Running            0          25m

demo-aai-aai-elasticsearch-f868cff98-p4grb             1/1       Running            0          25m

demo-aai-aai-gizmo-7b6ff8f6f-lkxwf                     2/2       Running            0          25m

demo-aai-aai-graphadmin-8485cd6c85-bls7f               0/2       Init:0/1           2          25m

demo-aai-aai-graphadmin-create-db-schema-mh4l9         1/1       Running            0          51s

demo-aai-aai-modelloader-77496bd596-wr9tp              2/2       Running            0          25m

demo-aai-aai-resources-6d8d78cb-jlsjf                  0/2       Init:0/1           2          25m

demo-aai-aai-search-data-5d7fc5cc8c-hcrl9              2/2       Running            0          25m

demo-aai-aai-sparky-be-6598bf956c-6nc28                0/2       Init:0/1           0          25m

demo-aai-aai-spike-6546658f99-2bwr9                    2/2       Running            0          25m

demo-aai-aai-traversal-5d8df67875-srngg                0/2       Init:0/1           2          25m

demo-aai-aai-traversal-update-query-data-xdf2w         0/1       Init:0/1           2          25m

 

This issue is blocking me from proceeding further. Any pointer is much appreciated.

 

Thanks,

Thiriloshini

 

From: David.PerezCaparros@... <David.PerezCaparros@...> 
Sent: Tuesday, March 19, 2019 7:58 AM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Keong.Lim@...; jf2512@...; Rao, Ravi <Ravi.Rao@...>
Subject: Re: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

Hi Thiriloshini, 

 

in case it helps, regarding making new edgerules work in a running deployment of Casablanca, this is what I did:

- add new edgerules in aai-resources, aai-traversal, aai-graphadmin, under v14 folder /opt/app/…/resources/schema/onap/dbedgerules/v14/

- run in aai-graphadmin as aaiadmin user the createDBSchema.sh script under /opt/app/aai-graphadmin/bin/

- restart docker containers (not deleting the pod) aai-resources, aai-traversal, aai-graphadmin

 

Regards

David




 

Keong,

 

I changed the EdgeRules in development environment by following the tutorial and things work as expected.

-        Changed the EdgeRule

-        Build aai-common,  resource, traversal, graphadmin.

-        Started resource and traversal microservices as suggested in the tutorial.

-        Deleting esr-thirdparty-sdnc deleted the associated pnfs.

 

I build the docker images – traversal, resource, graphadmin from the source code and used those images to run the container in

Deployment environment. 

The dev-aai-graphadmin-create-db-schema fails. When I try to execute the docker-entrypoint.sh and createDBSchema.sh manually inside the dev-aai-graphadmin-create-db-schema container I see the below error

aaiadmin@dev-aai-graphadmin-create-db-schema-bh2b2:/opt/app/aai-graphadmin/scripts$ sh createDBSchema.sh

 

Tue Mar 19 02:54:55 UTC 2019    Starting createDBSchema.sh

    ---- NOTE --- about to open graph (takes a little while)--------;

-- Loading new schema elements into JanusGraph --

Failed to run the tool createDBSchema.sh successfully

 

I do not any errors in error.log under logs/createDBSchema

 

I also tried the below:

 

Instead of using the imaged build from development environment, used the same images that comes with the Casablanca deployment environment. Changed the edgerules in resource, traversal, graphadmin and run the createDBSchema.sh in graphadmin. The edgerules change doesn’t take effect. I understand that this method isn’t persistent.

 

Any pointer would be useful.

 

Thanks,

Thiriloshini

 

From: Keong Lim <Keong.Lim@...> 
Sent: Sunday, March 17, 2019 7:24 PM
To: Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>; onap-discuss@...; FORSYTH, JAMES <jf2512@...>
Cc: Rao, Ravi <Ravi.Rao@...>
Subject: RE: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

Hi Thiriloshini,

 

Yes, the EdgeRules can be changed in a running OOM-based system, however the aai-traversal is not enough.

As per the wiki Tutorial, the change also needs to be in schema-service, graphadmin and aai-resources, and you need to run create-db-schema script to apply it to the database.

 

However, the method you are using has not been documented, because it is not a recommended method and it isn’t persistent when the pods are re-deployed.

 

If you can do it, please build new containers and deploy them into your OOM-based system.

 

 

Keong

 

 

From: Thiriloshini.ThoppeKrishnakumar@... [mailto:Thiriloshini.ThoppeKrishnakumar@...] 
Sent: Saturday, 16 March 2019 18:10
To: onap-discuss@...; Keong Lim <Keong.Lim@...>; FORSYTH, JAMES <jf2512@...>
Cc: Ravi.Rao@...
Subject: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

 

Please find my questions below

 

1.      Can the DbEdgeRules be changed in a deployment environment ?

2.      If it can be done, am I changing in the right place ? 

3.      Please let me know if I am missing something here.

 

Any pointer is much appreciated.

 

Thanks,

Thiriloshini

 

<Job_aai-graphadmin-create-db-schema_exception.txt>

 


Re: [AAI] Changing dbedgerules in onap deployment environment

Thiriloshini.ThoppeKrishnakumar@us.fujitsu.com
 

David,

 

Yes, I did

 

From: David.PerezCaparros@... <David.PerezCaparros@...>
Sent: Tuesday, March 19, 2019 12:45 PM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Keong.Lim@...; jf2512@...; Rao, Ravi <Ravi.Rao@...>
Subject: Re: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

did you also deleted the persistent volume claims before redeploying?

# kubectl get pvc -n onap | grep aai



 

David/ Keong,

 

Thanks for your response.

 

In the process of bringing the set up back up, I am facing exception in aai-aai-graphadmin-create-db-schema job and aai pods would not start.

 

I did a fresh helm deploy (sudo helm deploy demo ./onap --namespace onap) using new rancher. Cleared the /dockerdata-nfs. So it doesn’t have any stale entries.

I am using Casablanca oom kubernetes deployment environment. The same thing was working fine earlier and I haven’t changed anything.

 

Please find the exception attached.  It fails to instantiate Graph.  I also see same exception when I try to execute the command sh createDBSchema.sh inside the container with aaiadmin user.

 

Please find the aai pods below.

aaiadmin@demo-aai-aai-graphadmin-create-db-schema-mh4l9:/opt/app/aai-graphadmin/bin$ sh createDBSchema.sh

 

 

demo-aai-aai-75b9c64998-tdkrc                          0/1       Init:0/1           2          25m

demo-aai-aai-babel-5499b48894-f8qf2                    2/2       Running            0          25m

demo-aai-aai-cassandra-0                               1/1       Running            0          25m

demo-aai-aai-cassandra-1                               1/1       Running            1          22m

demo-aai-aai-cassandra-2                               1/1       Running            0          21m

demo-aai-aai-champ-75f5d6f664-26295                    1/2       Running            0          25m

demo-aai-aai-data-router-94f79b78f-dqp8l               2/2       Running            0          25m

demo-aai-aai-elasticsearch-f868cff98-p4grb             1/1       Running            0          25m

demo-aai-aai-gizmo-7b6ff8f6f-lkxwf                     2/2       Running            0          25m

demo-aai-aai-graphadmin-8485cd6c85-bls7f               0/2       Init:0/1           2          25m

demo-aai-aai-graphadmin-create-db-schema-mh4l9         1/1       Running            0          51s

demo-aai-aai-modelloader-77496bd596-wr9tp              2/2       Running            0          25m

demo-aai-aai-resources-6d8d78cb-jlsjf                  0/2       Init:0/1           2          25m

demo-aai-aai-search-data-5d7fc5cc8c-hcrl9              2/2       Running            0          25m

demo-aai-aai-sparky-be-6598bf956c-6nc28                0/2       Init:0/1           0          25m

demo-aai-aai-spike-6546658f99-2bwr9                    2/2       Running            0          25m

demo-aai-aai-traversal-5d8df67875-srngg                0/2       Init:0/1           2          25m

demo-aai-aai-traversal-update-query-data-xdf2w         0/1       Init:0/1           2          25m

 

This issue is blocking me from proceeding further. Any pointer is much appreciated.

 

Thanks,

Thiriloshini

 

From: David.PerezCaparros@... <David.PerezCaparros@...> 
Sent: Tuesday, March 19, 2019 7:58 AM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Keong.Lim@...; jf2512@...; Rao, Ravi <Ravi.Rao@...>
Subject: Re: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

Hi Thiriloshini, 

 

in case it helps, regarding making new edgerules work in a running deployment of Casablanca, this is what I did:

- add new edgerules in aai-resources, aai-traversal, aai-graphadmin, under v14 folder /opt/app/…/resources/schema/onap/dbedgerules/v14/

- run in aai-graphadmin as aaiadmin user the createDBSchema.sh script under /opt/app/aai-graphadmin/bin/

- restart docker containers (not deleting the pod) aai-resources, aai-traversal, aai-graphadmin

 

Regards

David




 

Keong,

 

I changed the EdgeRules in development environment by following the tutorial and things work as expected.

-        Changed the EdgeRule

-        Build aai-common,  resource, traversal, graphadmin.

-        Started resource and traversal microservices as suggested in the tutorial.

-        Deleting esr-thirdparty-sdnc deleted the associated pnfs.

 

I build the docker images – traversal, resource, graphadmin from the source code and used those images to run the container in

Deployment environment. 

The dev-aai-graphadmin-create-db-schema fails. When I try to execute the docker-entrypoint.sh and createDBSchema.sh manually inside the dev-aai-graphadmin-create-db-schema container I see the below error

aaiadmin@dev-aai-graphadmin-create-db-schema-bh2b2:/opt/app/aai-graphadmin/scripts$ sh createDBSchema.sh

 

Tue Mar 19 02:54:55 UTC 2019    Starting createDBSchema.sh

    ---- NOTE --- about to open graph (takes a little while)--------;

-- Loading new schema elements into JanusGraph --

Failed to run the tool createDBSchema.sh successfully

 

I do not any errors in error.log under logs/createDBSchema

 

I also tried the below:

 

Instead of using the imaged build from development environment, used the same images that comes with the Casablanca deployment environment. Changed the edgerules in resource, traversal, graphadmin and run the createDBSchema.sh in graphadmin. The edgerules change doesn’t take effect. I understand that this method isn’t persistent.

 

Any pointer would be useful.

 

Thanks,

Thiriloshini

 

From: Keong Lim <Keong.Lim@...> 
Sent: Sunday, March 17, 2019 7:24 PM
To: Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>; onap-discuss@...; FORSYTH, JAMES <jf2512@...>
Cc: Rao, Ravi <Ravi.Rao@...>
Subject: RE: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

Hi Thiriloshini,

 

Yes, the EdgeRules can be changed in a running OOM-based system, however the aai-traversal is not enough.

As per the wiki Tutorial, the change also needs to be in schema-service, graphadmin and aai-resources, and you need to run create-db-schema script to apply it to the database.

 

However, the method you are using has not been documented, because it is not a recommended method and it isn’t persistent when the pods are re-deployed.

 

If you can do it, please build new containers and deploy them into your OOM-based system.

 

 

Keong

 

 

From: Thiriloshini.ThoppeKrishnakumar@... [mailto:Thiriloshini.ThoppeKrishnakumar@...] 
Sent: Saturday, 16 March 2019 18:10
To: onap-discuss@...; Keong Lim <Keong.Lim@...>; FORSYTH, JAMES <jf2512@...>
Cc: Ravi.Rao@...
Subject: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

 

Please find my questions below

 

1.      Can the DbEdgeRules be changed in a deployment environment ?

2.      If it can be done, am I changing in the right place ? 

3.      Please let me know if I am missing something here.

 

Any pointer is much appreciated.

 

Thanks,

Thiriloshini

 

<Job_aai-graphadmin-create-db-schema_exception.txt>

 


Re: [AAI] Changing dbedgerules in onap deployment environment

David Perez Caparros
 

did you also deleted the persistent volume claims before redeploying?
# kubectl get pvc -n onap | grep aai


David/ Keong,
 
Thanks for your response.
 
In the process of bringing the set up back up, I am facing exception in aai-aai-graphadmin-create-db-schema job and aai pods would not start.
 
I did a fresh helm deploy (sudo helm deploy demo ./onap --namespace onap) using new rancher. Cleared the /dockerdata-nfs. So it doesn’t have any stale entries.
I am using Casablanca oom kubernetes deployment environment. The same thing was working fine earlier and I haven’t changed anything.
 
Please find the exception attached.  It fails to instantiate Graph.  I also see same exception when I try to execute the command sh createDBSchema.sh inside the container with aaiadmin user.
 
Please find the aai pods below.
aaiadmin@demo-aai-aai-graphadmin-create-db-schema-mh4l9:/opt/app/aai-graphadmin/bin$ sh createDBSchema.sh
 
 
demo-aai-aai-75b9c64998-tdkrc                          0/1       Init:0/1           2          25m
demo-aai-aai-babel-5499b48894-f8qf2                    2/2       Running            0          25m
demo-aai-aai-cassandra-0                               1/1       Running            0          25m
demo-aai-aai-cassandra-1                               1/1       Running            1          22m
demo-aai-aai-cassandra-2                               1/1       Running            0          21m
demo-aai-aai-champ-75f5d6f664-26295                    1/2       Running            0          25m
demo-aai-aai-data-router-94f79b78f-dqp8l               2/2       Running            0          25m
demo-aai-aai-elasticsearch-f868cff98-p4grb             1/1       Running            0          25m
demo-aai-aai-gizmo-7b6ff8f6f-lkxwf                     2/2       Running            0          25m
demo-aai-aai-graphadmin-8485cd6c85-bls7f               0/2       Init:0/1           2          25m
demo-aai-aai-graphadmin-create-db-schema-mh4l9         1/1       Running            0          51s
demo-aai-aai-modelloader-77496bd596-wr9tp              2/2       Running            0          25m
demo-aai-aai-resources-6d8d78cb-jlsjf                  0/2       Init:0/1           2          25m
demo-aai-aai-search-data-5d7fc5cc8c-hcrl9              2/2       Running            0          25m
demo-aai-aai-sparky-be-6598bf956c-6nc28                0/2       Init:0/1           0          25m
demo-aai-aai-spike-6546658f99-2bwr9                    2/2       Running            0          25m
demo-aai-aai-traversal-5d8df67875-srngg                0/2       Init:0/1           2          25m
demo-aai-aai-traversal-update-query-data-xdf2w         0/1       Init:0/1           2          25m
 
This issue is blocking me from proceeding further. Any pointer is much appreciated.
 
Thanks,
Thiriloshini
 
From: David.PerezCaparros@... <David.PerezCaparros@...> 
Sent: Tuesday, March 19, 2019 7:58 AM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Keong.Lim@...; jf2512@...; Rao, Ravi <Ravi.Rao@...>
Subject: Re: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment
 
Hi Thiriloshini, 
 
in case it helps, regarding making new edgerules work in a running deployment of Casablanca, this is what I did:
- add new edgerules in aai-resources, aai-traversal, aai-graphadmin, under v14 folder /opt/app/…/resources/schema/onap/dbedgerules/v14/
- run in aai-graphadmin as aaiadmin user the createDBSchema.sh script under /opt/app/aai-graphadmin/bin/
- restart docker containers (not deleting the pod) aai-resources, aai-traversal, aai-graphadmin
 
Regards
David


 
Keong,
 
I changed the EdgeRules in development environment by following the tutorial and things work as expected.
-        Changed the EdgeRule
-        Build aai-common,  resource, traversal, graphadmin.
-        Started resource and traversal microservices as suggested in the tutorial.
-        Deleting esr-thirdparty-sdnc deleted the associated pnfs.
 
I build the docker images – traversal, resource, graphadmin from the source code and used those images to run the container in
Deployment environment. 
The dev-aai-graphadmin-create-db-schema fails. When I try to execute the docker-entrypoint.sh and createDBSchema.sh manually inside the dev-aai-graphadmin-create-db-schema container I see the below error
aaiadmin@dev-aai-graphadmin-create-db-schema-bh2b2:/opt/app/aai-graphadmin/scripts$ sh createDBSchema.sh
 
Tue Mar 19 02:54:55 UTC 2019    Starting createDBSchema.sh
    ---- NOTE --- about to open graph (takes a little while)--------;
-- Loading new schema elements into JanusGraph --
Failed to run the tool createDBSchema.sh successfully
 
I do not any errors in error.log under logs/createDBSchema
 
I also tried the below:
 
Instead of using the imaged build from development environment, used the same images that comes with the Casablanca deployment environment. Changed the edgerules in resource, traversal, graphadmin and run the createDBSchema.sh in graphadmin. The edgerules change doesn’t take effect. I understand that this method isn’t persistent.
 
Any pointer would be useful.
 
Thanks,
Thiriloshini
 
From: Keong Lim <Keong.Lim@...> 
Sent: Sunday, March 17, 2019 7:24 PM
To: Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>; onap-discuss@...; FORSYTH, JAMES <jf2512@...>
Cc: Rao, Ravi <Ravi.Rao@...>
Subject: RE: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment
 
Hi Thiriloshini,
 
Yes, the EdgeRules can be changed in a running OOM-based system, however the aai-traversal is not enough.
As per the wiki Tutorial, the change also needs to be in schema-service, graphadmin and aai-resources, and you need to run create-db-schema script to apply it to the database.
 
However, the method you are using has not been documented, because it is not a recommended method and it isn’t persistent when the pods are re-deployed.
 
If you can do it, please build new containers and deploy them into your OOM-based system.
 
 
Keong
 
 
From: Thiriloshini.ThoppeKrishnakumar@... [mailto:Thiriloshini.ThoppeKrishnakumar@...] 
Sent: Saturday, 16 March 2019 18:10
To: onap-discuss@...; Keong Lim <Keong.Lim@...>; FORSYTH, JAMES <jf2512@...>
Cc: Ravi.Rao@...
Subject: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment
 
 
Please find my questions below
 
1.      Can the DbEdgeRules be changed in a deployment environment ?
2.      If it can be done, am I changing in the right place ? 
3.      Please let me know if I am missing something here.
 
Any pointer is much appreciated.
 
Thanks,
Thiriloshini

 
<Job_aai-graphadmin-create-db-schema_exception.txt>


Re: [AAI] Changing dbedgerules in onap deployment environment

Thiriloshini.ThoppeKrishnakumar@us.fujitsu.com
 

David/ Keong,

 

Thanks for your response.

 

In the process of bringing the set up back up, I am facing exception in aai-aai-graphadmin-create-db-schema job and aai pods would not start.

 

I did a fresh helm deploy (sudo helm deploy demo ./onap --namespace onap) using new rancher. Cleared the /dockerdata-nfs. So it doesn’t have any stale entries.

I am using Casablanca oom kubernetes deployment environment. The same thing was working fine earlier and I haven’t changed anything.

 

Please find the exception attached.  It fails to instantiate Graph.  I also see same exception when I try to execute the command sh createDBSchema.sh inside the container with aaiadmin user.

 

Please find the aai pods below.

aaiadmin@demo-aai-aai-graphadmin-create-db-schema-mh4l9:/opt/app/aai-graphadmin/bin$ sh createDBSchema.sh

 

 

demo-aai-aai-75b9c64998-tdkrc                          0/1       Init:0/1           2          25m

demo-aai-aai-babel-5499b48894-f8qf2                    2/2       Running            0          25m

demo-aai-aai-cassandra-0                               1/1       Running            0          25m

demo-aai-aai-cassandra-1                               1/1       Running            1          22m

demo-aai-aai-cassandra-2                               1/1       Running            0          21m

demo-aai-aai-champ-75f5d6f664-26295                    1/2       Running            0          25m

demo-aai-aai-data-router-94f79b78f-dqp8l               2/2       Running            0          25m

demo-aai-aai-elasticsearch-f868cff98-p4grb             1/1       Running            0          25m

demo-aai-aai-gizmo-7b6ff8f6f-lkxwf                     2/2       Running            0          25m

demo-aai-aai-graphadmin-8485cd6c85-bls7f               0/2       Init:0/1           2          25m

demo-aai-aai-graphadmin-create-db-schema-mh4l9         1/1       Running            0          51s

demo-aai-aai-modelloader-77496bd596-wr9tp              2/2       Running            0          25m

demo-aai-aai-resources-6d8d78cb-jlsjf                  0/2       Init:0/1           2          25m

demo-aai-aai-search-data-5d7fc5cc8c-hcrl9              2/2       Running            0          25m

demo-aai-aai-sparky-be-6598bf956c-6nc28                0/2       Init:0/1           0          25m

demo-aai-aai-spike-6546658f99-2bwr9                    2/2       Running            0          25m

demo-aai-aai-traversal-5d8df67875-srngg                0/2       Init:0/1           2          25m

demo-aai-aai-traversal-update-query-data-xdf2w         0/1       Init:0/1           2          25m

 

This issue is blocking me from proceeding further. Any pointer is much appreciated.

 

Thanks,

Thiriloshini

 

From: David.PerezCaparros@... <David.PerezCaparros@...>
Sent: Tuesday, March 19, 2019 7:58 AM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Keong.Lim@...; jf2512@...; Rao, Ravi <Ravi.Rao@...>
Subject: Re: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

Hi Thiriloshini,

 

in case it helps, regarding making new edgerules work in a running deployment of Casablanca, this is what I did:

- add new edgerules in aai-resources, aai-traversal, aai-graphadmin, under v14 folder /opt/app/…/resources/schema/onap/dbedgerules/v14/

- run in aai-graphadmin as aaiadmin user the createDBSchema.sh script under /opt/app/aai-graphadmin/bin/

- restart docker containers (not deleting the pod) aai-resources, aai-traversal, aai-graphadmin

 

Regards

David



 

Keong,

 

I changed the EdgeRules in development environment by following the tutorial and things work as expected.

-        Changed the EdgeRule

-        Build aai-common,  resource, traversal, graphadmin.

-        Started resource and traversal microservices as suggested in the tutorial.

-        Deleting esr-thirdparty-sdnc deleted the associated pnfs.

 

I build the docker images – traversal, resource, graphadmin from the source code and used those images to run the container in

Deployment environment. 

The dev-aai-graphadmin-create-db-schema fails. When I try to execute the docker-entrypoint.sh and createDBSchema.sh manually inside the dev-aai-graphadmin-create-db-schema container I see the below error

aaiadmin@dev-aai-graphadmin-create-db-schema-bh2b2:/opt/app/aai-graphadmin/scripts$ sh createDBSchema.sh

 

Tue Mar 19 02:54:55 UTC 2019    Starting createDBSchema.sh

    ---- NOTE --- about to open graph (takes a little while)--------;

-- Loading new schema elements into JanusGraph --

Failed to run the tool createDBSchema.sh successfully

 

I do not any errors in error.log under logs/createDBSchema

 

I also tried the below:

 

Instead of using the imaged build from development environment, used the same images that comes with the Casablanca deployment environment. Changed the edgerules in resource, traversal, graphadmin and run the createDBSchema.sh in graphadmin. The edgerules change doesn’t take effect. I understand that this method isn’t persistent.

 

Any pointer would be useful.

 

Thanks,

Thiriloshini

 

From: Keong Lim <Keong.Lim@...> 
Sent: Sunday, March 17, 2019 7:24 PM
To: Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>; onap-discuss@...; FORSYTH, JAMES <jf2512@...>
Cc: Rao, Ravi <Ravi.Rao@...>
Subject: RE: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

Hi Thiriloshini,

 

Yes, the EdgeRules can be changed in a running OOM-based system, however the aai-traversal is not enough.

As per the wiki Tutorial, the change also needs to be in schema-service, graphadmin and aai-resources, and you need to run create-db-schema script to apply it to the database.

 

However, the method you are using has not been documented, because it is not a recommended method and it isn’t persistent when the pods are re-deployed.

 

If you can do it, please build new containers and deploy them into your OOM-based system.

 

 

Keong

 

 

From: Thiriloshini.ThoppeKrishnakumar@... [mailto:Thiriloshini.ThoppeKrishnakumar@...] 
Sent: Saturday, 16 March 2019 18:10
To: onap-discuss@...; Keong Lim <Keong.Lim@...>; FORSYTH, JAMES <jf2512@...>
Cc: Ravi.Rao@...
Subject: [onap-discuss] [AAI] Changing dbedgerules in onap deployment environment

 

 

Please find my questions below

 

1.      Can the DbEdgeRules be changed in a deployment environment ?

2.      If it can be done, am I changing in the right place ? 

3.      Please let me know if I am missing something here.

 

Any pointer is much appreciated.

 

Thanks,

Thiriloshini

 


Re: demo-k8s.sh onap init failing

Brian Freeman
 

You dont need to modify /etc/hosts on the robot server unless you are having a dns issue.

Simply put the ip for the keystone server into the appropriate variable in values.yaml or integration-override.yaml

 

The robot section of integration-override.yaml should look something like this (Dublin).

 

robot:

  enabled: true

  flavor: large

  appcUsername: "WWWW "

  appcPassword: "XXXXXXXXX"

  openStackKeyStoneUrl: "http://10.12.25.2:5000"

  openStackPublicNetId: "971040b2-7059-49dc-b220-4fab50cb2ad4"

  openStackTenantId: "41d6d38489bd40b09ea8a6b6b852dcbd"

  openStackUserName: "XXXXX"

  ubuntu14Image: "ubuntu-14-04-cloud-amd64"

  ubuntu16Image: "ubuntu-16-04-cloud-amd64"

  openStackPrivateNetId: "a92eabce-986a-49f3-bb1b-3b555b6b72f1"

  openStackPrivateSubnetId: "19d93c41-1ab0-490a-b54b-63748ed9d2ce"

  openStackPrivateNetCidr: "10.0.0.0/16"

  openStackSecurityGroup: "af234ffb-1510-4c92-b6c0-453a22d976b5"

  openStackOamNetworkCidrPrefix: "10.0"

  dcaeCollectorIp: "10.12.5.111"

  vnfPubKey: "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDKXDgoo3+WOqcUG8/5uUbk81+yczgwC4Y8ywTmuQqbNxlY1oQ0YxdMUqUnhitSXs5S/yRuAVOYHwGg2mCs20oAINrP+mxBI544AMIb9itPjCtgqtE2EWo6MmnFGbHB4Sx3XioE7F4VPsh7japsIwzOjbrQe+Mua1TGQ5d4nfEOQaaglXLLPFfuc7WbhbJbK6Q7rHqZfRcOwAMXgDoBqlyqKeiKwnumddo2RyNT8ljYmvB6buz7KnMinzo7qB0uktVT05FH9Rg0CTWH5norlG5qXgP2aukL0gk1ph8iAt7uYLf1ktp+LJI2gaF6L0/qli9EmVCSLr1uJ38Q8CBflhkh"

  demoArtifactsVersion: "1.3.0"

  demoArtifactsRepoUrl: "https://nexus.onap.org/content/repositories/releases"

  scriptVersion: "1.3.0"

  rancherIpAddress: "10.12.5.137"

  config:

    openStackEncryptedPasswordHere: "bbaefXXXXXXXXXXXXXXXXX7dbb9"

From: onap-discuss@... <onap-discuss@...> On Behalf Of kranthi guttikonda
Sent: Tuesday, March 19, 2019 10:32 AM
To: onap-discuss@...; oparindeoyebimpe1@...; FREEMAN, BRIAN D <bf1936@...>
Subject: Re: [onap-discuss] demo-k8s.sh onap init failing

 

Do you have connectivity to keystone ip?

 

Login to robot container and try to ping.

 

You have to update robot deployment by modifying templates/demployment.yaml (I am thinking to give this enhancement)

 

For an example in pod.spec update like below

 

hostAliases:

  - ip: "1.2.3.4"

    hostnames:

    - "novncproxy.openstack.svc.cluster.local"

    - "keystone.openstack.svc.cluster.local"

    - "nova.openstack.svc.cluster.local"

    - "neutron.openstack.svc.cluster.local"

    - "glance.openstack.svc.cluster.local"

    - "cinder.openstack.svc.cluster.local"

    - "heat.openstack.svc.cluster.local"

 

This will add entries to robot /etc/hosts file automatically or you need to adjust your upstream DNS servers to resolve these but again your kube-dns or Coredns must be configured to use upstream DNS servers.

 

Make robot and onap

 

Redeploy.

 

Thanks,
Kranthi

 

From: <onap-discuss@...> on behalf of "Oyebimpe Oparinde via Lists.Onap.Org" <oparindeoyebimpe1=gmail.com@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "oparindeoyebimpe1@..." <oparindeoyebimpe1@...>
Date: Tuesday, March 19, 2019 at 10:12 AM
To: "FREEMAN, BRIAN D" <bf1936@...>
Cc: "onap-discuss@..." <onap-discuss@...>
Subject: Re: [onap-discuss] demo-k8s.sh onap init failing

 

Thanks for your response.

 

I ran the make robot; make onap command and I got this error :(

 

 

ubuntu@k8s-1:~/oom/kubernetes$ make robot; make onap

 

[robot]

make[1]: Entering directory '/home/ubuntu/oom/kubernetes'

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879):

Get http://127.0.0.1:8879/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused

Update Complete. Happy Helming!

Saving 1 charts

Downloading common from repo http://127.0.0.1:8879

Save error occurred:  could not download http://127.0.0.1:8879/charts/common-3.0.0.tgz: Get http://127.0.0.1:8879/charts/common-3.0.0.tgz: dial tcp 127.0.0.1:8879: connect: connection refused

Deleting newly downloaded charts, restoring pre-update state

Makefile:42: recipe for target 'dep-robot' failed

make[1]: *** [dep-robot] Error 1

make[1]: Leaving directory '/home/ubuntu/oom/kubernetes'

Makefile:35: recipe for target 'robot' failed

make: *** [robot] Error 2

 

[onap]

make[1]: Entering directory '/home/ubuntu/oom/kubernetes'

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879):

Get http://127.0.0.1:8879/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused

Update Complete. Happy Helming!

Saving 30 charts

Downloading aaf from repo http://127.0.0.1:8879

Save error occurred:  could not download http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: Get http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: dial tcp 127.0.0.1:8879: connect: connection refused

Deleting newly downloaded charts, restoring pre-update state

Error: could not download http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: Get http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: dial tcp 127.0.0.1:8879: connect: connection refused

Makefile:42: recipe for target 'dep-onap' failed

make[1]: *** [dep-onap] Error 1

make[1]: Leaving directory '/home/ubuntu/oom/kubernetes'

Makefile:35: recipe for target 'onap' failed

make: *** [onap] Error 2

 

 

Did I miss something? Please help.

 

Thanks in advance,

Bimpe.

 

On Tue, Mar 19, 2019 at 1:38 PM FREEMAN, BRIAN D <bf1936@...> wrote:

Did you run make robot ; make onap ?

Your robot is still using the default ip

 

Brian

 

 

 

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

 

 

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

From: Oyebimpe Oparinde <oparindeoyebimpe1@...>

Date: 3/19/19 4:35 AM (GMT-05:00)

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

Subject: demo-k8s.sh onap init failing

 

Hi,

 

I'm trying to implement the vFW use case on ONAP C release.

 

I ran the ./demo-k8s.sh onap init command but failed with the below error.

 

btw; I have edited the values.yaml file in the directory  ~/oom/kubernetes/robot/values.yaml

 

 

 

Number of parameters:

2

KEY:

init

++ kubectl --namespace onap get pods

++ sed 's/ .*//'

++ grep robot

+ POD=dev-robot-d474f544c-sjr78

+ ETEHOME=/var/opt/OpenECOMP_ETE

++ kubectl --namespace onap exec dev-robot-d474f544c-sjr78 -- bash -c 'ls -1q /share/logs/ | wc -l'

+ export GLOBAL_BUILD_NUMBER=31

+ GLOBAL_BUILD_NUMBER=31

++ printf %04d 31

+ OUTPUT_FOLDER=0031_demo_init

+ DISPLAY_NUM=121

+ VARIABLEFILES='-V /share/config/vm_properties.py -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py'

+ kubectl --namespace onap exec dev-robot-d474f544c-sjr78 -- /var/opt/OpenECOMP_ETE/runTags.sh -V /share/config/vm_properties.py -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py -d /share/logs/0031_demo_init -i InitDemo --display 121

Starting Xvfb on display :121 with res 1280x1024x24

Executing robot tests at log level TRACE

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

Testsuites                                                                    

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

Testsuites.Demo :: Executes the VNF Orchestration Test cases including setu...

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

Initialize Customer And Models                                        | FAIL |

ConnectionError: HTTPConnectionPool(host='1.2.3.4', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7ff3bd05d890>: Failed to establish a new connection: [Errno 101] Network is unreachable',))

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

Testsuites.Demo :: Executes the VNF Orchestration Test cases inclu... | FAIL |

1 critical test, 0 passed, 1 failed

1 test total, 0 passed, 1 failed

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

Testsuites                                                            | FAIL |

1 critical test, 0 passed, 1 failed

1 test total, 0 passed, 1 failed

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

Output:  /share/logs/0031_demo_init/output.xml

Log:     /share/logs/0031_demo_init/log.html

Report:  /share/logs/0031_demo_init/report.html

 

 

 

Please help solve the problem.

 

Kind Regards,

Bimpe.


Re: demo-k8s.sh onap init failing

kranthi guttikonda
 

Also for helm make errors. Make sure you run the helm server

 

Helm serve &

 

Thanks,
Kranthi

 

From: Kranthi Guttikonda <kranthi.guttikonda@...>
Date: Tuesday, March 19, 2019 at 10:31 AM
To: "onap-discuss@..." <onap-discuss@...>, "oparindeoyebimpe1@..." <oparindeoyebimpe1@...>, "FREEMAN, BRIAN D" <bf1936@...>
Subject: Re: [onap-discuss] demo-k8s.sh onap init failing

 

Do you have connectivity to keystone ip?

 

Login to robot container and try to ping.

 

You have to update robot deployment by modifying templates/demployment.yaml (I am thinking to give this enhancement)

 

For an example in pod.spec update like below

 

hostAliases:

  - ip: "1.2.3.4"

    hostnames:

    - "novncproxy.openstack.svc.cluster.local"

    - "keystone.openstack.svc.cluster.local"

    - "nova.openstack.svc.cluster.local"

    - "neutron.openstack.svc.cluster.local"

    - "glance.openstack.svc.cluster.local"

    - "cinder.openstack.svc.cluster.local"

    - "heat.openstack.svc.cluster.local"

 

This will add entries to robot /etc/hosts file automatically or you need to adjust your upstream DNS servers to resolve these but again your kube-dns or Coredns must be configured to use upstream DNS servers.

 

Make robot and onap

 

Redeploy.

 

Thanks,
Kranthi

 

From: <onap-discuss@...> on behalf of "Oyebimpe Oparinde via Lists.Onap.Org" <oparindeoyebimpe1=gmail.com@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "oparindeoyebimpe1@..." <oparindeoyebimpe1@...>
Date: Tuesday, March 19, 2019 at 10:12 AM
To: "FREEMAN, BRIAN D" <bf1936@...>
Cc: "onap-discuss@..." <onap-discuss@...>
Subject: Re: [onap-discuss] demo-k8s.sh onap init failing

 

Thanks for your response.

 

I ran the make robot; make onap command and I got this error :(

 

 

ubuntu@k8s-1:~/oom/kubernetes$ make robot; make onap

 

[robot]

make[1]: Entering directory '/home/ubuntu/oom/kubernetes'

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879):

Get http://127.0.0.1:8879/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused

Update Complete. Happy Helming!

Saving 1 charts

Downloading common from repo http://127.0.0.1:8879

Save error occurred:  could not download http://127.0.0.1:8879/charts/common-3.0.0.tgz: Get http://127.0.0.1:8879/charts/common-3.0.0.tgz: dial tcp 127.0.0.1:8879: connect: connection refused

Deleting newly downloaded charts, restoring pre-update state

Makefile:42: recipe for target 'dep-robot' failed

make[1]: *** [dep-robot] Error 1

make[1]: Leaving directory '/home/ubuntu/oom/kubernetes'

Makefile:35: recipe for target 'robot' failed

make: *** [robot] Error 2

 

[onap]

make[1]: Entering directory '/home/ubuntu/oom/kubernetes'

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879):

Get http://127.0.0.1:8879/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused

Update Complete. Happy Helming!

Saving 30 charts

Downloading aaf from repo http://127.0.0.1:8879

Save error occurred:  could not download http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: Get http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: dial tcp 127.0.0.1:8879: connect: connection refused

Deleting newly downloaded charts, restoring pre-update state

Error: could not download http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: Get http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: dial tcp 127.0.0.1:8879: connect: connection refused

Makefile:42: recipe for target 'dep-onap' failed

make[1]: *** [dep-onap] Error 1

make[1]: Leaving directory '/home/ubuntu/oom/kubernetes'

Makefile:35: recipe for target 'onap' failed

make: *** [onap] Error 2

 

 

Did I miss something? Please help.

 

Thanks in advance,

Bimpe.

 

On Tue, Mar 19, 2019 at 1:38 PM FREEMAN, BRIAN D <bf1936@...> wrote:

Did you run make robot ; make onap ?

Your robot is still using the default ip

 

Brian

 

 

 

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

 

 

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

From: Oyebimpe Oparinde <oparindeoyebimpe1@...>

Date: 3/19/19 4:35 AM (GMT-05:00)

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

Subject: demo-k8s.sh onap init failing

 

Hi,

 

I'm trying to implement the vFW use case on ONAP C release.

 

I ran the ./demo-k8s.sh onap init command but failed with the below error.

 

btw; I have edited the values.yaml file in the directory  ~/oom/kubernetes/robot/values.yaml

 

 

 

Number of parameters:

2

KEY:

init

++ kubectl --namespace onap get pods

++ sed 's/ .*//'

++ grep robot

+ POD=dev-robot-d474f544c-sjr78

+ ETEHOME=/var/opt/OpenECOMP_ETE

++ kubectl --namespace onap exec dev-robot-d474f544c-sjr78 -- bash -c 'ls -1q /share/logs/ | wc -l'

+ export GLOBAL_BUILD_NUMBER=31

+ GLOBAL_BUILD_NUMBER=31

++ printf %04d 31

+ OUTPUT_FOLDER=0031_demo_init

+ DISPLAY_NUM=121

+ VARIABLEFILES='-V /share/config/vm_properties.py -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py'

+ kubectl --namespace onap exec dev-robot-d474f544c-sjr78 -- /var/opt/OpenECOMP_ETE/runTags.sh -V /share/config/vm_properties.py -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py -d /share/logs/0031_demo_init -i InitDemo --display 121

Starting Xvfb on display :121 with res 1280x1024x24

Executing robot tests at log level TRACE

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

Testsuites                                                                    

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

Testsuites.Demo :: Executes the VNF Orchestration Test cases including setu...

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

Initialize Customer And Models                                        | FAIL |

ConnectionError: HTTPConnectionPool(host='1.2.3.4', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7ff3bd05d890>: Failed to establish a new connection: [Errno 101] Network is unreachable',))

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

Testsuites.Demo :: Executes the VNF Orchestration Test cases inclu... | FAIL |

1 critical test, 0 passed, 1 failed

1 test total, 0 passed, 1 failed

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

Testsuites                                                            | FAIL |

1 critical test, 0 passed, 1 failed

1 test total, 0 passed, 1 failed

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

Output:  /share/logs/0031_demo_init/output.xml

Log:     /share/logs/0031_demo_init/log.html

Report:  /share/logs/0031_demo_init/report.html

 

 

 

Please help solve the problem.

 

Kind Regards,

Bimpe.


Re: demo-k8s.sh onap init failing

Brian Freeman
 

I suspect there are steps you are missing to run  start the helm server and run make all locally the first time (and maybe copy deploy to your .helm)

 

If you update helm charts you need a functioning helm repo to save them do which is what make onap does.

 

Integration-override.yaml is how we set environment specific settings but if you directly modify values.yaml’s then you need helm.

 

https://onap.readthedocs.io/en/casablanca/submodules/oom.git/docs/oom_quickstart_guide.html

 

has steps for that.

 

https://wiki.onap.org/pages/viewpage.action?pageId=29787124

also has some quick kubectl/helm command lines that might be helpful.

 

Brian

 

 

From: Oyebimpe Oparinde <oparindeoyebimpe1@...>
Sent: Tuesday, March 19, 2019 9:57 AM
To: FREEMAN, BRIAN D <bf1936@...>
Cc: onap-discuss@...
Subject: Re: demo-k8s.sh onap init failing

 

Thanks for your response.

 

I ran the make robot; make onap command and I got this error :(

 

 

ubuntu@k8s-1:~/oom/kubernetes$ make robot; make onap

 

[robot]

make[1]: Entering directory '/home/ubuntu/oom/kubernetes'

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879):

               Get http://127.0.0.1:8879/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused

Update Complete. Happy Helming!

Saving 1 charts

Downloading common from repo http://127.0.0.1:8879

Save error occurred:  could not download http://127.0.0.1:8879/charts/common-3.0.0.tgz: Get http://127.0.0.1:8879/charts/common-3.0.0.tgz: dial tcp 127.0.0.1:8879: connect: connection refused

Deleting newly downloaded charts, restoring pre-update state

Makefile:42: recipe for target 'dep-robot' failed

make[1]: *** [dep-robot] Error 1

make[1]: Leaving directory '/home/ubuntu/oom/kubernetes'

Makefile:35: recipe for target 'robot' failed

make: *** [robot] Error 2

 

[onap]

make[1]: Entering directory '/home/ubuntu/oom/kubernetes'

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879):

               Get http://127.0.0.1:8879/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused

Update Complete. Happy Helming!

Saving 30 charts

Downloading aaf from repo http://127.0.0.1:8879

Save error occurred:  could not download http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: Get http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: dial tcp 127.0.0.1:8879: connect: connection refused

Deleting newly downloaded charts, restoring pre-update state

Error: could not download http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: Get http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: dial tcp 127.0.0.1:8879: connect: connection refused

Makefile:42: recipe for target 'dep-onap' failed

make[1]: *** [dep-onap] Error 1

make[1]: Leaving directory '/home/ubuntu/oom/kubernetes'

Makefile:35: recipe for target 'onap' failed

make: *** [onap] Error 2

 

 

Did I miss something? Please help.

 

Thanks in advance,

Bimpe.

 

On Tue, Mar 19, 2019 at 1:38 PM FREEMAN, BRIAN D <bf1936@...> wrote:

Did you run make robot ; make onap ?

Your robot is still using the default ip

 

Brian

 

 

 

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

 

 

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

From: Oyebimpe Oparinde <oparindeoyebimpe1@...>

Date: 3/19/19 4:35 AM (GMT-05:00)

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

Subject: demo-k8s.sh onap init failing

 

Hi,

 

I'm trying to implement the vFW use case on ONAP C release.

 

I ran the ./demo-k8s.sh onap init command but failed with the below error.

 

btw; I have edited the values.yaml file in the directory  ~/oom/kubernetes/robot/values.yaml

 

 

 

Number of parameters:

2

KEY:

init

++ kubectl --namespace onap get pods

++ sed 's/ .*//'

++ grep robot

+ POD=dev-robot-d474f544c-sjr78

+ ETEHOME=/var/opt/OpenECOMP_ETE

++ kubectl --namespace onap exec dev-robot-d474f544c-sjr78 -- bash -c 'ls -1q /share/logs/ | wc -l'

+ export GLOBAL_BUILD_NUMBER=31

+ GLOBAL_BUILD_NUMBER=31

++ printf %04d 31

+ OUTPUT_FOLDER=0031_demo_init

+ DISPLAY_NUM=121

+ VARIABLEFILES='-V /share/config/vm_properties.py -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py'

+ kubectl --namespace onap exec dev-robot-d474f544c-sjr78 -- /var/opt/OpenECOMP_ETE/runTags.sh -V /share/config/vm_properties.py -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py -d /share/logs/0031_demo_init -i InitDemo --display 121

Starting Xvfb on display :121 with res 1280x1024x24

Executing robot tests at log level TRACE

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

Testsuites                                                                    

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

Testsuites.Demo :: Executes the VNF Orchestration Test cases including setu...

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

Initialize Customer And Models                                        | FAIL |

ConnectionError: HTTPConnectionPool(host='1.2.3.4', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7ff3bd05d890>: Failed to establish a new connection: [Errno 101] Network is unreachable',))

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

Testsuites.Demo :: Executes the VNF Orchestration Test cases inclu... | FAIL |

1 critical test, 0 passed, 1 failed

1 test total, 0 passed, 1 failed

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

Testsuites                                                            | FAIL |

1 critical test, 0 passed, 1 failed

1 test total, 0 passed, 1 failed

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

Output:  /share/logs/0031_demo_init/output.xml

Log:     /share/logs/0031_demo_init/log.html

Report:  /share/logs/0031_demo_init/report.html

 

 

 

Please help solve the problem.

 

Kind Regards,

Bimpe.

7021 - 7040 of 23234