Date   

#ccsdk #sdnc CCSDK and SDNC Java 11 port complete, except for CDS #ccsdk #sdnc

Dan Timoney
 

All SDNC containers that use Java have now been ported to Java 11. 

 

Most CCSDK containers that use Java 11, with the exception of CDS, have also been ported to Java 11.  That work is in progress – some issues are being worked through.

 


#dcae team meeting (UTC) - Wed, 09/09/2020 2:30pm-3:30pm #dcaegen2 #cal-reminder

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

Reminder: #dcae team meeting (UTC)

When: Wednesday, 9 September 2020, 2:30pm to 3:30pm, (GMT+00:00) UTC

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

View Event

Organizer: Vijay Venkatesh Kumar vv770d@...

Description: ONAP Meeting 11 is inviting you to a scheduled Zoom meeting.

Join Zoom Meeting
https://zoom.us/j/98967242523

 
Meeting ID: 989 6724 2523
One tap mobile
+13126266799,,98967242523# US (Chicago)
+16465588656,,98967242523# US (New York)

Dial by your location
        +1 312 626 6799 US (Chicago)
        +1 646 558 8656 US (New York)
        +1 669 900 6833 US (San Jose)
        877 369 0926 US Toll-free
        855 880 1246 US Toll-free
Meeting ID: 989 6724 2523
Find your local number: https://zoom.us/u/ad1U59khic


#policy biweekly - Wed, 09/09/2020 2:00pm-3:00pm #policy #cal-reminder

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

Reminder: #policy biweekly

When: Wednesday, 9 September 2020, 2:00pm to 3:00pm, (GMT+00:00) UTC

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

View Event

Organizer: Pamela Dragosh pdragosh@...

Description:

ONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
 
Topic: #policy Bi-weekly (UTC)
Time: Jun 17, 2020 02:00 PM Universal Time UTC
        Every week on Wed, until Apr 7, 2021, 43 occurrence(s)
        Jun 17, 2020 02:00 PM
        Jun 24, 2020 02:00 PM
        Jul 1, 2020 02:00 PM
        Jul 8, 2020 02:00 PM
        Jul 15, 2020 02:00 PM
        Jul 22, 2020 02:00 PM
        Jul 29, 2020 02:00 PM
        Aug 5, 2020 02:00 PM
        Aug 12, 2020 02:00 PM
        Aug 19, 2020 02:00 PM
        Aug 26, 2020 02:00 PM
        Sep 2, 2020 02:00 PM
        Sep 9, 2020 02:00 PM
        Sep 16, 2020 02:00 PM
        Sep 23, 2020 02:00 PM
        Sep 30, 2020 02:00 PM
        Oct 7, 2020 02:00 PM
        Oct 14, 2020 02:00 PM
        Oct 21, 2020 02:00 PM
        Oct 28, 2020 02:00 PM
        Nov 4, 2020 02:00 PM
        Nov 11, 2020 02:00 PM
        Nov 18, 2020 02:00 PM
        Nov 25, 2020 02:00 PM
        Dec 2, 2020 02:00 PM
        Dec 9, 2020 02:00 PM
        Dec 16, 2020 02:00 PM
        Dec 23, 2020 02:00 PM
        Dec 30, 2020 02:00 PM
        Jan 6, 2021 02:00 PM
        Jan 13, 2021 02:00 PM
        Jan 20, 2021 02:00 PM
        Jan 27, 2021 02:00 PM
        Feb 3, 2021 02:00 PM
        Feb 10, 2021 02:00 PM
        Feb 17, 2021 02:00 PM
        Feb 24, 2021 02:00 PM
        Mar 3, 2021 02:00 PM
        Mar 10, 2021 02:00 PM
        Mar 17, 2021 02:00 PM
        Mar 24, 2021 02:00 PM
        Mar 31, 2021 02:00 PM
        Apr 7, 2021 02:00 PM
Please download and import the following iCalendar (.ics) files to your calendar system.
Weekly: https://zoom.us/meeting/uZIucu-prD0vb9S9SRiKhzBv8ATNhc1dBw/ics?icsToken=98tyKu2urT4sG9aTtVzte7MqA8H9bN-xlHMXmfpurhbOCzpxdFvXAsxKMeN7Ms-B
 
Join Zoom Meeting
https://zoom.us/j/463561265
 
Meeting ID: 463 561 265
One tap mobile
+13126266799,,463561265# US (Chicago)
+16465588656,,463561265# US (New York)
 
Dial by your location
        +1 312 626 6799 US (Chicago)
        +1 646 558 8656 US (New York)
        +1 301 715 8592 US (Germantown)
        +1 346 248 7799 US (Houston)
        +1 669 900 6833 US (San Jose)
        +1 253 215 8782 US (Tacoma)
        877 369 0926 US Toll-free
        855 880 1246 US Toll-free
Meeting ID: 463 561 265
Find your local number: https://zoom.us/u/ROllI
 


#oom Weekly - Wed, 09/09/2020 2:00pm-3:00pm #cal-reminder #oom

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

Reminder: #oom Weekly

