date:20171031

[onap-discuss] [integration][holmes] VoLTE use case integration test with Holmes

2017-10-31 Thread Yang Xu (Yang, Fixed Network)

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Yang Xu (Yang, Fixed Network)":MAILTO:yang@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 ss:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, November 01\, 2017 9:00 AM-11:
 00 AM (UTC-05:00) Eastern Time (US & Canada).\nWhere: https://zoom.us/j/42
 38608129\n\nNote: The GMT offset above does not reflect daylight saving ti
 me adjustments.\n\n*~*~*~*~*~*~*~*~*~*\n\nTopic: Test Holmes with simulate
 d alarms from MultiVIM and EMS driver\n\n
SUMMARY;LANGUAGE=en-US:[integration][holmes] VoLTE use case integration tes
 t with Holmes
DTSTART;TZID=Eastern Standard Time:20171101T09
DTEND;TZID=Eastern Standard Time:20171101T11
UID:04008200E00074C5B7101A82E008F0507673AD52D301000
 01000FD79B6EFB93D2D4C82A42CA9FEF15AA7
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171101T050704Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:https://zoom.us/j/4238608129
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:1277278177
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] compile about aai-spark-fe

2017-10-31 Thread Arul Nambi

Hi,
Sparky FE is a react application. And I think you are using maven commands to 
build the application.
I would not recommend running just the FE, but if you need it for development 
purposes, you can run the react UI(FE) as is without the BE for which you will 
need NPM and node installed on your machine. Please refer to the readme in the 
repo and let me know if you still have questions.
Regards
Arul


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of aijianwen
Sent: Tuesday, October 31, 2017 9:10 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] compile about aai-spark-fe

Hi, team
   I compile the module: aai-spark-fe. Then it is not stable.
I compile it in Oct. 24:
[INFO] Installing 
/directory/var/jenkins/workspace/aai-spark-fe-1.1.0/target/sparky-fe-1.0.0-SNAPSHOT.war
 to 
/directory/repository/org/onap/aai/sparky-fe/sparky-fe/1.0.0-SNAPSHOT/sparky-fe-1.0.0-SNAPSHOT.war
[INFO] Installing /directory/var/jenkins/workspace/aai-spark-fe-1.1.0/pom.xml 
to 
/directory/repository/org/onap/aai/sparky-fe/sparky-fe/1.0.0-SNAPSHOT/sparky-fe-1.0.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 06:05 min
[INFO] Finished at: 2017-10-25T11:50:54+08:00
[INFO] Final Memory: 22M/1126M
[INFO] 

Oct. 31, I downloaded the new code, then it can't be compiled:

[INFO] 

[INFO] Building aai-sparky-fe 1.0.0-SNAPSHOT

[INFO] 

[INFO]

[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ sparky-fe ---

[INFO]

[INFO] --- frontend-maven-plugin:1.4:install-node-and-npm (install node and 
npm) @ sparky-fe ---

[INFO] Installing node version v6.2.2

[INFO] Unpacking 
/directory/repository/com/github/eirslett/node/6.2.2/node-6.2.2-linux-x64.tar.gz
 into /directory/var/jenkins/workspace/aai-spark-fe-compile-1.1.0/node/tmp

[INFO] Copying node binary from 
/directory/var/jenkins/workspace/aai-spark-fe-compile-1.1.0/node/tmp/node-v6.2.2-linux-x64/bin/node
 to /directory/var/jenkins/workspace/aai-spark-fe-compile-1.1.0/node/node

[INFO] Installed node locally.

[INFO] Installing npm version 3.10.3

[INFO] Unpacking 
/directory/repository/com/github/eirslett/npm/3.10.3/npm-3.10.3.tar.gz into 
/directory/var/jenkins/workspace/aai-spark-fe-compile-1.1.0/node/node_modules

[INFO] 

[INFO] BUILD FAILURE

[INFO] 

[INFO] Total time: 2.480 s

[INFO] Finished at: 2017-10-31T11:28:00+08:00

[INFO] Final Memory: 31M/1963M

[INFO] 

[ERROR] Failed to execute goal 
com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-npm (install 
node and npm) on project sparky-fe: Could not extract the npm archive: Could 
not extract archive: 
'/directory/repository/com/github/eirslett/npm/3.10.3/npm-3.10.3.tar.gz': Error 
detected parsing the header: Invalid byte 37 at offset 7 in 't__(se{NUL}%' 
len=8 -> [Help 1]

How to solve it?
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 mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP Helpdesk #47527] [DOC] Documentation RTD Build Reaching the Default Time/Memory Quota

2017-10-31 Thread Jessica Wagantall via RT

Dear Rich, 

do you still have issues with these docs?
Can you please send us a screenshot or any more info please?

Thanks!
Jess

On Sat Oct 28 20:37:56 2017, KennyPaul wrote:
> Can you provide some screenshots or some other debug info?
> Not sure what the issue is here but ODL ran into something like this
> once and it was caused by inefficient scripting .
> 
> On Thu Oct 26 10:23:10 2017, rb2...@att.com wrote:
> > With recent additions of documentation source we are reaching the
> > default time/memory quota at Readthedocs.
> >
> > There are some things we are doing that will reduce our requirements
> > but increasing the quota at the Readthedocs would improve turnaround
> > time as we finalize the Amsterdam Release.
> >
> > Does the LF release engineering team have a contact with readthedocs
> > to request a change in quota?
> >
> > Thank you
> >
> > Rich



___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] CSIT Jenkins jobs failed

2017-10-31 Thread Gary Wu

To clarify, the branch/stream field for the CSIT job template refers to the 
branch on the integration repo.  At this time, only the master branch exists on 
the integration repo.  So, you just need a single CSIT job which is 
"master-csit", but you should ensure that your test case scripts are pulling 
the correct docker image tags for your Amsterdam deliverables.

