Date   
Re: [EXT] Re: [onap-discuss] SO issues about certificates during installation #casablanca #so

D'Alessandro Alessandro Gerardo
 

Hi Ruby,

unfortunately we were NOT able to fix the issue at that time and therefore we moved to Dublin…

 

 

From: ruby.li@... [mailto:ruby.li@...]
Sent: venerdì 18 ottobre 2019 10:59
To: D'Alessandro Alessandro Gerardo <alessandro.dalessandro@...>; onap-discuss@...
Subject: [EXT] Re: [onap-discuss] SO issues about certificates during installation #casablanca #SO

 

On Fri, Feb 15, 2019 at 09:05 AM, D'Alessandro Alessandro Gerardo wrote:

there anyone that can suggest a workaround /solutions for the issue above described?

Hi,
I got the same issue on Dublin release, do you solve the issue? Thanks!
Ruby

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

Rispetta l'ambiente. Non stampare questa mail se non è necessario.

Re: #mariadb-galera #sdc #so #mariadb-galera #sdc #so

Dmitry Puzikov
 

Hi, Marko,

All mariadb data is kept under /dockerdata-nfs/dev-mariadb-galera/mariadb-galera/*{0..2}
I'd reather scale down mariadb to 0 pods, backup those data dirs then delete them for pod1 and pod2  *{1..2} keeping pod0 data dir intact. After that modify grastate.dat as it proposed in the log:
"edit the grastate.dat file manually and set safe_to_bootstrap to 1" and after that scale mariadb up to 1 pod to see if it started successfully. If it is just scale up to 3 or what number you need.

Regards,
Dmitry


From: onap-discuss@... <onap-discuss@...> on behalf of Ferrero Marco Angelo via Lists.Onap.Org <marco.ferrero=telecomitalia.it@...>
Sent: Monday, October 21, 2019 11:35
To: onap-discuss@... <onap-discuss@...>
Subject: [onap-discuss] #mariadb-galera #sdc #so
 
Hi all, today after 73 days con correct working (since August,9 to October,21) all the three pods of mariadb-galera are in CrashLoopbackOff state.
I tried to delete pods dev-mariadb-galera-mariadb-galera-1 and dev-mariadb-galera-mariadb-galera-2 hoping in pods re-creation by kubernetes.
It doesn't happened.
Pod dev-mariadb-galera-mariadb-galera-0 fails because of the readiness check. Mysql in not able to correctly start before the readiness check.
Here is the log of the pods dev-mariadb-galera-mariadb-galera-0

root@cp-1:~/oom/kubernetes# kubectl logs -n onap -f dev-mariadb-galera-mariadb-galera-0 >  faulty_mariadb_galera
root@cp-1:~/oom/kubernetes# cat faulty_mariadb_galera
+ CONTAINER_SCRIPTS_DIR=/usr/share/container-scripts/mysql
+ EXTRA_DEFAULTS_FILE=/etc/my.cnf.d/galera.cnf
+ '[' -z onap ']'
+ echo 'Galera: Finding peers'
Galera: Finding peers
++ hostname -f
++ cut -d. -f2
+ K8S_SVC_NAME=mariadb-galera
+ echo 'Using service name: mariadb-galera'
+ cp /usr/share/container-scripts/mysql/galera.cnf /etc/my.cnf.d/galera.cnf
Using service name: mariadb-galera
+ /usr/bin/peer-finder -on-start=/usr/share/container-scripts/mysql/configure-galera.sh -service=mariadb-galera
2019/10/21 09:01:46 Peer list updated
was []
now [dev-mariadb-galera-mariadb-galera-0.mariadb-galera.onap.svc.cluster.local]
2019/10/21 09:01:46 execing: /usr/share/container-scripts/mysql/configure-galera.sh with stdin: dev-mariadb-galera-mariadb-galera-0.mariadb-galera.onap.svc.cluster.local
2019/10/21 09:01:46
2019/10/21 09:01:47 Peer finder exiting
+ '[' '!' -d /var/lib/mysql/mysql ']'
+ exec mysqld
2019-10-21  9:01:47 140401625143552 [Note] mysqld (mysqld 10.1.24-MariaDB) starting as process 1 ...
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Read nil XID from storage engines, skipping position init
2019-10-21  9:01:47 140401625143552 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib64/galera/libgalera_smm.so'
2019-10-21  9:01:47 140401625143552 [Note] WSREP: wsrep_load(): Galera 25.3.20(r3703) by Codership Oy <info@...> loaded successfully.
2019-10-21  9:01:47 140401625143552 [Note] WSREP: CRC-32C: using hardware acceleration.
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Found saved state: 00000000-0000-0000-0000-000000000000:-1, safe_to_bootsrap: 0
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Passing config to GCS: base_dir = /var/lib/mysql/; base_host = dev-mariadb-galera-mariadb-galera-0.mariadb-galera.onap.svc.cluster.local; base_port = 4567; cert.log_conflicts = no; debug = no; evs.auto_evict = 0; evs.delay_margin = PT1S; evs.delayed_keep_period = PT30S; evs.inactive_check_period = PT0.5S; evs.inactive_timeout = PT15S; evs.join_retrans_period = PT1S; evs.max_install_timeouts = 3; evs.send_window = 4; evs.stats_report_period = PT1M; evs.suspect_timeout = PT5S; evs.user_send_window = 2; evs.view_forget_timeout = PT24H; gcache.dir = /var/lib/mysql/; gcache.keep_pages_size = 0; gcache.mem_size = 0; gcache.name = /var/lib/mysql//galera.cache; gcache.page_size = 128M; gcache.recover = no; gcache.size = 128M; gcomm.thread_prio = ; gcs.fc_debug = 0; gcs.fc_factor = 1.0; gcs.fc_limit = 16; gcs.fc_master_slave = no; gcs.max_packet_size = 64500; gcs.max_throttle = 0.25; gcs.recv_q_hard_limit = 9223372036854775807; gcs.recv_q_soft_limit = 0.25; gcs.sync_donor = no; gmcast.segment = 0; gmcast.versi
2019-10-21  9:01:47 140401625143552 [Note] WSREP: GCache history reset: old(00000000-0000-0000-0000-000000000000:0) -> new(00000000-0000-0000-0000-000000000000:-1)
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Assign initial position for certification: -1, protocol version: -1
2019-10-21  9:01:47 140401625143552 [Note] WSREP: wsrep_sst_grab()
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Start replication
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Setting initial position to 00000000-0000-0000-0000-000000000000:-1
2019-10-21  9:01:47 140401625143552 [ERROR] WSREP: It may not be safe to bootstrap the cluster from this node. It was not the last one to leave the cluster and may not contain all the updates. To force cluster bootstrap with this node, edit the grastate.dat file manually and set safe_to_bootstrap to 1 .
2019-10-21  9:01:47 140401625143552 [ERROR] WSREP: wsrep::connect(gcomm://) failed: 7
2019-10-21  9:01:47 140401625143552 [ERROR] Aborting
 

Someone has an idea of what whas happened ?
Somemone knows how to re-deploy mariadb-galera KEEPING all the data in the underlying databasse ?
Thank you for the help

Marco F.

#mariadb-galera #sdc #so #mariadb-galera #sdc #so

Ferrero Marco Angelo
 

Hi all, today after 73 days con correct working (since August,9 to October,21) all the three pods of mariadb-galera are in CrashLoopbackOff state.
I tried to delete pods dev-mariadb-galera-mariadb-galera-1 and dev-mariadb-galera-mariadb-galera-2 hoping in pods re-creation by kubernetes.
It doesn't happened.
Pod dev-mariadb-galera-mariadb-galera-0 fails because of the readiness check. Mysql in not able to correctly start before the readiness check.
Here is the log of the pods dev-mariadb-galera-mariadb-galera-0

root@cp-1:~/oom/kubernetes# kubectl logs -n onap -f dev-mariadb-galera-mariadb-galera-0 >  faulty_mariadb_galera
root@cp-1:~/oom/kubernetes# cat faulty_mariadb_galera
+ CONTAINER_SCRIPTS_DIR=/usr/share/container-scripts/mysql
+ EXTRA_DEFAULTS_FILE=/etc/my.cnf.d/galera.cnf
+ '[' -z onap ']'
+ echo 'Galera: Finding peers'
Galera: Finding peers
++ hostname -f
++ cut -d. -f2
+ K8S_SVC_NAME=mariadb-galera
+ echo 'Using service name: mariadb-galera'
+ cp /usr/share/container-scripts/mysql/galera.cnf /etc/my.cnf.d/galera.cnf
Using service name: mariadb-galera
+ /usr/bin/peer-finder -on-start=/usr/share/container-scripts/mysql/configure-galera.sh -service=mariadb-galera
2019/10/21 09:01:46 Peer list updated
was []
now [dev-mariadb-galera-mariadb-galera-0.mariadb-galera.onap.svc.cluster.local]
2019/10/21 09:01:46 execing: /usr/share/container-scripts/mysql/configure-galera.sh with stdin: dev-mariadb-galera-mariadb-galera-0.mariadb-galera.onap.svc.cluster.local
2019/10/21 09:01:46
2019/10/21 09:01:47 Peer finder exiting
+ '[' '!' -d /var/lib/mysql/mysql ']'
+ exec mysqld
2019-10-21  9:01:47 140401625143552 [Note] mysqld (mysqld 10.1.24-MariaDB) starting as process 1 ...
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Read nil XID from storage engines, skipping position init
2019-10-21  9:01:47 140401625143552 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib64/galera/libgalera_smm.so'
2019-10-21  9:01:47 140401625143552 [Note] WSREP: wsrep_load(): Galera 25.3.20(r3703) by Codership Oy <info@...> loaded successfully.
2019-10-21  9:01:47 140401625143552 [Note] WSREP: CRC-32C: using hardware acceleration.
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Found saved state: 00000000-0000-0000-0000-000000000000:-1, safe_to_bootsrap: 0
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Passing config to GCS: base_dir = /var/lib/mysql/; base_host = dev-mariadb-galera-mariadb-galera-0.mariadb-galera.onap.svc.cluster.local; base_port = 4567; cert.log_conflicts = no; debug = no; evs.auto_evict = 0; evs.delay_margin = PT1S; evs.delayed_keep_period = PT30S; evs.inactive_check_period = PT0.5S; evs.inactive_timeout = PT15S; evs.join_retrans_period = PT1S; evs.max_install_timeouts = 3; evs.send_window = 4; evs.stats_report_period = PT1M; evs.suspect_timeout = PT5S; evs.user_send_window = 2; evs.view_forget_timeout = PT24H; gcache.dir = /var/lib/mysql/; gcache.keep_pages_size = 0; gcache.mem_size = 0; gcache.name = /var/lib/mysql//galera.cache; gcache.page_size = 128M; gcache.recover = no; gcache.size = 128M; gcomm.thread_prio = ; gcs.fc_debug = 0; gcs.fc_factor = 1.0; gcs.fc_limit = 16; gcs.fc_master_slave = no; gcs.max_packet_size = 64500; gcs.max_throttle = 0.25; gcs.recv_q_hard_limit = 9223372036854775807; gcs.recv_q_soft_limit = 0.25; gcs.sync_donor = no; gmcast.segment = 0; gmcast.versi
2019-10-21  9:01:47 140401625143552 [Note] WSREP: GCache history reset: old(00000000-0000-0000-0000-000000000000:0) -> new(00000000-0000-0000-0000-000000000000:-1)
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Assign initial position for certification: -1, protocol version: -1
2019-10-21  9:01:47 140401625143552 [Note] WSREP: wsrep_sst_grab()
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Start replication
2019-10-21  9:01:47 140401625143552 [Note] WSREP: Setting initial position to 00000000-0000-0000-0000-000000000000:-1
2019-10-21  9:01:47 140401625143552 [ERROR] WSREP: It may not be safe to bootstrap the cluster from this node. It was not the last one to leave the cluster and may not contain all the updates. To force cluster bootstrap with this node, edit the grastate.dat file manually and set safe_to_bootstrap to 1 .
2019-10-21  9:01:47 140401625143552 [ERROR] WSREP: wsrep::connect(gcomm://) failed: 7
2019-10-21  9:01:47 140401625143552 [ERROR] Aborting
 

Someone has an idea of what whas happened ?
Somemone knows how to re-deploy mariadb-galera KEEPING all the data in the underlying databasse ?
Thank you for the help

Marco F.

Re: SO issues about certificates during installation #so #casablanca

Li, Ruby (NSB - CN/Qingdao)
 

On Fri, Feb 15, 2019 at 09:05 AM, D'Alessandro Alessandro Gerardo wrote:
there anyone that can suggest a workaround /solutions for the issue above described?
Hi,
I got the same issue on Dublin release, do you solve the issue? Thanks!
Ruby

#so OOM Deploy SO fail on Dublin release #so

Li, Ruby (NSB - CN/Qingdao)
 

Hi,

I deployed the ONAP dublin release following https://docs.onap.org/en/dublin/submodules/integration.git/docs/onap-oom-heat.html. 
While it always failed at SO component (I tried several times), lots of the pods status are "CrashLoopBackOff":

dev-so-so-5cc657c449-t72gj                                  0/1     CrashLoopBackOff   297        26h
dev-so-so-bpmn-infra-5b4f566958-nn9c2                       1/1     Running            298        26h
dev-so-so-catalog-db-adapter-848cfb744f-lvpj4               0/1     CrashLoopBackOff   303        26h
dev-so-so-mariadb-config-job-ngqqb                          0/1     Completed          0          26h
dev-so-so-monitoring-fbd9fcdfb-tt57f                        1/1     Running            0          26h
dev-so-so-openstack-adapter-594c649b5-5bcrf                 0/1     CrashLoopBackOff   299        26h
dev-so-so-request-db-adapter-55dfd64c57-9xd2p               0/1     CrashLoopBackOff   304        26h
dev-so-so-sdc-controller-55cb98599c-6fngn                   0/1     CrashLoopBackOff   299        26h
dev-so-so-sdnc-adapter-678cf47746-mvlpj                     1/1     Running            0          26h
dev-so-so-vfc-adapter-685969bcd6-ws42n                      0/1     CrashLoopBackOff   301        26h
dev-so-so-vnfm-adapter-79cfd5b9-lvgs6                       1/1     Running            0          26h


I debug the pod and docker, following logs printed: 
root@onap-rancher:~/oom/kubernetes/so# kubectl logs dev-so-so-5cc657c449-t72gj -c so
Installing onap-ca.crt in /usr/local/share/ca-certificates
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
JVM Arguments:  -Djava.security.egd=file:/dev/./urandom -Dlogs_dir=./logs/apih/ -Dlogging.config=/app/logback-spring.xml  -Dspring.config.additional-location=/app/config/override.yaml
 
  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::        (v2.0.5.RELEASE)
 
Application exiting with status code 1

What is the issue for this? I check the "catalogdb" in each dev-mariadb-galera-mariadb-galera-x pod, seems there is no "catalogdb" database. is this the root cause for SO fail? how to fix it?

Thanks,
Ruby

ONAP SO working #so

gantapritham4@...
 

I would like to know the working of SO block in ONAP and the modules within. Can anyone help me out ?

Thanks
Priyatham

[AAI] [portal] Not able to access AAI GUI from ONAP Portal - Latest master (El Alto)

Thiriloshini.ThoppeKrishnakumar@us.fujitsu.com
 

Hi,

 

I have an ONAP Cluster deployed using OOM on latest master (El-Alto)

 

1.      The AAI containers are up and running

ubuntu@onap-rancher-vm:~$ kubectl get po -n onap -o wide | grep aai

dev-aai-aai-66c5dbb669-jbqmm                            1/1     Running            1          22h   10.42.1.131   onap-k8s-vm-1   <none>           <none>

dev-aai-aai-babel-6c74f9f776-bh7n7                      2/2     Running            2          45h   10.42.2.87    onap-k8s-vm-2   <none>           <none>

dev-aai-aai-data-router-76dfd7f4bb-zbr5g                2/2     Running            2          45h   10.42.2.96    onap-k8s-vm-2   <none>           <none>

dev-aai-aai-elasticsearch-665b4859c8-btmk9              1/1     Running            1          45h   10.42.2.91    onap-k8s-vm-2   <none>           <none>

dev-aai-aai-graphadmin-6d4b8fccc4-bk2mj                 2/2     Running            2          45h   10.42.1.111   onap-k8s-vm-1   <none>           <none>

dev-aai-aai-graphadmin-create-db-schema-vldhz           0/1     Completed          0          45h   10.42.2.14    onap-k8s-vm-2   <none>           <none>

dev-aai-aai-graphgraph-7645ff8687-g5f56                 1/1     Running            1          45h   10.42.2.95    onap-k8s-vm-2   <none>           <none>

dev-aai-aai-modelloader-6dffb4788f-c9wfs                2/2     Running            2          45h   10.42.1.118   onap-k8s-vm-1   <none>           <none>

dev-aai-aai-resources-57f96dfbd6-59m8w                  2/2     Running            2          45h   10.42.2.93    onap-k8s-vm-2   <none>           <none>

dev-aai-aai-schema-service-595f644b5-n6bv5              2/2     Running            2          45h   10.42.2.82    onap-k8s-vm-2   <none>           <none>

dev-aai-aai-search-data-9c5bcc994-rh8kg                 2/2     Running            2          45h   10.42.2.85    onap-k8s-vm-2   <none>           <none>

dev-aai-aai-sparky-be-5fc6985fb6-zqvnb                  2/2     Running            2          45h   10.42.2.92    onap-k8s-vm-2   <none>           <none>

dev-aai-aai-traversal-76788cbfdc-mgsj6                  2/2     Running            2          45h   10.42.2.86    onap-k8s-vm-2   <none>           <none>

dev-aai-aai-traversal-update-query-data-xrhh7           0/1     Completed          0          45h   10.42.1.16    onap-k8s-vm-1   <none>           <none>

ubuntu@onap-rancher-vm:~$

ubuntu@onap-rancher-vm:~$ kubectl get services -n onap -o wide | grep aai

aai                        NodePort       10.43.166.80    <none>            8443:30233/TCP                                                45h   app=aai

aai-babel                  NodePort       10.43.212.34    <none>            9516:30279/TCP                                                45h   app=aai-babel,release=dev-aai

aai-elasticsearch          ClusterIP      None            <none>            9200/TCP,8443/TCP                                             45h   app=aai-elasticsearch,release=dev-aai

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

aai-graphgraph             ClusterIP      10.43.9.26      <none>            8453/TCP                                                      45h   app=aai-graphgraph,release=dev-aai

aai-modelloader            NodePort       10.43.46.140    <none>            8080:30210/TCP,8443:30229/TCP                                 45h   app=aai-modelloader,release=dev-aai

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

aai-schema-service         ClusterIP      None            <none>            8452/TCP,5005/TCP                                             45h   app=aai-schema-service,release=dev-aai

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

aai-sparky-be              NodePort       10.43.183.209   <none>            8000:30220/TCP                                                45h   app=aai-sparky-be,release=dev-aai

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

2.      Please find the portal-app service below

ubuntu@onap-rancher-vm:~$ kubectl get services -n onap -o wide | grep portal

portal-app                 LoadBalancer   10.43.36.76     167.254.204.109   8989:30215/TCP,8006:30213/TCP,8010:30214/TCP,8443:30225/TCP   25h   app=portal-app,release=dev-portal

3.      I have my /etc/hosts updated with the below data

 

167.254.204.109 portal.api.simpledemo.onap.org

167.254.204.109 vid.api.simpledemo.onap.org

167.254.204.109 sdc.api.fe.simpledemo.onap.org

167.254.204.109 portal-sdk.simpledemo.onap.org

167.254.204.109 policy.api.simpledemo.onap.org

167.254.204.109 aai.ui.simpledemo.onap.org

167.254.204.109 cli.api.simpledemo.onap.org

167.254.204.109 msb.api.discovery.simpledemo.onap.org

167.254.204.109 portal-app.onap

167.254.204.109 so-monitoring

4.      I logged in to the portal using the username jh0003 (admin). I’m able to login to SDC without any issue. I don’t see the AAI in ONAP Portal.

5.      Followed the link and added the role to user_id (jh0003)

 

Insert into fn_role (ROLE_ID,ROLE_NAME,ACTIVE_YN,PRIORITY,APP_ID,APP_ROLE_ID) values (2144,'ui_view','Y', NULL, 7,2144);
Insert into fn_user_role (USER_ID,ROLE_ID,PRIORITY,APP_ID) values (2,2144,null,7);

 

Please find the available users for reference

 

MariaDB [portal]> SELECT USER_ID, login_id, first_name, org_user_id, email FROM fn_user;

+---------+----------+------------+-------------+-------------------+

| USER_ID | login_id | first_name | org_user_id | email             |

+---------+----------+------------+-------------+-------------------+

|       2 | jh0003   | Jimmy      | jh0003      | admin@...    |

|       3 | cs0008   | Carlos     | cs0008      | designer@... |

|       4 | jm0007   | Joni       | jm0007      | tester@...   |

|       5 | op0001   | Steve      | op0001      | ops@...      |

|       6 | gv0001   | David      | gv0001      | governor@... |

|       7 | pm0001   | Teddy      | pm0001      | pm1@...      |

|       8 | ps0001   | Eden       | ps0001      | ps1@...      |

|       9 | vid1     | vid1       | vid1        | vid1@...     |

|      10 | vid2     | vid2       | vid2        | vid2@...     |

|      11 | vid3     | vid3       | vid3        | vid3@...     |

|      12 | steve    | steve      | steve       | steve@...    |

+---------+----------+------------+-------------+-------------------+

 

6.      After the above step, I see AAI in the ONAP Portal

 

 

7.      When I click on AAI, it says portal.api.simpledemo.onap.org refused to connect.

 

 

8.      When I try to open AAI in a separate tab using http://aai.ui.simpledemo.onap.org:30220/services/aai/webapp/index.html, it returns ERR_INVALID_HTTP_RESPONSE. Using https instead of http http://aai.ui.simpledemo.onap.org:30220/services/aai/webapp/index.html, redirects to ONAP Portal page.

 

Any input is highly appreciated.

Please let me know if more information is needed.

 

Thanks,

Thiriloshini

Re: [OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

Thiriloshini.ThoppeKrishnakumar@us.fujitsu.com
 

Thanks Marco

 

From: PLATANIA, MARCO (MARCO) <platania@...>
Sent: Thursday, October 17, 2019 7:51 AM
To: Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>; onap-discuss@...
Cc: Miao, Xin <Xin.Miao@...>
Subject: Re: [onap-discuss][OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

 

See below the docker, K8S, and helm versions used by integration team, in addition to RKE v0.2.8. Helm 2.14.2 is good.

 

  76   docker_version:

  77     type: string

  78     default: "18.09.5"

  79

  80   kubectl_version:

  81     type: string

  82     default: "1.15.3"

  83

  84   helm_version:

  85     type: string

  86     default: "2.14.2"

 

Marco

 

From: "Thiriloshini.ThoppeKrishnakumar@..." <Thiriloshini.ThoppeKrishnakumar@...>
Date: Wednesday, October 16, 2019 at 5:40 PM
To: "PLATANIA, MARCO (MARCO)" <platania@...>, "onap-discuss@..." <onap-discuss@...>
Cc: "Xin.Miao@..." <Xin.Miao@...>
Subject: RE: [onap-discuss][OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

 

Macro,

 

Thanks for the response.

I see RKE version 0.2.8 and kubernetes version v1.15.3-rancher1-1.

 

Is the helm version 2.14.2 good enough ?

 

Thanks,

Thiriloshini

 

From: PLATANIA, MARCO (MARCO) <platania@...>
Sent: Wednesday, October 16, 2019 3:46 PM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Miao, Xin <Xin.Miao@...>
Subject: Re: [onap-discuss][OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

 

Integration team uses RKE v0.2.8. See deploy.sh here: https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=deployment/heat/onap-rke/scripts/deploy.sh;h=5bb2f0a7c7e4def4fb4b677a5364a6c7947db4d6;hb=refs/heads/elalto

 

Marco

 

 

From: <onap-discuss@...> on behalf of "Thiriloshini.ThoppeKrishnakumar@..." <thiriloshini.thoppekrishnakumar@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "thiriloshini.thoppekrishnakumar@..." <thiriloshini.thoppekrishnakumar@...>
Date: Wednesday, October 16, 2019 at 3:59 PM
To: "onap-discuss@..." <onap-discuss@...>
Cc: "Xin.Miao@..." <Xin.Miao@...>
Subject: [onap-discuss][OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

 

Hi,

 

I am trying to bring up an ONAP cluster (El-Alto) using OOM.

 

The software requirements for El Alto has been given in the OOM_cloud_setup-Guide as

 

Release

Kubernetes

Helm

kubectl

Docker

el alto

1.15.2

2.14.2

1.15.2

18.09.x

 

Can somebody please let me know the corresponding RKE version that needs to be used for El Alto.

 

In the RKE git repo, the only release version that had kubernetes v1.15.2 is rke v0.2.7. But the kubernetes v1.15.2 is experimental in that release. No other release has kubernetes v1.15.2 as default.

 

Can somebody please help me point to the right RKE version for El Alto.

 

Thanks,

Thiriloshini

Re: Missing image in multicloud

Kiran Kamineni
 

Released images are supposed to be pulled from dockerhub and not from nexus3.

The other repositories should also be making the relevant changes.

 

-- K i r a n

 

From: t.levora@... <t.levora@...>
Sent: Thursday, October 17, 2019 11:52 PM
To: onap-discuss@...; Kamineni, Kiran K <kiran.k.kamineni@...>; o.smalec@...; 'Yang, Bin' <bin.yang@...>
Cc: 'Michal Ptacek' <m.ptacek@...>
Subject: RE: [onap-discuss] Missing image in multicloud

 

Hi Kiran,

 

Is the image somehow different from the nexus3.onap.org:10001/onap/multicloud-framework-artifactbroker:1.4.2 ?

 

If not, I don’t understand why use different registry for multicloud-k8s than for multicloud-windriver and multicloud-starlingx

 

This is how it looks like after your suggested changset (97170):

 

multicloud-k8s

image: "registry.hub.docker.com/onap/multicloud-framework-artifactbroker:1.4.2"

 

multicloud-windriver

image: "nexus3.onap.org:10001/onap/multicloud-framework-artifactbroker:1.4.2"

 

multicloud-starlingx

"nexus3.onap.org:10001/onap/multicloud-framework-artifactbroker:1.4.2"

 

We should really unify it and reduce the number of different source of the same images.

 

Thank you

 

Regards

 

Tomas

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Kiran Kamineni
Sent: Thursday, October 17, 2019 8:52 PM
To: o.smalec@...; 'Yang, Bin' <bin.yang@...>; onap-discuss@...; t.levora@...
Cc: 'Michal Ptacek' <m.ptacek@...>
Subject: Re: [onap-discuss] Missing image in multicloud

 

The image had not been uploaded to dockerhub. It has been now. I will update the charts with the correct version.


From: onap-discuss@... <onap-discuss@...> on behalf of t.levora via Lists.Onap.Org <t.levora=partner.samsung.com@...>
Sent: Thursday, October 17, 2019 1:46 AM
To: o.smalec@... <o.smalec@...>; 'Yang, Bin' <Bin.Yang@...>; onap-discuss@... <onap-discuss@...>
Cc: 'Michal Ptacek' <m.ptacek@...>
Subject: Re: [onap-discuss] Missing image in multicloud

 

Hi,

 

Another thing is that there’s the same image used in three charts, so why use two times nexus3.onap.org and once registry.hub.docker.com. Should be unified.

 

Regards

 

Tomas

 

From: o.smalec@... <o.smalec@...>
Sent: Thursday, October 17, 2019 10:44 AM
To: 'Yang, Bin' <Bin.Yang@...>; onap-discuss@...; t.levora@...
Cc: 'Michal Ptacek' <m.ptacek@...>
Subject: RE: [onap-discuss] Missing image in multicloud

 

Hello,

 

Yes this is working as I stated in the ticket MULTICLOUD-844.

 

The thing is that we need to review suggested patches and get it working in upstream.

 

Best Regards,

Ondrej Smalec

 

From: Yang, Bin <Bin.Yang@...>
Sent: Thursday, October 17, 2019 10:29 AM
To: onap-discuss@...; t.levora@...
Cc: 'Michal Ptacek' <m.ptacek@...>; o.smalec@...
Subject: RE: [onap-discuss] Missing image in multicloud

 

Hi,

 

Try this :

 

registry.hub.docker.com/onap/multicloud-framework-artifactbroker:1.4.2

 

The naming seems changed after pushing to docker hub:

     onap/multicloud/framework-artifactbroker => onap/multicloud-framework-artifactbroker

 

 

Best Regards,

Bin Yang,    Solution Engineering Team,    Wind River

ONAP Multi-VIM/Cloud PTL

Direct +86,10,84777126    Mobile +86,13811391682    Fax +86,10,64398189

Skype: yangbincs993

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of t.levora via Lists.Onap.Org
Sent: Thursday, October 17, 2019 4:15 PM
To: onap-discuss@...
Cc: 'Michal Ptacek'; o.smalec@...
Subject: [onap-discuss] Missing image in multicloud

 

Hi,

 

The current master and elalto branches requires image registry.hub.docker.com/onap/multicloud/framework-artifactbroker:1.4.2 which is not downloadable.

 

It’s broken by change 8e8dd7d4efcb6050643caf7eb138a6b1cfb3d674. There is created JIRA ticket MULTICLOUD-844 since 10/01 and the following suggested patches:

 

https://gerrit.onap.org/r/c/oom/+/96789 in master

 

https://gerrit.onap.org/r/c/oom/+/97170 in elalto

 

Best regards

 

Tomas

 

 

 

 

 

  

 

 

  

Re: Missing image in multicloud

t.levora@...
 

Hi Kiran,

 

Is the image somehow different from the nexus3.onap.org:10001/onap/multicloud-framework-artifactbroker:1.4.2 ?

 

If not, I don’t understand why use different registry for multicloud-k8s than for multicloud-windriver and multicloud-starlingx

 

This is how it looks like after your suggested changset (97170):

 

multicloud-k8s

image: "registry.hub.docker.com/onap/multicloud-framework-artifactbroker:1.4.2"

 

multicloud-windriver

image: "nexus3.onap.org:10001/onap/multicloud-framework-artifactbroker:1.4.2"

 

multicloud-starlingx

"nexus3.onap.org:10001/onap/multicloud-framework-artifactbroker:1.4.2"

 

We should really unify it and reduce the number of different source of the same images.

 

Thank you

 

Regards

 

Tomas

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Kiran Kamineni
Sent: Thursday, October 17, 2019 8:52 PM
To: o.smalec@...; 'Yang, Bin' <bin.yang@...>; onap-discuss@...; t.levora@...
Cc: 'Michal Ptacek' <m.ptacek@...>
Subject: Re: [onap-discuss] Missing image in multicloud

 

The image had not been uploaded to dockerhub. It has been now. I will update the charts with the correct version.


From: onap-discuss@... <onap-discuss@...> on behalf of t.levora via Lists.Onap.Org <t.levora=partner.samsung.com@...>
Sent: Thursday, October 17, 2019 1:46 AM
To: o.smalec@... <o.smalec@...>; 'Yang, Bin' <Bin.Yang@...>; onap-discuss@... <onap-discuss@...>
Cc: 'Michal Ptacek' <m.ptacek@...>
Subject: Re: [onap-discuss] Missing image in multicloud

 

Hi,

 

Another thing is that there’s the same image used in three charts, so why use two times nexus3.onap.org and once registry.hub.docker.com. Should be unified.

 

Regards

 

Tomas

 

From: o.smalec@... <o.smalec@...>
Sent: Thursday, October 17, 2019 10:44 AM
To: 'Yang, Bin' <Bin.Yang@...>; onap-discuss@...; t.levora@...
Cc: 'Michal Ptacek' <m.ptacek@...>
Subject: RE: [onap-discuss] Missing image in multicloud

 

Hello,

 

Yes this is working as I stated in the ticket MULTICLOUD-844.

 

The thing is that we need to review suggested patches and get it working in upstream.

 

Best Regards,

Ondrej Smalec

 

From: Yang, Bin <Bin.Yang@...>
Sent: Thursday, October 17, 2019 10:29 AM
To: onap-discuss@...; t.levora@...
Cc: 'Michal Ptacek' <m.ptacek@...>; o.smalec@...
Subject: RE: [onap-discuss] Missing image in multicloud

 

Hi,

 

Try this :

 

registry.hub.docker.com/onap/multicloud-framework-artifactbroker:1.4.2

 

The naming seems changed after pushing to docker hub:

     onap/multicloud/framework-artifactbroker => onap/multicloud-framework-artifactbroker

 

 

Best Regards,

Bin Yang,    Solution Engineering Team,    Wind River

ONAP Multi-VIM/Cloud PTL

Direct +86,10,84777126    Mobile +86,13811391682    Fax +86,10,64398189

Skype: yangbincs993

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of t.levora via Lists.Onap.Org
Sent: Thursday, October 17, 2019 4:15 PM
To: onap-discuss@...
Cc: 'Michal Ptacek'; o.smalec@...
Subject: [onap-discuss] Missing image in multicloud

 

Hi,

 

The current master and elalto branches requires image registry.hub.docker.com/onap/multicloud/framework-artifactbroker:1.4.2 which is not downloadable.

 

It’s broken by change 8e8dd7d4efcb6050643caf7eb138a6b1cfb3d674. There is created JIRA ticket MULTICLOUD-844 since 10/01 and the following suggested patches:

 

https://gerrit.onap.org/r/c/oom/+/96789 in master

 

https://gerrit.onap.org/r/c/oom/+/97170 in elalto

 

Best regards

 

Tomas

 

 

 

 

 

  

 

  

Catch the OVP Webinar on Tuesday, Oct 22, 10:00 AM PT

Brandon Wick
 

LFN Community:

For those not yet familiar, the OPNFV Verification Program (OVP) is an open source, community-led compliance and verification program to demonstrate the readiness and availability of commercial NFV products and services, including NFVI and VNFs, using OPNFV and ONAP components.

LFN has contracted with SDxCentral in order to raise awareness of the program via a webinar this coming Tuesday at 10:00 AM PT How the OPNFV Verification Program (OVP) Can Boost VNF Interoperability. Community leaders Lincoln Lavoie, Rabi Abdel, and Amar Kapadia will provide an overview of the program, explain the benefits, and invite participation from the industry. 

If you'd like to learn more about the program, please register and join us on Tuesday. If you can't attend live, please register to be informed when the on-demand replay is available. Also, if you work with any industry partners that you feel might be interested in the webinar, please forward them the link: https://www.sdxcentral.com/resources/sponsored/webinars/linux-foundation-opnfv-verification-program-boosts-vnf-interoperability/

Thank you!

Best,

Brandon Wick
Senior Integrated Marketing Manager
The Linux Foundation
+1.917.282.0960


Re: Missing image in multicloud

Kiran Kamineni
 

The image had not been uploaded to dockerhub. It has been now. I will update the charts with the correct version.


From: onap-discuss@... <onap-discuss@...> on behalf of t.levora via Lists.Onap.Org <t.levora=partner.samsung.com@...>
Sent: Thursday, October 17, 2019 1:46 AM
To: o.smalec@... <o.smalec@...>; 'Yang, Bin' <Bin.Yang@...>; onap-discuss@... <onap-discuss@...>
Cc: 'Michal Ptacek' <m.ptacek@...>
Subject: Re: [onap-discuss] Missing image in multicloud
 

Hi,

 

Another thing is that there’s the same image used in three charts, so why use two times nexus3.onap.org and once registry.hub.docker.com. Should be unified.

 

Regards

 

Tomas

 

From: o.smalec@... <o.smalec@...>
Sent: Thursday, October 17, 2019 10:44 AM
To: 'Yang, Bin' <Bin.Yang@...>; onap-discuss@...; t.levora@...
Cc: 'Michal Ptacek' <m.ptacek@...>
Subject: RE: [onap-discuss] Missing image in multicloud

 

Hello,

 

Yes this is working as I stated in the ticket MULTICLOUD-844.

 

The thing is that we need to review suggested patches and get it working in upstream.

 

Best Regards,

Ondrej Smalec

 

From: Yang, Bin <Bin.Yang@...>
Sent: Thursday, October 17, 2019 10:29 AM
To: onap-discuss@...; t.levora@...
Cc: 'Michal Ptacek' <m.ptacek@...>; o.smalec@...
Subject: RE: [onap-discuss] Missing image in multicloud

 

Hi,

 

Try this :

 

registry.hub.docker.com/onap/multicloud-framework-artifactbroker:1.4.2

 

The naming seems changed after pushing to docker hub:

     onap/multicloud/framework-artifactbroker => onap/multicloud-framework-artifactbroker

 

 

Best Regards,

Bin Yang,    Solution Engineering Team,    Wind River

ONAP Multi-VIM/Cloud PTL

Direct +86,10,84777126    Mobile +86,13811391682    Fax +86,10,64398189

Skype: yangbincs993

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of t.levora via Lists.Onap.Org
Sent: Thursday, October 17, 2019 4:15 PM
To: onap-discuss@...
Cc: 'Michal Ptacek'; o.smalec@...
Subject: [onap-discuss] Missing image in multicloud

 

Hi,

 

The current master and elalto branches requires image registry.hub.docker.com/onap/multicloud/framework-artifactbroker:1.4.2 which is not downloadable.

 

It’s broken by change 8e8dd7d4efcb6050643caf7eb138a6b1cfb3d674. There is created JIRA ticket MULTICLOUD-844 since 10/01 and the following suggested patches:

 

https://gerrit.onap.org/r/c/oom/+/96789 in master

 

https://gerrit.onap.org/r/c/oom/+/97170 in elalto

 

Best regards

 

Tomas

 

 

 

 

  

Re: MACRO workflow

Marco Platania
 

WorkflowActionBB is the entry point for many operations that use Generic Resource APIs (GRA). That block loops over the list of building blocks (BBs) that compose a specific workflow/operation. For each operation, the list of BBs is in the orchestration_flow_reference table. The sequence number field in that table defines the order in which BBs are executed within a given flow. When you use macro workflow for service/VNF/VF-module instantiation, some blocks could be executed multiple times, as you pointed out, based on the number of VNFs and VF-modules that the service model contains. To execute the same building block multiple times back to back for different instances of the same resource type, see WorkflowAction class for operations that use the macro APIs. Some methods in this class traverse different data structures (e.g. Catalog DB or AAI) to count how many resources a macro workflow should handle. Based on this count, the buildExecuteBuildingBlockList() method iterates through the ordered list of building blocks to execute for a given flow and adds a block of the same type for each instance of a given resource type (e.g. VF module). The base module (module-0 in the service model) is executed first, then all the other modules are executed based on the order in which they appear in the module. For scale out use case, the vPKG is module-1, the vLB is module-2, the vDNS is module-3. As such, SO instantiates the vPKG, vLB, and vDNS in this order. I can't remember on top of my head if you can specify the order of modules in SDC during service creation. The VNF descriptor (for example Heat template) has to contain one base module that SDC interprets as module-0, and it may contain several non-base modules that SDC interprets has module-1, module-2, etc. but I'm not sure whether you can specify an order. You should build modules in such a way that the base one contains shared resources that must be instantiated first, while the other modules should be independent and instantiated in any order.

#ccsdk weekly call cancelled 10/18 #ccsdk

TIMONEY, DAN
 

CCSDK team,

 

I need to cancel this week’s CCSDK project team call.  We’ll meet next week.

 

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: Reminder: [onap-discuss] [release] [docs] Checklist for El Alto documentation

seshu kumar m
 

Hi Sofia

Release notes changes of SO are not reflected in the SO:
https://docs.onap.org/en/elalto/submodules/so.git/docs/release-notes.html


Changes on gerrit for the SO elalto release:

Have requested the LF to help on the issue through the issue IT-17923

Requesting your suport in resolving the same.


Thanks and Regards,
M Seshu Kumar
Senior System Architect
uTraffic, Software BU,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___________________________________________________________________________________________________
This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------


From: onap-release@... [onap-release@...] on behalf of Sofia Wallin [sofia.wallin@...]
Sent: Thursday, October 17, 2019 7:10 PM
To: onap-release@...; onap-discuss@...
Subject: [Onap-release] Reminder: [onap-discuss] [release] [docs] Checklist for El Alto documentation

Friendly reminder.

 

Best regards,

Sofia

 

From: Sofia Wallin <sofia.wallin@...>
Date: Thursday, 10 October 2019 at 16:38
To: "onap-discuss@..." <onap-discuss@...>, "onap-release@..." <onap-release@...>
Cc: "jbaker@..." <jbaker@...>, "catherine.lefevre@..." <catherine.lefevre@...>
Subject: [onap-discuss] [release] [docs] Checklist for El Alto documentation

 

Hello ONAP community,

Sign-off for El Alto is scheduled to October 24th.

 

Prior to this please make sure that you,

•             Updated relevant content. If no major additions or changes don’t forget to change from Dublin to El Alto where needed.

•             Update your release notes with the final information for El Alto (release data as below)

•             Ensure that your updated documentation appears on https://docs.onap.org/en/elalto/index.html

 

Please reach out to anyone in the documentation project if you have questions or need support!

 

BR,

Sofia 

 

Release Data

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

 

+--------------------------------------+--------------------------------------+

| **Project**                          | <addme>                              |

|                                      |                                      |

+--------------------------------------+--------------------------------------+

| **Release name**                     | El Alto Release                      |

|                                      |                                      |

+--------------------------------------+--------------------------------------+

| **Release version**                  | El Alto 5.0.1                        |

|                                      |                                      |

+--------------------------------------+--------------------------------------+

| **Release date**                     | October 24 2019                      |

|                                      |                                      |

+--------------------------------------+--------------------------------------+

Re: [OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

Marco Platania
 

See below the docker, K8S, and helm versions used by integration team, in addition to RKE v0.2.8. Helm 2.14.2 is good.

 

  76   docker_version:

  77     type: string

  78     default: "18.09.5"

  79

  80   kubectl_version:

  81     type: string

  82     default: "1.15.3"

  83

  84   helm_version:

  85     type: string

  86     default: "2.14.2"

 

Marco

 

From: "Thiriloshini.ThoppeKrishnakumar@..." <Thiriloshini.ThoppeKrishnakumar@...>
Date: Wednesday, October 16, 2019 at 5:40 PM
To: "PLATANIA, MARCO (MARCO)" <platania@...>, "onap-discuss@..." <onap-discuss@...>
Cc: "Xin.Miao@..." <Xin.Miao@...>
Subject: RE: [onap-discuss][OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

 

Macro,

 

Thanks for the response.

I see RKE version 0.2.8 and kubernetes version v1.15.3-rancher1-1.

 

Is the helm version 2.14.2 good enough ?

 

Thanks,

Thiriloshini

 

From: PLATANIA, MARCO (MARCO) <platania@...>
Sent: Wednesday, October 16, 2019 3:46 PM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Miao, Xin <Xin.Miao@...>
Subject: Re: [onap-discuss][OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

 

Integration team uses RKE v0.2.8. See deploy.sh here: https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=deployment/heat/onap-rke/scripts/deploy.sh;h=5bb2f0a7c7e4def4fb4b677a5364a6c7947db4d6;hb=refs/heads/elalto

 

Marco

 

 

From: <onap-discuss@...> on behalf of "Thiriloshini.ThoppeKrishnakumar@..." <thiriloshini.thoppekrishnakumar@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "thiriloshini.thoppekrishnakumar@..." <thiriloshini.thoppekrishnakumar@...>
Date: Wednesday, October 16, 2019 at 3:59 PM
To: "onap-discuss@..." <onap-discuss@...>
Cc: "Xin.Miao@..." <Xin.Miao@...>
Subject: [onap-discuss][OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

 

Hi,

 

I am trying to bring up an ONAP cluster (El-Alto) using OOM.

 

The software requirements for El Alto has been given in the OOM_cloud_setup-Guide as

 

Release

Kubernetes

Helm

kubectl

Docker

el alto

1.15.2

2.14.2

1.15.2

18.09.x

 

Can somebody please let me know the corresponding RKE version that needs to be used for El Alto.

 

In the RKE git repo, the only release version that had kubernetes v1.15.2 is rke v0.2.7. But the kubernetes v1.15.2 is experimental in that release. No other release has kubernetes v1.15.2 as default.

 

Can somebody please help me point to the right RKE version for El Alto.

 

Thanks,

Thiriloshini

#sdnc Dublin "Unable to create initial connections of pool." error on every install #sdnc

Marek Szwałkiewicz (DT)
 

Hi,

I tried to install and reinstall SDNC in many different ways but every time Karaf on dev-sdnc-sdnc-0 is throwing the same exception every couple seconds:

2019-10-17T12:32:30,914 | ERROR | DBResourcemanagerWatchThread | ConnectionPool                   | 152 - org.apache.tomcat.jdbc - 8.5.14 |  -  | Unable to create initial connections of pool.
java.sql.SQLException: Unable to load class: org.mariadb.jdbc.Driver from ClassLoader:org.eclipse.osgi.internal.loader.EquinoxClassLoader@2c6ab45b[org.apache.tomcat.jdbc:8.5.14(id=152)];ClassLoader:org.eclipse.osgi.internal.framework.Con
textFinder@5e56f644
        at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:283) [152:org.apache.tomcat.jdbc:8.5.14]
        at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:203) [152:org.apache.tomcat.jdbc:8.5.14]
        at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:735) [152:org.apache.tomcat.jdbc:8.5.14]
        at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:667) [152:org.apache.tomcat.jdbc:8.5.14]
        at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:482) [152:org.apache.tomcat.jdbc:8.5.14]
        at org.apache.tomcat.jdbc.pool.ConnectionPool.<init>(ConnectionPool.java:154) [152:org.apache.tomcat.jdbc:8.5.14]
        at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:118) [152:org.apache.tomcat.jdbc:8.5.14]
        at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:107) [152:org.apache.tomcat.jdbc:8.5.14]
        at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:131) [152:org.apache.tomcat.jdbc:8.5.14]
        at org.onap.ccsdk.sli.core.dblib.CachedDataSource.getConnection(CachedDataSource.java:121) [225:org.onap.ccsdk.sli.core.dblib-provider:0.4.4]
        at org.onap.ccsdk.sli.core.dblib.CachedDataSource.testConnection(CachedDataSource.java:369) [225:org.onap.ccsdk.sli.core.dblib-provider:0.4.4]
        at org.onap.ccsdk.sli.core.dblib.CachedDataSource.testConnection(CachedDataSource.java:359) [225:org.onap.ccsdk.sli.core.dblib-provider:0.4.4]
        at org.onap.ccsdk.sli.core.dblib.DBResourceManager$RecoveryMgr.resetConnectionPool(DBResourceManager.java:442) [225:org.onap.ccsdk.sli.core.dblib-provider:0.4.4]
        at org.onap.ccsdk.sli.core.dblib.DBResourceManager$RecoveryMgr.run(DBResourceManager.java:415) [225:org.onap.ccsdk.sli.core.dblib-provider:0.4.4]
Caused by: java.lang.ClassNotFoundException: Unable to load class: org.mariadb.jdbc.Driver from ClassLoader:org.eclipse.osgi.internal.loader.EquinoxClassLoader@2c6ab45b[org.apache.tomcat.jdbc:8.5.14(id=152)];ClassLoader:org.eclipse.osgi.
internal.framework.ContextFinder@5e56f644
        at org.apache.tomcat.jdbc.pool.ClassLoaderUtil.loadClass(ClassLoaderUtil.java:56) ~[?:?]
        at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:271) ~[?:?]
        ... 13 more
Caused by: java.lang.ClassNotFoundException: org.mariadb.jdbc.Driver
        at java.net.URLClassLoader.findClass(URLClassLoader.java:382) ~[?:?]
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:?]
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) ~[?:?]
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:?]
        at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132) ~[?:?]
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:?]
        at java.lang.Class.forName0(Native Method) ~[?:?]
        at java.lang.Class.forName(Class.java:348) ~[?:?]
        at org.apache.tomcat.jdbc.pool.ClassLoaderUtil.loadClass(ClassLoaderUtil.java:38) ~[?:?]
        at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:271) ~[?:?]
        ... 13 more
2019-10-17T12:32:30,917 | INFO  | DBResourcemanagerWatchThread | CachedDataSource                 | 225 - org.onap.ccsdk.sli.core.dblib-provider - 0.4.4 |  -  | SQL DataSource < sdnctldb01 > test failed. Cause : Unable to load class: org
.mariadb.jdbc.Driver from ClassLoader:org.eclipse.osgi.internal.loader.EquinoxClassLoader@2c6ab45b[org.apache.tomcat.jdbc:8.5.14(id=152)];ClassLoader:org.eclipse.osgi.internal.framework.ContextFinder@5e56f644> test failed. Cause : {}

and if I try to use SDNC it responds with "SQL query failed". Robot health check for SDNC fails with:
Resolving variable '${resp.json()['output']['response-code']}' failed: JSONDecodeError: Expecting value: line 1 column 1 (char 0)
 
I can easily connect from dev-sdnc-sdnc-0 to mariadb-galera databases, sdnctl database is populated and tables exist.

Did any of you encountered this before? I would be grateful for any tips and hints how to solve this issue.

Thanks,
Marek Szwałkiewicz

Re: [OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

Michal Ptacek
 

Thanks Thiriloshini for raising that question,

 

we are now fighting in offline installer for deciding what RKE version would be good to us for El-Alto refference deployments

to match with requirements specified by OOM team in

https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_cloud_setup_guide.html

 

Release

Kubernetes

Helm

kubectl

Docker

el alto

1.15.2

2.14.2

1.15.2

18.09.x

 

We thought it’s good to use RKE version which stable kubernetes support higher than 1.15.2,

so we end-up in RKE 0.3.0 but having some challenges now to get it running ….

 

(With RKE 0.2.8 there is just experimenal support of 1.15.3 k8s so we don’t think it’s a good candidate)

https://github.com/rancher/rke/releases?after=v0.3.0-rc11

 

Anyway I think we should modify recommended versions with ones used by integration team

so we will have some level of confidence that most of ONAP E2E testing was done on those versions

 

Please comment,

Thanks,

Michal

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Thiriloshini.ThoppeKrishnakumar@...
Sent: Wednesday, October 16, 2019 11:40 PM
To: PLATANIA, MARCO (MARCO) <platania@...>; onap-discuss@...
Cc: Xin.Miao@...
Subject: Re: [onap-discuss][OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

 

Macro,

 

Thanks for the response.

I see RKE version 0.2.8 and kubernetes version v1.15.3-rancher1-1.

 

Is the helm version 2.14.2 good enough ?

 

Thanks,

Thiriloshini

 

From: PLATANIA, MARCO (MARCO) <platania@...>
Sent: Wednesday, October 16, 2019 3:46 PM
To: onap-discuss@...; Thoppekrishnakumar, Thiriloshini <Thiriloshini.ThoppeKrishnakumar@...>
Cc: Miao, Xin <Xin.Miao@...>
Subject: Re: [onap-discuss][OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

 

Integration team uses RKE v0.2.8. See deploy.sh here: https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=deployment/heat/onap-rke/scripts/deploy.sh;h=5bb2f0a7c7e4def4fb4b677a5364a6c7947db4d6;hb=refs/heads/elalto

 

Marco

 

 

From: <onap-discuss@...> on behalf of "Thiriloshini.ThoppeKrishnakumar@..." <thiriloshini.thoppekrishnakumar@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "thiriloshini.thoppekrishnakumar@..." <thiriloshini.thoppekrishnakumar@...>
Date: Wednesday, October 16, 2019 at 3:59 PM
To: "onap-discuss@..." <onap-discuss@...>
Cc: "Xin.Miao@..." <Xin.Miao@...>
Subject: [onap-discuss][OOM] [Onap-Integration] ONAP Deployment (El Alto) - RKE Version

 

Hi,

 

I am trying to bring up an ONAP cluster (El-Alto) using OOM.

 

The software requirements for El Alto has been given in the OOM_cloud_setup-Guide as

 

Release

Kubernetes

Helm

kubectl

Docker

el alto

1.15.2

2.14.2

1.15.2

18.09.x

 

Can somebody please let me know the corresponding RKE version that needs to be used for El Alto.

 

In the RKE git repo, the only release version that had kubernetes v1.15.2 is rke v0.2.7. But the kubernetes v1.15.2 is experimental in that release. No other release has kubernetes v1.15.2 as default.

 

Can somebody please help me point to the right RKE version for El Alto.

 

Thanks,

Thiriloshini

 

  

Reminder: [onap-discuss] [release] [docs] Checklist for El Alto documentation

Sofia Wallin
 

Friendly reminder.

 

Best regards,

Sofia

 

From: Sofia Wallin <sofia.wallin@...>
Date: Thursday, 10 October 2019 at 16:38
To: "onap-discuss@..." <onap-discuss@...>, "onap-release@..." <onap-release@...>
Cc: "jbaker@..." <jbaker@...>, "catherine.lefevre@..." <catherine.lefevre@...>
Subject: [onap-discuss] [release] [docs] Checklist for El Alto documentation

 

Hello ONAP community,

Sign-off for El Alto is scheduled to October 24th.

 

Prior to this please make sure that you,

•             Updated relevant content. If no major additions or changes don’t forget to change from Dublin to El Alto where needed.

•             Update your release notes with the final information for El Alto (release data as below)

•             Ensure that your updated documentation appears on https://docs.onap.org/en/elalto/index.html

 

Please reach out to anyone in the documentation project if you have questions or need support!

 

BR,

Sofia 

 

Release Data

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

 

+--------------------------------------+--------------------------------------+

| **Project**                          | <addme>                              |

|                                      |                                      |

+--------------------------------------+--------------------------------------+

| **Release name**                     | El Alto Release                      |

|                                      |                                      |

+--------------------------------------+--------------------------------------+

| **Release version**                  | El Alto 5.0.1                        |

|                                      |                                      |

+--------------------------------------+--------------------------------------+

| **Release date**                     | October 24 2019                      |

|                                      |                                      |

+--------------------------------------+--------------------------------------+

Re: [onap-tsc] Resign As Committer

Catherine LEFEVRE
 

 

Congratulations Marcus on the arrival of your new baby boy!

Thank you for all your outstanding contribution to the ONAP Community.

 

Best regards

Catherine