Re: [onap-discuss] DCAE Build Error: dcaegen2/platform/cdapbroker ?

[Vijay VK]

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@lists.onap.org  On Behalf Of 
HEKMAT, ARASH
Sent: Friday, July 13, 2018 4:29 PM
To: onap-discuss@lists.onap.org
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,
you may review at 
https://www.amdocs.com/about/email-disclaimer

[onap-discuss] DCAE Build Error: dcaegen2/platform/cdapbroker ?

[Arash Hekmat]

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,

you may review at https://www.amdocs.com/about/email-disclaimer 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11125): https://lists.onap.org/g/onap-discuss/message/11125
Mute This Topic: https://lists.onap.org/mt/23395864/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [modeling] ONAP Information Model in Papyrus

[Steve Polston]

Awesome! Thank you all.


From: onap-discuss@lists.onap.org  On Behalf Of 
Jessie Jewitt
Sent: Friday, July 13, 2018 2:00 PM
To: onap-discuss 
Subject: [onap-discuss] [modeling] ONAP Information Model in Papyrus

We finally have a "draft" ONAP model in a working branch in Gerrit.
It contains modeling work that is in progress, and does not represent anything 
committed yet to R3. When the model is approved, it will move to a master 
branch.

If you would like to use Papyrus for viewing this model, you can follow the 
instructions 
here

If you would like to be an official model editor, please let me know, as you 
will need to undergo some training first.

You can do any work (i.e. create an input model proposal for discussion) using 
Papyrus on your local machine, but only the model editors can actually check-in 
model updates in Gerrit.

Many thanks to Deng Hui, Chris Donley, Kevin Skaggs, and Yang Xu for helping us 
get the model up and running!

-Jessie


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11124): https://lists.onap.org/g/onap-discuss/message/11124
Mute This Topic: https://lists.onap.org/mt/23394659/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] [modeling] ONAP Information Model in Papyrus

[Jessie Jewitt]

We finally have a "draft" ONAP model in a working branch in Gerrit.
It contains modeling work that is in progress, and does not represent
anything committed yet to R3. When the model is approved, it will move to a
master branch.

If you would like to use Papyrus for viewing this model, you can follow the
instructions here


If you would like to be an official model editor, please let me know, as
you will need to undergo some training first.

You can do any work (i.e. create an input model proposal for discussion)
using Papyrus on your *local machine,* but only the model editors can
actually check-in model updates in Gerrit.

Many thanks to Deng Hui, Chris Donley, Kevin Skaggs, and Yang Xu for
helping us get the model up and running!

-Jessie

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11123): https://lists.onap.org/g/onap-discuss/message/11123
Mute This Topic: https://lists.onap.org/mt/23394659/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] Logging-Analytics 3 Committer Promotions - overview: Geora Barsky, Shane Daniel, Prudence Au