When: Wednesday, 9 September 2020, 2:00pm to 3:00pm, (GMT+00:00) UTC

Where:https://zoom.us/j/96113493781?pwd=cER3aHgvZ1MrNmtXZVV1K0hmQjhnQT09

View Event

Organizer: OOM PTL

Description:


Re: Power Outage - Intel Oregon

Gooch, Stephen
 

At this time, I have been informed that power was restored, but I am not able to reach the lab.  I’ll update the group once I hear back from lab operations.

 

Br,

- Stephen

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Gooch, Stephen
Sent: Tuesday, September 08, 2020 15:11
To: onap-discuss@...
Subject: [onap-discuss] Power Outage - Intel Oregon

 

Hello,

 

The intel Oregon lab is experiences power outages.  They have been advised not to restore power to the rack until 20:00 UTC on Sept 7th.

 

Br,

- Stephen

 

-- 

 


Error being displayed regarding image in the VNFD yaml files

CDOT ONAP
 

Hi,

I have used the name of image file for VNF in the TOSCA based yaml file as given below:
artifacts: # This needs to be check for current release of ONAP
sw_image:
#file: { get_input: my_image }
file: ../Artifacts/Deployment/Other/image
type: tosca.artifacts.nfv.SwImage

inject_files:
source_path: ../Artifacts/Deployment/OTHER/authorized_keys #SSH
authorized_keys
dest_path: /home/ubuntu/.ssh/authorized_keys

The similar code is also found in the vCPE example of ONAP.

While distributing the service created by same VNF, following error is seen at GUI:

SO-COpenSource-Env11
service-Pcscf7Service-csar.csar
/sdc/v1/catalog/services/Pcscf7Service/1.0/artifacts/service-Pcscf7Service-csar.csar

9/9/20, 6:10 AM
DEPLOY_ERROR



SO-COpenSource-Env11
id_rsa.pub
/sdc/v1/catalog/services/Pcscf7Service/1.0/resourceInstances/pcscf_70/artifacts/id_rsa.
pub

9/9/20, 6:10 AM
DEPLOY_ERROR



SO-COpenSource-Env11
authorized_keys
/sdc/v1/catalog/services/Pcscf7Service/1.0/resourceInstances/pcscf_70/artifacts/authori
zed_keys

9/9/20, 6:10 AM
DEPLOY_ERROR



SO-COpenSource-Env11
id_rsa
/sdc/v1/catalog/services/Pcscf7Service/1.0/resourceInstances/pcscf_70/artifacts/id_rsa

9/9/20, 6:10 AM
DEPLOY_ERROR



SO-COpenSource-Env11
image
/sdc/v1/catalog/services/Pcscf7Service/1.0/resourceInstances/pcscf_70/artifacts/image

9/9/20, 6:10 AM
DEPLOY_ERROR

Below error is seen in the log file of SDC controller:
2020-09-09T05:07:53.343Z|ecf04ace-776e-443f-bf91-42cbc68ec129|pool-3-thread-
2|||||ERROR|500||Unable to process resource received from SDC
org.onap.so.asdc.etsi.pkg.processor.exceptions.SOL004ResourcePackageFailureException:
Failed to onboard vnf with UUID: 1296f8b2-e957-4b87-96c0-0206b712f591 job status: error
errorCode: CATALOG_EXCEPTION
2020-09-09T05:07:53.362Z|ecf04ace-776e-443f-bf91-42cbc68ec129|pool-3-thread-
2|||||ERROR|500||ASDC_ARTIFACT_INSTALL_EXC No element listed 300 Exception caught
during installation of pcscf_5. Transaction rollback
org.onap.so.asdc.etsi.pkg.processor.exceptions.SOL004ResourcePackageProcessingException
: Unable to process resource received from SDC


Caused by:
org.onap.so.asdc.etsi.pkg.processor.exceptions.SOL004ResourcePackageFailureException:
Failed to onboard vnf with UUID: 1296f8b2-e957-4b87-96c0-0206b712f591 job status: error
errorCode: CATALOG_EXCEPTION
2020-09-09T05:07:53.365Z|ecf04ace-776e-443f-bf91-42cbc68ec129|pool-3-thread-
2|||||ERROR|500||Exception occurred

Please suggest for any resolution of same.


-------------------------------------------------------------------------------
::Disclaimer::
-------------------------------------------------------------------------------

The contents of this email and any attachment(s) are confidential and intended
for the named recipient(s) only. It shall not attach any liability on C-DOT.
Any views or opinions presented in this email are solely those of the author
and may not necessarily reflect the opinions of C-DOT. Any form of
reproduction, dissemination, copying, disclosure, modification, distribution
and / or publication of this message without the prior written consent of the
author of this e-mail is strictly prohibited. If you have received this email
in error please delete it and notify the sender immediately.

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


Mount Netconf Server (eNB) which doesn't support yang on APPC #frankfurt #appc

saboohi.dhawan@...
 

Hi,

I wish to perform Netconf Mount of a 4G RAN node (eNB) on APPC. My eNB port doesn't support yang. Can someone please provide information regarding how to proceed further with it?
It's capabilities are :

