Date   

Re: [logging-analytics] POMBA Merge request - non-author code review field not populating correctly after +2 - fixed was in draft

Michael O'Brien <frank.obrien@...>
 

Team, 

   Never mind – I didn’t notice that the review was in draft – the merge button now shows and was submitted

   Thank you

   /michael

 

From: Michael O'Brien
Sent: Tuesday, July 17, 2018 10:11 AM
To: Jennie Jia <Jennie.Jia@...>; Gildas Lanilis <gildas.lanilis@...>
Cc: onap-discuss@...; 'helpdesk@...' <helpdesk@...>
Subject: RE: [logging-analytics] POMBA Merge request - non-author code review field not populating correctly after +2

 

Jessica, Gildas,

   Is there anything we are missing – I don’t see the normal “submit” button because the non-author commit check is blocking it

   /michael

 

Yes, looks like an issue – the “non-author code review” should have been populated when one of us did a +2 – I even hit the verify (can’t actually verify the partial seed code until we get a runnable skeleton and docker builds going) – didn’t populate the field

 

Asking the LF.

/michael

 

From: Luke Parker
Sent: Monday, July 16, 2018 11:48 PM
To: Prudence Au <Prudence.Au@...>; Michael O'Brien <Frank.Obrien@...>; Luke Parker <lparker@...>; Avdhut Kholkar <avdhut.kholkar@...>; lb7179@...
Subject: Re: [logging-analytics] POMBA Merge request

 

+2d, but I don't get the option to merge. The gerrit configuration is a little different to ours, so I can't remember exactly what it normally offers, and this is the only review currently pending, so I can't cross-check. Anybody else?

Thanks,
Luke

On 17/07/18 04:20, Prudence Au wrote:

Hi logging-analytics committers,
 
For tomorrow's meeting, I would like to bring to your attention for the following code review.  This is the pojo repo needed for other POMBA components.  The POMBA team would like to have it merged so that we can continue on with other work.
 
https://gerrit.onap.org/r/#/c/56223/7
 
Thanks in advance.
 
Cheers,
Prudence
 
Prudence Au
Software Development Manager
Data Experience
 
251455038 (office - internal)
613-595-5038 (office - external)
613-327-7646 (mobile)
 
[amdocs-a]
 
Read the latest on Amdocs.com<http://www.amdocs.com/> and the Amdocs blog network<http://blogs.amdocs.com/> - and follow us on Facebook<http://www.facebook.com/Amdocs>, Twitter<http://twitter.com/Amdocs>, LinkedIn<http://www.linkedin.com/company/amdocs> and YouTube<http://www.youtube.com/amdocs>.
 
 
 

 

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,


Re: [logging-analytics] POMBA Merge request - non-author code review field not populating correctly after +2

Michael O'Brien <frank.obrien@...>
 

Jessica, Gildas,

   Is there anything we are missing – I don’t see the normal “submit” button because the non-author commit check is blocking it

   /michael

 

Yes, looks like an issue – the “non-author code review” should have been populated when one of us did a +2 – I even hit the verify (can’t actually verify the partial seed code until we get a runnable skeleton and docker builds going) – didn’t populate the field

 

Asking the LF.

/michael

 

From: Luke Parker
Sent: Monday, July 16, 2018 11:48 PM
To: Prudence Au <Prudence.Au@...>; Michael O'Brien <Frank.Obrien@...>; Luke Parker <lparker@...>; Avdhut Kholkar <avdhut.kholkar@...>; lb7179@...
Subject: Re: [logging-analytics] POMBA Merge request

 

+2d, but I don't get the option to merge. The gerrit configuration is a little different to ours, so I can't remember exactly what it normally offers, and this is the only review currently pending, so I can't cross-check. Anybody else?

Thanks,
Luke


On 17/07/18 04:20, Prudence Au wrote:

Hi logging-analytics committers,
 
For tomorrow's meeting, I would like to bring to your attention for the following code review.  This is the pojo repo needed for other POMBA components.  The POMBA team would like to have it merged so that we can continue on with other work.
 
https://gerrit.onap.org/r/#/c/56223/7
 
Thanks in advance.
 
Cheers,
Prudence
 
Prudence Au
Software Development Manager
Data Experience
 
251455038 (office - internal)
613-595-5038 (office - external)
613-327-7646 (mobile)
 
[amdocs-a]
 
Read the latest on Amdocs.com<http://www.amdocs.com/> and the Amdocs blog network<http://blogs.amdocs.com/> - and follow us on Facebook<http://www.facebook.com/Amdocs>, Twitter<http://twitter.com/Amdocs>, LinkedIn<http://www.linkedin.com/company/amdocs> and YouTube<http://www.youtube.com/amdocs>.
 
 
 

 

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,


Re: DCAE Build Error: dcaegen2/platform/cdapbroker ?

Arash Hekmat <arash.hekmat@...>
 

Makes sense. Thanks Vijay and Tommy.

 

Arash

 

From: VENKATESH KUMAR, VIJAY <vv770d@...>
Sent: Monday, July 16, 2018 7:44 PM
To: CARPENTER, TOMMY J <tommy@...>; Arash Hekmat <Arash.Hekmat@...>
Cc: onap-discuss@...
Subject: RE: DCAE Build Error: dcaegen2/platform/cdapbroker ?

 

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 integration comes along, CDAP can be deprecated.

 

Regards,

Vijay.

 

From: CARPENTER, TOMMY J
Sent: Monday, July 16, 2018 7:19 PM
To: HEKMAT, ARASH <arash.hekmat@...>
Cc: VENKATESH KUMAR, VIJAY <vv770d@...>; onap-discuss@...
Subject: Re: DCAE Build Error: dcaegen2/platform/cdapbroker ?

 

I had thought there was a formal process to deprecate something, rather than just deleting a repo, and perhaps that this had to be approved by the TSC. There are two other code sources in DCAE relating to this; the CDAP plugin, as well as the CDAP deployment blueprints. Formally removing CDAP would mean deleting all such code. 


On Jul 16, 2018, at 7:12 PM, HEKMAT, ARASH <arash.hekmat@...> wrote:

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 dcaegen2/platform/cdapbroker from ONAP Gerrit.

 

Thanks,

Arash

 