Thanks,
Gary

-Original Message-
From: Lando,Michael [mailto:ml6...@intl.att.com] 
Sent: Tuesday, October 31, 2017 10:03 AM
To: Gary Wu ; Shlosberg, Yuli 
Cc: Gitelman, Tal ; Amit, Idan ; 
onap-discuss 
Subject: RE: CSIT Jenkins jobs failed

For sdc release 1.1.0 is the amsterdam release

 Original Message 
From: Gary Wu 
Date: Tue, Oct 31, 2017, 18:53
To: "Lando,Michael" , "Shlosberg, Yuli" 

CC: "Gitelman, Tal" , "Amit, Idan" , 
onap-discuss 
Subject: RE: CSIT Jenkins jobs failed

I recommend that you remove the release-1.1.0-csit jobs for the time being.  
Until we work out the branching strategy for CSIT, it's expected that the 
master-csit jobs be testing Amsterdam deliverables.

Thanks,
Gary

-Original Message-
From: Lando,Michael [mailto:ml6...@intl.att.com]
Sent: Tuesday, October 31, 2017 8:37 AM
To: Gary Wu ; Shlosberg, Yuli 
Cc: Lando,Michael ; Gitelman, Tal ; 
Amit, Idan ; onap-discuss 
Subject: RE: CSIT Jenkins jobs failed

Thank you for the answer.

So this means that once each project branches we will lose the abelty to use 
csit.

I think thia needs to be comunicated to guilds because we are being tracked by 
him regurding the state of our jobs.

 Original Message 
From: Gary Wu 
Date: Tue, Oct 31, 2017, 17:31
To: "Shlosberg, Yuli" 
CC: "Lando,Michael" , "Gitelman, Tal" 
, "Amit, Idan" , onap-discuss 

Subject: RE: CSIT Jenkins jobs failed

Hi Yuli,

The integration repo doesn't have a "release-1.1.0" branch, so 
release-1.1.0-csit jobs would not work.

We'll need to figure out a way to have CSIT support project branches given that 
every project may a different branch name.  Once we have this figured out we'll 
update the community.

Thanks,
Gary

From: Shlosberg, Yuli [mailto:ys9...@intl.att.com]
Sent: Tuesday, October 31, 2017 8:23 AM
To: Gary Wu 
Cc: Lando,Michael ; Gitelman, Tal ; 
Amit, Idan 
Subject: RE: CSIT Jenkins jobs failed

Hi Gary,

Did you have a chance to take a look on below issue?

Thanks,
Yuli

From: Shlosberg, Yuli
Sent: Sunday, October 29, 2017 1:19 PM
To: 'gary.i...@huawei.com' >
Cc: Lando,Michael >; Gitelman, 
Tal >; Amit, Idan 
>
Subject: CSIT Jenkins jobs failed

Hi Gary,

Can you please help me, we start work with several "streams" e.g. master and 
release 1.1.0 but it seem that Jenkins jobs failed.
Could you please take a look on below job and advise what action should be 
taken?

https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_CSIT_job_sdc-2Drelease-2D1.1.0-2Dcsit-2Dnightly_7_=DwIFAg=LFYZ-o9_HUMeMTSQicvjIg=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY=zG5vGCtY31o0J_Tzigmk2vUv2Zi1wpy9D3r4Z2Pt3zM=6KbExR-IpuIs1NkFOBpMgfv_Tpbp-6-FUyOISv0OixA=
 



Also we have few jobs that even not started :

https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_CSIT_job_sdc-2Drelease-2D1.1.0-2Dverify-2Dcsit-2Dnightly_=DwIFAg=LFYZ-o9_HUMeMTSQicvjIg=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY=zG5vGCtY31o0J_Tzigmk2vUv2Zi1wpy9D3r4Z2Pt3zM=sxdZzGepV1uyZ4D0awfi0B_iulDIlQ20weP3Hd_i8NQ=

Re: [onap-discuss] CSIT Jenkins jobs failed

2017-10-31 Thread Lando,Michael

For sdc release 1.1.0 is the amsterdam release

 Original Message 
From: Gary Wu 
Date: Tue, Oct 31, 2017, 18:53
To: "Lando,Michael" , "Shlosberg, Yuli" 

CC: "Gitelman, Tal" , "Amit, Idan" , 
onap-discuss 
Subject: RE: CSIT Jenkins jobs failed

I recommend that you remove the release-1.1.0-csit jobs for the time being.  
Until we work out the branching strategy for CSIT, it's expected that the 
master-csit jobs be testing Amsterdam deliverables.

Thanks,
Gary

-Original Message-
From: Lando,Michael [mailto:ml6...@intl.att.com]
Sent: Tuesday, October 31, 2017 8:37 AM
To: Gary Wu ; Shlosberg, Yuli 
Cc: Lando,Michael ; Gitelman, Tal ; 
Amit, Idan ; onap-discuss 
Subject: RE: CSIT Jenkins jobs failed

Thank you for the answer.

So this means that once each project branches we will lose the abelty to use 
csit.

I think thia needs to be comunicated to guilds because we are being tracked by 
him regurding the state of our jobs.

 Original Message 
From: Gary Wu 
Date: Tue, Oct 31, 2017, 17:31
To: "Shlosberg, Yuli" 
CC: "Lando,Michael" , "Gitelman, Tal" 
, "Amit, Idan" , onap-discuss 

Subject: RE: CSIT Jenkins jobs failed

Hi Yuli,

The integration repo doesn't have a "release-1.1.0" branch, so 
release-1.1.0-csit jobs would not work.

We'll need to figure out a way to have CSIT support project branches given that 
every project may a different branch name.  Once we have this figured out we'll 
update the community.

Thanks,
Gary