<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
   <capabilities>
      <capability>urn:ietf:params:netconf:base:1.0</capability>
      <capability>urn:com:ericsson:ebase:0.1.0</capability>
      <capability>urn:com:ericsson:ebase:1.1.0</capability>
      <capability>urn:com:ericsson:ebase:1.2.0</capability>
      <capability>urn:com:ericsson:ebase:2.0.0</capability>
      <capability>urn:ietf:params:netconf:capability:writable-running:1.0</capability>
      <capability>urn:ietf:params:netconf:capability:rollback-on-error:1.0</capability>
      <capability>urn:ietf:params:netconf:capability:notification:1.0</capability>
      <capability>urn:ericsson:com:netconf:action:1.0</capability>
      <capability>urn:ericsson:com:netconf:heartbeat:1.0</capability>
      <capability>urn:com:ericsson:netconf:operation:1.0</capability>
      <capability>urn:ietf:params:netconf:capability:interleave:1.0</capability>
      <capability>urn:com:ericsson:netconf:notifications-aggregation:1.0</capability>
   </capabilities>


Regards
-Saboohi


Re: [onap-oom] Mariab-galera wont be redeployed

Krzysztof Opasiak
 

+ Sylvain

On 09.09.2020 02:58, Xin.Miao@fujitsu.com wrote:
Thanks, Krzysztof,

I tried and got the following:

ubuntu@onap-rancher-vm:~/oom/kubernetes$ helm install --name mariadb -f ~/xin/integration-override.yaml --namespace onap --debug --timeout 900 onap
[debug] Created tunnel using local port: '35245'

[debug] SERVER: "127.0.0.1:35245"

[debug] Original chart version: ""
[debug] CHART PATH: /home/ubuntu/oom/kubernetes/onap

2020/09/08 21:40:25 Warning: Merging destination map for chart 'music-cassandra'. Overwriting table item 'image', with non table value: onap/optf-osdf:2.0.4
2020/09/08 21:40:32 Warning: Merging destination map for chart 'elasticsearch'. Overwriting table item 'image', with non table value: onap/sdnc-image:1.8.4
2020/09/08 21:40:33 Warning: Merging destination map for chart 'master'. Overwriting table item 'image', with non table value: onap/sdnc-image:1.8.4
2020/09/08 21:40:34 Warning: Merging destination map for chart 'data'. Overwriting table item 'image', with non table value: onap/sdnc-image:1.8.4
2020/09/08 21:40:34 Warning: Merging destination map for chart 'curator'. Overwriting table item 'image', with non table value: onap/sdnc-image:1.8.4

Error: release mariadb failed: secrets "aaf-cert-service-secret" already exists
To me it looks like you have a broken override file and you are trying
to deploy way more than mariadb-galera


Thanks,

Xin Miao
Solution Engineering
Fujitsu Network Communication
(W)972-479-2263 (M)469-268-5226
2811 Telecom Drive
Richardson, TX 75081, USA


-----Original Message-----
From: Krzysztof Opasiak [mailto:k.opasiak@samsung.com]
Sent: Tuesday, September 8, 2020 3:37 PM
To: Miao, Xin <Xin.Miao@fujitsu.com>; morgan.richomme@orange.com
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-oom] Mariab-galera wont be redeployed



On 08.09.2020 22:27, Xin.Miao@fujitsu.com wrote:
Thank you, Krzysztof, for your quick response!

I have not try 'helm install'. Could you show me a complete syntax example of running 'helm install' for an onap component?

With 'helm deploy' I have the following:

ubuntu@onap-rancher-vm:~/oom/kubernetes$ helm deploy
dev-mariadb-galera local/onap --timeout 900 -f
~/xin/integration-override.yaml --namespace onap --verbose fetching
local/onap ubuntu@onap-rancher-vm:~/oom/kubernetes$
$ helm install \
--name mariadb \
-f ~/xin/integration-override.yaml \
--namespace onap \
--debug \
--timeout 900 \
onap


Thanks,

Xin Miao
Solution Engineering
Fujitsu Network Communication
(W)972-479-2263 (M)469-268-5226
2811 Telecom Drive
Richardson, TX 75081, USA


-----Original Message-----
From: Krzysztof Opasiak [mailto:k.opasiak@samsung.com]
Sent: Tuesday, September 8, 2020 3:22 PM
To: Miao, Xin <Xin.Miao@fujitsu.com>; morgan.richomme@orange.com
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-oom] Mariab-galera wont be redeployed



On 08.09.2020 22:19, Xin.Miao@fujitsu.com wrote:
Hi, Morgan/ Krzysztof/Team,

I tried to redeploy mariadb-galera after I ran 'helm undeploy
dev-mariadb-galera -purge' and cleaned up everything. However, the
'helm deploy dev-mariadb-galera . .' command returned  quietly
without anything happened.
Any difference if you do helm install instead of helm deploy?


I ran into this before. What I did previously was to redeploy the
entire ONAP cluster to get it back. But I really do not want to do it
this time since that will destroy everything that I have already
deployed, configured and distributed. I can redeploy other components
successfully. This only happens to dev-mariadb-galera component. It
is in master branch.