From: CARPENTER, TOMMY J (TOMMY J) <tommy@...>
Sent: Friday, July 13, 2018 5:41 PM
To: VENKATESH KUMAR, VIJAY <vv770d@...>
Cc: onap-discuss@...; Arash Hekmat <Arash.Hekmat@...>
Subject: Re: DCAE Build Error: dcaegen2/platform/cdapbroker ?

 

Yes the CDAP Broker is not a released or built artifact in R2+. I don’t know what the formal deprecation process is, but consider it deprecated since R1. Probably many things in it are out of date including its compatibility with CDAP. 


On Jul 13, 2018, at 5:35 PM, VENKATESH KUMAR, VIJAY <vv770d@...> wrote:

Hi Arash,

   Just FYI, the R2 deployment of DCAE does not include CDAP and hence CDAP broker was not deployed either (this may be deprecated in later releases).

 

CDAP Broker code is largely un-modified since R1; looking through the build report – seems normal and latest build was successful.

 

Suspect if local setup issue; looping Tommy who could give some pointers.

 

Regards,

Vijay

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of HEKMAT, ARASH
Sent: Friday, July 13, 2018 4:29 PM
To: onap-discuss@...
Subject: [onap-discuss] DCAE Build Error: dcaegen2/platform/cdapbroker ?

 

Hi DCAE team,

 

All of a sudden, I am getting this error when building dcaegen2/platform/cdapbroker. This is supposed to be a warning but in this case it’s turned into an error.

The reason seems to be that an old version of rebar executable (rebar 2.5.1) is pulled into dcaegen2/platform/cdapbroker/_build/default/lib/meck.

And also, in file dcaegen2/platform/cdapbroker/_build/default/lib/meck/rebar.config the compile flag “warnings_as_errors” is set.

I can remove this flag “warnings_as_errors” but I’d rather not touch this file because the whole “_build” subtree is pulled in at build time.

 

Any idea how to resolve this?

 

I have rebar3 & OTP 21 installed: rebar 3.5.0 on Erlang/OTP 21 Erts 10.0

 

Thanks,

Arash

 


===> Compiling cowboy

_build/default/lib/cowboy/src/cowboy_handler.erl:97: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

_build/default/lib/cowboy/src/cowboy_handler.erl:128: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

_build/default/lib/cowboy/src/cowboy_handler.erl:255: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

_build/default/lib/cowboy/src/cowboy_handler.erl:296: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

 

_build/default/lib/cowboy/src/cowboy_rest.erl:81: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

_build/default/lib/cowboy/src/cowboy_rest.erl:1010: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

 

_build/default/lib/cowboy/src/cowboy_websocket.erl:174: Warning: call to crypto:sha/1 will fail, since it was removed in 20.0; use crypto:hash/2

 

===> Compiling leptus

_build/default/lib/leptus/src/leptus_handler.erl:560: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

 

_build/default/lib/leptus/src/leptus_utils.erl:147: Warning: variable 'Rest' is unused

 

_build/default/lib/leptus/src/leptus.erl:289: Warning: erlang:now/0: Deprecated BIF. See the "Time and Time Correction in Erlang" chapter of the ERTS User's Guide for more information.

 

===> Compiling meck

===> Compiling _build/default/lib/meck/src/meck_code_gen.erl failed

_build/default/lib/meck/src/meck_code_gen.erl:198: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

 

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 51.604 s

[INFO] Finished at: 2018-07-13T15:38:19-04:00

[INFO] Final Memory: 25M/290M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile script) on project cdapbroker: Command execution failed.: Process exited with an error: 1 (Exit value: 1) -> [Help 1]

[ERROR]

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException


 

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,


Re: [CLAMP] "java.security.Principal;"

Martial
 

Hi Jonathan,

 

Yes, we are using Servlets, let’s try your suggestion and see if it works.

It seems Xue tried that already but was not able to get everything but she is going to try again and come back to you if there is issues.

 

Thanks,

Martial

 

From: GATHMAN, JONATHAN C
Sent: mardi 17 juillet 2018 15:00
To: Ngueko, Gervais-Martial <gn422w@...>; onap-discuss@...
Cc: O'KEEFE, TIMOTHY J <to1982@...>; MCCRAY, CHRISTOPHER <cm6826@...>
Subject: Re: [AAF][CLAMP] is "java.security.Principal;"

 

Greetings,

  Are you writing via Servlets?

 

  If so, then the Principal involved in the Transaction is available on the ‘HttpServletRequest’… getUserPrincipal(), I believe.

 

-- 

Jonathan Gathman

Principled-System Architect

ATO Tech Dev/SEAT/Platform Architecture and Technology Management

 

AT&T Services, Inc.

2349 Oaker, Arnold, MO 63010

m  314-550-3312  |  jonathan.gathman@...

 

 

From: "NGUEKO, GERVAIS-MARTIAL" <gn422w@...>
Date: Tuesday, July 17, 2018 at 7:13 AM
To: "onap-discuss@..." <onap-discuss@...>, "GATHMAN, JONATHAN C" <jg1555@...>
Cc: "O'KEEFE, TIMOTHY J" <to1982@...>, "MCCRAY, CHRISTOPHER" <cm6826@...>
Subject: [AAF][CLAMP] is "java.security.Principal;"

 

Hello AAF team,

 

Do you know of a way to retrieve the ”java.security.Principal; “ without using the jaxrs library “javax.ws.rs.core.SecurityContext;”

As you know, Due to security issue we need to go away from using the jaxrs package. Currently we are using the code:

Principal p = securityContext.getUserPrincipal();

 

So does someone know another library with no security issue to achieve the same result?

 

BR

 

Gervais-Martial Ngueko
CLAMP PTL

 


VVP PTL Election results

WRIGHT, STEVEN A
 

Steven Wright elected as PTL for VVP project. Election results available on the project organization wiki page.

 

best regards
Steven Wright, MBA, PhD, JD.

Tech Integration

AT&T Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319

 


[vnfrqts] PTL Election results

WRIGHT, STEVEN A
 

Steven Wright elected as PTL for VNFRQTS project. Poll results available on the Project organization wiki page.

 

best regards
Steven Wright, MBA, PhD, JD.

Tech Integration

AT&T Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319

 


jira.onap.org still timing out during early am EST

Pamela Dragosh
 

Jessica,

 