From: Shlosberg, Yuli [mailto:ys9...@intl.att.com]
Sent: Tuesday, October 31, 2017 8:23 AM
To: Gary Wu 
Cc: Lando,Michael ; Gitelman, Tal ; 
Amit, Idan 
Subject: RE: CSIT Jenkins jobs failed

Hi Gary,

Did you have a chance to take a look on below issue?

Thanks,
Yuli

From: Shlosberg, Yuli
Sent: Sunday, October 29, 2017 1:19 PM
To: 'gary.i...@huawei.com' >
Cc: Lando,Michael >; Gitelman, 
Tal >; Amit, Idan 
>
Subject: CSIT Jenkins jobs failed

Hi Gary,

Can you please help me, we start work with several "streams" e.g. master and 
release 1.1.0 but it seem that Jenkins jobs failed.
Could you please take a look on below job and advise what action should be 
taken?

https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_CSIT_job_sdc-2Drelease-2D1.1.0-2Dcsit-2Dnightly_7_=DwIFAg=LFYZ-o9_HUMeMTSQicvjIg=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY=zG5vGCtY31o0J_Tzigmk2vUv2Zi1wpy9D3r4Z2Pt3zM=6KbExR-IpuIs1NkFOBpMgfv_Tpbp-6-FUyOISv0OixA=

Also we have few jobs that even not started :

https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_CSIT_job_sdc-2Drelease-2D1.1.0-2Dverify-2Dcsit-2Dnightly_=DwIFAg=LFYZ-o9_HUMeMTSQicvjIg=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY=zG5vGCtY31o0J_Tzigmk2vUv2Zi1wpy9D3r4Z2Pt3zM=sxdZzGepV1uyZ4D0awfi0B_iulDIlQ20weP3Hd_i8NQ=

https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_CSIT_job_sdc-2Drelease-2D1.1.0-2Dcsit-2Dsanity_=DwIFAg=LFYZ-o9_HUMeMTSQicvjIg=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY=zG5vGCtY31o0J_Tzigmk2vUv2Zi1wpy9D3r4Z2Pt3zM=OdfYaWTe47kOtBSjB22yNXB9B3uKv0agiaFCWGcsTsk=

Many thanks in advance,

Yuli Shlosberg
Software Engineer
AT Network Applications Development * SD Tel Aviv | Tampa | Atlanta | New 
Jersey |Chicago

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] CSIT Jenkins jobs failed

2017-10-31 Thread Gary Wu

I recommend that you remove the release-1.1.0-csit jobs for the time being.  
Until we work out the branching strategy for CSIT, it's expected that the 
master-csit jobs be testing Amsterdam deliverables.

Thanks,
Gary

-Original Message-
From: Lando,Michael [mailto:ml6...@intl.att.com] 
Sent: Tuesday, October 31, 2017 8:37 AM
To: Gary Wu ; Shlosberg, Yuli 
Cc: Lando,Michael ; Gitelman, Tal ; 
Amit, Idan ; onap-discuss 
Subject: RE: CSIT Jenkins jobs failed

Thank you for the answer.

So this means that once each project branches we will lose the abelty to use 
csit.

I think thia needs to be comunicated to guilds because we are being tracked by 
him regurding the state of our jobs.

 Original Message 
From: Gary Wu 
Date: Tue, Oct 31, 2017, 17:31
To: "Shlosberg, Yuli" 
CC: "Lando,Michael" , "Gitelman, Tal" 
, "Amit, Idan" , onap-discuss 

Subject: RE: CSIT Jenkins jobs failed

Hi Yuli,

The integration repo doesn't have a "release-1.1.0" branch, so 
release-1.1.0-csit jobs would not work.

We'll need to figure out a way to have CSIT support project branches given that 
every project may a different branch name.  Once we have this figured out we'll 
update the community.

Thanks,
Gary

From: Shlosberg, Yuli [mailto:ys9...@intl.att.com]
Sent: Tuesday, October 31, 2017 8:23 AM
To: Gary Wu 
Cc: Lando,Michael ; Gitelman, Tal ; 
Amit, Idan 
Subject: RE: CSIT Jenkins jobs failed

Hi Gary,

Did you have a chance to take a look on below issue?

Thanks,
Yuli

From: Shlosberg, Yuli
Sent: Sunday, October 29, 2017 1:19 PM
To: 'gary.i...@huawei.com' >
Cc: Lando,Michael >; Gitelman, 
Tal >; Amit, Idan 
>
Subject: CSIT Jenkins jobs failed

Hi Gary,

Can you please help me, we start work with several "streams" e.g. master and 
release 1.1.0 but it seem that Jenkins jobs failed.
Could you please take a look on below job and advise what action should be 
taken?

https://jenkins.onap.org/view/CSIT/job/sdc-release-1.1.0-csit-nightly/7/


Also we have few jobs that even not started :

https://jenkins.onap.org/view/CSIT/job/sdc-release-1.1.0-verify-csit-nightly/
https://jenkins.onap.org/view/CSIT/job/sdc-release-1.1.0-csit-sanity/


Many thanks in advance,

Yuli Shlosberg
Software Engineer
AT Network Applications Development * SD Tel Aviv | Tampa | Atlanta | New 
Jersey |Chicago

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP Helpdesk #47650] [cli][lf] Create branch release 1.1.0 for onap/cli

2017-10-31 Thread Jessica Wagantall via RT

Dear Kanagaraj, 

you should be able to create the branch from the UI in gerrit. 
Try adding the branch here and let me know if this works for you:
https://gerrit.onap.org/r/#/admin/projects/cli,branches

For enabling the Jenkins jobs, you should add the new branch as part of the 
stream list in the yaml template:
/ci-management/jjb/cli/cli.yaml

Let me know if you have any questions and if you would like me to review your 
gerrit. 

Thanks!
Jess