Did I missed something specifically?

Thanks a lot for your insight and help!

/Xin Miao/

/Solution Engineering/

/Fujitsu Network Communication/

/(W)972-479-2263 (M)469-268-5226/

/2811 Telecom Drive/

/Richardson, TX 75081, USA/
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics

--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics


Re: [onap-oom] Mariab-galera wont be redeployed

Xin.Miao@fujitsu.com
 

Thanks, Krzysztof,

I tried and got the following:

ubuntu@onap-rancher-vm:~/oom/kubernetes$ helm install --name mariadb -f ~/xin/integration-override.yaml --namespace onap --debug --timeout 900 onap
[debug] Created tunnel using local port: '35245'

[debug] SERVER: "127.0.0.1:35245"

[debug] Original chart version: ""
[debug] CHART PATH: /home/ubuntu/oom/kubernetes/onap

2020/09/08 21:40:25 Warning: Merging destination map for chart 'music-cassandra'. Overwriting table item 'image', with non table value: onap/optf-osdf:2.0.4
2020/09/08 21:40:32 Warning: Merging destination map for chart 'elasticsearch'. Overwriting table item 'image', with non table value: onap/sdnc-image:1.8.4
2020/09/08 21:40:33 Warning: Merging destination map for chart 'master'. Overwriting table item 'image', with non table value: onap/sdnc-image:1.8.4
2020/09/08 21:40:34 Warning: Merging destination map for chart 'data'. Overwriting table item 'image', with non table value: onap/sdnc-image:1.8.4
2020/09/08 21:40:34 Warning: Merging destination map for chart 'curator'. Overwriting table item 'image', with non table value: onap/sdnc-image:1.8.4

Error: release mariadb failed: secrets "aaf-cert-service-secret" already exists

Thanks,

Xin Miao
Solution Engineering
Fujitsu Network Communication
(W)972-479-2263 (M)469-268-5226
2811 Telecom Drive
Richardson, TX 75081, USA

-----Original Message-----
From: Krzysztof Opasiak [mailto:k.opasiak@samsung.com]
Sent: Tuesday, September 8, 2020 3:37 PM
To: Miao, Xin <Xin.Miao@fujitsu.com>; morgan.richomme@orange.com
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-oom] Mariab-galera wont be redeployed



On 08.09.2020 22:27, Xin.Miao@fujitsu.com wrote:
Thank you, Krzysztof, for your quick response!

I have not try 'helm install'. Could you show me a complete syntax example of running 'helm install' for an onap component?

With 'helm deploy' I have the following:

ubuntu@onap-rancher-vm:~/oom/kubernetes$ helm deploy
dev-mariadb-galera local/onap --timeout 900 -f
~/xin/integration-override.yaml --namespace onap --verbose fetching
local/onap ubuntu@onap-rancher-vm:~/oom/kubernetes$
$ helm install \
--name mariadb \
-f ~/xin/integration-override.yaml \
--namespace onap \
--debug \
--timeout 900 \
onap


Thanks,

Xin Miao
Solution Engineering
Fujitsu Network Communication
(W)972-479-2263 (M)469-268-5226
2811 Telecom Drive
Richardson, TX 75081, USA


-----Original Message-----
From: Krzysztof Opasiak [mailto:k.opasiak@samsung.com]
Sent: Tuesday, September 8, 2020 3:22 PM
To: Miao, Xin <Xin.Miao@fujitsu.com>; morgan.richomme@orange.com
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-oom] Mariab-galera wont be redeployed



On 08.09.2020 22:19, Xin.Miao@fujitsu.com wrote:
Hi, Morgan/ Krzysztof/Team,

I tried to redeploy mariadb-galera after I ran 'helm undeploy
dev-mariadb-galera -purge' and cleaned up everything. However, the
'helm deploy dev-mariadb-galera . .' command returned  quietly
without anything happened.
Any difference if you do helm install instead of helm deploy?


I ran into this before. What I did previously was to redeploy the
entire ONAP cluster to get it back. But I really do not want to do it
this time since that will destroy everything that I have already
deployed, configured and distributed. I can redeploy other components
successfully. This only happens to dev-mariadb-galera component. It
is in master branch.

Did I missed something specifically?

Thanks a lot for your insight and help!

/Xin Miao/

/Solution Engineering/

/Fujitsu Network Communication/

/(W)972-479-2263 (M)469-268-5226/

/2811 Telecom Drive/

/Richardson, TX 75081, USA/
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics

--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics


Re: #sdnc Facing issues while trying to mount netconf server #sdnc

Kamel Idir
 

Hi Brian,

Do you know what configuration changes I need to make with schemaless connection?

Thanks,
Kamel


Re: [onap-sdnc] Rpc logs and DG logs not printed out in SDNC in Master deployment

Kamel Idir
 

Hi Xin,

I can see similar WARN message in our Frankfurt SDNC /var/log/onap/sdnc/karaf.log. Did you fix this issue?