Sorry – but I’m trying to get a new sprint organized today and I can’t even look at JIRA’s because the system keeps timing out on me. Can someone please look into the logs and see what the problem is??

 

Thanks,

 

Pam


[AAF][CLAMP] is "java.security.Principal;"

Martial
 

Hello AAF team,

 

Do you know of a way to retrieve the ”java.security.Principal; “ without using the jaxrs library “javax.ws.rs.core.SecurityContext;”

As you know, Due to security issue we need to go away from using the jaxrs package. Currently we are using the code:

Principal p = securityContext.getUserPrincipal();

 

So does someone know another library with no security issue to achieve the same result?

 

BR

 

Gervais-Martial Ngueko
CLAMP PTL

 


Re: [modeling] High level requirement reviewed by PTLs and SDC

denghui (L)
 

Hello owners of requirements,

 

Thanks PTL meeting time and theirs kind comments, we have moved 3+5 out of high level requirement into other table.

For the left of those requirements, please help to join the dedicated discussion today with SDC after modeling subcommittee call

 

From yesterday, PTL and TSC has strong concern about modeling requirement bring additional work besides of M1 requirement.

Please each owner identify with impacted PTL, whether your requirement in the scope of M1 of that impact projects,

if not, that requirement will also have to be moved into lower priority for future release other than R3.

 

As SDC suggested in the list, each of owner, please help to prepare and explain your requirement

 

Thanks a lot

 

DENG Hui

 

 

From: denghui (L)
Sent: Monday, July 16, 2018 4:46 PM
To: onap-discuss@...; ONAP-TSC@...
Cc: 'Lando,Michael' <ml636r@...>; 'anatoly.katzman@...' <anatoly.katzman@...>
Subject: [modeling] High level requirement reviewed by PTLs and SDC

 

Hello, owners of requirements

 

I have sent you a private email last week about today PTL’s meeting that you will kindly help to explain your proposed high requirement to PTLs,

whether impacted PTLs agree it and allocate the implementation resource to support it

If impacted PTLs agree, this requirement will stay in R3 high level requirement, otherwise, it will move to lower priority category.

 

Since there are so many high level requirements related to SDC, if today PTL session time is not enough,

SDC PTLs could help to discuss it on Tuesday again right after modeling subcommittee call, we can use the same bridge of modeling subcommittee on Tuesday.

 

Thanks a lot for your attendance

Best regards,

 

DENG Hui


Re: VID : Distributed Services not displayed

Ofir Sonsino <os0695@...>
 

Hi Manoj,

 

VID actually pulls the distributed services from AAI, not SDC, with a different API then the one you mentioned.

Can you please run the following and share the result:

curl -X PUT 'https://AAI_IP:8443/aai/v13/query?format=resource' -H 'authorization: Basic VklEOlZJRA==' -H 'cache-control: no-cache' -H 'content-type: application/json' -H 'x-fromappid: VidAaiController' -H 'x-transactionid: bd6e812a-dad2-481f-aaaa-c36cec2f8494' -d '{"start" : "service-design-and-creation/models/", "query" : "query/serviceModels-byDistributionStatus?distributionStatus=DISTRIBUTION_COMPLETE_OK"}' -k

 

Also please supply further information as described in this comment with a similar issue:

https://jira.onap.org/browse/VID-245?focusedCommentId=24397&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-24397

Along with other log files (debug.log, application.log)

 

Thanks,

Ofir

 

From: Manoj K Nair [mailto:manoj.k.nair@...]
Sent: Monday, July 16, 2018 8:51 PM
To: Sonsino, Ofir <os0695@...>
Subject: VID : Distributed Services not displayed

 

Hi Ofir,

 

We installed ONAP Beijing using Heat Orchestration and currently trying to verify vFW Service onboarding , instantiation. We are not able to retrieve the distributed services from SDC Catalog and on clicking “Browse SDC Service Models” we are getting an empty response. I am attaching the vid_error.log . Additionally we verified that SDC Catalog has the entry as below and A&AI also has entries for the service .  Appreciate if you can let us know how to fix this issue. We are using VID artifact version – 1.3.0-SNAPSHOT and docker version – 2.0.0

 

ubuntu@onap-vid:/opt/config$ sudo docker ps

CONTAINER ID        IMAGE                                  COMMAND                  CREATED             STATUS              PORTS                    NAMES

2f03712e87fa        nexus3.onap.org:10001/onap/vid:2.0.0   "/tmp/vid/localize.sh"   3 hours ago         Up 3 hours          0.0.0.0:8080->8080/tcp   vid-server

cc52f39a5a9f        mariadb:10                             "docker-entrypoint..."   3 hours ago         Up 3 hours          3306/tcp                 vid-mariadb

ubuntu@onap-vid:/opt/config$

 

 

 

 

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.  


vCPE deployment on new cloud region and tenant

A. Yahia Badr Eddine
 

Hello,

I am performing steps as described in this tutorial to run the vCPE demo.
https://wiki.onap.org/display/DW/vCPE+Use+Case+Tutorial%3A+Design+and+Deploy+based+on+ONAP

I have already designed and distributed vcpe services and now i want to deploy it on a second RegionTwo and tenant2.

How should I modify this json in the vcpecommon.py and which region information should i put ?
Is there any changes in the other scripts in my case?

cloud = {
    '--os-auth-url': 'http://10.12.25.2:5000',
    '--os-username': 'kxi',
    '--os-user-domain-id': 'default',
    '--os-project-domain-id': 'default',
    '--os-tenant-id': '087050388b204c73a3e418dd2c1fe30b',
    '--os-region-name': 'RegionOne',
    '--os-password': 'yourpassword',
    '--os-project-domain-name': 'Integration-SB-01',
    '--os-identity-api-version': '3'
}
 
common_preload_config = {
    'oam_onap_net': 'oam_onap_oTA1',
    'oam_onap_subnet': 'oam_onap_oTA1',
    'public_net': 'external',
    'public_net_id': '971040b2-7059-49dc-b220-4fab50cb2ad4'
}

Thanks,

Badr Eddine AY.


Re: Working demo ?

Antti Salmi <a.salmi@...>
 

Hello,

I would also like to know the answers to those questions which Lars rised, especially the second one regarding the link between marketplace and SDC.

BR,
Antti Salmi


Re: [OOM] SO port(s) not exposed #so #oom

