Date   

[aai] docker image dependency chart

Paul Vaduva
 

Hi aai team

 

I am Paul Vaduva and I am part of the dockerhub migration effort together with Linux Foundation, as presented in various meetings at the DDF in June and anounced in multiple TSC meetings we need to create a dependency chart of docker images for every ONAP project before the migration happens in order for it to run smoothly according to Linux Foundation. As the team who is working on the aai project you are the ones to ask about this docker images dependency list. However because your time is preciouse and there is a constant need of resources, I started this effort to create the dependency chart of all the docker images for all the project. Due to the multitude of docker iamges the manual process is tedious at best so I used an automated text parser to make a best effort list which is not complete and cannot be due to multiple inconsistent type of formated text output in docker build jobs logs. However it's a starting point and since each tech team should have the final work I invite you to have a look at the dependency list for aai porject and give input in some form of your choosing (comments, edits, reply to this email, etc.) here:

https://wiki.onap.org/display/DW/Docker+images+dependency+list

You can see the list of docker images dependencies for each project in a roughly form like this:

1 --> 2 --> 3 ... --> n

where 1 is the dependency for the image (what you find in the FROM clause of a Dcokerfile), 2 is the dependent image (the name of the image that your project builds) and form 3 onward there are usually other tags of the same proejct image.

The previous wiki page is just a way to centralize the information regarding docker iamges dependency chart.

As Martial (PTL of clamp project) mentioned you can intruduce in the list the docker-compose dependencies (They are usually upstream project so already in dockerhub but better check them as well).

 

Thanks you,

Paul


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


Re: ODP: [onap-discuss] [vLBMS] Create instance into VID fails

Sanchita Pathak
 

Hello Marco,


I am facing the same error STATUS: Error from SDNC: Invalid index values [0,] while doing simple vFW usecase. I have done SDNC preload with GENERIC-RESOURCE-API:preload-vf-module-topology-operation API

SDNC version is sdnc-image:1.5.4. SO debug log is attached. Can you please help?

Thanks,
Sanchita





From: onap-discuss@lists.onap.org <onap-discuss@lists.onap.org> On Behalf Of Marco Platania
Sent: Tuesday, June 11, 2019 8:58 PM
To: MALINCONICO ANIELLO PAOLO <aniello.malinconico@polito.it>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] ODP: [onap-discuss] [vLBMS] Create instance into VID fails

I think you should update SDNC to 1.5.3-STAGING-latest. You are getting stuck with an error in the assignment DG that is calling gw-vfmodule-update when it shouldn’t, unless you are actually trying to install the vCPE VNF. If that is the case, perhaps SDNC Team can help better.

Marco


From: MALINCONICO ANIELLO PAOLO <aniello.malinconico@polito.it<mailto:aniello.malinconico@polito.it>>
Date: Tuesday, June 11, 2019 at 10:47 AM
To: "PLATANIA, MARCO (MARCO)" <platania@research.att.com<mailto:platania@research.att.com>>, "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] ODP: [onap-discuss] [vLBMS] Create instance into VID fails

Hi Marco, I have executed your instructions and it goes on. Thanks a lot.
But, the vfmodule creation still fails. Now the error is sbout the SDNC.
The VID returns:

"requestId": "daf7eb7d-7b5f-44df-bc63-e2c8be7bcf00",

"requestType": "createInstance",

"timestamp": "Tue, 11 Jun 2019 16:34:39",

"requestState": "FAILED",

"requestStatus": "STATUS: Error from SDNC: Invalid index values [0,] FLOW STATUS: All Rollback flows have completed successfully ROLLBACK STATUS: Rollback has been completed successfully.",

"percent-progress": "100"


The BPMN log gives the same error.
The SDNC log is the following:
2019-06-11T14:34:25,597 | INFO | qtp1306934935-46932 | SvcLogicServiceImplBase | 475 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar - 0.0.0 | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=vf-module-topology-operation-assign, mode=sync, version=1.6.0, md5sum=ada50a4524093aa35645b8a3da11b796] - 17 (block) | About to execute node # 18 (set)
2019-06-11T14:34:25,598 | INFO | qtp1306934935-46932 | SvcLogicServiceImplBase | 475 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar - 0.0.0 | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=vf-module-topology-operation-assign, mode=sync, version=1.6.0, md5sum=ada50a4524093aa35645b8a3da11b796] - 18 (set) | About to execute node # 19 (break)
2019-06-11T14:34:25,599 | ERROR | qtp1306934935-46932 | ForNodeExecutor | 475 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar - 0.0.0 | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=vf-module-topology-operation-assign, mode=sync, version=1.6.0, md5sum=ada50a4524093aa35645b8a3da11b796] - 19 (break) | ForNodeExecutor caught break
org.onap.ccsdk.sli.core.sli.BreakNodeException: BreakNodeExecutor encountered break with nodeId 19
at org.onap.ccsdk.sli.core.sli.provider.base.BreakNodeExecutor.execute(BreakNodeExecutor.java:39) [475:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.executeNode(SvcLogicServiceImplBase.java:147) [475:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.BlockNodeExecutor.execute(BlockNodeExecutor.java:62) [475:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar:0.0.0]

2019-06-11T14:34:28,727 | INFO | qtp1306934935-46932 | SvcLogicServiceImplBase | 475 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar - 0.0.0 | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=gw-vfmodule-update, mode=sync, version=1.6.0, md5sum=bd430b5bcad3bda1825dacce45fbd6b3] - 1 (block) | About to execute node # 2 (set)
2019-06-11T14:34:28,728 | INFO | qtp1306934935-46932 | SvcLogicServiceImplBase | 475 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar - 0.0.0 | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=gw-vfmodule-update, mode=sync, version=1.6.0, md5sum=bd430b5bcad3bda1825dacce45fbd6b3] - 2 (set) | About to execute node # 3 (set)
2019-06-11T14:34:28,729 | INFO | qtp1306934935-46932 | SvcLogicServiceImplBase | 475 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar - 0.0.0 | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=gw-vfmodule-update, mode=sync, version=1.6.0, md5sum=bd430b5bcad3bda1825dacce45fbd6b3] - 3 (set) | About to execute node # 4 (get-resource)
2019-06-11T14:34:28,732 | INFO | qtp1306934935-46932 | ConfigResource | 218 - org.onap.ccsdk.sli.adaptors.mdsal-resource-provider - 0.5.0.SNAPSHOT | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=gw-vfmodule-update, mode=sync, version=1.6.0, md5sum=bd430b5bcad3bda1825dacce45fbd6b3] - 4 (get-resource) | Querying resource: GENERIC-RESOURCE-API. At URL: restconf/config/GENERIC-RESOURCE-API:tunnelxconn-allotted-resources/
2019-06-11T14:34:28,732 | INFO | qtp1306934935-46932 | ConfigResource | 218 - org.onap.ccsdk.sli.adaptors.mdsal-resource-provider - 0.5.0.SNAPSHOT | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=gw-vfmodule-update, mode=sync, version=1.6.0, md5sum=bd430b5bcad3bda1825dacce45fbd6b3] - 4 (get-resource) | Sending REST GET to http://localhost:8181/restconf/config/GENERIC-RESOURCE-API:tunnelxconn-allotted-resources/
2019-06-11T14:34:28,740 | INFO | qtp1306934935-46932 | ConfigResource | 218 - org.onap.ccsdk.sli.adaptors.mdsal-resource-provider - 0.5.0.SNAPSHOT | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=gw-vfmodule-update, mode=sync, version=1.6.0, md5sum=bd430b5bcad3bda1825dacce45fbd6b3] - 4 (get-resource) | Response: 404 Not Found
2019-06-11T14:34:28,741 | INFO | qtp1306934935-46932 | ConfigResource | 218 - org.onap.ccsdk.sli.adaptors.mdsal-resource-provider - 0.5.0.SNAPSHOT | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=gw-vfmodule-update, mode=sync, version=1.6.0, md5sum=bd430b5bcad3bda1825dacce45fbd6b3] - 4 (get-resource) | Response body :
<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"><error><error-type>application</error-type><error-tag>data-missing</error-tag><error-message>Request could not be completed because the relevant data model content does not exist </error-message></error></errors>