2020-09-08T21:53:01,677 | WARN  | qtp2082108077-9006 | AbstractAuthenticator            | 141 - org.apache.shiro.core - 1.3.2 |  -  | Authentication failed for token submission [org.apache.shiro.authc.UsernamePasswordToken - admin, rememberMe=false].  Possible unexpected error? (Typical or expected login exceptions should extend from AuthenticationException). org.opendaylight.aaa.api.AuthenticationException: UserName / Password not found
        at org.opendaylight.aaa.shiro.idm.IdmLightProxy.dbAuthenticate(IdmLightProxy.java:105) ~[?:?]
        at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660) ~[?:?]
        at org.opendaylight.aaa.shiro.idm.IdmLightProxy.authenticate(IdmLightProxy.java:66) ~[?:?]
        at org.opendaylight.aaa.shiro.idm.IdmLightProxy.authenticate(IdmLightProxy.java:39) ~[?:?]
        at org.opendaylight.aaa.shiro.tokenauthrealm.auth.HttpBasicAuth.generateAuthentication(HttpBasicAuth.java:102) ~[?:?]
        at org.opendaylight.aaa.shiro.tokenauthrealm.auth.HttpBasicAuth.validate(HttpBasicAuth.java:122) ~[?:?]
        at org.opendaylight.aaa.shiro.realm.TokenAuthRealm.doGetAuthenticationInfo(TokenAuthRealm.java:147) ~[?:?]
        at org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568) ~[141:org.apache.shiro.core:1.3.2]
        at org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180) ~[141:org.apache.shiro.core:1.3.2]
        at org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267) ~[141:org.apache.shiro.core:1.3.2]
        at org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198) [141:org.apache.shiro.core:1.3.2]
        at org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106) [141:org.apache.shiro.core:1.3.2]
        at org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270) [141:org.apache.shiro.core:1.3.2]
        at org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256) [141:org.apache.shiro.core:1.3.2]
        at org.opendaylight.aaa.authenticator.ODLAuthenticator.login(ODLAuthenticator.java:80) [257:org.opendaylight.aaa.shiro:0.9.1]
        at org.opendaylight.aaa.authenticator.ODLAuthenticator.authenticate(ODLAuthenticator.java:50) [257:org.opendaylight.aaa.shiro:0.9.1]
        at Proxy74f732ac_eb3c_4b76_8640_04d85be54491.authenticate(Unknown Source) [?:?]
        at org.jolokia.osgi.security.ServiceAuthenticationHttpContext.handleSecurity(ServiceAuthenticationHttpContext.java:72) [200:org.jolokia.osgi:1.6.0]
        at org.ops4j.pax.web.service.internal.WebContainerContextWrapper.handleSecurity(WebContainerContextWrapper.java:46) [400:org.ops4j.pax.web.pax-web-runtime:7.2.5]
        at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:69) [398:org.ops4j.pax.web.pax-web-jetty:7.2.5]
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) [163:org.eclipse.jetty.security:9.4.12.v20180830]
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:293) [398:org.ops4j.pax.web.pax-web-jetty:7.2.5]
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) [166:org.eclipse.jetty.servlet:9.4.12.v20180830]
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) [398:org.ops4j.pax.web.pax-web-jetty:7.2.5]
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.server.Server.handle(Server.java:503) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) [165:org.eclipse.jetty.server:9.4.12.v20180830]
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305) [157:org.eclipse.jetty.io:9.4.12.v20180830]
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) [157:org.eclipse.jetty.io:9.4.12.v20180830]
        at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) [157:org.eclipse.jetty.io:9.4.12.v20180830]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) [168:org.eclipse.jetty.util:9.4.12.v20180830]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) [168:org.eclipse.jetty.util:9.4.12.v20180830]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168) [168:org.eclipse.jetty.util:9.4.12.v20180830]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126) [168:org.eclipse.jetty.util:9.4.12.v20180830]
        at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366) [168:org.eclipse.jetty.util:9.4.12.v20180830]
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765) [168:org.eclipse.jetty.util:9.4.12.v20180830]
        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683) [168:org.eclipse.jetty.util:9.4.12.v20180830]
        at java.lang.Thread.run(Thread.java:748) [?:?]

Thanks,
Kamel


Re: [onap-oom] Mariab-galera wont be redeployed

Krzysztof Opasiak
 

On 08.09.2020 22:27, Xin.Miao@fujitsu.com wrote:
Thank you, Krzysztof, for your quick response!

I have not try 'helm install'. Could you show me a complete syntax example of running 'helm install' for an onap component?

With 'helm deploy' I have the following:

ubuntu@onap-rancher-vm:~/oom/kubernetes$ helm deploy dev-mariadb-galera local/onap --timeout 900 -f ~/xin/integration-override.yaml --namespace onap --verbose
fetching local/onap
ubuntu@onap-rancher-vm:~/oom/kubernetes$
$ helm install \
--name mariadb \
-f ~/xin/integration-override.yaml \
--namespace onap \
--debug \
--timeout 900 \
onap


Thanks,

Xin Miao
Solution Engineering
Fujitsu Network Communication
(W)972-479-2263 (M)469-268-5226
2811 Telecom Drive
Richardson, TX 75081, USA