[Michael O'Brien]

Team,
  As you know the logging project has recently expanded its' scope for the ONAP 
Casablanca release to include the POMBA set of 10 microservices that span the 
Logging-analytics (6), SDNC (3) and AA&I (1) projects.
https://wiki.onap.org/display/DW/POMBA
We have also expanded our work in the following areas.

  1.  Logging standards around a proposed logging library and a WIP AOP wrapper 
to help implement it.

https://wiki.onap.org/pages/viewpage.action?pageId=28378955

  1.  Acumos.org logging alignment (project teams on both ONAP/Acumos sides 
have been working together to come up with a common spec and work through 
implementations of the ELK deployment and logging library implementation.


NEW Committers:
As part of this expansion of work I will be proposing two phases of adding 
additional committers to the logging-analytics repo to bring in designers that 
have and will continue to add to the project.

Geora Barsky: https://wiki.onap.org/pages/viewpage.action?pageId=35522327
Geora started last year by contributing the SNIRO container to ONAP in the 
demo/robot pod, he is one of the architects and a developer on the POMBA seed 
code coming into ONAP and is critical to the project.

Shane Daniel: https://wiki.onap.org/pages/viewpage.action?pageId=35522331
Shane has been working with ONAP and the logging project since mid last year 
and has contributed significant pieces of work such as the kibana tracing 
dashboards, logging code and configuration in both the logging and oom repos 
and the dashboard for the CD system - we rely on Shane.

Prudence Au: https://wiki.onap.org/pages/viewpage.action?pageId=35522137
Prudence was part of the team that delivered the SDNC geo redundancy POC to 
ONAP earlier this year.  She has committed and reviewed patches related to 
POMBA, SDNC and Logging.  Prudence is essential to POMBA.

Current:
  I am sending out three requests for +1 to the 4 current committers on the 
project before sending out TSC formal mails after the results are in.

Future:
   In addition to the current committers - Luke Parker, Avdhut Kholkar and Lee 
Breslau - I would like to thank our active contributors - Neal Chatterley, 
Lorraine Welch, Shishir B Thakore, Spondon Dey, Sanjay Agraharam, Jun Nicolas 
Hu, Bob Ferro, Dave Williamson, Joanna Xu.  I would also like to introduce our 
POMBA active contributors - Sharon Chisholm, Jenny Jia, Geora Barsky, James 
MacNider, Vitaly Lavrusevich, Shane Daniel, Prudence Au, Brad Benesch, Pierre 
Rioux.

Thank you
/michael


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

you may review at https://www.amdocs.com/about/email-disclaimer 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11122): https://lists.onap.org/g/onap-discuss/message/11122
Mute This Topic: https://lists.onap.org/mt/23391242/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [DMaaP] - PTL Nominations

[Sai Gandham]

+1 for Ram koya

Thanks
Sai Gandham

From: LUNANUOVA, DOMINIC
Sent: Thursday, July 12, 2018 2:31 PM
To: KOYA, RAMPRASAD ; 'onap-discuss@lists.onap.org' 
; GANDHAM, SAI ; UNNAVA, SUNIL 
; 'hg0071...@techmahindra.com' 
Subject: RE: [DMaaP] - PTL Nominations

+1

From: KOYA, RAMPRASAD
Sent: Thursday, July 12, 2018 2:57 PM
To: 'onap-discuss@lists.onap.org' 
mailto:onap-discuss@lists.onap.org>>; GANDHAM, SAI 
mailto:sg4...@att.com>>; UNNAVA, SUNIL 
mailto:su6...@att.com>>; 'hg0071...@techmahindra.com' 
mailto:hg0071...@techmahindra.com>>; LUNANUOVA, 
DOMINIC (DOMINIC) mailto:d...@research.att.com>>
Subject: RE: [DMaaP] - PTL Nominations

Dear ONAP DMaaP Committers,

I would like to nominate myself for the role of PTL of ONAP DMaaP project.

I was the PTL of ONAP DMaaP project in the past year and delivered both 
Amsterdam and Beijing release. I've been with AT&T for more than 6 years, 
during which I developed many solutions including highly scalable enterprise 
grade CICD enabled microservice, data analytics and machine learning reusable 
templates minimizing application development allowing developers to focus on 
core business functions.  Also provided product vision, architecture and 
leadership to API platform modernization supporting microservices by delivering 
Docker/Kubernetes based platform, Java, node.js and python based enterprise 
grade application development templates.

My overall qualifications:

I had over 25+ years of experience working as lead architect of large-scale, 
mission-critical projects including open sourcing common platforms and 
frameworks, and also adopting a lot of opensource products with in enterprises. 
Led the product architecture and development of highly innovative and 
self-sufficiency tools, frameworks and SDKs supporting 180k+ wireless 
application developers, 200+ partners and 2000+ enterprises in creating mobile 
applications. Launched many of the industry first mobile data products and 
solutions in the world, including launching the first mobile app store, first 
mobile handsets that supported OTA app downloads, handset and product launches 
involving 3G, 4G and LTE networks.

I enjoyed working with you in the past and hope to continue getting your 
support going forward.

Regards,
Ram Koya

From: KOYA, RAMPRASAD
Sent: Thursday, July 12, 2018 1:19 PM
To: 'onap-discuss@lists.onap.org' 
mailto:onap-discuss@lists.onap.org>>; GANDHAM, SAI 
mailto:sg4...@att.com>>; UNNAVA, SUNIL 
mailto:su6...@att.com>>; 'hg0071...@techmahindra.com' 
mailto:hg0071...@techmahindra.com>>; LUNANUOVA, 
DOMINIC mailto:d...@research.att.com>>
Subject: [DMaaP] - PTL Nominations

Dear DmaaP 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+Election

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

We will close the self-nomination window by 23:59 PDT July 13th, Friday, 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 7/19.

Regards,
Ram Koya


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11121): https://lists.onap.org/g/onap-discuss/message/11121
Mute This Topic: https://lists.onap.org/mt/23291639/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] [VNFPkg] New Bridge for today

[Andy Mayer]

https://zoom.us/j/4996638718

Best Regards,
Andy

Andy Mayer, Ph.D. | PMTS, D2.0 Integration | AT&T Labs | Phone: +1 (732) 
420-9945 | am8...@att.com
[cid:image001.jpg@01D2E10C.0410C230]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9): https://lists.onap.org/g/onap-discuss/message/9
Mute This Topic: https://lists.onap.org/mt/23390205/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [Onap-seccom] [onap-discuss] Att: PTL - Languages supported in ONAP

[Arash Hekmat]

Erlang may also being used in some projects (DCAE?) but it's for the PTLs to 
confirm.

Thanks,
Arash

From: onap-discuss@lists.onap.org  On Behalf Of 
Kiran Kamineni
Sent: Wednesday, July 11, 2018 11:41 AM
To: Addepalli, Srinivasa R ; 
onap-discuss@lists.onap.org; shankarp...@gmail.com
Cc: Arul Nambi ; onap-sec...@lists.onap.org
Subject: Re: [Onap-seccom] [onap-discuss] Att: PTL - Languages supported in ONAP

