[onap-discuss] #dcaegen2 - ONS.EU - Interested in helping with the PNDA demo booth to showcase DCAE-PNDA integration?

Hi folks, at ONS Europe (next week, Sept/25-27), we'll have a small demo booth for PNDA - see https://events.linuxfoundation.org/events/open-networking-summit-europe-2018/features-and-add-ons/lf-networking-demos/ As part of that, we're planning to provide a glimpse at the integration of PNDA and

Re: [onap-discuss] [APPC] Problem accessing /jolokia/read/org.opendaylight.controller:type=DistributedConfigDatastore,Category=ShardManager,name=shard-manager-config.

Hello, Please find below the request passed via APPC swagger. { "appc-provider-lcm:input": { "appc-provider-lcm:common-header": { "appc-provider-lcm:timestamp": "2018-09-19T11:39:56.97Z" , "appc-provider-lcm:api-ver": "2.00", "appc-provider-lcm:originator-id": "originator-

Re: [onap-discuss] Memory and CPU limits for containers #oom

Hi Eric, You are right Eric, some of the values are too high and some of the ranges between small and large are not ideal. We are working right now to reduce some that we know are concerning. Great effort has been made to reach out and get accurate values for each component from the project te

[onap-discuss] [cia] OOF container image optimization

Dear CIA team members, As we agreed to last week, we will build the list of "ONAP Normative Base Images." We are using OOF as a test bed so we want to recommend an alpine image to minimize OOF container image footprint. Here are the Dockerfile(s) available in the OOF repo: - Optimization ser

[onap-discuss] [oom] Helm deploy plugin to address configmap limitation

To support the full deployment of ONAP in the Casablanca release, it is now necessary to use a Helm plugin that addresses the config map limitation of the parent ‘onap’ helm chart. It does this by deploying each subchart in its own Helm release. The initial version of the plugin is available fo

Re: [onap-discuss] Onap installation issue "Error: getting deployed release "dev": release: "dev" not found"

It’s unfortunate, but in order to deploy the Casablanca release of ONAP, it is now necessary to use a Helm plugin that addresses the config map limitation of the parent ‘onap’ helm chart. It does this by deploying each subchart in its own Helm release. The initial version of the plugin is avail

[onap-discuss] mvn35 is available in Jenkins

Dear ONAP team, This is just to let you know that Maven 3.5.4 is available in Jenkins and teams can move into this version if they do not want to use mvn33. Here is an example on how to input this change into your project's yaml file in ci-management: https://github.com/onap/ci-management/blob/ma

Re: [onap-discuss] Onap installation issue "Error: getting deployed release "dev": release: "dev" not found"

On Wed, Sep 19, 2018 at 07:04 AM, Brian wrote: > > configMap has exceeded the boundary I have the same issue on master. A possible workaround to avoid exceeding the configmap boundary is to delete all the component charts for the components that you do not want to deploy. Eric -=-=-=-=-=-=-=

Re: [onap-discuss] Replace single Karaf Feature in running APPC container #appc

I have noticed the same thing. Karaf does not seem very stable when uninstalling features. What I have found works is to stop and then restart karaf after the feature is uninstalled. From within the docker container, you want to run "/opt/opendaylight/bin/stop". Then once the docker container s

[onap-discuss] Memory and CPU limits for containers #oom

Hello When deploying the master branch, I noticed that most of components have now defined resources requirements in helm charts for 2 configurations: small and large. That is good to avoid containers to consume all the memory. But, I believe that the minimum values set are very high for a smal

[onap-discuss] Replace single Karaf Feature in running APPC container #appc

Hi all, We deployed APPC container in a Linux development environment and I try to rebuild a single APPC Karaf feature and replace the running version by the freshly compiled version in a running APPC container. When I try to stop any existing feature using "feature:stop ".  I get some errors

Re: [onap-discuss] [AAI] AAI containers in CrashLoopBackOff after OOM Rancher/Kubernetes installation

AAI is still looking/fixing those three - they are not needed for distribution Brian From: onap-discuss@lists.onap.org On Behalf Of George Clapp Sent: Wednesday, September 19, 2018 12:42 PM To: onap-discuss@lists.onap.org Subject: [onap-discuss] [AAI] AAI containers in CrashLoopBackOff after O

[onap-discuss] [AAI] AAI containers in CrashLoopBackOff after OOM Rancher/Kubernetes installation

I installed a set of ONAP components using OOM rancher/kubernetes, and some AAI containers have been in CrashLoopBackOff (please see the information below). I'd appreciate any suggestions on how to get them running. Thanks much, George _ %: kubectl get pods -o wide -n onap | g

Re: [onap-discuss] [PORTAL]: cannot log in after install

hi Hector here are steps i did. 1. before starting, result of "helm status portal-19s" .. ==> v1/Pod(related) NAME  READY  STATUS  RESTARTS  AGE portal-19s-portal-app-84b789fd9d-hvj9g    2/2    Running

[onap-discuss] Edge Automation Working Group focus for R4

Hi, I wanted to discuss today in edge automation working group. But, we ran out of time. We will discuss this next week. To give chance to review, sending this. In next meeting, let us review this and get understanding of R4 scope. -Original Appointment- From: ONAP Meetings and Event

Re: [onap-discuss] [onap-discussion]#vnfrqts#5G PnP: Updated Requirements

Hello, Ben Thanks for updating the text. A few more comments below in red. By the way, Steven has some additional comments on the Jira ticket page, which you may want to take into consideration as well. Have a nice day Zu Qiang From: Cheung, Ben (Nokia - US/Murray

Re: [onap-discuss] [onap-discussion]#vnfrqts#5G PnP: Updated Requirements

If someone would make the changes to the JIRA ticket, later today I’ll arrange for it to be pushed into RTD… If we still need some tweaks, we can make some smaller bug tickets… best regards Steven Wright, MBA, PhD, JD. [Tech Integration] AT&T Services Inc. 1057 Lenox Park Blvd NE, STE 4D28 Atlant

Re: [onap-discuss] [DOC] Request for Feedback - ReadTheDocs Theme Change & Report Issue JIRA Link

Thanks Rich The theme is cool and it is mobile friendly ;-) The report issue can help, but we must review the default Issue Type and Priority. Best regards Eric -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12520): https://lists.onap.org/g/on

Re: [onap-discuss] DCAE - Adding ML based network analytics

Thanks Vijay. Understood. We are moving away from CDAP to PNDA and Apache Flink as big data platform. As I understand from PNDA website, it seems to be based on Spark. Since Spark supports Machine learning analytics (via MLlib as well as Bring your own models), I think PNDA/Spark may be what we

Re: [onap-discuss] Why we need manual SDN-C preloading?

Tomek, The issue is how to assign the per instance data that can not part of the model that is used multiple times for instantiation. There are 3 mechanisms for setting that per instance data. 1. Preload to SDN-C where the instance specific hostnames , network information needed for the VN

Re: [onap-discuss] onap-sdnc-ansible-server cannot launch

Thank you Taka. Anyway, the issue seems to be at RestServer.py documented here:  https://jira.onap.org/browse/SDNC-439 Any workaround? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12517): https://lists.onap.org/g/onap-discuss/message/12517 Mute

Re: [onap-discuss] onap-sdnc-ansible-server cannot launch

Hi,  I'm facing the same problem, and i think it's python compatability issue, I've changed the startAnsibleServer.sh script and include [ "apt-get update", "apt-get -y install software-properties-common", "apt-add-repository -y ppa:ansible/ansible", "apt-get -y install ansible", "apt-get insta

Re: [onap-discuss] Onap installation issue "Error: getting deployed release "dev": release: "dev" not found"

The problem is with the last round of changes to project helm charts the configMap has exceeded the boundary. There is a change being tested to use a new approach for installation from the OOM team to use a per project release that solves the problem. Its a new deploy/undeploy plugin to helm. M

Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

You don’t need preload, you can simply pass the params into SO. It will still make a call to SDNC, but the data will just be sourced from the input. This flow is being tested in Casablanca now. Thanks -Steve From: on behalf of "Viswanath Kumar Skand Priya via Lists.Onap.Org" Reply-To: "o

Re: [onap-discuss] DCAE - Adding ML based network analytics

According to the PNDA Confluence page (see here: https://cwiki.pnda.io/display/public/PNDA/PDP-3%3A+Support+for+Flink) Flink is being integrated into PDNA (the Jira is marked as IN PROGRESS). Cheers, Roger From: on behalf of Vijay VK Reply-To: "onap-d

Re: [onap-discuss] [APPC] Problem accessing /jolokia/read/org.opendaylight.controller:type=DistributedConfigDatastore,Category=ShardManager,name=shard-manager-config.

Hi, What’s your request look like? Taka From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Viresh R Navalli Sent: Wednesday, September 19, 2018 7:35 AM To: onap-discuss@lists.onap.org Subject: [onap-discuss] [APPC] Problem accessing /jolokia/read/org.opendaylig

Re: [E] Re: [onap-discuss] Why we need manual SDN-C preloading?

Hi Brian / Rene / Steven, Thanks for the pointers. I understand the need for preload during deployment and that's exactly what VID is trying to achieve . My only comment is about the mandatory flow that exists between SO and SDN-C, inspite of ignoring SDN-C for a deployment. Runtime values could

Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

How I can pass these param sinto SO? Thanks, Tomek Logo Orange Tomasz Osiński, Główny Specjalista R&D Orange Labs Polska, Wydział Rozwoju Zaawansowanych Systemów Sieciowych Tel.: +48 50 130 06 88, Orange Polska, Obrzeżna 7, 02-691 Warszawa www.orange.pl From: SMOKOWSKI

Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

There were around 40 new bpmns in Casablanca behind that API, if you want a review please setup a discussion. Thanks -Steve From: "rene.rob...@orange.com" Date: Wednesday, September 19, 2018 at 8:31 AM To: "onap-discuss@lists.onap.org" , "SMOKOWSKI, STEVEN" , OSIŃSKI Tomasz O-PL , "viswanat

Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

Designer is not related to this. There is no need for a new BPMN as the BPMN already support this. Thanks -Steve From: on behalf of Tomek Reply-To: "onap-discuss@lists.onap.org" , "tomasz.osins...@orange.com" Date: Wednesday, September 19, 2018 at 8:35 AM To: ROBERT René IMT/OLN , "onap-

Re: [onap-discuss] onap-sdnc-ansible-server cannot launch

Hi, I don’t think that is a bug. If you look at the Dockerfile on gerrit: https://gerrit.onap.org/r/gitweb?p=ccsdk/distribution.git;a=blob;f=ansible-server/src/main/docker/Dockerfile;h=86b368c9fd62efa6c8afb33271b9401e0371d3a4;hb=HEAD Those apt packages should be installed. Maybe that is somethin

Re: [onap-discuss] Why we need manual SDN-C preloading?

Not sure. I usually test with the SDNC preload option. I suspect its only the .env parameters since the data is added to the parameter line in the stack create when they match .env parameters and ignored if not. SO might do other things with that data though. Brian From: Rajewski Łukasz - Korpo

Re: [onap-discuss] Why we need manual SDN-C preloading?

Thanks Brian, it explains a lot. regarding the option 2, this file contains only values of parameters specified in .env file for heat or there are some other ones required? Regards, [Logo Orange] Łukasz Rajewski, R&D Expert Orange Labs Polska, Advancend Networking Systems Agency, Warsaw Mobile

Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

Hi shouldn’t VID allow to specify values of this parameters in the moment of vf-module instance creation? Regards, [Logo Orange] Łukasz Rajewski, R&D Expert Orange Labs Polska, Advancend Networking Systems Agency, Warsaw Mobile: +48 519 310 854 Orange Polska, Obrzeżna 7, 02-691 Warszawa www.o

Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

I agree. Passing parameters via SO API and using VID UI to input these parameters would be satisfying enough. According to adding new BPMN workflows, I believe workflow designer is what will be used for that. https://wiki.onap.org/display/DW/Workflow+Designer Logo Orange Tomasz Osiński, Głów

Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

A new BPMN behind that API ? René De : onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] De la part de Steve Smokowski Envoyé : mercredi 19 septembre 2018 14:23 À : OSIŃSKI Tomasz O-PL; onap-discuss@lists.onap.org; viswanath.kumarskandpr...@verizon.com Cc : RAJEWSKI Lukasz O-PL O

Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

Hi Preload is about providing some Heat parameters value at instantiation time. Without preload, your Heat stack will use default values from your Heat templates coming from SDC (after distribution). For example, “image name” or “flavor name” are not the same from one VIM to another VIM. You a

Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

It should allow it on the newer GR-API Flow, I do believe VID has a toggle mechanism to perform this. The older VNF API flow does not support not using pre-load. Be aware the GR-API flow is still under test in Casablanca, and is yet to reach full stability. Here is a sample macro request wit

Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

I second this comment. We are also having same question and infact we even tried to bypass this SDN-C preload check but not successful so far. We modified BPMN file to skip the SDN-C interaction altogether, however SO's state is still stuck in "In Progess" state. IMHO SDN-C preload is optional ste

[onap-discuss] [APPC] Problem accessing /jolokia/read/org.opendaylight.controller:type=DistributedConfigDatastore,Category=ShardManager,name=shard-manager-config.

Hello Guys, Trying to run the Configure API via APPC swagger. The protocol used by VNF is ansible and rpc is DGOrchestrator. Getting the below error: Problem accessing /jolokia/read/org.opendaylight.controller:type=DistributedConfigDatastore,Category=ShardManager,name=shard-manager-config. Reas

[onap-discuss] Onap installation issue "Error: getting deployed release "dev": release: "dev" not found"

Hi We are facing strange issue during fresh installation of Casablance release. After "make all" and "helm install local/onap -n dev --namespace onap" we got following error: NAME: dev Error: getting deployed release "dev": release: "dev" not found After this error installation starts in ku

Re: [onap-discuss] onap-sdnc-ansible-server cannot launch

Hi all, *sdnc-ansible-server* has a *bug* reported here ( https://jira.onap.org/browse/SDNC-439 ) for Casablanca release. However, I think 2.0.0-ONAP and Beijing releases are experiencing the same issue. I tried what Abdelmuhaimen Seaudi suggested by updating the initial instructions to be exe

[onap-discuss] Why we need manual SDN-C preloading?

Hello, As in title, why we need manual SDN-C preloading in ONAP? We use and work with ONAP from Amsterdam release. It was surprising for us that there are some additional, manual steps needed to perform orchestration for any single VNF. We have currently ongoing development of Casablanca releas

Re: [onap-discuss][SO] : pending delete ?

Done ! Many thanks for the suggestion. René De : Kranthi Guttikonda [mailto:kranthi.guttiko...@b-yond.com] Envoyé : mardi 18 septembre 2018 18:44 À : onap-discuss@lists.onap.org; ROBERT René IMT/OLN; Seshu m (seshu.kuma...@huawei.com) Objet : Re: [onap-discuss][SO] : pending delete ? You could