-----Original Message-----
From: Krzysztof Opasiak [mailto:k.opasiak@samsung.com]
Sent: Tuesday, September 8, 2020 3:22 PM
To: Miao, Xin <Xin.Miao@fujitsu.com>; morgan.richomme@orange.com
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-oom] Mariab-galera wont be redeployed



On 08.09.2020 22:19, Xin.Miao@fujitsu.com wrote:
Hi, Morgan/ Krzysztof/Team,

I tried to redeploy mariadb-galera after I ran 'helm undeploy
dev-mariadb-galera -purge' and cleaned up everything. However, the
'helm deploy dev-mariadb-galera . .' command returned  quietly without
anything happened.
Any difference if you do helm install instead of helm deploy?


I ran into this before. What I did previously was to redeploy the
entire ONAP cluster to get it back. But I really do not want to do it
this time since that will destroy everything that I have already
deployed, configured and distributed. I can redeploy other components
successfully. This only happens to dev-mariadb-galera component. It is
in master branch.

Did I missed something specifically?

Thanks a lot for your insight and help!

/Xin Miao/

/Solution Engineering/

/Fujitsu Network Communication/

/(W)972-479-2263 (M)469-268-5226/

/2811 Telecom Drive/

/Richardson, TX 75081, USA/
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics

--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics


Re: [onap-oom] Mariab-galera wont be redeployed

Xin.Miao@fujitsu.com
 

Thank you, Krzysztof, for your quick response!

I have not try 'helm install'. Could you show me a complete syntax example of running 'helm install' for an onap component?

With 'helm deploy' I have the following:

ubuntu@onap-rancher-vm:~/oom/kubernetes$ helm deploy dev-mariadb-galera local/onap --timeout 900 -f ~/xin/integration-override.yaml --namespace onap --verbose
fetching local/onap
ubuntu@onap-rancher-vm:~/oom/kubernetes$

Thanks,

Xin Miao
Solution Engineering
Fujitsu Network Communication
(W)972-479-2263 (M)469-268-5226
2811 Telecom Drive
Richardson, TX 75081, USA

-----Original Message-----
From: Krzysztof Opasiak [mailto:k.opasiak@samsung.com]
Sent: Tuesday, September 8, 2020 3:22 PM
To: Miao, Xin <Xin.Miao@fujitsu.com>; morgan.richomme@orange.com
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-oom] Mariab-galera wont be redeployed



On 08.09.2020 22:19, Xin.Miao@fujitsu.com wrote:
Hi, Morgan/ Krzysztof/Team,

I tried to redeploy mariadb-galera after I ran 'helm undeploy
dev-mariadb-galera -purge' and cleaned up everything. However, the
'helm deploy dev-mariadb-galera . .' command returned  quietly without
anything happened.
Any difference if you do helm install instead of helm deploy?


I ran into this before. What I did previously was to redeploy the
entire ONAP cluster to get it back. But I really do not want to do it
this time since that will destroy everything that I have already
deployed, configured and distributed. I can redeploy other components
successfully. This only happens to dev-mariadb-galera component. It is
in master branch.

Did I missed something specifically?

Thanks a lot for your insight and help!

/Xin Miao/

/Solution Engineering/

/Fujitsu Network Communication/

/(W)972-479-2263 (M)469-268-5226/

/2811 Telecom Drive/

/Richardson, TX 75081, USA/
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics


Re: [onap-oom] Mariab-galera wont be redeployed

Krzysztof Opasiak
 

On 08.09.2020 22:19, Xin.Miao@fujitsu.com wrote:
Hi, Morgan/ Krzysztof/Team,
I tried to redeploy mariadb-galera after I ran ‘helm undeploy dev-mariadb-galera –purge’ and cleaned up everything. However, the ‘helm deploy dev-mariadb-galera … …’ command returned  quietly without anything happened.
Any difference if you do helm install instead of helm deploy?

I ran into this before. What I did previously was to redeploy the entire ONAP cluster to get it back. But I really do not want to do it this time since that will destroy everything that I have already deployed, configured and distributed. I can redeploy other components successfully. This only happens to dev-mariadb-galera component. It is in master branch.
Did I missed something specifically?
Thanks a lot for your insight and help!
/Xin Miao/
/Solution Engineering/
/Fujitsu Network Communication/
/(W)972-479-2263 (M)469-268-5226/
/2811 Telecom Drive/
/Richardson, TX 75081, USA/
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics


[onap-oom] Mariab-galera wont be redeployed

Xin.Miao@fujitsu.com
 

Hi, Morgan/ Krzysztof/Team,

 

I tried to redeploy mariadb-galera after I ran ‘helm undeploy dev-mariadb-galera –purge’ and cleaned up everything. However, the ‘helm deploy dev-mariadb-galera … …’ command returned  quietly without anything happened.

 

I ran into this before. What I did previously was to redeploy the entire ONAP cluster to get it back. But I really do not want to do it this time since that will destroy everything that I have already deployed, configured and distributed.  I can redeploy other components successfully. This only happens to dev-mariadb-galera component. It is in master branch.

 