On Tue Oct 31 03:28:21 2017, kanagaraj.manic...@huawei.com wrote:
> Hi,
> 
> To enabled release artifact for Amsterdam release, I would like to
> create new git branch release-1.1.0 for CLI (onap/cli) project and
> enable new jenkins jobs under this branch to build following binaries
> and mark them as Amsterdam release candidate.
> (I assume that existing Jenkins jobs will not get affected and will
> continuous produce these artifacts from master branch, and let me know
> otherwise).
> 
> 
> 1.   NEXUS artifact zip:  org.onap.cli :: cli-zip :: 1.1.0
> 
> 2.   Docker container image:  onap/cli (tag: 1.1.0)
> 
> 3.   Document
> 
> 4.   Sonar
> 
> 5.   CSIT
> 
> Could you please help ? Thank you.
> 
> Regards
> Kanagaraj M
> ONAP-CLI-PTL
> 
> ***
> 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
> 
> ***
> This e-mail and its attachments contain confidential information from
> HUAWEI, which is intended only for the person  or entity whose address
> is listed above. Any use of the information contained herein in any
> way (including, but not   limited to, total or partial disclosure,
> reproduction, or dissemination) by persons other than the intended
> recipient(s) is  prohibited. If you receive this e-mail in error,
> please notify the sender by phone or email immediately and delete it!
> ***
> 



___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Demo cert for AAI expires on 30 Nov

2017-10-31 Thread FORSYTH, JAMES

Dear ONAP Security Subcommittee,

I raised this issue below on yesterday's PTL call and they recommended I bring 
it to the security subcommittee.  Can we discuss this on the weekly security 
subcommittee meeting tomorrow?

Thanks,
jimmy

From: FORSYTH, JAMES
Sent: Tuesday, October 10, 2017 9:44 AM
To: onap-discuss@lists.onap.org
Subject: [aai] [integration] Demo cert for AAI expires on 30 Nov

All,

The demo certificates that AAI is shipping with the current docker images will 
expire on 30 Nov.

Alias name: aaiopenecomp
Creation date: Nov 30, 2016
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: 
EMAILADDRESS=aai-h...@api.simpledemo.openecomp.org,
 CN=aai.api.simpledemo
.openecomp.org, OU=SimpleDemo, O=OpenECOMP, L=Bedminster, ST=NJ, C=US
Issuer: 
EMAILADDRESS=simpled...@openecomp.org,
 CN=OpenECOMP simpledemo Server CA
X1, OU=simpledemo, O=OpenECOMP, L=Bedminster, ST=NJ, C=US
Serial number: 83ca7c32dc9f7329
Valid from: Wed Nov 30 10:38:39 EST 2016 until: Thu Nov 30 10:38:39 EST 2017

@Integration team (or anyone who knows), is there an onap demo CA from which 
AAI can request a new demo certificate for testing?  My team can provide a new 
ONAP demo cert/CA which other systems can trust, but would prefer if there were 
a standard source for all ONAP systems that are participating in the testing.

Thanks,
jimmy
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] F2F Dec - submission date extended to 6 Nov on (2 of 3 sites). Confirmation?

2017-10-31 Thread Michael O'Brien

Kenny,
   Fast service as usual – one more question for the ONAP community for the F2F 
extension
   In the last TSC a proposal to move from 31 Oct (Halloween)  to 6 Nov was 
asked – this has been implemented right?
   VERIFICATION: 6 Nov deadline for submissions? I expect YES from your changes 
below.

   We would like to do a bit more coordination between ONAP teams (OOM, Logging 
for example) for the F2F proposals tomorrow before submitting.
   Only asking this because 2 of 3 of the locations have the updated date of 6 
nov


1)  The old google docs site says 6 Nov = OK
https://docs.google.com/forms/d/e/1FAIpQLSe8BEcFGYsAOtClTkhQsLGJF3XolnmoJuP76foVRVK8BLMWyA/closedform
Deadline to submit is Monday, November 6 at 11:59 PM PT



2)  The new survey stated 6 Nov = OK
https://www.surveymonkey.com/r/ZNDY6MV
CFP Close: Monday, November 6, 2017, 11:59 PST


3)  ONAP Wiki

https://wiki.onap.org/display/DW/ONAP+Beijing+Release+Developer+Forum%2C+Dec.+11-13%2C+2017%2C+Santa+Clara%2C+CA+US
CFP Close: Tuesday, October 31, 2017, 11:59 PST


Refs
https://lists.onap.org/pipermail/onap-discuss/2017-October/005949.html





From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of DRAGOSH, PAMELA L (PAM)
Sent: Monday, October 30, 2017 15:13
To: Kenny Paul 
Cc: onap-discuss ; onap-tsc 

Subject: Re: [onap-tsc] F2F Dec option "hands-on" missing

Kenny,

Myself and a few other folks are going to submit a combination presentation and 
panel discussion. We’d like 2 hours in order for a few presentations to begin 
with and then have hour for panel discussion. Is it possible to change or can 
we just wing it with the current version?

Sorry to be a pain.

Pam


From: > 
on behalf of Michael O'Brien 
>
Date: Monday, October 30, 2017 at 3:10 PM
To: Kenny Paul >
Cc: onap-discuss 
>, onap-tsc 
>
Subject: [onap-tsc] F2F Dec option "hands-on" missing

Kenny,
   Hi, can we get the 3rd “hands-on” option returned to the f2f 
form – for today
 Thank you
  
https://www.surveymonkey.com/r/ZNDY6MV


Michael O’Brien
Amdocs Technology
16135955268
55268
[mdocs-a]

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 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfrqts] meeting record posted

2017-10-31 Thread WRIGHT, STEVEN A

VNFRQTS  project team meeting record posted on wiki at : 
https://wiki.onap.org/pages/viewpage.action?pageId=10783610


best regards
Steven Wright, MBA, PhD, JD.
[Tech Integration]
AT Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319
P: 470.415.3156