2019-06-11T14:34:28,748 | INFO | qtp1306934935-46932 | SvcLogicServiceImplBase | 475 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar - 0.0.0 | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=gw-vfmodule-update, mode=sync, version=1.6.0, md5sum=bd430b5bcad3bda1825dacce45fbd6b3] - 4 (get-resource) | About to execute node # 5 (for)
2019-06-11T14:34:28,749 | ERROR | qtp1306934935-46932 | GenericResourceApiProvider | 244 - org.onap.sdnc.northbound.generic-resource-api-provider - 1.6.0.SNAPSHOT | SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=gw-vfmodule-update, mode=sync, version=1.6.0, md5sum=bd430b5bcad3bda1825dacce45fbd6b3] - 5 (for) | Caught exception executing service logic for vf-module-topology-operation org.onap.ccsdk.sli.core.sli.SvcLogicException: Invalid index values [0,]
at org.onap.ccsdk.sli.core.sli.provider.base.ForNodeExecutor.execute(ForNodeExecutor.java:68) [475:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.executeNode(SvcLogicServiceImplBase.java:147) [475:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.BlockNodeExecutor.execute(BlockNodeExecutor.java:62) [475:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.executeNode(SvcLogicServiceImplBase.java:147) [475:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.execute(SvcLogicServiceImplBase.java:117) [475:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.5.0-SNAPSHOT_sli-provider-base-0.5.0-SNAPSHOT.jar:0.0.0]




The entire SDNC log is the attached file.
Can you help me to go on ?

Thanks,

Aniello

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


Re: [Dublin] VF Module Scale Out Use Case

Aniello Paolo Malinconico
 

Hi Yuriy,
I have redeployed the sdnc component from the Dublin 4.0.0-ONAP tag and redone all steps.
But I have always the same error :

2019-07-12T09:18:06,221 | ERROR | qtp643911459-138 | ExecuteNodeExecutor              | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | SvcLogicGraph [module=
GENERIC-RESOURCE-API, rpc=self-serve-vfmodule-ra-assignment, mode=sync, version=1.5.4, md5sum=d7709b8bad002dda1b3fd4e37ba263d9] - 31 (execute) | Could not execute plugin. SvcLogic status will be set to failure.
org.onap.ccsdk.sli.core.sli.SvcLogicException: problem with jsonStringToCtx
        at org.onap.ccsdk.sli.core.slipluginutils.SliPluginUtils.jsonStringToCtx(SliPluginUtils.java:817) [230:org.onap.ccsdk.sli.core.sliPluginUtils-provider:0.4.4]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
 
Caused by: com.google.gson.JsonSyntaxException: com.google.gson.stream.MalformedJsonException: Unterminated object at line 101 column 24 path $.resource-accumulator-resolved-data[24].param-value
        at com.google.gson.internal.Streams.parse(Streams.java:60) ~[34:com.google.gson:2.8.5]
        at com.google.gson.JsonParser.parse(JsonParser.java:84) ~[34:com.google.gson:2.8.5]
        at com.google.gson.JsonParser.parse(JsonParser.java:59) ~[34:com.google.gson:2.8.5]
        at com.google.gson.JsonParser.parse(JsonParser.java:45) ~[34:com.google.gson:2.8.5]
        at org.onap.ccsdk.sli.core.slipluginutils.SliPluginUtils.writeJsonToCtx(SliPluginUtils.java:823) ~[?:?]
        at org.onap.ccsdk.sli.core.slipluginutils.SliPluginUtils.jsonStringToCtx(SliPluginUtils.java:815) ~[?:?]

Caused by: com.google.gson.stream.MalformedJsonException: Unterminated object at line 101 column 24 path $.resource-accumulator-resolved-data[24].param-value
        at com.google.gson.stream.JsonReader.syntaxError(JsonReader.java:1568) ~[34:com.google.gson:2.8.5]
        at com.google.gson.stream.JsonReader.doPeek(JsonReader.java:491) ~[34:com.google.gson:2.8.5]
        at com.google.gson.stream.JsonReader.hasNext(JsonReader.java:414) ~[34:com.google.gson:2.8.5]
 

The SDNC image version are :

root@cp-1:~/oom_26_June/kubernetes# grep -nri "image:" sdnc/ | grep onap
sdnc/charts/ueb-listener/values.yaml:30:image: onap/sdnc-ueb-listener-image:1.5.4
sdnc/charts/dmaap-listener/values.yaml:30:image: onap/sdnc-dmaap-listener-image:1.5.4
sdnc/charts/sdnc-portal/values.yaml:30:image: onap/admportal-sdnc-image:1.5.4
sdnc/charts/sdnc-ansible-server/values.yaml:30:image: onap/sdnc-ansible-server-image:1.5.4
sdnc/values.yaml:35:image: onap/sdnc-image:1.5.4
sdnc/sdnc-prom/values.yaml:34:image: onap/music/prom:1.0.5


There are new version of sdnc images:

    "1.5.4",
    "1.5.4-STAGING-20190616T152603Z",
    "1.5.4-STAGING-20190617T152607Z",
    "1.5.4-STAGING-20190618T152628Z",
    "1.5.4-STAGING-latest",
    "1.6-STAGING-latest",
    "1.6.0-STAGING-20190616T202604Z",
    "1.6.0-STAGING-20190617T202620Z",
    "1.6.0-STAGING-20190618T202637Z",
    "1.6.0-STAGING-20190619T202610Z",
    "1.6.0-STAGING-20190620T202611Z",
    "1.6.0-STAGING-20190621T202614Z",
    "1.6.0-STAGING-20190622T202609Z",
    "1.6.0-STAGING-20190623T202614Z",
    "1.6.0-STAGING-20190624T202626Z",
    "1.6.0-STAGING-20190626T202636Z",
    "1.6.0-STAGING-20190627T202626Z",
    "1.6.0-STAGING-20190628T202615Z",
    "1.6.0-STAGING-20190629T202611Z",
    "1.6.0-STAGING-20190630T202601Z",
    "1.6.0-STAGING-20190701T202617Z",
    "1.6.0-STAGING-20190702T202619Z",
    "1.6.0-STAGING-20190703T202617Z",
    "1.6.0-STAGING-20190704T202611Z",
    "1.6.0-STAGING-20190705T202614Z",
    "1.6.0-STAGING-20190706T202608Z",
    "1.6.0-STAGING-20190707T202611Z",
    "1.6.0-STAGING-20190708T191410Z",
    "1.6.0-STAGING-20190708T202616Z",
    "1.6.0-STAGING-20190709T202611Z",
    "1.6.0-STAGING-20190710T202605Z",
    "1.6.0-STAGING-20190711T202635Z",
    "1.6.0-STAGING-latest",


Should I try to install the 1.6.0 to solve this issue?

Thanks,
Aniello Paolo Malinconico
 


Re: [ccsdk] docker image dependency chart

Paul Vaduva
 

Kind reminder,

 

Can someone from the ccsdk  team take a look on the list of docker image depdencies here please:

https://wiki.onap.org/display/DW/Docker+images+dependency+list

And confirm it’s complete or add missing dependencies ?

 

Best Regards,

Paul

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Paul Vaduva
Sent: Monday, July 8, 2019 2:06 PM
To: onap-discuss@...
Cc: dtimoney@...; Jessica Wagantall <jwagantall@...>; Jim Baker <jbaker@...>; Kenny Paul <kpaul@...>; Cristina Pauna <Cristina.Pauna@...>
Subject: [onap-discuss][ccsdk] docker image dependency chart

 

Hi ccsdk team

 

I am Paul Vaduva and I am part of the dockerhub migration effort together with Linux Foundation, as presented in various meetings at the DDF in June and anounced in multiple TSC meetings we need to create a dependency chart of docker images for every ONAP project before the migration happens in order for it to run smoothly according to Linux Foundation. As the team who is working on the ccsdk project you are the ones to ask about this docker images dependency list. However because your time is preciouse and there is a constant need of resources, I started this effort to create the dependency chart of all the docker images for all the project. Due to the multitude of docker iamges the manual process is tedious at best so I used an automated text parser to make a best effort list which is not complete and cannot be due to multiple inconsistent type of formated text output in docker build jobs logs. However it's a starting point and since each tech team should have the final work I invite you to have a look at the dependency list for ccsdk porject and give input in some form of your choosing (comments, edits, reply to this email, etc.) here:

https://wiki.onap.org/display/DW/Docker+images+dependency+list

You can see the list of docker images dependencies for each project in a roughly form like this:

1 --> 2 --> 3 ... --> n

where 1 is the dependency for the image (what you find in the FROM clause of a Dcokerfile), 2 is the dependent image (the name of the image that your project builds) and form 3 onward there are usually other tags of the same proejct image.

The previous wiki page is just a way to centralize the information regarding docker iamges dependency chart.

As Martial (PTL of clamp project) mentioned you can intruduce in the list the docker-compose dependencies (They are usually upstream project so already in dockerhub but better check them as well).

 

Thanks you,

Paul


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


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


Re: [Dublin] AAI Docker setup on a single VM failed

Vivekanandan Muthukrishnan
 

Hi Dmitry,

Thanks for the quick response and it worked along with  setting the kernel parameter vm.max_map_count=262144.

I am still not able to access the AAI UI. I can see that Sparky-be Java process is listening on port 8000, and accepting requests.

While accessing the Sparky URL (https://sparky-be:8000), it is redirecting to the Portal login page (http://portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm). 

Is there a workaround to load the AAI Sparky UI alone without ONAP Portal ?

Regards
Vivek

AAI Container status

root@aai-vivek-01:/opt/test-config# docker ps -a
CONTAINER ID        IMAGE                                                 COMMAND                  CREATED              STATUS                   PORTS                                                                                                      NAMES
4ff7949ec4e7        nexus3.onap.org:10001/onap/babel                      "/opt/app/babel/bin/…"   About a minute ago   Up About a minute        0.0.0.0:9516->9516/tcp                                                                                     testconfig_babel_1
0a8236389bf8        nexus3.onap.org:10001/onap/spike                      "/opt/app/spike/bin/…"   About a minute ago   Up About a minute        0.0.0.0:9518->9518/tcp                                                                                     testconfig_spike-service_1
6ec9927d94c1        nexus3.onap.org:10001/onap/gizmo                      "/opt/app/crud-api/b…"   About a minute ago   Up About a minute        0.0.0.0:9520->9520/tcp                                                                                     testconfig_crud-service_1
1d8de1f17af0        nexus3.onap.org:10001/onap/champ                      "/opt/app/champ-serv…"   About a minute ago   Up About a minute        0.0.0.0:9522->9522/tcp                                                                                     testconfig_champ-service_1
0357729da494        nexus3.onap.org:10001/onap/search-data-service        "/opt/app/search-dat…"   About a minute ago   Up About a minute        0.0.0.0:9509->9509/tcp                                                                                     testconfig_aai.searchservice.simpledemo.openecomp.org_1
14435795e4ee        nexus3.onap.org:10001/onap/model-loader               "/opt/app/model-load…"   About a minute ago   Up About a minute                                                                                                                   testconfig_model-loader_1
fca63a495972        nexus3.onap.org:10001/onap/data-router                "/opt/app/data-route…"   About a minute ago   Up About a minute        0.0.0.0:9502->9502/tcp                                                                                     testconfig_datarouter_1
b459a618b6e2        nexus3.onap.org:10001/onap/sparky-be                  "/opt/app/sparky/bin…"   About a minute ago   Up About a minute        8000/tcp, 0.0.0.0:9517->9517/tcp                                                                           testconfig_sparky-be_1
90d93b99afdb        aaionap/haproxy:1.2.3                                 "/docker-entrypoint.…"   2 minutes ago        Up 2 minutes             0.0.0.0:8443->8443/tcp                                                                                     testconfig_aai.api.simpledemo.onap.org_1
7ce302d939d2        nexus3.onap.org:10001/onap/aai-traversal              "/bin/bash /opt/app/…"   2 minutes ago        Up 2 minutes (healthy)   0.0.0.0:8446->8446/tcp                                                                                     testconfig_aai-traversal.api.simpledemo.onap.org_1
bea69410006b        nexus3.onap.org:10001/onap/aai-resources              "/bin/bash /opt/app/…"   3 minutes ago        Up 3 minutes (healthy)   0.0.0.0:8447->8447/tcp                                                                                     testconfig_aai-resources.api.simpledemo.onap.org_1
5e084de1f8f5        nexus3.onap.org:10001/onap/aai-graphadmin             "/bin/bash /opt/app/…"   3 minutes ago        Up 3 minutes (healthy)   0.0.0.0:8449->8449/tcp                                                                                     testconfig_aai-graphadmin.api.simpledemo.onap.org_1
19685cb8cbfa        docker.elastic.co/elasticsearch/elasticsearch:6.1.2   "/usr/local/bin/dock…"   4 minutes ago        Up 4 minutes             0.0.0.0:9200->9200/tcp, 9300/tcp                                                                           elasticsearch
271dc13329dc        cassandra:2.1                                         "docker-entrypoint.s…"   4 minutes ago        Up 4 minutes             0.0.0.0:7000-7001->7000-7001/tcp, 0.0.0.0:7199->7199/tcp, 0.0.0.0:9042->9042/tcp, 0.0.0.0:9160->9160/tcp   testconfig_aai.hbase.simpledemo.onap.org_1




On Thu, Jul 11, 2019 at 5:01 PM Puzikov Dmitry <dmitry.puzikov@...> wrote:

Hi, 


The line 1 of elasticsearch.yml contains unparseable symbol at position 13 right after "Copyright", just remove it and you're good to go. Hope it helps.


Regards,

Dmitry





From: onap-discuss@... <onap-discuss@...> on behalf of Vivekanandan Muthukrishnan <vmuthukrishnan@...>
Sent: Thursday, July 11, 2019 12:56:17 PM
To: onap-discuss@...; jf2512@...
Subject: Re: [onap-discuss] [Dublin] AAI Docker setup on a single VM failed
 
Hi James

I followed the below Wiki page and all AAI Docker containers came up except Elasticsearch. I did disable AAF authentication ( spring.profiles.active=production,one-way-ssl,dmaap) as suggested in the Wiki page.


The issue is that i am not able to access the AAI UI. I can see that Sparky-be Java process is listening on port 8000, and accepting requests.

While accessing the Sparky URL (https://sparky-be:8000), it is redirecting to the Portal login page (http://portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm)

I guess there is way to bypass the user authentication to load Sparky UI. Could you let me know, if there are any configuration files to disable user authentication. This would would help us to proceed further in setting up our AAI development environment.

Below are the log snippets from my development environment. Please let me know, if you need any additional details.

Regards
Vivek

Docker containers
------------------------

CONTAINER ID        IMAGE                                                 COMMAND                  CREATED             STATUS                   PORTS                                                                                                      NAMES
1e20e39ef3ea        nexus3.onap.org:10001/onap/babel                      "/opt/app/babel/bin/…"   2 hours ago         Up 2 hours               0.0.0.0:9516->9516/tcp                                                                                     testconfig_babel_1
8d79b8fef8c4        nexus3.onap.org:10001/onap/spike                      "/opt/app/spike/bin/…"   2 hours ago         Up 2 hours               0.0.0.0:9518->9518/tcp                                                                                     testconfig_spike-service_1
99ed2ce5b16f        nexus3.onap.org:10001/onap/gizmo                      "/opt/app/crud-api/b…"   2 hours ago         Up 2 hours               0.0.0.0:9520->9520/tcp                                                                                     testconfig_crud-service_1
1dbd5ac054de        nexus3.onap.org:10001/onap/champ                      "/opt/app/champ-serv…"   2 hours ago         Up 2 hours               0.0.0.0:9522->9522/tcp                                                                                     testconfig_champ-service_1
f2f400f52666        nexus3.onap.org:10001/onap/search-data-service        "/opt/app/search-dat…"   2 hours ago         Up 2 hours               0.0.0.0:9509->9509/tcp                                                                                     testconfig_aai.searchservice.simpledemo.openecomp.org_1
7452f46106d5        nexus3.onap.org:10001/onap/model-loader               "/opt/app/model-load…"   2 hours ago         Up 2 hours                                                                                                                          testconfig_model-loader_1
e1bf591a6d3c        nexus3.onap.org:10001/onap/data-router                "/opt/app/data-route…"   2 hours ago         Up 2 hours               0.0.0.0:9502->9502/tcp                                                                                     testconfig_datarouter_1
f6baf127ed18        nexus3.onap.org:10001/onap/sparky-be                  "/opt/app/sparky/bin…"   2 hours ago         Up 2 hours               8000/tcp, 0.0.0.0:9517->9517/tcp                                                                           testconfig_sparky-be_1
00771ebf35e5        aaionap/haproxy:1.2.3                                 "/docker-entrypoint.…"   2 hours ago         Up 2 hours               0.0.0.0:8443->8443/tcp                                                                                     testconfig_aai.api.simpledemo.onap.org_1
6c7888567b89        nexus3.onap.org:10001/onap/aai-traversal              "/bin/bash /opt/app/…"   2 hours ago         Up 2 hours (healthy)     0.0.0.0:8446->8446/tcp                                                                                     testconfig_aai-traversal.api.simpledemo.onap.org_1
5b04ac83e54f        nexus3.onap.org:10001/onap/aai-resources              "/bin/bash /opt/app/…"   2 hours ago         Up 2 hours (healthy)     0.0.0.0:8447->8447/tcp                                                                                     testconfig_aai-resources.api.simpledemo.onap.org_1
e5b1e3750ad3        nexus3.onap.org:10001/onap/aai-graphadmin             "/bin/bash /opt/app/…"   2 hours ago         Up 2 hours (healthy)     0.0.0.0:8449->8449/tcp                                                                                     testconfig_aai-graphadmin.api.simpledemo.onap.org_1
91f99c7b9769        docker.elastic.co/elasticsearch/elasticsearch:6.1.2   "/usr/local/bin/dock…"   2 hours ago         Exited (1) 2 hours ago                                                                                                              elasticsearch
a225d5867075        cassandra:2.1                                         "docker-entrypoint.s…"   2 hours ago         Up 2 hours               0.0.0.0:7000-7001->7000-7001/tcp, 0.0.0.0:7199->7199/tcp, 0.0.0.0:9042->9042/tcp, 0.0.0.0:9160->9160/tcp   testconfig_aai.hbase.simpledemo.onap.org_1


Elasticsearch container error log

root@aai-vivek-01:/opt/test-config# docker logs 91f99c7b9769
Exception in thread "main" SettingsException[Failed to load settings from [elasticsearch.yml]]; nested: YAMLException[java.io.CharConversionException: Invalid UTF-8 start byte 0xa9 (at char #13, byte #-1)]; nested: CharConversionException[Invalid UTF-8 start byte 0xa9 (at char #13, byte #-1)];
at org.elasticsearch.common.settings.Settings$Builder.loadFromStream(Settings.java:1186)
at org.elasticsearch.common.settings.Settings$Builder.loadFromPath(Settings.java:1161)
at org.elasticsearch.node.InternalSettingsPreparer.prepareEnvironment(InternalSettingsPreparer.java:99)
at org.elasticsearch.cli.EnvironmentAwareCommand.createEnv(EnvironmentAwareCommand.java:95)
at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86)
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124)
at org.elasticsearch.cli.MultiCommand.execute(MultiCommand.java:75)
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124)
at org.elasticsearch.cli.Command.main(Command.java:90)
at org.elasticsearch.plugins.PluginCli.main(PluginCli.java:48)
Caused by: org.yaml.snakeyaml.error.YAMLException: java.io.CharConversionException: Invalid UTF-8 start byte 0xa9 (at char #13, byte #-1)
at org.yaml.snakeyaml.reader.StreamReader.update(StreamReader.java:200)
at org.yaml.snakeyaml.reader.StreamReader.<init>(StreamReader.java:60)
at com.fasterxml.jackson.dataformat.yaml.YAMLParser.<init>(YAMLParser.java:152)
at com.fasterxml.jackson.dataformat.yaml.YAMLFactory._createParser(YAMLFactory.java:420)
at com.fasterxml.jackson.dataformat.yaml.YAMLFactory.createParser(YAMLFactory.java:321)
at org.elasticsearch.common.xcontent.yaml.YamlXContent.createParser(YamlXContent.java:84)
at org.elasticsearch.common.settings.Settings$Builder.loadFromStream(Settings.java:1176)
... 9 more




On Wed, Jul 10, 2019 at 3:34 PM Vivekanandan Muthukrishnan via Lists.Onap.Org <vmuthukrishnan=aarnanetworks.com@...> wrote:
Hi AAI team,

I am trying to follow the below Wiki page to Docker setup AAI on a single VM and it failed.


Could someone clarify the following questions would be really helpful.

1. What is the following line means?  Should i change it to Dublin AAI version?
    
   echo "1.1-STAGING-latest" > /opt/config/docker_version.txt

2. The script deploy_vm1.sh has lot of Docker image versions define. Are these updated to the latest Dublin release? I see that Docker image version is referring to old releases.

Thanks & Regards
Vivek



Re: [MultiCloud][AAI] : about AAI updates by MultiCloud : is it implemented in Dublin release ?

Lukasz Rajewski
 

Yes, I confirm. We should also discuss asap on that how the data from the existing AAI data model should be mapped to the data model existing in K8s – if that was not done and reported already somewhere. I believe most profitable would be to reuse as much as possible of existing AAI data model to have some functionalities already developed in ONAP working also for K8S, i.e. OOF and HPA.

 

Regards,

 

Logo Orange

Łukasz Rajewski, R&D Expert
Orange Labs Poland, Advanced Network Systems Agency
Mob.: +48 519 310 854
Orange Polska, Obrzeżna 7, 02-691 Warsaw
www.orange.pl

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Srini
Sent: Thursday, July 11, 2019 4:41 PM
To: onap-discuss@...; Multanen, Eric W; ROBERT René TGI/OLN; bin.yang@...; Kamineni, Kiran K; Sood, Ritu
Subject: Re: [onap-discuss][MultiCloud][AAI] : about AAI updates by MultiCloud : is it implemented in Dublin release ?

 

AAI updates on the status of workload deployments in K8S based Cloud region support was not done yet in R4.  Kiran and Eric (copied here) plan is to get this gap fixed in R5.  BTW, This is also requested by Lukasz. 

 

There are two parts to it:

 

1.      Monitoring the remote resources for completeness/Ready,  after deployment is triggered by Multi-Cloud K8S plugin service.

2.      Updating A&AI

 

I tried to search for the JIRA stories. Could not get it.  I will let Kiran to share the JIRA stories. Any help from the community would be appreciated.

 

Thanks

Srini

 

 

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Multanen, Eric W
Sent: Thursday, July 11, 2019 7:27 AM
To: onap-discuss@...; rene.robert@...; bin.yang@...
Subject: Re: [onap-discuss][MultiCloud][AAI] : about AAI updates by MultiCloud : is it implemented in Dublin release ?

 

The SO multicloud plugin adapter in Dublin does make the POST call as described in the link during vfmodule creation.

The multicloud openstack plugin(s) does an AAI update with some information.  The multicloud K8S plugin does ‘not’ support it in Dublin.

This functionality has not been fully tested, etc.  – I don’t believe it handles updates, deletes and such.  It may not support all of the same

data that the heatbridge script supports.    So, it’s more of a PoC.

 

Note also – there has been some discussion about how the aai update should be done.  It became too much to handle in Dublin.

My notes on these discussions are captured here:  https://wiki.onap.org/pages/viewpage.action?pageId=58228881

 

Eric

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Rene Robert via Lists.Onap.Org
Sent: Thursday, July 11, 2019 5:08 AM
To: onap-discuss@...; bin.yang@...
Subject: [onap-discuss][MultiCloud][AAI] : about AAI updates by MultiCloud : is it implemented in Dublin release ?

 

Hello

 

There is that description in the documentation.

 

https://docs.onap.org/en/dublin/submodules/multicloud/framework.git/docs/specs/multicloud-heat-aai-bridge.html

 

Is it implemented in Dublin ?

 

 

Logo Orange

 

René Robert
«Open and Smart solutions for autOmating Network Services»
ORANGE/IMT/OLN/CNC/NARA/OSONS

 

Fixe : +33 2 96 07 39 29
Mobile : +33 6 74 78 68 43
rene.robert@...

 

 

 

_________________________________________________________________________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


Re: [MultiCloud] : about service/VNF instantiation on a K8S "cloud"

Lukasz Rajewski
 

Hi

 

I go over this process and I make some small corrections to the wiki page, so the readthedocs will have to be updated as well at the end.

 

Regards,

 

Logo Orange

Łukasz Rajewski, R&D Expert
Orange Labs Poland, Advanced Network Systems Agency
Mob.: +48 519 310 854
Orange Polska, Obrzeżna 7, 02-691 Warsaw
www.orange.pl

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Srini
Sent: Thursday, July 11, 2019 8:59 PM
To: onap-discuss@...; ROBERT René TGI/OLN; bin.yang@...
Subject: Re: [onap-discuss][MultiCloud] : about service/VNF instantiation on a K8S "cloud"

 

There is readthedocs page too.

 

Srini

 

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Rene Robert via Lists.Onap.Org
Sent: Thursday, July 11, 2019 5:35 AM
To: onap-discuss@...; bin.yang@...
Subject: [onap-discuss][MultiCloud] : about service/VNF instantiation on a K8S "cloud"

 

Hello

 

Can you confirm the procedure ? Is it working in Dublin Release ?

 

https://wiki.onap.org/display/DW/Deploying+vFw+and+EdgeXFoundry+Services+on+Kubernets+Cluster+with+ONAP

 

If yes, I will propose a contribution on ONAP readthedocs.

 

René

 

 

Logo Orange

 

René Robert
«Open and Smart solutions for autOmating Network Services»
ORANGE/IMT/OLN/CNC/NARA/OSONS

 

Fixe : +33 2 96 07 39 29
Mobile : +33 6 74 78 68 43
rene.robert@...

 

 

_________________________________________________________________________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


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

Keong Lim
 

Hi Thiriloshini,

I don't know if this will fix your problem, but when I recently tried to use the AAI UI, I also needed to update my hosts file with these additional names:

10.1.8.103 aaf-onap-test.osaaf.org
10.1.8.103 aai.ui.simpledemo.onap.org

Also, I needed to add a root certificate to my browsers so that the self-signed certificates did not cause any problems:
https://wiki.onap.org/download/attachments/64007235/onap_root.pem?api=v2

I tested across Firefox, Chrome and IE 11.

The HTTP port has been closed, so that error is expected.
The direct access to HTTPS is also expected to redirect to the Portal login page.

If you continue to have problems with the AAI UI, we will try to get Francis Paquette to help when he is back from holiday.

Keong


Re: ODP: [onap-discuss] [vLBMS] Create instance into VID fails

krzysztof.kurczewski@...
 

Hi Marco,


Could you provide more details for kubernetes setup?


Where this json is located? I found only few xml files on pod dev-sdnc-sdnc-0 and no trace of "check for VNF-API-preload and copy" action inside any of them.


GENERIC-RESOURCE-API_vf-module-topology-operation-assign-no-preload.xml
GENERIC-RESOURCE-API_vf-module-topology-operation-assign-preload.xml
GENERIC-RESOURCE-API_vf-module-topology-operation-assign.xml

Also, is there any related ticket?


From: onap-discuss@... <onap-discuss@...> on behalf of Marco Platania via Lists.Onap.Org <platania=research.att.com@...>
Sent: Monday, July 8, 2019 11:00:10 PM
To: onap-discuss@...; a.malinconico@...
Subject: Re: [onap-discuss] ODP: [onap-discuss] [vLBMS] Create instance into VID fails
 

Aniello,

 

Not sure you still have this issue, I just ran into it myself. To solve it, just import GENERIC-RESOURCE-API_vf-module-topology-operation-assign.json file into the SDNC DG builder, search for the node called call “check for VNF-API-preload and copy” and remove it.

 

Then, upload the modified DG and retry.

 

Thanks,

Marco

 

From: <onap-discuss@...> on behalf of Aniello Paolo Malinconico <a.malinconico@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "a.malinconico@..." <a.malinconico@...>
Date: Friday, July 5, 2019 at 9:04 AM
To: Aniello Paolo Malinconico <a.malinconico@...>, "onap-discuss@..." <onap-discuss@...>
Subject: Re: [onap-discuss] ODP: [onap-discuss] [vLBMS] Create instance into VID fails

 

More specific log is the file attached fromsdnc container.
Here the error extract:

2019-07-05 12:56:36,408 | INFO  | 1534955105-48303 | PropertiesNode                   | 240 - org.onap.ccsdk.sli.plugins.properties-node-provider - 0.4.4 | +++ prop.restapi.tx-allottedresource: [/restconf/config/GENERIC-RESOURCE-API:tunnelxconn-allotted-resources/tunnelxconn-allotted-resource/{allotted-resource-id}/]
2019-07-05 12:56:36,409 | INFO  | 1534955105-48303 | PropertiesNode                   | 240 - org.onap.ccsdk.sli.plugins.properties-node-provider - 0.4.4 | +++ prop.restapi.connection-oof-url: [
http://oof-osdf:8698/api/oof/v1/route]
2019-07-05 12:56:36,409 | INFO  | 1534955105-48303 | PropertiesNode                   | 240 - org.onap.ccsdk.sli.plugins.properties-node-provider - 0.4.4 | +++ prop.restapi.naming.gen-name.templatefile: [naming-ms-post-gen-name.json]
2019-07-05 12:56:36,410 | INFO  | 1534955105-48303 | SvcLogicServiceImplBase          | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | About to execute node # 3 (switch)
2019-07-05 12:56:36,411 | INFO  | 1534955105-48303 | SvcLogicServiceImplBase          | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | About to execute node # 4 (block)
2019-07-05 12:56:36,412 | INFO  | 1534955105-48303 | SvcLogicServiceImplBase          | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | About to execute node # 6 (switch)
2019-07-05 12:56:36,412 | INFO  | 1534955105-48303 | SvcLogicServiceImplBase          | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | About to execute node # 7 (block)
2019-07-05 12:56:36,413 | INFO  | 1534955105-48303 | SvcLogicServiceImplBase          | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | About to execute node # 9 (set)
2019-07-05 12:56:36,414 | INFO  | 1534955105-48303 | SvcLogicServiceImplBase          | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | About to execute node # 10 (switch)
2019-07-05 12:56:36,414 | INFO  | 1534955105-48303 | SvcLogicExprListener             | 227 - org.onap.ccsdk.sli.core.sli-common - 0.4.4 | Outcome (1) not found, keys are { ("") (Other)}
2019-07-05 12:56:36,415 | INFO  | 1534955105-48303 | SvcLogicServiceImplBase          | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | About to execute node # 12 (for)
2019-07-05 12:56:36,416 | INFO  | 1534955105-48303 | SvcLogicServiceImplBase          | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | About to execute node # 13 (switch)
2019-07-05 12:56:36,417 | INFO  | 1534955105-48303 | SvcLogicServiceImplBase          | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | About to execute node # 14 (block)
2019-07-05 12:56:36,417 | INFO  | 1534955105-48303 | SvcLogicServiceImplBase          | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | About to execute node # 15 (set)
2019-07-05 12:56:36,418 | INFO  | 1534955105-48303 | SvcLogicServiceImplBase          | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | About to execute node # 16 (break)
2019-07-05 12:56:36,419 | ERROR | 1534955105-48303 | ForNodeExecutor                  | 477 - wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar - 0.0.0 | ForNodeExecutor caught break
org.onap.ccsdk.sli.core.sli.BreakNodeException: BreakNodeExecutor encountered break with nodeId 16
at org.onap.ccsdk.sli.core.sli.provider.base.BreakNodeExecutor.execute(BreakNodeExecutor.java:39) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.executeNode(SvcLogicServiceImplBase.java:147) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.BlockNodeExecutor.execute(BlockNodeExecutor.java:62) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.executeNode(SvcLogicServiceImplBase.java:147) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.ForNodeExecutor.execute(ForNodeExecutor.java:94) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.executeNode(SvcLogicServiceImplBase.java:147) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.BlockNodeExecutor.execute(BlockNodeExecutor.java:62) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.executeNode(SvcLogicServiceImplBase.java:147) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.execute(SvcLogicServiceImplBase.java:117) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.CallNodeExecutor.execute(CallNodeExecutor.java:131) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.executeNode(SvcLogicServiceImplBase.java:147) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.BlockNodeExecutor.execute(BlockNodeExecutor.java:62) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.executeNode(SvcLogicServiceImplBase.java:147) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.base.SvcLogicServiceImplBase.execute(SvcLogicServiceImplBase.java:117) [477:wrap_file__opt_opendaylight_system_org_onap_ccsdk_sli_core_sli-provider-base_0.4.4_sli-provider-base-0.4.4.jar:0.0.0]
at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:112) [228:org.onap.ccsdk.sli.core.sli-provider:0.4.4]
at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:91) [228:org.onap.ccsdk.sli.core.sli-provider:0.4.4]
at Proxyb1891dae_ebe0_4112_bdd5_e6f953ee0921.execute(Unknown Source) [?:?]
at Proxye4076403_951d_4506_b1d2_30a529eb1eae.execute(Unknown Source) [?:?]
at org.onap.sdnc.northbound.GenericResourceApiSvcLogicServiceClient.execute(GenericResourceApiSvcLogicServiceClient.java:73) [245:org.onap.sdnc.northbound.generic-resource-api-provider:1.5.3.SNAPSHOT]
at org.onap.sdnc.northbound.GenericResourceApiProvider.tryGetProperties(GenericResourceApiProvider.java:764) [245:org.onap.sdnc.northbound.generic-resource-api-provider:1.5.3.SNAPSHOT]
at org.onap.sdnc.northbound.GenericResourceApiProvider.vfModuleTopologyOperation(GenericResourceApiProvider.java:1324) [245:org.onap.sdnc.northbound.generic-resource-api-provider:1.5.3.SNAPSHOT]


Re: #appc NETCONF/TLS in ODL #appc

francesca.vezzosi@...
 

Hi Patrick,

Thank you for your reply.
I am familiar with the page you found and it indeed works fine in SDNC, but it looks like in APPC the ODL commands listed at the bottom of the page are not implemented (I get the error in my first message when I try using the add-keystone-entry RPC).
The ODL version might be an explanation, but according to this JIRA entry APPC has already been upgraded with Fluorine SR2. Is this not correct? Do you have more information about that?

Regards,
Francesca


Re: [onap-tsc][onap-discuss] Onap Dublin offline platform released

Michal Ptacek
 

Added into agenda, I will join PTL call

 

Thanks Catherine,

 

Michal

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Catherine LEFEVRE
Sent: Thursday, July 11, 2019 9:28 PM
To: onap-tsc@...; onap-discuss@...
Subject: Re: [onap-tsc][onap-discuss] Onap Dublin offline platform released

 

Good evening Michal,

 

These are great information !

 

Would you be available on July 15th, 2019 to present your findings during the next PTL call?

If yes then please feel free to add this topic to the agenda

https://wiki.onap.org/display/DW/PTL+2019-07-15

 

Many thanks and regards

Catherine

 

From: onap-tsc@... [mailto:onap-tsc@...] On Behalf Of Michal Ptacek via Lists.Onap.Org
Sent: Thursday, July 11, 2019 3:07 PM
To: onap-tsc@...; onap-discuss@...
Subject: Re: [onap-tsc][onap-discuss] Onap Dublin offline platform released

 

Thanks Catherine, I collected some more detailed report about Dublin images (see attached)

 

Few suggestions regarding that:

 

  • Maybe we can decrease the size of images by using recommended base images, there is a nice page from Adolfo about that

https://wiki.onap.org/display/DW/ONAP+Normative+container+base+images

 

  • We are using different versions of base images even within single ONAP component (e.g. dcaegen2 -  docker.io/openjdk:11-jre-slim, openjdk:8-jre-alpine, openjdk:8-jre, java:8-jre)

https://wiki.onap.org/display/DW/Docker+images+dependency+list

 

  • Different components are using different versions of same image, which can be unified

(e.g oomk8s_readiness-check_2.0.0.tar, oomk8s_readiness-check_2.0.1.tar, oomk8s_readiness-check_2.0.2.tar)

 

I think those issues were already raised from CIA team but I am not sure if there is sufficient attention and capacity for improving that from projects,

 

Best regards,

Michal

 

From: onap-tsc@... <onap-tsc@...> On Behalf Of Catherine LEFEVRE
Sent: Wednesday, July 10, 2019 8:41 PM
To: onap-tsc@...; onap-discuss@...; m.ptacek@...
Subject: Re: [onap-tsc][onap-discuss] Onap Dublin offline platform released

 

Thank you Michal for your feedback. Great job !

 

I have asked the ONAP APPC Team to investigate about

2,9  G nexus3.onap.org_10001_onap_appc-image_1.5.3.tar

 

Best regards

Catherine

 

From: onap-tsc@... [mailto:onap-tsc@...] On Behalf Of VENKATESH KUMAR, VIJAY
Sent: Wednesday, July 10, 2019 6:19 PM
To: onap-tsc@...; onap-discuss@...; m.ptacek@...
Subject: Re: [onap-tsc][onap-discuss] Onap Dublin offline platform released

 

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Hello Michael,  Just to clarify, both dcaegen2* images are analytics modules dependent on external distribution.

 

org.onap.dcaegen2.deployments.tca-cdap-container uses caskdata/cdap-standalone:4.1.2 which is ~2GB

org.onap.dcaegen2.deployments.pnda-mirror-container sources several upstream pnda dependencies. The image size was indeed causing issue to incorporate into ONAP CI/CD flow hence maintained in external PNDA repo. Cisco team were looking to optimize this build; this also has dependency on upstream PNDA project.

 

Regards,

Vijay

From: onap-tsc@... <onap-tsc@...> On Behalf Of Michal Ptacek via Lists.Onap.Org
Sent: Wednesday, July 10, 2019 11:19 AM
To: onap-discuss@...; m.ptacek@...; onap-tsc@...
Subject: Re: [onap-tsc][onap-discuss] Onap Dublin offline platform released

 

I am sorry, need to correct winners for biggest images in Dublin contest …

 

Biggest 3 images in Dublin:

11,0 G pndareg.ctao6.net_onap_org.onap.dcaegen2.deployments.pnda-mirror-container_5.0.0.tar

2,9  G nexus3.onap.org_10001_onap_appc-image_1.5.3.tar

2,6  G nexus3.onap.org_10001_onap_org.onap.dcaegen2.deployments.tca-cdap-container_1.1.2.tar

 

Br,

M.

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Michal Ptacek via Lists.Onap.Org
Sent: Wednesday, July 10, 2019 3:58 PM
To: onap-tsc@...; onap-discuss@...
Subject: [onap-tsc][onap-discuss] Onap Dublin offline platform released

 

Hi All,

 

we have reached important milestone in offline deployments and created Dublin branch in oom/offline-installer repo to separate new efforts for El-Alto continuing in master,

 

couple of highlights:

- improvements in Dublin ONAP seen related to being able to work in offline lab (special thanks for Policy for offline friendly new Policy Framework)

- improvements in automatic datalist collecting (automatic parsing OOM for getting list of images for download)

- improvements in redesigned download procedure (faster & more reliable, newly in python3)

- vFWCL fully automated (thanks to AT&T guys)

 

All documents related to offline installer were updated

https://docs.onap.org/en/dublin/submodules/oom/offline-installer.git/docs/index.html

As of now we are still working on Centos 7.6 validation and adding CI pipeline to Orange Lab

 

If we compare Casablanca and Dublin offline platform, we have more images which are in total slightly smaller

but much bigger in blobs format (maybe we have more binary like code in images not shrinking too much to blob)

 

 

Casablanca

Dublin

Nr. of ONAP images

194

229

ONAP images size in tar format

110G

108G

ONAP images size in nexus blobs format

72G

97G

 

Biggest 3 images in Casablanca:

2,8 G nexus3.onap.org_10001_onap_appc-image_1.4.4.tar

2,6 G nexus3.onap.org_10001_onap_org.onap.dcaegen2.deployments.tca-cdap-container_1.1.0.tar

2,3 G nexus3.onap.org_10001_onap_org.onap.dcaegen2.deployments.cm-container_1.4.2.tar

 

Biggest 3 images in Dublin:

11,0 G nexus3.onap.org_10001_onap_org.onap.dcaegen2.deployments.tca-cdap-container_1.1.2.tar

2,9  G nexus3.onap.org_10001_onap_appc-image_1.5.3.tar

2,6  G pndareg.ctao6.net_onap_org.onap.dcaegen2.deployments.pnda-mirror-container_5.0.0.tar

 

Thanks to all involved,

Dublin is big leap forward for ONAP to works more easily offline,

Let’s see if we can finish that effort in El-Alto

 

On behalf of Samsung team,

Michal

 

 

 

 

 

 

  


APPC Cloud properties Ehnancement #configproperties #appc #casablanca

Paulo Duarte
 

Hi All,

I would like to edit the Cloud provider setup in appc.properties. I tried to enhance the appc.properties file that be found in the /opt/onap/appc/data/properties directory of appc container, but this file seems to read-only.
There are any way to configure the Cloud provider without a new deployment?

Note: Using Casablanca Release

Someone can help me?
Thanks,
Paulo


[AAI] Problem accessing AAI GUI from ONAP Portal

Thiriloshini.ThoppeKrishnakumar@us.fujitsu.com
 

Hi Jimmy/ Keong/ Harish,

 

I have a ONAP Dublin cluster which was deployed using OOM RKE Kubernetes.

I am able to access the ONAP Portal but I am unable to access the AAI GUI. Other GUI Applications like SDC, So-Monitoring work fine.

 

### All AAI pods are up and running.

 

### Please find the AAI Sparky service below

 

aai-sparky-be                   NodePort       10.43.107.114   <none>                  8000:30220/TCP                                                2d19h   app=aai-sparky-be,release=dev-aai

 

### I accessed the aai-sparky-be container and it was listening on port 8000.

 

root@dev-aai-aai-sparky-be-6495c4f754-cbh76:/# netstat -tunlp

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name

tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN      40/java

root@dev-aai-aai-sparky-be-6495c4f754-cbh76:/#

 

### Added the below contents in /etc/hosts

 

10.1.8.103 portal.api.simpledemo.onap.org

10.1.8.103 vid.api.simpledemo.onap.org

10.1.8.103 sdc.api.fe.simpledemo.onap.org

10.1.8.103 sdc.fe.simpledemo.onap.org

10.1.8.103 portal-sdk.simpledemo.onap.org

10.1.8.103 policy.api.simpledemo.onap.org

10.1.8.103 aai.api.sparky.simpledemo.onap.org

10.1.8.103 cli.api.simpledemo.onap.org

10.1.8.103 msb.api.discovery.simpledemo.onap.org

10.1.8.103 portal-app.onap

 

 

### When I try to open the AAI GUI from ONAP portal, it says “temporarily down or may have moved to  a new address”. Other GUIs like SDC, So-Monitoring work fine.

 

 

### I also tried to open AAI GUI from a new tab using the URL http://aai.api.sparky.simpledemo.onap.org:30220/services/aai/webapp/index.html and I get the below error.  When I try using https, it redirects me to the onap portal page.

 

 

 

 

 

I have used the same method in ONAP Casablanca and was able to access the AAI GUI.

Can you please let me know what am I missing or if something has changed in Dublin.

Please let me know if you need more information.

Any pointer is much appreciated.

 

 

Thanks,

Thiriloshini


Re: #appc NETCONF/TLS in ODL #appc

Patrick <patrick.brady@...>
 

I found this page which describes how to add the certificates for netconf TLS: https://onap.readthedocs.io/en/latest/submodules/sdnc/oam.git/docs/cert_installation.html

Also, I have been informed that netconf TLS support possibly was not added until SR2 version of OpenDaylight Fluorine. Appc is currently running on SR1 version, so this could be causing a problem.


Re: [onap-tsc][onap-discuss] Onap Dublin offline platform released

Catherine LEFEVRE
 

Good evening Michal,

 

These are great information !

 

Would you be available on July 15th, 2019 to present your findings during the next PTL call?

If yes then please feel free to add this topic to the agenda

https://wiki.onap.org/display/DW/PTL+2019-07-15

 

Many thanks and regards

Catherine

 

From: onap-tsc@... [mailto:onap-tsc@...] On Behalf Of Michal Ptacek via Lists.Onap.Org
Sent: Thursday, July 11, 2019 3:07 PM
To: onap-tsc@...; onap-discuss@...
Subject: Re: [onap-tsc][onap-discuss] Onap Dublin offline platform released

 

Thanks Catherine, I collected some more detailed report about Dublin images (see attached)

 

Few suggestions regarding that:

 

  • Maybe we can decrease the size of images by using recommended base images, there is a nice page from Adolfo about that

https://wiki.onap.org/display/DW/ONAP+Normative+container+base+images

 

  • We are using different versions of base images even within single ONAP component (e.g. dcaegen2 -  docker.io/openjdk:11-jre-slim, openjdk:8-jre-alpine, openjdk:8-jre, java:8-jre)

https://wiki.onap.org/display/DW/Docker+images+dependency+list

 

·        Different components are using different versions of same image, which can be unified

(e.g oomk8s_readiness-check_2.0.0.tar, oomk8s_readiness-check_2.0.1.tar, oomk8s_readiness-check_2.0.2.tar)

 

I think those issues were already raised from CIA team but I am not sure if there is sufficient attention and capacity for improving that from projects,

 

Best regards,

Michal

 

From: onap-tsc@... <onap-tsc@...> On Behalf Of Catherine LEFEVRE
Sent: Wednesday, July 10, 2019 8:41 PM
To: onap-tsc@...; onap-discuss@...; m.ptacek@...
Subject: Re: [onap-tsc][onap-discuss] Onap Dublin offline platform released

 

Thank you Michal for your feedback. Great job !

 

I have asked the ONAP APPC Team to investigate about

2,9  G nexus3.onap.org_10001_onap_appc-image_1.5.3.tar

 

Best regards

Catherine

 

From: onap-tsc@... [mailto:onap-tsc@...] On Behalf Of VENKATESH KUMAR, VIJAY
Sent: Wednesday, July 10, 2019 6:19 PM
To: onap-tsc@...; onap-discuss@...; m.ptacek@...
Subject: Re: [onap-tsc][onap-discuss] Onap Dublin offline platform released

 

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Hello Michael,  Just to clarify, both dcaegen2* images are analytics modules dependent on external distribution.

 

org.onap.dcaegen2.deployments.tca-cdap-container uses caskdata/cdap-standalone:4.1.2 which is ~2GB

org.onap.dcaegen2.deployments.pnda-mirror-container sources several upstream pnda dependencies. The image size was indeed causing issue to incorporate into ONAP CI/CD flow hence maintained in external PNDA repo. Cisco team were looking to optimize this build; this also has dependency on upstream PNDA project.

 

Regards,

Vijay

From: onap-tsc@... <onap-tsc@...> On Behalf Of Michal Ptacek via Lists.Onap.Org
Sent: Wednesday, July 10, 2019 11:19 AM
To: onap-discuss@...; m.ptacek@...; onap-tsc@...
Subject: Re: [onap-tsc][onap-discuss] Onap Dublin offline platform released

 

I am sorry, need to correct winners for biggest images in Dublin contest …

 

Biggest 3 images in Dublin:

11,0 G pndareg.ctao6.net_onap_org.onap.dcaegen2.deployments.pnda-mirror-container_5.0.0.tar

2,9  G nexus3.onap.org_10001_onap_appc-image_1.5.3.tar

2,6  G nexus3.onap.org_10001_onap_org.onap.dcaegen2.deployments.tca-cdap-container_1.1.2.tar

 

Br,

M.

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Michal Ptacek via Lists.Onap.Org
Sent: Wednesday, July 10, 2019 3:58 PM
To: onap-tsc@...; onap-discuss@...
Subject: [onap-tsc][onap-discuss] Onap Dublin offline platform released

 

Hi All,

 

we have reached important milestone in offline deployments and created Dublin branch in oom/offline-installer repo to separate new efforts for El-Alto continuing in master,

 

couple of highlights:

- improvements in Dublin ONAP seen related to being able to work in offline lab (special thanks for Policy for offline friendly new Policy Framework)

- improvements in automatic datalist collecting (automatic parsing OOM for getting list of images for download)

- improvements in redesigned download procedure (faster & more reliable, newly in python3)

- vFWCL fully automated (thanks to AT&T guys)

 

All documents related to offline installer were updated

https://docs.onap.org/en/dublin/submodules/oom/offline-installer.git/docs/index.html

As of now we are still working on Centos 7.6 validation and adding CI pipeline to Orange Lab

 

If we compare Casablanca and Dublin offline platform, we have more images which are in total slightly smaller

but much bigger in blobs format (maybe we have more binary like code in images not shrinking too much to blob)

 

 

Casablanca

Dublin

Nr. of ONAP images

194

229

ONAP images size in tar format

110G

108G

ONAP images size in nexus blobs format

72G

97G

 

Biggest 3 images in Casablanca:

2,8 G nexus3.onap.org_10001_onap_appc-image_1.4.4.tar

2,6 G nexus3.onap.org_10001_onap_org.onap.dcaegen2.deployments.tca-cdap-container_1.1.0.tar

2,3 G nexus3.onap.org_10001_onap_org.onap.dcaegen2.deployments.cm-container_1.4.2.tar

 

Biggest 3 images in Dublin:

11,0 G nexus3.onap.org_10001_onap_org.onap.dcaegen2.deployments.tca-cdap-container_1.1.2.tar

2,9  G nexus3.onap.org_10001_onap_appc-image_1.5.3.tar

2,6  G pndareg.ctao6.net_onap_org.onap.dcaegen2.deployments.pnda-mirror-container_5.0.0.tar

 

Thanks to all involved,

Dublin is big leap forward for ONAP to works more easily offline,

Let’s see if we can finish that effort in El-Alto

 

On behalf of Samsung team,

Michal

 

 

 

 

 

 

  


Re: #appc NETCONF/TLS in ODL #appc

Patrick <patrick.brady@...>
 

I believe OpenDaylight Fluorine, which is being used by Dublin version of Appc, should have support for TLS netconf. The netconf connector is a function of OpenDaylight itself, so the steps to use netconf over TLS should be the same as it is in any OpenDaylight deployment. Unfortunately, I have not had a chance to setup a TLS connection in OpenDaylight myself, so I'm not sure what the exact steps will look like.


Re: [MultiCloud] : about service/VNF instantiation on a K8S "cloud"

Srini
 

There is readthedocs page too.

 

Srini

 

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Rene Robert via Lists.Onap.Org
Sent: Thursday, July 11, 2019 5:35 AM
To: onap-discuss@...; bin.yang@...
Subject: [onap-discuss][MultiCloud] : about service/VNF instantiation on a K8S "cloud"

 

Hello

 

Can you confirm the procedure ? Is it working in Dublin Release ?

 

https://wiki.onap.org/display/DW/Deploying+vFw+and+EdgeXFoundry+Services+on+Kubernets+Cluster+with+ONAP

 

If yes, I will propose a contribution on ONAP readthedocs.

 

René

 

 

Logo Orange

 

René Robert
«Open and Smart solutions for autOmating Network Services»
ORANGE/IMT/OLN/CNC/NARA/OSONS

 

Fixe : +33 2 96 07 39 29
Mobile : +33 6 74 78 68 43
rene.robert@...

 

 

_________________________________________________________________________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


Re: Steps to Remove Deployment of ONAP

Manoj K Nair
 

Thanks Marco and Brian.

 

For the following step

kubectl delete namespace onap

Error from server (Conflict): Operation cannot be fulfilled on namespaces "onap": The system is ensuring all content is removed from this namespace.  Upon completion, this namespace will automatically be purged by the system.

 

I also had to do following to delete the namespace .

kubectl get namespace onap -o json > tmp.json

 

Removed kubernetes under finalizer block in tmp.json

 

kubectl proxy &

 

curl -k -H "Content-Type: application/json" -X PUT --data-binary @tmp.json http://localhost:8001/api/v1/namespaces/onap/finalize

 

Without the above steps onap namespace was not getting deleted

 

Regards

 

Manoj

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Marco Platania
Sent: Thursday, July 11, 2019 9:04 PM
To: onap-discuss@...; FREEMAN, BRIAN D <bf1936@...>; Manoj K Nair <manoj.k.nair@...>
Subject: Re: [onap-discuss] Steps to Remove Deployment of ONAP

 

Manoj,

 

Two small comments:

1.       ./cleanup.sh so (not dev-so, dev is added automatically by the script)

2.       This is what the script removes: secrets, configmaps, pvc, pv, services, deployments, statefulsets, clusterrolebinding

 

You can try to add job to that list and see what happens. If it works, it would be a nice thing to have.

 

The complete set of operations to delete a specific component is:

·         helm del --purge dev-<component_name>

·         rm -rf /dockerdata-nfs/dev-<component_name>/*

·         ./cleanup.sh <component_name>

 

The reason why we created the cleanup.sh script is because helm del --purge doesn’t always remove everything.

 

Thanks,

Marco

 

From: <onap-discuss@...> on behalf of BRIAN FREEMAN <bf1936@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, BRIAN FREEMAN <bf1936@...>
Date: Thursday, July 11, 2019 at 11:20 AM
To: "'onap-discuss@...'" <onap-discuss@...>, "'manoj.k.nair@...'" <manoj.k.nair@...>
Subject: Re: [onap-discuss] Steps to Remove Deployment of ONAP

 

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Sorry that is the script for an individual module

 

./cleanup.sh dev-so  for example.

 

Brian

 

 

From: FREEMAN, BRIAN D
Sent: Thursday, July 11, 2019 11:19 AM
To: onap-discuss@...; manoj.k.nair@...
Subject: RE: [onap-discuss] Steps to Remove Deployment of ONAP

 

I use this script (you have most of the steps) and then check jobs

 

[integration.git] / deployment / heat / onap-rke / scripts / cleanup.sh

 

Cd ...

./cleanup.sh

kubectl -n onap get jobs

kubectl -n onap delete job xxxx

 

(cleanup.sh might have been updated to handle jobs but I’m not sure )

 

Brian

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Manoj K Nair
Sent: Thursday, July 11, 2019 11:13 AM
To: onap-discuss@...
Subject: [onap-discuss] Steps to Remove Deployment of ONAP

 

Hi,

 

I would like to know is there is any recommended steps for removing a bad ONAP deployment (not individual projects, but whole ONAP that failed due to timing issues, sync issues etc).  I noted that in page here, following steps are mentioned

kubectl delete namespace onap

sudo helm delete --purge onap

kubectl delete pv --all

kubectl delete pvc --all

kubectl delete secrets --all

kubectl delete clusterrolebinding --all

sudo rm -rf /dockerdata-nfs/onap-<pod>

 

This used to work in Casablanca. But in Dublin it seems some additional steps are required like patching the finalizer for namespace/pv/pvc etc. Appreciate if someone can suggest the recommended steps for undeploy/redeploy ONAP in case of a failed installation attempt.

 

Regards

 

Manoj

 


The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.  

 


The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
 


Re: Steps to Remove Deployment of ONAP

Marco Platania
 

Manoj,

 

Two small comments:

1.       ./cleanup.sh so (not dev-so, dev is added automatically by the script)

2.       This is what the script removes: secrets, configmaps, pvc, pv, services, deployments, statefulsets, clusterrolebinding

 

You can try to add job to that list and see what happens. If it works, it would be a nice thing to have.

 

The complete set of operations to delete a specific component is:

·         helm del --purge dev-<component_name>

·         rm -rf /dockerdata-nfs/dev-<component_name>/*

·         ./cleanup.sh <component_name>

 

The reason why we created the cleanup.sh script is because helm del --purge doesn’t always remove everything.

 

Thanks,

Marco

 

From: <onap-discuss@...> on behalf of BRIAN FREEMAN <bf1936@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, BRIAN FREEMAN <bf1936@...>
Date: Thursday, July 11, 2019 at 11:20 AM
To: "'onap-discuss@...'" <onap-discuss@...>, "'manoj.k.nair@...'" <manoj.k.nair@...>
Subject: Re: [onap-discuss] Steps to Remove Deployment of ONAP

 

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.


Sorry that is the script for an individual module

 

./cleanup.sh dev-so  for example.

 

Brian

 

 

From: FREEMAN, BRIAN D
Sent: Thursday, July 11, 2019 11:19 AM
To: onap-discuss@...; manoj.k.nair@...
Subject: RE: [onap-discuss] Steps to Remove Deployment of ONAP

 

I use this script (you have most of the steps) and then check jobs

 

[integration.git] / deployment / heat / onap-rke / scripts / cleanup.sh

 

Cd ...

./cleanup.sh

kubectl -n onap get jobs

kubectl -n onap delete job xxxx

 

(cleanup.sh might have been updated to handle jobs but I’m not sure )

 

Brian

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Manoj K Nair
Sent: Thursday, July 11, 2019 11:13 AM
To: onap-discuss@...
Subject: [onap-discuss] Steps to Remove Deployment of ONAP

 

Hi,

 

I would like to know is there is any recommended steps for removing a bad ONAP deployment (not individual projects, but whole ONAP that failed due to timing issues, sync issues etc).  I noted that in page here, following steps are mentioned

kubectl delete namespace onap

sudo helm delete --purge onap

kubectl delete pv --all

kubectl delete pvc --all

kubectl delete secrets --all

kubectl delete clusterrolebinding --all

sudo rm -rf /dockerdata-nfs/onap-<pod>

 

This used to work in Casablanca. But in Dublin it seems some additional steps are required like patching the finalizer for namespace/pv/pvc etc. Appreciate if someone can suggest the recommended steps for undeploy/redeploy ONAP in case of a failed installation attempt.

 

Regards

 

Manoj

 


The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.  


Re: Steps to Remove Deployment of ONAP

Brian Freeman
 

Sorry that is the script for an individual module

 

./cleanup.sh dev-so  for example.

 

Brian

 

 

From: FREEMAN, BRIAN D
Sent: Thursday, July 11, 2019 11:19 AM
To: onap-discuss@...; manoj.k.nair@...
Subject: RE: [onap-discuss] Steps to Remove Deployment of ONAP

 

I use this script (you have most of the steps) and then check jobs

 

[integration.git] / deployment / heat / onap-rke / scripts / cleanup.sh

 

Cd ...

./cleanup.sh

kubectl -n onap get jobs

kubectl -n onap delete job xxxx

 

(cleanup.sh might have been updated to handle jobs but I’m not sure )

 

Brian

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Manoj K Nair
Sent: Thursday, July 11, 2019 11:13 AM
To: onap-discuss@...
Subject: [onap-discuss] Steps to Remove Deployment of ONAP

 

Hi,

 

I would like to know is there is any recommended steps for removing a bad ONAP deployment (not individual projects, but whole ONAP that failed due to timing issues, sync issues etc).  I noted that in page here, following steps are mentioned

kubectl delete namespace onap

sudo helm delete --purge onap

kubectl delete pv --all

kubectl delete pvc --all

kubectl delete secrets --all

kubectl delete clusterrolebinding --all

sudo rm -rf /dockerdata-nfs/onap-<pod>

 

This used to work in Casablanca. But in Dublin it seems some additional steps are required like patching the finalizer for namespace/pv/pvc etc. Appreciate if someone can suggest the recommended steps for undeploy/redeploy ONAP in case of a failed installation attempt.

 

Regards

 

Manoj

 


The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.  

4701 - 4720 of 22693