Did I missed something specifically?

 

Thanks a lot for your insight and help!

 

Xin Miao

Solution Engineering

Fujitsu Network Communication

(W)972-479-2263 (M)469-268-5226

2811 Telecom Drive

Richardson, TX 75081, USA

 


Power Outage - Intel Oregon

Gooch, Stephen
 

Hello,

 

The intel Oregon lab is experiences power outages.  They have been advised not to restore power to the rack until 20:00 UTC on Sept 7th.

 

Br,

- Stephen

 

-- 

 


Re: #sdnc Facing issues while trying to mount netconf server #sdnc

Brian Freeman
 

I’m surprised that schemaless will work for you. Not the connection part but at the application level.

Can you make the configuration changes you need with a schemaless connection ?

 

brian

 

 

 

https://docs.opendaylight.org/projects/netconf/en/latest/user-guide.html

Connecting to a device supporting only NETCONF 1.0

OpenDaylight is schema-based distribution and heavily depends on YANG models. However some legacy NETCONF devices are not schema-based and implement just RFC 4741. This type of device does not utilize YANG models internally and OpenDaylight does not know how to communicate with such devices, how to validate data, or what the semantics of data are.

NETCONF connector can communicate also with these devices, but the trade-offs are worsened possibilities in utilization of NETCONF mountpoints. Using RESTCONF with such devices is not suported. Also communicating with schemaless devices from application code is slightly different.

To connect to schemaless device, there is a optional configuration option in netconf-node-topology model called schemaless. You have to set this option to true.

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Kamel Idir via lists.onap.org
Sent: Tuesday, September 8, 2020 1:47 PM
To: Kamel Idir <kamel.idir@...>; onap-discuss@...
Subject: Re: [onap-discuss] #sdnc Facing issues while trying to mount netconf server

 

Hi Brian,

I have fixed my netconf mount issue.

Basically I added this line in my netconf mount request body. and got connected to the gNB.

<schemaless xmlns="urn:opendaylight:netconf-node-topology">true</schemaless>

Here is the response of netconf connection check from my Postman.

{

    "node": [

        {

            "node-id": "bb294f67-9c53-4f08-ab8d-d7a842e88585",

            "netconf-node-topology:host": "10.x.x.x",

            "netconf-node-topology:connection-status": "connected",

            "netconf-node-topology:port": 840

        }

    ]

}

Thanks,
Kamel


Re: #sdnc Facing issues while trying to mount netconf server #sdnc

Kamel Idir
 

Hi Brian,

I have fixed my netconf mount issue.

Basically I added this line in my netconf mount request body. and got connected to the gNB.

<schemaless xmlns="urn:opendaylight:netconf-node-topology">true</schemaless>

Here is the response of netconf connection check from my Postman.
{
    "node": [
        {
            "node-id": "bb294f67-9c53-4f08-ab8d-d7a842e88585",
            "netconf-node-topology:host": "10.x.x.x",
            "netconf-node-topology:connection-status": "connected",
            "netconf-node-topology:port": 840
        }
    ]
}

Thanks,
Kamel


VNFQTS - VES Bi-Weekly Working Meeting - Tue, 09/08/2020 3:00pm-4:00pm #cal-reminder

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

Reminder: VNFQTS - VES Bi-Weekly Working Meeting

When: Tuesday, 8 September 2020, 3:00pm to 4:00pm, (GMT+00:00) UTC

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

View Event

Organizer: Trevor Lovett trevor.lovett@... ONAP9

Description: Recurring meeting to discuss updates to the VES Event Listener specification (part of the VNFRQTS project)

Join Zoom Meeting

https://zoom.us/j/619472067

 

Meeting ID: 619 472 067

 

One tap mobile

+13462487799,,619472067# US (Houston)

+16699006833,,619472067# US (San Jose)

 

Dial by your location

        +1 346 248 7799 US (Houston)

        +1 669 900 6833 US (San Jose)

        +1 301 715 8592 US

        +1 312 626 6799 US (Chicago)

        +1 646 558 8656 US (New York)

        +1 253 215 8782 US

        877 369 0926 US Toll-free

        855 880 1246 US Toll-free

        +1 647 558 0588 Canada

        +1 778 907 2071 Canada

        +1 438 809 7799 Canada

        +1 587 328 1099 Canada

        +1 647 374 4685 Canada

        855 703 8985 Canada Toll-free

Meeting ID: 619 472 067

Find your local number: https://zoom.us/u/adkHIVoaZR


Re: ONAP Dublin - [SDNC] Preload before adding VF Module

Brian Freeman
 

The error message is about the model not the preload but I haven’t seen that error in a long time.

 

but in answer to your question – yes you need preload data unless you are using CDS.

 

If you look at the vFWCL automated flow in the wiki for the Frankfurt tests

https://wiki.onap.org/display/DW/2%3A+Frankfurt+Release+Integration+Testing+Status

 

Row #1 , on the far right side there is the zip file with the log.html from the automated robot test. Expand until you see the point where preload is done.

 

Brian

 

 