sw3...@att.com
www.linkedin.com/in/drstevenawright/

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration][dcae][multicloud] Testing the closed loop for vFW- cont.

2017-10-31 Thread Yunxia Chen

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Yunxia Chen:MAILTO:helen.c...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 ss:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:When: Tuesday\, October 31\, 2017 10:00 AM-12:00
  PM. (UTC-08:00) Pacific Time (US & Canada)\nWhere: https://zoom.us/j/4466
 66\n\n*~*~*~*~*~*~*~*~*~*\n\n  1.  Re-test the DCAE and Mutlticloud fi
 x with the changes made at 10/30.\n\n  2.  Then testing closed loop\n\n\n
SUMMARY;LANGUAGE=en-US:[integration][dcae][multicloud] Testing the closed l
 oop for vFW- cont.
DTSTART;TZID=Pacific Standard Time:20171031T10
DTEND;TZID=Pacific Standard Time:20171031T12
UID:82BE3DDD-C37B-4117-98D7-AEF8B5FC533D
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171031T155949Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/44
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115698672
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:TRUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] CSIT Jenkins jobs failed

2017-10-31 Thread Lando,Michael

Thank you for the answer.

So this means that once each project branches we will lose the abelty to use 
csit.

I think thia needs to be comunicated to guilds because we are being tracked by 
him regurding the state of our jobs.

 Original Message 
From: Gary Wu 
Date: Tue, Oct 31, 2017, 17:31
To: "Shlosberg, Yuli" 
CC: "Lando,Michael" , "Gitelman, Tal" 
, "Amit, Idan" , onap-discuss 

Subject: RE: CSIT Jenkins jobs failed

Hi Yuli,

The integration repo doesn’t have a “release-1.1.0” branch, so 
release-1.1.0-csit jobs would not work.

We’ll need to figure out a way to have CSIT support project branches given that 
every project may a different branch name.  Once we have this figured out we’ll 
update the community.

Thanks,
Gary

From: Shlosberg, Yuli [mailto:ys9...@intl.att.com]
Sent: Tuesday, October 31, 2017 8:23 AM
To: Gary Wu 
Cc: Lando,Michael ; Gitelman, Tal ; 
Amit, Idan 
Subject: RE: CSIT Jenkins jobs failed

Hi Gary,

Did you have a chance to take a look on below issue?

Thanks,
Yuli

From: Shlosberg, Yuli
Sent: Sunday, October 29, 2017 1:19 PM
To: 'gary.i...@huawei.com' >
Cc: Lando,Michael >; Gitelman, 
Tal >; Amit, Idan 
>
Subject: CSIT Jenkins jobs failed

Hi Gary,

Can you please help me, we start work with several “streams” e.g. master and 
release 1.1.0 but it seem that Jenkins jobs failed.
Could you please take a look on below job and advise what action should be 
taken?

https://jenkins.onap.org/view/CSIT/job/sdc-release-1.1.0-csit-nightly/7/


Also we have few jobs that even not started :

https://jenkins.onap.org/view/CSIT/job/sdc-release-1.1.0-verify-csit-nightly/
https://jenkins.onap.org/view/CSIT/job/sdc-release-1.1.0-csit-sanity/


Many thanks in advance,

Yuli Shlosberg
Software Engineer
AT Network Applications Development · SD
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] CSIT Jenkins jobs failed

2017-10-31 Thread Gary Wu

Hi Yuli,

The integration repo doesn't have a "release-1.1.0" branch, so 
release-1.1.0-csit jobs would not work.

We'll need to figure out a way to have CSIT support project branches given that 
every project may a different branch name.  Once we have this figured out we'll 
update the community.

Thanks,
Gary

From: Shlosberg, Yuli [mailto:ys9...@intl.att.com]
Sent: Tuesday, October 31, 2017 8:23 AM
To: Gary Wu 
Cc: Lando,Michael ; Gitelman, Tal ; 
Amit, Idan 
Subject: RE: CSIT Jenkins jobs failed

Hi Gary,

Did you have a chance to take a look on below issue?

Thanks,
Yuli

From: Shlosberg, Yuli
Sent: Sunday, October 29, 2017 1:19 PM
To: 'gary.i...@huawei.com' >
Cc: Lando,Michael >; Gitelman, 
Tal >; Amit, Idan 
>
Subject: CSIT Jenkins jobs failed

Hi Gary,

Can you please help me, we start work with several "streams" e.g. master and 
release 1.1.0 but it seem that Jenkins jobs failed.
Could you please take a look on below job and advise what action should be 
taken?

https://jenkins.onap.org/view/CSIT/job/sdc-release-1.1.0-csit-nightly/7/


Also we have few jobs that even not started :

https://jenkins.onap.org/view/CSIT/job/sdc-release-1.1.0-verify-csit-nightly/
https://jenkins.onap.org/view/CSIT/job/sdc-release-1.1.0-csit-sanity/


Many thanks in advance,

Yuli Shlosberg
Software Engineer
AT Network Applications Development * SD
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfrqts] NCSP OS requirement discussion thread

2017-10-31 Thread WRIGHT, STEVEN A

>From today's project team call we had a discussion on some text deleted in 
>[Change 20089 - Merged]. We ran out of time 
>on the call, so this thread is to collect the followup discussion, so that we 
>can implement the decision after next week's call.

>From the discussion today we got to some proposed revised text, but with more 
>discussion needed:

{NCSPs could require that VNFs should use the NCSP's standard set of OS images 
to enable
compliance with security, audit, regulatory and other needs.} more discussion 
needed.

NB this text is from the VNF Guidelines document which was agreed to be 
general, aspirational an future oriented. So the objective here is to provide 
some general guidance to VNF developers here not a conformance requirement.

best regards
Steven Wright, MBA, PhD, JD.
[Tech Integration]
AT Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319
P: 470.415.3156