Borislav Glozman
 

It is not supposed to be exposed on host network. NodePort is exposed.

 

Thanks,

Borislav Glozman

O:+972.9.776.1988

M:+972.52.2835726

amdocs-a

Amdocs a Platinum member of ONAP

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of DeWayne Filppi
Sent: Tuesday, July 17, 2018 1:55 AM
To: onap-discuss@...
Subject: [onap-discuss] [OOM] SO port(s) not exposed #oom #so

 

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?

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,


[MSB] Please Vote on MSB Weekly Meeting Time Slot-Doodle Poll

Huabing Zhao <zhaohuabing@...>
 

Dear ONAPer,

Given that many guys have shown interest in the Istio service mesh integration, we'd better change the current MSB weekly meeting time to allow them to participate.

Please choose your available time at this doodle poll: https://doodle.com/poll/6uffdebvqpw6a63y

Thanks,
Huabing Zhao


[onap-tsc][integration] PTL Election for Integration - Result

Helen Chen
 

Dear ONAP TSC,

 

Based on the process of annual community elections for PTL described on https://wiki.onap.org/display/DW/Annual+Community+Elections, here’s the voting result for Integration project:

 

I have updated the Voting Results History page: https://wiki.onap.org/display/DW/Voting+Results+History . Thank you for your support!

 

Regards,

 

Helen Chen

 

From: Helen Chen 00725961 <Helen.Chen@...>
Date: Monday, July 9, 2018 at 5:31 PM
To: onap-discuss <onap-discuss@...>, onap-tsc <onap-tsc@...>
Subject: [onap-discuss][onap-tsc][integration] PTL Election for Integration

 

Dear ONAP Integration Committers,

  

As mandated by ONAP process, PTL elections must be held at least once a year.   You can read more details here: https://wiki.onap.org/display/DW/Annual+Community+Elections

 

If you are interested in the Integration PTL position.  Please reply to all to do self-nomination.

 

We will close the self-nomination window by 23:59 PDT July 11th, Wednesday, 2018.  Further instructions will be sent out to the committers on the election procedure.  The final result will be announced on the ONAP lists before the end of this week.

 

Regards,

Helen Chen


Re: [integration] create another vgw instance error

Liu Chenglong
 

Brian, Kang:
        There are some error information as blow when we running ‘vcpe.py customer':      
              "requestId": "91541b2a-cfd3-4e4d-aa4f-89ff2e2e995f",
              "requestScope": "service",
              "requestStatus": {
            "finishTime": "Tue, 17 Jul 2018 00:58:47 GMT",
            "percentProgress": 100,
            "requestState": "FAILED",
            "statusMessage": "Received error from SDN-C: Error updating md-sal for tunnelxconn-allotted-resource"
              },
             "requestType": "createInstance",
             "startTime": "Tue, 17 Jul 2018 00:58:07 GMT"

        So, we check sdnc sdnc_controller_container docker log file that is /opt/opendaylight/current/data/log/karaf.log, we found there are some error in log file. 
        And we check so testlab_mso_1 docker log file that is /var/log/ecomp/MSO/SDNCAdapter/errormso.log, we could found the error message.
        The two log file as blow.
        So please tell us how to resolve this issue, restart some docker or reinstall some docker?




----------------------------------------------
Regards,
Liu Chenglong



在 2018年7月17日,09:03,Liu Chenglong <lcl7608@...> 写道:

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?



----------------------------------------------
Regards,
Liu Chenglong



在 2018年7月17日,01:29,Multanen, Eric W <eric.w.multanen@...> 写道:

Yeah – we can take a look.
 
I recall – as Kang mentions – that there were intermittent issues.
 
Eric
 
From: Kang Xi [mailto:Kang.Xi@...] 
Sent: Monday, July 16, 2018 8:24 AM
To: FREEMAN, BRIAN D <bf1936@...>; Liu Chenglong <lcl7608@...>; Multanen, Eric W <eric.w.multanen@...>
Cc: huangzonghe <huangzh.bri@...>; onap-discuss@...
Subject: RE: [onap-discuss] [integration] create another vgw instance error
 

Brian,

Good suggestion.

Eric,

Is it possible to do so ?

--------------------------------------------------
Regards, 
Kang
From:FREEMAN, BRIAN D
To:Kang Xi,Liu Chenglong,
Cc:huangzonghe,onap-discuss@...,
Date:2018-07-16 11:13:39
Subject:RE: [onap-discuss] [integration] create another vgw instance error
 
Kang,
 
For Casablanca – I wonder if Eric can pre-install those packages into an image ?
 
Brian
 
 
From: Kang Xi <Kang.Xi@...> 
Sent: Monday, July 16, 2018 11:10 AM
To: Liu Chenglong <lcl7608@...>
Cc: FREEMAN, BRIAN D <bf1936@...>; huangzonghe <huangzh.bri@...>; onap-discuss@...
Subject: RE: [onap-discuss] [integration] create another vgw instance error
 
Chenglong,
 
Somehow the isc-dhcp package is not properly installed on vGW. This happened multiple times to me as well. My workaround is to manually install that service using ‘apt install isc-dhcp-server’. Restarting vGW does not help and you really don’t need to delete and re-instantiation vGW.
 
Regards,
Kang
 
From: Liu Chenglong [mailto:lcl7608@...] 
Sent: Monday, July 16, 2018 4:14
To: Kang Xi <Kang.Xi@...>
Cc: FREEMAN, BRIAN D <bf1936@...>; huangzonghe <huangzh.bri@...>; onap-discuss@...
Subject: Re: [onap-discuss] [integration] create another vgw instance error
 
Kang:
       We use new vcpe script that your had update in url to run vcpe use case. At first, we run vcpe.py infra success, but when we copy kea-sdnc-notify.so to vDHCP vm server, its doesnt work, we 
 
had write this question in another email. So, we delete all vcpes vnf stack and  network stack from windiver cloud platform. 
 
       After that we run vcpe.py infra again, this time kea-sdnc-notify.so is work now, we can query brgs mac address from docker sdnc_db_container in sdnc vm. when we run vcpe.py customer,  
 
yes, we create vgw ok. But when login vgw vm, we found that the isc-dhcp-server service not found, we run systemctl status isc-dhcp-servercommand and the result is show as flow 
 