From: Kuldeep Singh Negi <KuldeepSinghN@...>
Sent: Friday, September 4, 2020 11:22 AM
To: FREEMAN, BRIAN D <bf1936@...>
Cc: onap-discuss@...
Subject: RE: ONAP Dublin - [SDNC] Preload before adding VF Module

 

Hi Brian,

 

Just picking up on this old mail-thread as came across executing same scenario but with Frankfurt.

Is this SDNC preload still required/supported to be done before creating VNF Module while instantiating using VID?

 

Thanks for your help.

 

Regards,

Kuldeep

 

 

_____________________________________________
From: Kuldeep Singh Negi
Sent: Tuesday, January 28, 2020 1:11 AM
To: LTE Next Generation <lte-ng@...>
Cc: onap-discuss@...
Subject: RE: ONAP Dublin - [SDNC] Preload before adding VF Module

 

 

Thanks Hanif.

The creds have worked. Hence, could do the preloading, however adding VF Module in VID is failing with below error.

 

This reports VFC_MODEL table to have no entries for customization UUID.

Can you advise on how to address this ? Many Thanks.

 

"requestId": "505f2da6-f567-4536-bc0f-9d1f75f4b448",

"requestType": "createInstance",

"timestamp": "Tue, 28 Jan 2020 00:25:56",

"requestState": "FAILED",

"requestStatus": "STATUS: Error from SDNC: No entries found in VFC_MODEL table for customization UUID  FLOW STATUS: AssignVfModuleBB has failed.",

"percent-progress": "100"

 

"requestId": "505f2da6-f567-4536-bc0f-9d1f75f4b448",

"requestType": "createInstance",

"timestamp": "Tue, 28 Jan 2020 00:25:55",

"requestState": "IN_PROGRESS",

"requestStatus": undefined,

"percent-progress": undefined

 

"requestId": "505f2da6-f567-4536-bc0f-9d1f75f4b448",

"requestType": "createInstance",

"timestamp": "Tue, 28 Jan 2020 00:25:55",

"requestState": "IN_PROGRESS",

"requestStatus": undefined,

"percent-progress": undefined

 

"requestId": "505f2da6-f567-4536-bc0f-9d1f75f4b448",

"requestType": "createInstance",

"timestamp": "Tue, 28 Jan 2020 00:25:55",

"requestState": "IN_PROGRESS",

"requestStatus": undefined,

"percent-progress": undefined

 

"requestId": "505f2da6-f567-4536-bc0f-9d1f75f4b448",

"requestType": "createInstance",

"timestamp": "Tue, 28 Jan 2020 00:25:54",

"requestState": "IN_PROGRESS",

"requestStatus": undefined,

"percent-progress": undefined

 

"requestId": "505f2da6-f567-4536-bc0f-9d1f75f4b448",

"requestType": "createInstance",

"timestamp": "Tue, 28 Jan 2020 00:25:54",

"requestState": "IN_PROGRESS",

"requestStatus": undefined,

"percent-progress": undefined

 

01/28/20 00:25:53 HTTP Status: Accepted (202)

{

  "requestReferences": {

    "requestId": "505f2da6-f567-4536-bc0f-9d1f75f4b448",

    "instanceId": "97788213-930f-480f-91c8-e83d42d9a9cf",

  }

}

 

Regards,

Kuldeep

 

From: LTE Next Generation <lte-ng@...>
Sent: Monday, January 27, 2020 9:37 PM
To: onap-discuss@...; Kuldeep Singh Negi <KuldeepSinghN@...>
Cc: FREEMAN, BRIAN D <bf1936@...>
Subject: RE: ONAP Dublin - [SDNC] Preload before adding VF Module

 

[CAUTION: This Email is from outside the Organization. Do not click links or open attachments unless you trust the sender.]

Hi Kuldeep,

 

 

The login credentials:
username: admin
password: Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U

 

 

Thanks and Kind Regards,

Hanif Kukkalli

--

Hanif Kukkalli

highstreet technologies GmbH

Hähnelstraße 6

12159 Berlin

Telephone: +49 371 531 33402

 

Geschäftsführer: Dipl.-Ing. (FH) Alfons Mittermaier

Handelsregister: Amtsgericht Charlottenburg, HRB 114905 B

Firmensitz: Berlin

USt-IdNr.: DE261090513

 

5a 69 6e 64 61 20 48 6f 6f 6e 20 28 41 6c 69 76 65 29

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Kuldeep Singh Negi
Sent: 27 January 2020 17:03
To: onap-discuss@...
Cc: FREEMAN, BRIAN D <bf1936@...>
Subject: [onap-discuss] ONAP Dublin - [SDNC] Preload before adding VF Module

 

Hi All,

 

Can someone share the credentials to be used for SDNC-preload below?

In VID, before adding VNF modules to newly created VNF, needed to execute SDNC VNF-API steps @ https://wiki.onap.org/display/DW/Tutorial_vIMS+%3A+SDNC+Updates

 

Any help/guidance is highly appreciated. Thanks.

 

<< OLE Object: Picture (Device Independent Bitmap) >>

 

Regards,

Kuldeep

 

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.

 

1201 - 1220 of 23232