sw3...@att.com
www.linkedin.com/in/drstevenawright/

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Canceled event: [appc] Weekly Meeting @ Wed Nov 1, 2017 8am - 9am (PDT) (onap-discuss@lists.onap.org)

2017-10-31 Thread kpaul

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20171101T11
DTEND;TZID=America/New_York:20171101T12
DTSTAMP:20171031T150532Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:r023555rn4asffmqhvhrpqj8sg_r20170809t150...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0;X-RESPONSE-COMMENT="davidk@radcom.
 com":mailto:onap-discuss@lists.onap.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=cl
 6...@intl.att.com;X-NUM-GUESTS=0:mailto:cl6...@intl.att.com
RECURRENCE-ID;TZID=America/New_York:20171101T11
CLASS:PUBLIC
CREATED:20170620T150432Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 4 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/708562828\n\nOr iPhone one-tap (US Toll):  +14086380968\,\,708562828# o
 r +16465588656\,\,708562828#\n\nOr Telephone:\nDial: +1 408 638 0968 (U
 S Toll) or +1 646 558 8656 (US Toll)\n+1 855 880 1246 (US Toll Free)\n 
+1 877 369 0926 (US Toll Free)\nMeeting ID: 708 562 828\nInterna
 tional numbers available: https://zoom.us/zoomconference?m=nOkqgtoJBOGo7SuF
 C0OvOat13V5cLneM\n\n
LAST-MODIFIED:20171031T150531Z
LOCATION:https://zoom.us/j/708562828
SEQUENCE:2
STATUS:CANCELLED
SUMMARY:[appc] Weekly Meeting
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] SDC sdk versions

2017-10-31 Thread Seshu m

Michael Lando,

Updated for the SO, we too are using the SNAPSHOT versions.
This is currently blocking the SO docker build. Raised a bug to track the 
issue, SDC-561.

Best Regards,
Seshu
**
 This email and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained here in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: TIMONEY, DAN [dt5...@att.com]
Sent: Tuesday, October 31, 2017 9:26 PM
To: LANDO, MICHAEL; DAUGHERTY, ROBERT E; FORSYTH, JAMES; JI, LUSHENG; SONSINO, 
OFIR; MAHER, RANDA; Seshu m
Cc: LEFEVRE, CATHERINE; FREEMAN, BRIAN D; UNO, LARRY; 
onap-discuss@lists.onap.org
Subject: Re: SDC sdk versions

Michael,

I filled in the SDNC info below.  Note – we’re still using SNAPSHOT versions, 
so if there is a release version we can use instead, that would be great.

Thanks!
Dan

Dan Timoney
Principal Technical Staff Member
AT
Email : dtimo...@att.com
Office : +1 (732) 420-3226
Mobile : +1 (201) 960-1211
200 S Laurel Ave, Rm E2-2A03
Middletown, NJ 08873

From: "LANDO, MICHAEL" 
Date: Tuesday, October 31, 2017 at 8:09 AM
To: "TIMONEY, DAN" , "DAUGHERTY, ROBERT E" , 
"FORSYTH, JAMES" , "JI, LUSHENG" , 
"SONSINO, OFIR" , "MAHER, RANDA" , Seshu m 

Cc: "LEFEVRE, CATHERINE" , "FREEMAN, BRIAN D" 
, "UNO, LARRY" , 
"onap-discuss@lists.onap.org" 
Subject: SDC sdk versions

Hi,
I am trying to validate what version of the SDC dependency you are using so 
that I will be able to validate they are available as releases in LF please 
reply with the version your application is using.

>From what I know

  org.openecomp.sdc.sdc-distribution-client
  sdc-distribution-client


Users
Component

version

SO

 1.1.32-SNAPSHOT

SDNC

 1.1.32-SNAPSHOT

AA



DCAE



APPC






  org.openecomp.sdc.sdc-tosca
  sdc-tosca


Users
Component

version

SO

 1.1.32-SNAPSHOT

SDNC

 1.1.34-SNAPSHOT

VID








BR,

Michael Lando
Opensource TL , SDC
AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] SDC sdk versions

2017-10-31 Thread DAUGHERTY, ROBERT E

SO is using sdc-distribution-client 1.1.32 and sdc-tosca 1.1.34.
At least those are the versions we're trying to use.  Seshu is working on this 
right now.

From: SONSINO, OFIR
Sent: Tuesday, October 31, 2017 8:33 AM
To: LANDO, MICHAEL ; TIMONEY, DAN ; 
DAUGHERTY, ROBERT E ; FORSYTH, JAMES ; JI, 
LUSHENG ; MAHER, RANDA ; Seshu m 

Cc: LEFEVRE, CATHERINE ; FREEMAN, BRIAN D 
; UNO, LARRY ; 
onap-discuss@lists.onap.org
Subject: RE: SDC sdk versions

VID uses: sdc-tosca 1.1.32

Thanks,
Ofir

From: Lando,Michael
Sent: Tuesday, October 31, 2017 2:07 PM
To: TIMONEY, DAN >; DAUGHERTY, ROBERT E 
>; FORSYTH, JAMES 
>; JI, LUSHENG 
>; Sonsino, Ofir 
>; MAHER, RANDA 
>; Seshu m 
>
Cc: Lefevre, Catherine >; 
FREEMAN, BRIAN D >; UNO, LARRY 
>; 
onap-discuss@lists.onap.org
Subject: SDC sdk versions

Hi,
I am trying to validate what version of the SDC dependency you are using so 
that I will be able to validate they are available as releases in LF please 
reply with the version your application is using.

>From what I know

  org.openecomp.sdc.sdc-distribution-client
  sdc-distribution-client


Users
Component

version

SO



SDNC



AA



DCAE



APPC






  org.openecomp.sdc.sdc-tosca
  sdc-tosca


Users
Component

version

SO



SDNC