picture.Whatever we reboot vgw vm many time and its also not ok. Please tell us why this happend and how to solve it?
 
      <image002.png>
 
 
      So, we had to delete vgw stack and vnf instance from cloud platform and try to create vgw vm again. But there is a new question before we happened, the error message is :"statusMessage”: 
 
"Received error from SDN-C: Error updating md-sal for tunnelxconn-allotted-resource”.Please tell us why this happend and how to solve it?
 
     <image004.png>
 
 
 
----------------------------------------------
Regards,
Liu Chenglong
 
 

 

 2018716日,09:07Liu Chenglong <lcl7608@...> 写道:
 
Kang:
         Thanks for your new vcpe script. Today I will test it.
 
 
----------------------------------------------
Regards,
Liu Chenglong
 
 

 

 2018715日,22:00Kang Xi <Kang.Xi@...> 写道:
 
Chenglong,
 
Please get the new script at the following link. Note that you will need to use the entire package, NOT just a single .py file.
 
Regards,
Kang
 
From: Liu Chenglong [mailto:lcl7608@...] 
Sent: Thursday, July 12, 2018 22:39
To: FREEMAN, BRIAN D <bf1936@...>
Cc: Liu Chenglong <lcl7608@...>; Kang Xi <Kang.Xi@...>; onap-discuss@...; huangzonghe <huangzh.bri@...>
Subject: Re: [onap-discuss] [integration] create another vgw instance error
 
Brian,
     Thanks for your detailed explanation. We just waiting for Kangs new vcpe.py script. In the few days, I download msos code fromgerrit.oanp.org and read mso-api-handlers, mso-api-handler-
 
common, mso-api-handler-infra, I want to know the API running flow when vcpe.py call msos restful api.
 
 
 
----------------------------------------------
Regards,
Liu Chenglong
 
 

 

 2018712日,20:45FREEMAN, BRIAN D <bf1936@...> 写道:
 
Chenglong,
 
I mistakenly typed CPE_SIGNALING and I should have said CPE_PUBLIC.
 
Let me try to be more accurate since it is confusing.
 
A.  Kang modified the vCPE.py scripts to add a preload for the subsequent vGWs
 
For example for vGW2 the preload would add
 
                                {
                                  "name": "vgw_private_ip_2",
                                  "value": "10.2.0.3"
                                },
 
To the list of preload parameters for the vGW keyed by VNF name (VGW2BRG-fa:16:3e:8a:bd:93 for example).
 
template.vcpe_vgw_vfmodule.json is the pattern and I think he has a modification to that template and a change to  vcpe.py that increments the IP address.
 
You could modify that template for the second vGW as a work around.
 
We should not have to set vgw_private_ip_2 at all and it turns out that we did that to work around a heat engine issue in a previous release of Openstack and its no longer needed.   I have a fix to the heat templates so we would not need to set any vgw_private_ip_2 for vGW or vBRGEMU but its probably simpler to simply change the template for vGW2 (or use Kang’s latest vcpe.py scripts once he gets back). For Casablanca we will sue the modified heat template so we dont need vgw_private_ip_2.
 