We use golang in Secret Management project.
Regarding tools, golang has some built in tools for coverage (we already use 
this to report coverage numbers for each build) and static analysis.

-- K i r a n

From: onap-sec...@lists.onap.org 
[mailto:onap-sec...@lists.onap.org] On Behalf Of Srini
Sent: Wednesday, July 11, 2018 7:38 AM
To: onap-discuss@lists.onap.org; 
shankarp...@gmail.com
Cc: arul.na...@amdocs.com; 
onap-sec...@lists.onap.org
Subject: Re: [Onap-seccom] [onap-discuss] Att: PTL - Languages supported in ONAP

Keep golang also in mind

Thanks
Srini

On Jul 11, 2018, at 19:59, Shankar Narayanan 
mailto:shankarp...@gmail.com>> wrote:
Hi Arul,

Please do include Python as well to the list. There are quite a few projects 
that have significant Python code bases. OOF, for instance, is a pure python 
project, and would need python support from the tools used for code 
coverage/analysis.

Thanks,
Shankar.

On Wed, Jul 11, 2018 at 10:07 AM Arul Nambi 
mailto:arul.na...@amdocs.com>> wrote:
Hi PTL's/Community,
In the security committee we are looking for the list of languages that needs 
to be supported when we come up with new tools for code coverage and static 
analysis.
Currently we know of

  1.  Java(ofcourse)
  2.  Javascript
We think that we will need PHP and Phyton, but need confirmation from the 
projects(preferably PTLs) about the language support that is needed and the 
name of the project.
There is a query in gerrit which can be used to find projects with certain file 
extensions, but it hard think of all the languauges.
Once we have a complete list I can update the wiki page so that in future we 
will know the languages that we support.
Regards
Arul

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer

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

you may review at https://www.amdocs.com/about/email-disclaimer 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8): https://lists.onap.org/g/onap-discuss/message/8
Mute This Topic: https://lists.onap.org/mt/23246357/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [modeling] Papyrus working branch for modeling

[denghui (L)]

Chris

In order to build a validation job for papyrus, we need many days/Human 
resource to do this job in order to let papyrus file could follow LF official 
procedure, we also need do maven for it later as well.

I will try to manually merge this commit without the validation.

Thanks a lot

DENG Hui

From: Christopher Donley (Chris)
Sent: Friday, July 13, 2018 10:28 AM
To: onap-discuss@lists.onap.org; jessie.jew...@oamtechnologies.com; denghui (L) 

Subject: Re: [onap-discuss] [modeling] Papyrus working branch for modeling

Hui,

I don't think that repo has a validation job. It will either need to be 
manually validated by a Committer or you'll need to set up a jjb job. Since 
Papyrus generates xml files and not java/python code, I don't think there is a 
jjb job for it, so you may need to do it manually.

Chris

From: denghui (L)
To: onap-discuss@lists.onap.org; 
jessie.jew...@oamtechnologies.com;
Cc: Christopher Donley (Chris);
Subject: RE: [onap-discuss] [modeling] Papyrus working branch for modeling
Time: 2018-07-12 18:15:26

Hi Jessie,

Thanks a lot for your help.

Maybe this is your 1st time to submit to ONAP gerrit,  in order to get 
successfully merged, your commit needs to pass jbuilder check,
Could you kindly help to study from this wiki page about jbuilder : 
https://wiki.onap.org/display/DW/Using+Standard+Jenkins+Job+%28JJB%29+Templates
The recommit it again, then after jbuilder+2, then I could quickly merge this 
commit into the working branch.

Thanks a lot for your help

Best regards,

DENG Hui

From: onap-discuss@lists.onap.org 
[mailto:onap-discuss@lists.onap.org] On Behalf Of Jessie Jewitt
Sent: Friday, July 13, 2018 5:03 AM
To: onap-discuss 
mailto:onap-discuss@lists.onap.org>>; denghui (L) 
mailto:denghu...@huawei.com>>
Subject: Re: [onap-discuss] [modeling] Papyrus working branch for modeling

Deng Hui-
   I uploaded all the Papyrus files to the working branch. There is an 
outstanding issue open in Gerrit for you to approve to commit these files to 
the branch. Could you possibly do this so we can start downloading the model 
for people to work on starting tomorrow?
Thank you,
Jessie

On Tue, Jul 10, 2018 at 1:05 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:
Hello modelers

I have created a working branch (R3workingbranch) which will help papyrus 
contributors could submit papyrus files to Gerrit, folder name will be 
/modelspec/papyrus

Please kindly remember to submit the correct place by : git checkout 
R3workingbranch

Thanks a lot for your help

DENG Hui



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#7): https://lists.onap.org/g/onap-discuss/message/7
Mute This Topic: https://lists.onap.org/mt/23209084/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-