VID

1.1.32






BR,

Michael Lando
Opensource TL , SDC
AT Network Application Development * NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
***
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration][so][multi-cloud] How to configure OpenStack/Multi-cloud in SO ?

2017-10-31 Thread Kanagaraj Manickam

Dear Ethan,

We have Amsterdam ONAP installation in our lab and able to create Service and 
VNF but “VF module creation is failing” for vLB.
Assuming that it might be related to the configuration of  the multi-cloud or 
OpenStack details in SO.
Could you please help here? Thanks

Regards
Kanagaraj M

***
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**

***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [vnfsdk] - Docker packaging issues

2017-10-31 Thread Moshe Hoadley

Thanks a lot, indeed I missed that.
I was able to deploy it with docker-compose.

However, I had some problems compiling the projects due to problems in some pom 
files.
For example, in some poms, parent has a relative path of '../../oparent' 
however, the project file structure doesn't include it.

I changed the pom files and placed a gerrit review.
Could you please have a look at it? https://gerrit.onap.org/r/#/c/21463/

Thanks
Moshe Hoadley
* 972-9-77-62712
[cid:image001.png@01D2F989.346CD870]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Murali p
Sent: Tuesday, October 31, 2017 11:44 AM
To: Moshe Hoadley ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [vnfsdk] - Docker packaging issues

Moshe Hoadley,

Currently we use docker-compose to bring up both vnfmarket(FE-BE) dockers and 
PostGres DB docker.

The postgres-docker IP Address is passed to vnfmarket(FE-BE) docker 
dynamically(docker-compose) and before the docker is run, the JDBC string is 
changed to the postgres -docker IP address using docker-entry scripts.

The database connection, UI and backend works fine. Please let me know if you 
find any issues or have any suggestions.

FYI .. vnfmarket (refrepo) docker contains both front-end and backend.



With regards,
Murali

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Moshe Hoadley
Sent: 31 October 2017 12:47
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [vnfsdk] - Docker packaging issues

Hi
In addition, I found that the portal docker doesn't have access to the db 
docker.
After investigation I found that portal uses '172.0.0.1' in the db connection 
string - the db docker has a different IP even though they run on the same host.

The solution is to use a host name like 'marketdb' in the connection string and 
deploy the db container with the same name. docker will use its internal DNS to 
resolve the db docker ip.

With your permission I would like to go ahead and commit this fix.

Thanks
Moshe Hoadley
* 972-9-77-62712
[cid:image001.png@01D2F989.346CD870]

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Moshe Hoadley
Sent: Sunday, October 29, 2017 3:41 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [vnfsdk] - Docker packaging issues

Hi
I've started to play around with vnfsdk, I found that some .sh files contain a 
windows flavor end of file characters (CR LF).
Is it work in progress? If not, I would like to commit the fix for this issue.

Thanks
Moshe Hoadley
* 972-9-77-62712
[cid:image001.png@01D2F989.346CD870]

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
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 mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [vnfsdk] - Docker packaging issues

2017-10-31 Thread Murali p

Moshe Hoadley,

Currently we use docker-compose to bring up both vnfmarket(FE-BE) dockers and 
PostGres DB docker.

The postgres-docker IP Address is passed to vnfmarket(FE-BE) docker 
dynamically(docker-compose) and before the docker is run, the JDBC string is 
changed to the postgres -docker IP address using docker-entry scripts.

The database connection, UI and backend works fine. Please let me know if you 
find any issues or have any suggestions.

FYI .. vnfmarket (refrepo) docker contains both front-end and backend.



With regards,
Murali

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Moshe Hoadley
Sent: 31 October 2017 12:47
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [vnfsdk] - Docker packaging issues

Hi
In addition, I found that the portal docker doesn't have access to the db 
docker.
After investigation I found that portal uses '172.0.0.1' in the db connection 
string - the db docker has a different IP even though they run on the same host.

The solution is to use a host name like 'marketdb' in the connection string and 
deploy the db container with the same name. docker will use its internal DNS to 
resolve the db docker ip.

With your permission I would like to go ahead and commit this fix.

Thanks
Moshe Hoadley
* 972-9-77-62712
[cid:image001.png@01D2F989.346CD870]

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Moshe Hoadley
Sent: Sunday, October 29, 2017 3:41 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [vnfsdk] - Docker packaging issues

Hi
I've started to play around with vnfsdk, I found that some .sh files contain a 
windows flavor end of file characters (CR LF).
Is it work in progress? If not, I would like to commit the fix for this issue.

Thanks
Moshe Hoadley
* 972-9-77-62712
[cid:image001.png@01D2F989.346CD870]

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
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] The ticket SDC-533 was closed although the issue was not fixed, would you please check it?

2017-10-31 Thread Lando,Michael

It was closed by mistake I reopened it.





BR,

Michael Lando
Opensource TL , SDC
AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com

From: feng.yuanx...@zte.com.cn [mailto:feng.yuanx...@zte.com.cn]
Sent: Tuesday, October 31, 2017 3:35 AM
To: Lando,Michael 
Cc: onap-discuss@lists.onap.org; zhang.maope...@zte.com.cn; 
onap-discuss@lists.onap.org; ying.yunl...@zte.com.cn; fu.jin...@zte.com.cn
Subject: The ticket  SDC-533 was closed although the issue was not fixed, would 
you please check it?




SPGW 2:

  type: org.openecomp.resource.vf.Spgw

  metadata:

invariantUUID: 488587e7-051a-4fb8-9cd8-44738b3ef88c

UUID: e524a291-da5c-481f-9059-c0df2e375f73

customizationUUID: 17c4b1c0-6a5d-4988-b135-683affec6b0e

version: '0.2'

name: SPGW

description: SPGW

type: VF

category: Generic

subcategory: Network Elements

resourceVendor: zte

resourceVendorRelease: '1.0'