B.  WRT to the OOF/SNIRO emulator (not sure which you are using – we need Kang’s help since I’m not as familiar with that peace of the solution.  Marcus Williams might be able to help since he teste this for HPA as well.
 
Hope that helps
 
Brian
 
 
 
From: Liu Chenglong <lcl7608@...> 
Sent: Wednesday, July 11, 2018 10:39 PM
To: FREEMAN, BRIAN D <bf1936@...>; Kang Xi <Kang.Xi@...>
Cc: Liu Chenglong <lcl7608@...>; onap-discuss@...; huangzonghe <huangzh.bri@...>
Subject: Re: [onap-discuss] [integration] create another vgw instance error
 
Hi, Brian:
       At first, thanks a lot for you help. In our laboratory, the IP 10.2.0.3 that we found in base_vcpe_vgw.env file, and yes 10.2.0.3 that is allocated by 
sub network vcpe_net_cpe_public_201807060636 in vgw1 instance,  and 10.2.0.1 is the vDNS IP that is also allocated by subnetwork vcpe_net_cpe_public_201807060636.
      We check out vcpe script and preload_templates files , and we not found  "the CPE_SIGNALING IP on the vGW via preload. “. And we vDNS, vGw, vbrg’s network information are show in there pictures.
     
     the vgw’s network information:
      <image002.png>
 
 
      the vdnss network information:
     <image004.png>
 
    the vbrgs network information:
     <image006.png>
 
 
     Brian, Kang, please check these network information are right?
 
 
     We run vcpe.py customer again in last night, and we found thats another error happened, the error message is  "statusMessage": "Received a Bad Sync Response from Sniro/OOF.” That’s seem to we meet different error. So we hope to you can provide the running flow after the vcpe script call MSO restful API, the url or picture is ok. 
 
 
 
 
 
 



 2018712日,02:13FREEMAN, BRIAN D <bf1936@...> 写道:
 
Found the configuration problem on vDNS/vDHCP
 
 
Should have a fix pushed soon but you can also manually fix the config file.
 
I suspect the heat.yml for the vGW isnt quite right because it works without the DHCP on the CPE_PUBLIC side for the first vGW.
 
Brian
 
 
From: FREEMAN, BRIAN D 
Sent: Wednesday, July 11, 2018 9:59 AM
To: onap-discuss@...; FREEMAN, BRIAN D <bf1936@...>; lcl7608@...
Subject: RE: [onap-discuss] [integration] create another vgw instance error
 
I think the DHCP on that side of the vGW might not be working correctly.
 
I checked over the data in the integration environment and test data from Kang and I think we are setting the CPE_SIGNALING IP on the vGW via preload.
 
                                {
                                  "name": "vgw_private_ip_2",
                                  "value": "10.2.0.5"
                                },
 
 
Add vgw_private_ip_2 to the VGW2BRG-fa:16:3e:8a:bd:93 preload (or whatever your BRG MAC Address is)
 
And see if that unblocks the second vGW
 
Brian
 
 
From: onap-discuss@... <onap-discuss@...> On Behalf Of FREEMAN, BRIAN D
Sent: Tuesday, July 10, 2018 11:23 AM
To: onap-discuss@...; lcl7608@...
Subject: Re: [onap-discuss] [integration] create another vgw instance error
 

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

Chenglong,
 
Not sure why the neutron stack is rejecting that create since that IP should be assigned by the vdns VM on the CPE_PUBIC subnet not by the neutron heat stack call.
BTW the vGW1 should have gotten 10.2.0.2 not 10.2.0.3 if it was the first gateway to come up.
 
The dhcp addresses on the CPE_PUBLIC subnet are assigned by the vdns VNF and the log file is:
      "output": "/var/log/kea-dhcp4.log"
 
Also look in  /var/lib/kea/kea-leases4.csv to see if you are getting the DHCP lease assignments expected.
 
Kang did get multiple vGW/vBRGs working but he did have to change his scripts for it. He is expected back on Thursday and can probably provide better insight if we cant solve it before then.
 
Brian
 
 
 
From: onap-discuss@... <onap-discuss@...> On Behalf Of Liu Chenglong
Sent: Monday, July 09, 2018 11:21 PM
To: onap-discuss@...
Cc: Liu Chenglong <lcl7608@...>
Subject: [onap-discuss] [integration] create another vgw instance error
 
Hello:
 
    When we test vcpe use case, we had create a Vxlan tunnel success with a vbrg instance and a vgw named vgw1 instance. So we want to create another VxLANs tunnel. First, we create a new vbrg instance and success.  But there is an error when create the vgw instance named vgw2, the error message is: "Received vfModuleException from VnfAdapter: category='INTERNAL' message='Exception during create VF 0 : Stack error (CREATE_FAILED): Resource CREATE failed: Conflict:      resources.vgw_private_2_port: IP address 10.2.0.3 already allocated in subnet bb73e612-d22c-4537-a978-cf2ac9a7e8be\nNeutron server returns request_ids: ['req-8e0af890-9aa0-47bd-b950-8a cc6378f7dd'] - stack successfully deleted' rolledBack='true'". 
    The error message show this information "IP address 10.2.0.3 already allocated ", we check the ip address and found that is the first vgw1's ip, so it seems vDHCP instance don't allocate right IP address to vgw2 instance. So we want to know how to find where is ip address allocate and how to solve this error.
 
 
Regards,
Chenglong
 
 
 
 



[VNFSDK]VNFSDK Architecture Proposal

Gaoweitao(Victor)
 

Hi, VNFSDK Team member,

 

                I prepare several for VNFSDK architecture improvement. As we discussed in last VNFSDK meeting, let we exchange ideas and review by email.

 

                Attached is the proposal, please let me know your feedback. This is also available on wiki.

 

                Thanks in advance.

 

BR

Victor


Re: [integration] create another vgw instance error

Liu Chenglong
 

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?



----------------------------------------------
Regards,
Liu Chenglong



在 2018年7月17日,01:29,Multanen, Eric W <eric.w.multanen@...> 写道:

Yeah – we can take a look.
 
I recall – as Kang mentions – that there were intermittent issues.
 
Eric
 
From: Kang Xi [mailto:Kang.Xi@...] 
Sent: Monday, July 16, 2018 8:24 AM
To: FREEMAN, BRIAN D <bf1936@...>; Liu Chenglong <lcl7608@...>; Multanen, Eric W <eric.w.multanen@...>
Cc: huangzonghe <huangzh.bri@...>; onap-discuss@...
Subject: RE: [onap-discuss] [integration] create another vgw instance error
 

Brian,

Good suggestion.

Eric,

Is it possible to do so ?

--------------------------------------------------
Regards, 
Kang
From:FREEMAN, BRIAN D
To:Kang Xi,Liu Chenglong,
Cc:huangzonghe,onap-discuss@...,
Date:2018-07-16 11:13:39
Subject:RE: [onap-discuss] [integration] create another vgw instance error
 
Kang,
 
For Casablanca – I wonder if Eric can pre-install those packages into an image ?
 
Brian
 
 
From: Kang Xi <Kang.Xi@...> 
Sent: Monday, July 16, 2018 11:10 AM
To: Liu Chenglong <lcl7608@...>
Cc: FREEMAN, BRIAN D <bf1936@...>; huangzonghe <huangzh.bri@...>; onap-discuss@...
Subject: RE: [onap-discuss] [integration] create another vgw instance error
 
Chenglong,
 
Somehow the isc-dhcp package is not properly installed on vGW. This happened multiple times to me as well. My workaround is to manually install that service using ‘apt install isc-dhcp-server’. Restarting vGW does not help and you really don’t need to delete and re-instantiation vGW.
 
Regards,
Kang
 
From: Liu Chenglong [mailto:lcl7608@...] 
Sent: Monday, July 16, 2018 4:14
To: Kang Xi <Kang.Xi@...>
Cc: FREEMAN, BRIAN D <bf1936@...>; huangzonghe <huangzh.bri@...>; onap-discuss@...
Subject: Re: [onap-discuss] [integration] create another vgw instance error
 
Kang:
       We use new vcpe script that your had update in url to run vcpe use case. At first, we run vcpe.py infra success, but when we copy kea-sdnc-notify.so to vDHCP vm server, its doesnt work, we 
 
had write this question in another email. So, we delete all vcpes vnf stack and  network stack from windiver cloud platform. 
 
       After that we run vcpe.py infra again, this time kea-sdnc-notify.so is work now, we can query brgs mac address from docker sdnc_db_container in sdnc vm. when we run vcpe.py customer,  
 
yes, we create vgw ok. But when login vgw vm, we found that the isc-dhcp-server service not found, we run systemctl status isc-dhcp-servercommand and the result is show as flow 
 
picture.Whatever we reboot vgw vm many time and its also not ok. Please tell us why this happend and how to solve it?
 
      <image002.png>
 
 
      So, we had to delete vgw stack and vnf instance from cloud platform and try to create vgw vm again. But there is a new question before we happened, the error message is :"statusMessage”: 
 
"Received error from SDN-C: Error updating md-sal for tunnelxconn-allotted-resource”.Please tell us why this happend and how to solve it?
 
     <image004.png>
 
 
 
----------------------------------------------
Regards,
Liu Chenglong
 
 

 

 2018716日,09:07Liu Chenglong <lcl7608@...> 写道:
 
Kang:
         Thanks for your new vcpe script. Today I will test it.
 
 
----------------------------------------------
Regards,
Liu Chenglong
 
 

 

 2018715日,22:00Kang Xi <Kang.Xi@...> 写道:
 
Chenglong,
 
Please get the new script at the following link. Note that you will need to use the entire package, NOT just a single .py file.
 
Regards,
Kang
 
From: Liu Chenglong [mailto:lcl7608@...] 
Sent: Thursday, July 12, 2018 22:39
To: FREEMAN, BRIAN D <bf1936@...>
Cc: Liu Chenglong <lcl7608@...>; Kang Xi <Kang.Xi@...>; onap-discuss@...; huangzonghe <huangzh.bri@...>
Subject: Re: [onap-discuss] [integration] create another vgw instance error
 
Brian,
     Thanks for your detailed explanation. We just waiting for Kangs new vcpe.py script. In the few days, I download msos code fromgerrit.oanp.org and read mso-api-handlers, mso-api-handler-
 
common, mso-api-handler-infra, I want to know the API running flow when vcpe.py call msos restful api.
 
 
 
----------------------------------------------
Regards,
Liu Chenglong
 
 

 

 2018712日,20:45FREEMAN, BRIAN D <bf1936@...> 写道:
 
Chenglong,
 
I mistakenly typed CPE_SIGNALING and I should have said CPE_PUBLIC.
 
Let me try to be more accurate since it is confusing.
 
A.  Kang modified the vCPE.py scripts to add a preload for the subsequent vGWs
 
For example for vGW2 the preload would add
 
                                {
                                  "name": "vgw_private_ip_2",
                                  "value": "10.2.0.3"
                                },
 
To the list of preload parameters for the vGW keyed by VNF name (VGW2BRG-fa:16:3e:8a:bd:93 for example).
 
template.vcpe_vgw_vfmodule.json is the pattern and I think he has a modification to that template and a change to  vcpe.py that increments the IP address.
 
You could modify that template for the second vGW as a work around.
 
We should not have to set vgw_private_ip_2 at all and it turns out that we did that to work around a heat engine issue in a previous release of Openstack and its no longer needed.   I have a fix to the heat templates so we would not need to set any vgw_private_ip_2 for vGW or vBRGEMU but its probably simpler to simply change the template for vGW2 (or use Kang’s latest vcpe.py scripts once he gets back). For Casablanca we will sue the modified heat template so we dont need vgw_private_ip_2.
 
B.  WRT to the OOF/SNIRO emulator (not sure which you are using – we need Kang’s help since I’m not as familiar with that peace of the solution.  Marcus Williams might be able to help since he teste this for HPA as well.
 
Hope that helps
 
Brian
 
 
 
From: Liu Chenglong <lcl7608@...> 
Sent: Wednesday, July 11, 2018 10:39 PM
To: FREEMAN, BRIAN D <bf1936@...>; Kang Xi <Kang.Xi@...>
Cc: Liu Chenglong <lcl7608@...>; onap-discuss@...; huangzonghe <huangzh.bri@...>
Subject: Re: [onap-discuss] [integration] create another vgw instance error
 
Hi, Brian:
       At first, thanks a lot for you help. In our laboratory, the IP 10.2.0.3 that we found in base_vcpe_vgw.env file, and yes 10.2.0.3 that is allocated by 
sub network vcpe_net_cpe_public_201807060636 in vgw1 instance,  and 10.2.0.1 is the vDNS IP that is also allocated by subnetwork vcpe_net_cpe_public_201807060636.
      We check out vcpe script and preload_templates files , and we not found  "the CPE_SIGNALING IP on the vGW via preload. “. And we vDNS, vGw, vbrg’s network information are show in there pictures.
     
     the vgw’s network information:
      <image002.png>
 
 
      the vdnss network information:
     <image004.png>
 
    the vbrgs network information:
     <image006.png>
 
 
     Brian, Kang, please check these network information are right?
 
 
     We run vcpe.py customer again in last night, and we found thats another error happened, the error message is  "statusMessage": "Received a Bad Sync Response from Sniro/OOF.” That’s seem to we meet different error. So we hope to you can provide the running flow after the vcpe script call MSO restful API, the url or picture is ok. 
 
 
 
 
 
 



 2018712日,02:13FREEMAN, BRIAN D <bf1936@...> 写道:
 
Found the configuration problem on vDNS/vDHCP
 
 
Should have a fix pushed soon but you can also manually fix the config file.
 
I suspect the heat.yml for the vGW isnt quite right because it works without the DHCP on the CPE_PUBLIC side for the first vGW.
 
Brian
 
 
From: FREEMAN, BRIAN D 
Sent: Wednesday, July 11, 2018 9:59 AM
To: onap-discuss@...; FREEMAN, BRIAN D <bf1936@...>; lcl7608@...
Subject: RE: [onap-discuss] [integration] create another vgw instance error
 
I think the DHCP on that side of the vGW might not be working correctly.
 
I checked over the data in the integration environment and test data from Kang and I think we are setting the CPE_SIGNALING IP on the vGW via preload.
 
                                {
                                  "name": "vgw_private_ip_2",
                                  "value": "10.2.0.5"
                                },
 
 
Add vgw_private_ip_2 to the VGW2BRG-fa:16:3e:8a:bd:93 preload (or whatever your BRG MAC Address is)
 
And see if that unblocks the second vGW
 
Brian
 
 
From: onap-discuss@... <onap-discuss@...> On Behalf Of FREEMAN, BRIAN D
Sent: Tuesday, July 10, 2018 11:23 AM
To: onap-discuss@...; lcl7608@...
Subject: Re: [onap-discuss] [integration] create another vgw instance error
 

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

Chenglong,
 
Not sure why the neutron stack is rejecting that create since that IP should be assigned by the vdns VM on the CPE_PUBIC subnet not by the neutron heat stack call.
BTW the vGW1 should have gotten 10.2.0.2 not 10.2.0.3 if it was the first gateway to come up.
 
The dhcp addresses on the CPE_PUBLIC subnet are assigned by the vdns VNF and the log file is:
      "output": "/var/log/kea-dhcp4.log"
 
Also look in  /var/lib/kea/kea-leases4.csv to see if you are getting the DHCP lease assignments expected.
 
Kang did get multiple vGW/vBRGs working but he did have to change his scripts for it. He is expected back on Thursday and can probably provide better insight if we cant solve it before then.
 
Brian
 
 
 
From: onap-discuss@... <onap-discuss@...> On Behalf Of Liu Chenglong
Sent: Monday, July 09, 2018 11:21 PM
To: onap-discuss@...
Cc: Liu Chenglong <lcl7608@...>
Subject: [onap-discuss] [integration] create another vgw instance error
 
Hello:
 
    When we test vcpe use case, we had create a Vxlan tunnel success with a vbrg instance and a vgw named vgw1 instance. So we want to create another VxLANs tunnel. First, we create a new vbrg instance and success.  But there is an error when create the vgw instance named vgw2, the error message is: "Received vfModuleException from VnfAdapter: category='INTERNAL' message='Exception during create VF 0 : Stack error (CREATE_FAILED): Resource CREATE failed: Conflict:      resources.vgw_private_2_port: IP address 10.2.0.3 already allocated in subnet bb73e612-d22c-4537-a978-cf2ac9a7e8be\nNeutron server returns request_ids: ['req-8e0af890-9aa0-47bd-b950-8a cc6378f7dd'] - stack successfully deleted' rolledBack='true'". 
    The error message show this information "IP address 10.2.0.3 already allocated ", we check the ip address and found that is the first vgw1's ip, so it seems vDHCP instance don't allocate right IP address to vgw2 instance. So we want to know how to find where is ip address allocate and how to solve this error.
 
 
Regards,
Chenglong
 
 
 
 


Re: DCAE Build Error: dcaegen2/platform/cdapbroker ?

Vijay Venkatesh Kumar
 

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 integration comes along, CDAP can be deprecated.

 

Regards,

Vijay.

 

From: CARPENTER, TOMMY J
Sent: Monday, July 16, 2018 7:19 PM
To: HEKMAT, ARASH <arash.hekmat@...>
Cc: VENKATESH KUMAR, VIJAY <vv770d@...>; onap-discuss@...
Subject: Re: DCAE Build Error: dcaegen2/platform/cdapbroker ?

 

I had thought there was a formal process to deprecate something, rather than just deleting a repo, and perhaps that this had to be approved by the TSC. There are two other code sources in DCAE relating to this; the CDAP plugin, as well as the CDAP deployment blueprints. Formally removing CDAP would mean deleting all such code. 


On Jul 16, 2018, at 7:12 PM, HEKMAT, ARASH <arash.hekmat@...> wrote:

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 dcaegen2/platform/cdapbroker from ONAP Gerrit.

 

Thanks,

Arash

 

From: CARPENTER, TOMMY J (TOMMY J) <tommy@...>
Sent: Friday, July 13, 2018 5:41 PM
To: VENKATESH KUMAR, VIJAY <vv770d@...>
Cc: onap-discuss@...; Arash Hekmat <Arash.Hekmat@...>
Subject: Re: DCAE Build Error: dcaegen2/platform/cdapbroker ?

 

Yes the CDAP Broker is not a released or built artifact in R2+. I don’t know what the formal deprecation process is, but consider it deprecated since R1. Probably many things in it are out of date including its compatibility with CDAP. 


On Jul 13, 2018, at 5:35 PM, VENKATESH KUMAR, VIJAY <vv770d@...> wrote:

Hi Arash,

   Just FYI, the R2 deployment of DCAE does not include CDAP and hence CDAP broker was not deployed either (this may be deprecated in later releases).

 

CDAP Broker code is largely un-modified since R1; looking through the build report – seems normal and latest build was successful.

 

Suspect if local setup issue; looping Tommy who could give some pointers.

 

Regards,

Vijay

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of HEKMAT, ARASH
Sent: Friday, July 13, 2018 4:29 PM
To: onap-discuss@...
Subject: [onap-discuss] DCAE Build Error: dcaegen2/platform/cdapbroker ?

 

Hi DCAE team,

 

All of a sudden, I am getting this error when building dcaegen2/platform/cdapbroker. This is supposed to be a warning but in this case it’s turned into an error.

The reason seems to be that an old version of rebar executable (rebar 2.5.1) is pulled into dcaegen2/platform/cdapbroker/_build/default/lib/meck.

And also, in file dcaegen2/platform/cdapbroker/_build/default/lib/meck/rebar.config the compile flag “warnings_as_errors” is set.

I can remove this flag “warnings_as_errors” but I’d rather not touch this file because the whole “_build” subtree is pulled in at build time.

 

Any idea how to resolve this?

 

I have rebar3 & OTP 21 installed: rebar 3.5.0 on Erlang/OTP 21 Erts 10.0

 

Thanks,

Arash

 


===> Compiling cowboy

_build/default/lib/cowboy/src/cowboy_handler.erl:97: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

_build/default/lib/cowboy/src/cowboy_handler.erl:128: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

_build/default/lib/cowboy/src/cowboy_handler.erl:255: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

_build/default/lib/cowboy/src/cowboy_handler.erl:296: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

 

_build/default/lib/cowboy/src/cowboy_rest.erl:81: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

_build/default/lib/cowboy/src/cowboy_rest.erl:1010: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

 

_build/default/lib/cowboy/src/cowboy_websocket.erl:174: Warning: call to crypto:sha/1 will fail, since it was removed in 20.0; use crypto:hash/2

 

===> Compiling leptus

_build/default/lib/leptus/src/leptus_handler.erl:560: Warning: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

 

_build/default/lib/leptus/src/leptus_utils.erl:147: Warning: variable 'Rest' is unused

 

_build/default/lib/leptus/src/leptus.erl:289: Warning: erlang:now/0: Deprecated BIF. See the "Time and Time Correction in Erlang" chapter of the ERTS User's Guide for more information.

 

===> Compiling meck

===> Compiling _build/default/lib/meck/src/meck_code_gen.erl failed

_build/default/lib/meck/src/meck_code_gen.erl:198: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

 

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 51.604 s

[INFO] Finished at: 2018-07-13T15:38:19-04:00

[INFO] Final Memory: 25M/290M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile script) on project cdapbroker: Command execution failed.: Process exited with an error: 1 (Exit value: 1) -> [Help 1]

[ERROR]

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException


 

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,


[OOM] SO port(s) not exposed #so #oom

DeWayne Filppi
 

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?

12321 - 12340 of 23498