Brian, Kang:
This issue appear when we running “vcpe,py customer” that is
"statusMessage": "Received error from SDN-C: Error updating md-sal for
tunnelxconn-allotted-resource”. Do you have any idea to check and resolve this
issue?
--
The process will be to mark the repository as ready only and disable all
Jenkins jobs (repo deletion may not be an option).
We are looking to onboard other analytics platform into DCAE (e.g PNDA and
Flink, both having some community interest) in coming releases. Depending on
how those
After doing the Helm install (Beijing branch) in my environment, I notice that
port 8080 (jboss) isn't exposed on the host network, although all the
Dockerfiles I've seen (and even elm) charts seem to expose it. Intentional?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this
Thanks Vijay, Tommy,
I found the cause of the build error though. I had installed "Erlang/OTP 21"
which has deprecated some APIs. Once I downgraded to "Erlang/OTP 20" the build
succeeded.
In any case, if the CDAP Broker is deprecated it would be best to delete the
repo
Badr, To check the collector status, you can ssh into onap-dcae vm and verify
docker logs or (within container - /opt/app/VESCollector/logs). Please let me
know if you see any errors.
Regards,
Vijay
From: onap-discuss@lists.onap.org On Behalf Of
PLATANIA, MARCO
Sent: Monday, July 16, 2018
+ Vijay for the VES collector part.
Marco
From: Badr Eddine Aouled Yahia
Date: Monday, July 16, 2018 at 12:41 PM
To: "PLATANIA, MARCO (MARCO)"
Cc: "onap-discuss@lists.onap.org"
Subject: Re: [onap-discuss] vFwcl: no mesurements published to dmaap
It is heat based and i use the right ip and
Arun,
It should be possible to build the image using the master template and script
(i.e. the fix that was merged last week).
Then deploy the image with the Beijing release heat template.
Enyinna is going to run through that sequence and see if there are any issues.
Eric
From:
It is heat based and i use the right ip and port.
Could it be the ves collector the origin of the problem?
Any thing to check?
Thanks.
Badr Eddine AY
Le lun. 16 juil. 2018 à 18:35, PLATANIA, MARCO (MARCO) <
plata...@research.att.com> a écrit :
> Are you using Heat or OOM to install ONAP? IP
Are you using Heat or OOM to install ONAP? IP 10.0.4.1 and port 8081 are used
for Heat only. For OOM you can use any IP address in the K8S cluster and port
30235.
Marco
From: Badr Eddine Aouled Yahia
Date: Monday, July 16, 2018 at 12:22 PM
To: "PLATANIA, MARCO (MARCO)"
Cc:
{
"vnf-parameter-name": "repo_url_blob",
"vnf-parameter-value": "https://nexus.onap.org/content/sites/raw;
},
{
"vnf-parameter-name": "repo_url_artifacts",
"vnf-parameter-value": "https://nexus.onap.org/content/repositories/releases
"
},
{
"vnf-parameter-name": "demo_artifacts_version",
Is the VES agent running in the vFW VM? What parameters did you use for
demo_artifacts_version and install_script_version in the Heat env file or SDNC
preload for the vFW installation?
Marco
From: on behalf of "A. Yahia Badr Eddine"
Reply-To: "onap-discuss@lists.onap.org" ,
Hello community,
I am running the vfwcl usecase. The vfw service is deployed and works
correctly. But, i noticed that no mesurements or events were published to
dmaap. I analysed traffic on the vfw machine, no payload in the tcp packet
being sent to dcae (mvp) 8081 port.
could anyone help me
Hi we have dedicated meeting tomorrow after the modeling call to discuss all of
this this should be presented there.
BR,
[Michael Lando]
AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
Hi Eric,
I am using the Beijing release.
By the time this issue fixes do you have any localized patch or any other
branch which does not have the issue?
Best Regards,
Arun Arora
From: Multanen, Eric W
Sent: Monday, July 16, 9:15 PM
Subject: Re: [onap-discuss] vCPE R2: VGMux pre-built image
Hi Eric,
Would you please take a look? Thanks.
Regards,
Kang
From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Monday, July 16, 2018 4:14
To: Kang Xi ; onap-discuss@lists.onap.org
Subject: vCPE R2: VGMux pre-built image step fails with error in build script
execution
Hi Kang, ONAP
Hi Sudhakar,
The prefix – “DCAE.Config_” is used in Policy Handler to filter the policies
applicable for DCAE components. This is set as configuration into
policy-handler during startup and expectation for policies created (from
clamp/policy) are to set under same prefix (for policies being
Hi Deepak,
I ran in to same issue. The deployment works fine sometimes and sometimes I get
this error and helm ls shows the status as Failed.
Are you able to figure out the cause for this behaviour? I'm using a 5-node
cluster with 112GB RAM each.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all
Hi all,
Because many usual participants need to attend the PTL call today (which is at
the same time slot as the resource IM call), the call for resource IM interest
group is postponed to Wednesday. The time is the same as our usual call.
The current agenda includes discussion on the run time
I will check in CDAP cluster for more logs.
>> Also deployment for DCAE R2 has changed significantly (under heat and
OOM); DCAE is using CDAP sdk container to deploy TCA application.
.
Thanks for the link provided, Venkatesh!
Best Regards
Bharath T
On Wed, Jul 11, 2018 at 5:16 AM VENKATESH
19 matches
Mail list logo