resourceVendorModelNumber: ''

  properties:

nf_naming:

  ecomp_generated_naming: true

availability_zone_max_count: 1

  requirements:

  - virtualLink:

  capability: tosca.capabilities.nfv.VirtualLinkable

  node: mgmt

  - virtualLink:

  capability: tosca.capabilities.nfv.VirtualLinkable

  node: OM



[cid:image001.png@01D3523C.C0119710]




原始邮件
发件人：冯远兴10034308
收件人： >;
抄送人： 
>;张茂鹏10030173;
日 期 ：2017年10月25日 16:40
主 题 ：About the lack of requirements labels in service template using SDC to 
design vEPC service, I've created a ticket SDC-533. If there's anthing I've not 
described clearly, don't hesitate to contact me. Thanks.






https://jira.onap.org/browse/SDC-533



1) Onboard 3rd-party VNF csar files in SDC catalog

2) Import VSP in order to import those 3rd-party VNFs

3) Design a vEPC service using those VNFs.  When I am trying to drag a link 
between SPGW node, which is a VNF, and external virtual link. I could choose 
the requirement of SPGW node as the picture below shows. However, after I 
export this vEPC service template, I can't find the name of the requirement in 
that template. All I've got in service template is just virtual_link while I 
need the exact name of requirements, ToOM instead.

During the period of instantiation, VF-C parses the NSD template and then 
passes the information to VNFM in order to instantiate VNF.

Because of this issue, VF-C can't get the correct names of requirements. 
Therefore VNFM can't get those names too. So VNFM does not know how to attach 
the connection points to the external virtual link.



SPGW:

  metadata:

  ...
  properties:

  ...
  requirements:
  - virtual_link:
capability: tosca.capabilities.nfv.VirtualLinkable
node: Control Network
  - virtual_link:
capability: tosca.capabilities.nfv.VirtualLinkable
node: Mgmt Network






___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [cli][lf] Create branch release 1.1.0 for onap/cli

2017-10-31 Thread Kanagaraj Manickam

Hi,

To enabled release artifact for Amsterdam release, I would like to create new
git branch release-1.1.0 for CLI (onap/cli) project and enable new jenkins jobs
under this branch to build following binaries and mark them as Amsterdam
release candidate.
(I assume that existing Jenkins jobs will not get affected and will continuous
produce these artifacts from master branch, and let me know otherwise).

1. NEXUS artifact zip: org.onap.cli :: cli-zip :: 1.1.0

2. Docker container image: onap/cli (tag: 1.1.0)

3. Document

4. Sonar

5. CSIT

Could you please help ? Thank you.

Regards
Kanagaraj M
ONAP-CLI-PTL

***
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**

***
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient(s) is prohibited. If you receive
this e-mail in error, please notify the sender by phone or email immediately
and delete it!
***

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [vnfsdk] - Docker packaging issues

2017-10-31 Thread Moshe Hoadley

Hi
In addition, I found that the portal docker doesn't have access to the db 
docker.
After investigation I found that portal uses '172.0.0.1' in the db connection 
string - the db docker has a different IP even though they run on the same host.

The solution is to use a host name like 'marketdb' in the connection string and 
deploy the db container with the same name. docker will use its internal DNS to 
resolve the db docker ip.

With your permission I would like to go ahead and commit this fix.

Thanks
Moshe Hoadley
* 972-9-77-62712
[cid:image001.png@01D2F989.346CD870]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Moshe Hoadley
Sent: Sunday, October 29, 2017 3:41 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [vnfsdk] - Docker packaging issues

Hi
I've started to play around with vnfsdk, I found that some .sh files contain a 
windows flavor end of file characters (CR LF).
Is it work in progress? If not, I would like to commit the fix for this issue.

Thanks
Moshe Hoadley
* 972-9-77-62712
[cid:image001.png@01D2F989.346CD870]

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 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration][holmes] VoLTE use case integration test with Holmes

Re: [onap-discuss] compile about aai-spark-fe

[onap-discuss] [ONAP Helpdesk #47527] [DOC] Documentation RTD Build Reaching the Default Time/Memory Quota

Re: [onap-discuss] CSIT Jenkins jobs failed

Re: [onap-discuss] CSIT Jenkins jobs failed

Re: [onap-discuss] CSIT Jenkins jobs failed

[onap-discuss] [ONAP Helpdesk #47650] [cli][lf] Create branch release 1.1.0 for onap/cli

[onap-discuss] Demo cert for AAI expires on 30 Nov

Re: [onap-discuss] [onap-tsc] F2F Dec - submission date extended to 6 Nov on (2 of 3 sites). Confirmation?

[onap-discuss] [vnfrqts] meeting record posted

[onap-discuss] [integration][dcae][multicloud] Testing the closed loop for vFW- cont.

Re: [onap-discuss] CSIT Jenkins jobs failed

Re: [onap-discuss] CSIT Jenkins jobs failed

[onap-discuss] [vnfrqts] NCSP OS requirement discussion thread

[onap-discuss] Canceled event: [appc] Weekly Meeting @ Wed Nov 1, 2017 8am - 9am (PDT) (onap-discuss@lists.onap.org)

Re: [onap-discuss] SDC sdk versions

Re: [onap-discuss] SDC sdk versions

[onap-discuss] [integration][so][multi-cloud] How to configure OpenStack/Multi-cloud in SO ?

Re: [onap-discuss] [vnfsdk] - Docker packaging issues

Re: [onap-discuss] [vnfsdk] - Docker packaging issues

Re: [onap-discuss] The ticket SDC-533 was closed although the issue was not fixed, would you please check it?

[onap-discuss] [cli][lf] Create branch release 1.1.0 for onap/cli

Re: [onap-discuss] [vnfsdk] - Docker packaging issues

23 matches

Site Navigation

Mail list logo

Footer information