date:20180220

Re: [onap-discuss] [E] SDC VSP csar validation failed with error : null

2018-02-20 Thread Dhandapani, Karthikeyan via onap-discuss

Hi Ramu, Good Day !


The below command can be used for Validate CSAR file.
*vnfsdk csar-validate *
Please refer VNF Package tool link



I am facing problem in uploading CSAR File.

I created CSAR file using  "vnfsdk csar-create -d pa.csar --manifest pa.mf
--history history.txt --test Tests --licenses Licenses FirstVNF/ pa.yaml
and after extracting the CSAR ,the folder structure  looks like below

[image: Inline image 1]


While uploading I am getting below error :
[image: Inline image 2]



I have attached my pa.mf and generated TOSCA.meta file.
Could you please let me know if I am missing something ?.

It will be nice if you could share any links that you used for packaging
CSAR.



Thanks,
Karthik,
Verizon







On Fri, Feb 16, 2018 at 9:17 PM, Akula, Ramanjaneyul Reddy (Nokia -
US/Irving)  wrote:

> Hi SDC Team,
>
>   I’m trying to upload the CSAR file to SDC as part of VSP creation.
>
> Upload is successful.
>
>
>
> However when I try to validate it, I see below error.
>
>
>
>
>
>
>
> And I tried to scan through all the error logs within SDC VM. And didn’t
> get any clue out of it.
>
>
>
> Would you please let me know if there is any offline tool to validate the
> CSAR file.
>
>
>
>
>
> *Thanks & best regards,*
>
> *Ramu*
>
>
>
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=
> udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=
> GdaEPId9hKYMtPXKV15dbs9kz3xYUs7snO4l8n0bqo1PnH4S-bP4ZuW1dWGrRoOf=
> iJZ58Pya8pHezntOIvuLLbIzgZHDA4HNVvegIeuyh5c=3aE60B6hv7Txv1ikHal-F6i-
> 0l4HMFv1dZyW94Tbc_0=
>
>
Manifest-Version: 1.0
CSAR-Version: 1.0
Created-By: Karthik
Entry-Service-Template: pa.yaml
Sealed: false
source: pa.yaml
source: images/PA_8.0
source: Licences/LICENSE.TXT
source: Tests/test
source: history.txt
CSAR-Version: '1.1'
Created-By: ONAP
Entry-Change-Log: history.txt
Entry-Definitions: pa.yaml
Entry-Licenses: Licenses
Entry-Manifest: pa.mf
Entry-Tests: Tests
TOSCA-Meta-File-Version: '1.0'
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] [modeling] Beijing Release new functional requirements

2018-02-20 Thread Vul, Alex

Hi Michela,

Regarding HPA in particular This is a functional requirement at cuts across 
multiple use cases in support hardware optimized VNFs. HPA has been part of the 
IFA model starting with v2.3.1 of the IFA specification.

I have integrated the HPA related changes from the IFA IM into the latest 
stable version of the OASIS TOSCA NFV Profile. I have also done the same with 
the SOL001 specification that we will be working on in Nice next week.

I guess I am not sure what you mean by "analysis on-going" with respect to this 
item, given that it's slated for initial delivery into R2. Observe that the 
ONAP information model that we have been working on reflects the HPA changes 
based on the ETSI IFA specification as well.

Alex Vul
Intel Corporation


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Michela Bevilacqua
Sent: Tuesday, February 20, 2018 8:12 PM
To: denghui (L) ; onap-discuss@lists.onap.org; 
onap-...@lists.onap.org P 
Subject: Re: [onap-tsc] [modeling] Beijing Release new functional requirements

Hi,
In the context of Beijing release, it could be good to have some more inputs 
about possible ONAP IM and ONAP TOSCA DM impacts/expectations in relation to 
the new functional requirements:
1)  HPA: discussions progressed, analysis is ongoing
2)  Change Management: no input
3)  Scaling: no input
4)  PNF: no input


Can we add this point in agenda for the next modeling subcommittee meeting and 
ensure inputs from use case committee or from different reference functional 
requirement area ?

BR
Michela


From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of denghui (L)
Sent: den 14 februari 2018 04:46
To: onap-discuss@lists.onap.org; 
onap-...@lists.onap.org P 
>
Subject: [onap-tsc] [modeling] 20180213 modeling subcommittee Meeting Minutes

Hello all

Modeling subcommittee has been questioned when will our modeling DM spec come 
out, below are our meeting minutes this week.

Hi Kenny, We are going to cancel next week modeling subcommittee call due to 
china new year, thanks a lot for your help

-
20180213 modeling subcommittee Meeting agenda and Minutes
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings

1)  Resource IM YANG Xu
there is no consensus whether we need to follow ETSI NFV naming convention or 
change into ONAP naming.
Two polls will be set to decide the naming convention and future meeting time. 
The polls close on Feb 28th.
https://wiki.onap.org/display/DW/Meeting+Time+Poll
https://wiki.onap.org/display/DW/Naming+Convention+Poll

2)  Data modeling Anatoly Katzman
DENG Hui: modeling subcommittee have to finalize the 1st draft version by M3 
deadline, in this case, we need to allow solutions only 1 week, and make the 
decision on Feb. 28th.
DENG Hui: there are two solutions on the table now: Monolithic VDU design and 
TOSCA NFV profile, we are not make decision today, but would get basic impress 
what company would like to follow:
Vendors:
1) Ericsson  vote for  of ETSI NFV Profile
2) ZTE   vote for  ETSI SOL NFV profile
3) Huawei vote for  ETSI NFV profile
4) Nokia --no one on call
5) Netcracker (Priya TG) vote for ETSI NFV Profile
Operators:
1) AT: Monolithic VDU
2) China Mobile: lacking information to do an informed comparison hence no 
strong opinion to any specific proposal currently. The options on the table 
should firstly meet the requirement as a unified DM in the community with 
consistency to the IM and implementable in Beijing release cadence with vendors 
support. It would be better if we could align with SDO in the same time.
Next step:
a) check whether we have 3rd solution or not in a week
b) make decision on Feb.27th

3) Modeling tool poll(Jessie)
1) use github for papyrus revision
fine from IM's team (Kevin, Andy, Lingli, and YANG Xu)
Anyway, polling will end by the end of Feb.

Best regards,

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

Re: [onap-discuss] [onap-tsc] [modeling] Beijing Release new functional requirements

2018-02-20 Thread Michela Bevilacqua

Hi,
In the context of Beijing release, it could be good to have some more inputs 
about possible ONAP IM and ONAP TOSCA DM impacts/expectations in relation to 
the new functional requirements:

  1.  HPA: discussions progressed, analysis is ongoing
  2.  Change Management: no input
  3.  Scaling: no input
  4.  PNF: no input


Can we add this point in agenda for the next modeling subcommittee meeting and 
ensure inputs from use case committee or from different reference functional 
requirement area ?

BR
Michela


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of denghui (L)
Sent: den 14 februari 2018 04:46
To: onap-discuss@lists.onap.org; onap-...@lists.onap.org P 

Subject: [onap-tsc] [modeling] 20180213 modeling subcommittee Meeting Minutes

Hello all

Modeling subcommittee has been questioned when will our modeling DM spec come 
out, below are our meeting minutes this week.

Hi Kenny, We are going to cancel next week modeling subcommittee call due to 
china new year, thanks a lot for your help

-
20180213 modeling subcommittee Meeting agenda and Minutes
https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings

1)  Resource IM YANG Xu
there is no consensus whether we need to follow ETSI NFV naming convention or 
change into ONAP naming.
Two polls will be set to decide the naming convention and future meeting time. 
The polls close on Feb 28th.
https://wiki.onap.org/display/DW/Meeting+Time+Poll
https://wiki.onap.org/display/DW/Naming+Convention+Poll

2)  Data modeling Anatoly Katzman
DENG Hui: modeling subcommittee have to finalize the 1st draft version by M3 
deadline, in this case, we need to allow solutions only 1 week, and make the 
decision on Feb. 28th.
DENG Hui: there are two solutions on the table now: Monolithic VDU design and 
TOSCA NFV profile, we are not make decision today, but would get basic impress 
what company would like to follow:
Vendors:
1) Ericsson  vote for  of ETSI NFV Profile
2) ZTE   vote for  ETSI SOL NFV profile
3) Huawei vote for  ETSI NFV profile
4) Nokia --no one on call
5) Netcracker (Priya TG) vote for ETSI NFV Profile
Operators:
1) AT: Monolithic VDU
2) China Mobile: lacking information to do an informed comparison hence no 
strong opinion to any specific proposal currently. The options on the table 
should firstly meet the requirement as a unified DM in the community with 
consistency to the IM and implementable in Beijing release cadence with vendors 
support. It would be better if we could align with SDO in the same time.
Next step:
a) check whether we have 3rd solution or not in a week
b) make decision on Feb.27th

3) Modeling tool poll(Jessie)
1) use github for papyrus revision
fine from IM's team (Kevin, Andy, Lingli, and YANG Xu)
Anyway, polling will end by the end of Feb.

Best regards,

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

[onap-discuss] COE meeting of Feb 26, 2018 will be chair by Bin Hu or skipped. (was Re: Invitation: [coe] Weekly (updated Jan 12, 2018) @ Weekly from 10am to 11am on Tuesday from Tue Jan 16 to Tue Dec

2018-02-20 Thread Isaku Yamahata

Hello.

COE meeting on Feb 26, 2018: Bin Hu may chair it if we have major issue.

Isaku would be absent because he's attending OpenStack PTG.
BTW, does anyone attend OpenStack PTG?

thanks,


On Sat, Jan 13, 2018 at 12:41:38AM +,
kp...@linuxfoundation.org wrote:

> You have been invited to the following event.
> 
> Title: [coe] Weekly (updated Jan 12, 2018)
> Hi there,
> 
> ONAP Meeting 5 is inviting you to a scheduled Zoom meeting.
> 
> Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/961993336
> 
> Or iPhone one-tap :
> US: +16465588656,,961993336#  or +16699006833,,961993336#
> Or Telephone:
> Dial(for higher quality, dial a number based on your current location):
> US: +1 646 558 8656  or +1 669 900 6833  or +1 855 880 1246 (Toll
> Free) or +1 877 369 0926 (Toll Free)
> Meeting ID: 961 993 336
> International numbers available:
> https://zoom.us/zoomconference?m=NyDGIiAbPmpKt_zpBGMCPXUZ8OTi9LqS
> 
> 
> When: Weekly from 10am to 11am on Tuesday from Tue Jan 16 to Tue Dec 25
> Pacific Time
> Where: https://zoom.us/j/961993336
> Calendar: onap-discuss@lists.onap.org
> Who:
> * kp...@linuxfoundation.org - creator
> * isaku yamahata
> * onap-discuss@lists.onap.org
> 
> Event details: 
> https://www.google.com/calendar/event?action=VIEW=MDRhdTIycGJyZmxkY3FsZHV2aTNsbjVvdGMgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tYjU4MzNmNGUwMjFjM2M4ZGJhNzJlNGMzODMyZjE5ZmI0Mzc1YmI3Zg=America/Los_Angeles=en
> 
> Invitation from Google Calendar: https://www.google.com/calendar/
> 
> You are receiving this courtesy email at the account
> onap-discuss@lists.onap.org because you are an attendee of this event.
> 
> To stop receiving future updates for this event, decline this event.
> Alternatively you can sign up for a Google account at
> https://www.google.com/calendar/ and control your notification settings for
> your entire calendar.
> 
> Forwarding this invitation could allow any recipient to modify your RSVP
> response. Learn more at
> https://support.google.com/calendar/answer/37135#forwarding


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


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

[onap-discuss] vCPE: Matching VNF names with Services

2018-02-20 Thread Arun Arora (c)

Hi All,

I am going through the vCPE use-case and have a doubt in matching the VNF 
templates available in the Demo repo with the services mentioned in the vCPE 
use case wiki.
Following is the table which I need to fix the match in. Can anyone with prior 
info help in this.


VNF Name

Description

Service Name

infra



GenInfra Service

vbng



vBngInfra Service

vbrgemu

Bridged Residential Gateway Emulator

BRG_EMU Service

vgmux



BNG_MUX

vgw



vGMuxInfra Service



With Regards,
Arun Arora
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

2018-02-20 Thread HERNANDEZ-HERRERO, JORGE

Hi Bharath, you should be able to do all operations within the drools 
container, try this:

docker exec -it drools bash
cd /tmp
wget 
https://git.onap.org/policy/drools-applications/tree/controlloop/packages/apps/src/files/apps-installer
(may have to tweak it to go through proxy)
chmod +x apps-installer
./apps-installer
policy stop
policy start

You can also verify with telemetry shell (as an alternative to curl commands), 
if the controller was stoop up ok:

telemetry
cd controllers/amsterdam/drools
get

if all ok, should see maven coordinates attached in the json output.

Jorge

From: bharath thiruveedula [mailto:bharath_...@hotmail.com]
Sent: Tuesday, February 20, 2018 12:34 PM
To: HERNANDEZ-HERRERO, JORGE ; onap-discuss@lists.onap.org; 
DRAGOSH, PAM ; liam.fal...@ericsson.com; Kranthi 
Guttikonda 
Subject: Re: [Policy] Empty policies in Standalone mode


Hi Jorge,



Do you mean to run apps-installer file in drools container and restart the 
drools container?

Is that my understanding right?



Best Regards

Bharath T


From: HERNANDEZ-HERRERO, JORGE >
Sent: Tuesday, February 20, 2018 11:53 PM
To: bharath thiruveedula; 
onap-discuss@lists.onap.org; DRAGOSH, PAM; 
liam.fal...@ericsson.com; Kranthi Guttikonda
Subject: RE: [Policy] Empty policies in Standalone mode


Hi Bharat,



Yes, proxy issue seems like, collecting the dependencies.



Can you try to see you can get out through proxy with linux shell, by running 
this script:

https://git.onap.org/policy/drools-applications/tree/controlloop/packages/apps/src/files/apps-installer

If that works, restart pdp-d, that should cached the dependent jars in the 
local maven repo.



Jorge



From: bharath thiruveedula [mailto:bharath_...@hotmail.com]
Sent: Tuesday, February 20, 2018 12:04 PM
To: HERNANDEZ-HERRERO, JORGE >; 
onap-discuss@lists.onap.org; DRAGOSH, PAM 
>; 
liam.fal...@ericsson.com; Kranthi Guttikonda 
>
Subject: Re: [Policy] Empty policies in Standalone mode





Hi Jorge,



I have tried the same with the policy VM in original ONAP setup I got the same 
output. After adding proxy, now I am facing the following error in drools 
container

[name=amsterdam, alive=false, locked=false, droolsController=null]: cannot 
init-drools because of 
org.eclipse.aether.collection.DependencyCollectionException: Failed to collect 
dependencies at 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0 -> 
org.onap.policy.drools-applications:events:jar:1.1.3
java.lang.RuntimeException: 
org.eclipse.aether.collection.DependencyCollectionException: Failed to collect 
dependencies at 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0 -> 
org.onap.policy.drools-applications:events:jar:1.1.3
at 
org.kie.scanner.MavenRepository.getArtifactDependecies(MavenRepository.java:121)
at 
org.kie.scanner.ArtifactResolver.getArtifactDependecies(ArtifactResolver.java:72)
at 
org.kie.scanner.KieRepositoryScannerImpl.buildArtifact(KieRepositoryScannerImpl.java:170)
at 
org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:127)
at 
org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:122)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.loadKieModuleFromMavenRepo(KieRepositoryImpl.java:154)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:140)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:117)
at 
org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:184)
at 
org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:172)
at org.onap.policy.drools.core.PolicyContainer.(PolicyContainer.java:117)
at org.onap.policy.drools.core.PolicyContainer.(PolicyContainer.java:91)
at 
org.onap.policy.drools.controller.internal.MavenDroolsController.(MavenDroolsController.java:143)
at

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

2018-02-20 Thread bharath thiruveedula

Hi Jorge,


Do you mean to run apps-installer file in drools container and restart the 
drools container?

Is that my understanding right?


Best Regards

Bharath T


From: HERNANDEZ-HERRERO, JORGE 
Sent: Tuesday, February 20, 2018 11:53 PM
To: bharath thiruveedula; onap-discuss@lists.onap.org; DRAGOSH, PAM; 
liam.fal...@ericsson.com; Kranthi Guttikonda
Subject: RE: [Policy] Empty policies in Standalone mode


Hi Bharat,



Yes, proxy issue seems like, collecting the dependencies.



Can you try to see you can get out through proxy with linux shell, by running 
this script:

https://git.onap.org/policy/drools-applications/tree/controlloop/packages/apps/src/files/apps-installer

If that works, restart pdp-d, that should cached the dependent jars in the 
local maven repo.



Jorge



From: bharath thiruveedula [mailto:bharath_...@hotmail.com]
Sent: Tuesday, February 20, 2018 12:04 PM
To: HERNANDEZ-HERRERO, JORGE ; onap-discuss@lists.onap.org; 
DRAGOSH, PAM ; liam.fal...@ericsson.com; Kranthi 
Guttikonda 
Subject: Re: [Policy] Empty policies in Standalone mode





Hi Jorge,



I have tried the same with the policy VM in original ONAP setup I got the same 
output. After adding proxy, now I am facing the following error in drools 
container

[name=amsterdam, alive=false, locked=false, droolsController=null]: cannot 
init-drools because of 
org.eclipse.aether.collection.DependencyCollectionException: Failed to collect 
dependencies at 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0 -> 
org.onap.policy.drools-applications:events:jar:1.1.3
java.lang.RuntimeException: 
org.eclipse.aether.collection.DependencyCollectionException: Failed to collect 
dependencies at 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0 -> 
org.onap.policy.drools-applications:events:jar:1.1.3
at 
org.kie.scanner.MavenRepository.getArtifactDependecies(MavenRepository.java:121)
at 
org.kie.scanner.ArtifactResolver.getArtifactDependecies(ArtifactResolver.java:72)
at 
org.kie.scanner.KieRepositoryScannerImpl.buildArtifact(KieRepositoryScannerImpl.java:170)
at 
org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:127)
at 
org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:122)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.loadKieModuleFromMavenRepo(KieRepositoryImpl.java:154)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:140)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:117)
at 
org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:184)
at 
org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:172)
at org.onap.policy.drools.core.PolicyContainer.(PolicyContainer.java:117)
at org.onap.policy.drools.core.PolicyContainer.(PolicyContainer.java:91)
at 
org.onap.policy.drools.controller.internal.MavenDroolsController.(MavenDroolsController.java:143)
at 
org.onap.policy.drools.controller.IndexedDroolsControllerFactory.build(DroolsControllerFactory.java:412)
at 
org.onap.policy.drools.controller.IndexedDroolsControllerFactory.build(DroolsControllerFactory.java:193)
at 
org.onap.policy.drools.system.internal.AggregatedPolicyController.initDrools(AggregatedPolicyController.java:145)
at 
org.onap.policy.drools.system.internal.AggregatedPolicyController.(AggregatedPolicyController.java:130)
at 
org.onap.policy.drools.system.IndexedPolicyControllerFactory.build(PolicyControllerFactory.java:225)
at 
org.onap.policy.drools.system.PolicyEngineManager.createPolicyController(PolicyEngine.java:563)
at org.onap.policy.drools.system.Main.main(Main.java:134)
Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed 
to collect dependencies at 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0 -> 
org.onap.policy.drools-applications:events:jar:1.1.3
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291)
at 
org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316)
at 
org.kie.scanner.MavenRepository.getArtifactDependecies(MavenRepository.java:119)
... 19 common frames omitted
Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to 
read artifact descriptor for 
org.onap.policy.drools-applications:events:jar:1.1.3
at

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

2018-02-20 Thread HERNANDEZ-HERRERO, JORGE

Hi Bharat,

Yes, proxy issue seems like, collecting the dependencies.

Can you try to see you can get out through proxy with linux shell, by running 
this script:

https://git.onap.org/policy/drools-applications/tree/controlloop/packages/apps/src/files/apps-installer

If that works, restart pdp-d, that should cached the dependent jars in the 
local maven repo.

Jorge

From: bharath thiruveedula [mailto:bharath_...@hotmail.com]
Sent: Tuesday, February 20, 2018 12:04 PM
To: HERNANDEZ-HERRERO, JORGE ; onap-discuss@lists.onap.org; 
DRAGOSH, PAM ; liam.fal...@ericsson.com; Kranthi 
Guttikonda 
Subject: Re: [Policy] Empty policies in Standalone mode




Hi Jorge,



I have tried the same with the policy VM in original ONAP setup I got the same 
output. After adding proxy, now I am facing the following error in drools 
container

[name=amsterdam, alive=false, locked=false, droolsController=null]: cannot 
init-drools because of 
org.eclipse.aether.collection.DependencyCollectionException: Failed to collect 
dependencies at 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0 -> 
org.onap.policy.drools-applications:events:jar:1.1.3
java.lang.RuntimeException: 
org.eclipse.aether.collection.DependencyCollectionException: Failed to collect 
dependencies at 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0 -> 
org.onap.policy.drools-applications:events:jar:1.1.3
at 
org.kie.scanner.MavenRepository.getArtifactDependecies(MavenRepository.java:121)
at 
org.kie.scanner.ArtifactResolver.getArtifactDependecies(ArtifactResolver.java:72)
at 
org.kie.scanner.KieRepositoryScannerImpl.buildArtifact(KieRepositoryScannerImpl.java:170)
at 
org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:127)
at 
org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:122)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.loadKieModuleFromMavenRepo(KieRepositoryImpl.java:154)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:140)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:117)
at 
org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:184)
at 
org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:172)
at org.onap.policy.drools.core.PolicyContainer.(PolicyContainer.java:117)
at org.onap.policy.drools.core.PolicyContainer.(PolicyContainer.java:91)
at 
org.onap.policy.drools.controller.internal.MavenDroolsController.(MavenDroolsController.java:143)
at 
org.onap.policy.drools.controller.IndexedDroolsControllerFactory.build(DroolsControllerFactory.java:412)
at 
org.onap.policy.drools.controller.IndexedDroolsControllerFactory.build(DroolsControllerFactory.java:193)
at 
org.onap.policy.drools.system.internal.AggregatedPolicyController.initDrools(AggregatedPolicyController.java:145)
at 
org.onap.policy.drools.system.internal.AggregatedPolicyController.(AggregatedPolicyController.java:130)
at 
org.onap.policy.drools.system.IndexedPolicyControllerFactory.build(PolicyControllerFactory.java:225)
at 
org.onap.policy.drools.system.PolicyEngineManager.createPolicyController(PolicyEngine.java:563)
at org.onap.policy.drools.system.Main.main(Main.java:134)
Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed 
to collect dependencies at 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0 -> 
org.onap.policy.drools-applications:events:jar:1.1.3
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291)
at 
org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316)
at 
org.kie.scanner.MavenRepository.getArtifactDependecies(MavenRepository.java:119)
... 19 common frames omitted
Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to 
read artifact descriptor for 
org.onap.policy.drools-applications:events:jar:1.1.3
at 
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
at 
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:217)
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.resolveCachedArtifactDescriptor(DefaultDependencyCollector.java:525)
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.getArtifactDescriptorResult(DefaultDependencyCollector.java:509)
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:409)
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363)
at

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

2018-02-20 Thread bharath thiruveedula


Hi Jorge,


I have tried the same with the policy VM in original ONAP setup I got the same 
output. After adding proxy, now I am facing the following error in drools 
container

[name=amsterdam, alive=false, locked=false, droolsController=null]: cannot 
init-drools because of 
org.eclipse.aether.collection.DependencyCollectionException: Failed to collect 
dependencies at 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0 -> 
org.onap.policy.drools-applications:events:jar:1.1.3
java.lang.RuntimeException: 
org.eclipse.aether.collection.DependencyCollectionException: Failed to collect 
dependencies at 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0 -> 
org.onap.policy.drools-applications:events:jar:1.1.3
at 
org.kie.scanner.MavenRepository.getArtifactDependecies(MavenRepository.java:121)
at 
org.kie.scanner.ArtifactResolver.getArtifactDependecies(ArtifactResolver.java:72)
at 
org.kie.scanner.KieRepositoryScannerImpl.buildArtifact(KieRepositoryScannerImpl.java:170)
at 
org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:127)
at 
org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:122)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.loadKieModuleFromMavenRepo(KieRepositoryImpl.java:154)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:140)
at 
org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:117)
at 
org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:184)
at 
org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:172)
at org.onap.policy.drools.core.PolicyContainer.(PolicyContainer.java:117)
at org.onap.policy.drools.core.PolicyContainer.(PolicyContainer.java:91)
at 
org.onap.policy.drools.controller.internal.MavenDroolsController.(MavenDroolsController.java:143)
at 
org.onap.policy.drools.controller.IndexedDroolsControllerFactory.build(DroolsControllerFactory.java:412)
at 
org.onap.policy.drools.controller.IndexedDroolsControllerFactory.build(DroolsControllerFactory.java:193)
at 
org.onap.policy.drools.system.internal.AggregatedPolicyController.initDrools(AggregatedPolicyController.java:145)
at 
org.onap.policy.drools.system.internal.AggregatedPolicyController.(AggregatedPolicyController.java:130)
at 
org.onap.policy.drools.system.IndexedPolicyControllerFactory.build(PolicyControllerFactory.java:225)
at 
org.onap.policy.drools.system.PolicyEngineManager.createPolicyController(PolicyEngine.java:563)
at org.onap.policy.drools.system.Main.main(Main.java:134)
Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed 
to collect dependencies at 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0 -> 
org.onap.policy.drools-applications:events:jar:1.1.3
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291)
at 
org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316)
at 
org.kie.scanner.MavenRepository.getArtifactDependecies(MavenRepository.java:119)
... 19 common frames omitted
Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to 
read artifact descriptor for 
org.onap.policy.drools-applications:events:jar:1.1.3
at 
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
at 
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:217)
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.resolveCachedArtifactDescriptor(DefaultDependencyCollector.java:525)
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.getArtifactDescriptorResult(DefaultDependencyCollector.java:509)
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:409)
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363)
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351)
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:254)
... 21 common frames omitted
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not 
transfer artifact org.onap.policy.drools-applications:events:pom:1.1.3 from/to 
onap-staging (https://nexus.onap.org/content/repositories/staging/): connect 
timed out
at 
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
at 
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
at

[onap-discuss] UUI health-check amsterdam

2018-02-20 Thread Alexis de Talhouët

Hi UUI experts,

UUI health-check has been failing on amsterdam for a few weeks now, I could 
find that patch has changed the uri to use https://gerrit.onap.org/r/#/c/28431/ 

Amsterdam is giving 200 OK for /iui/usecase-ui/ and 502 for /iui/usecaseui/ so 
since this patch came in, it’s failing.

What should be the URI to use for amsterdam for this health-check ?

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

Re: [onap-discuss] [ccsdk][sdnc] Congratulations to our newest committer - Ryan Goulding

2018-02-20 Thread Ryan Goulding

Thanks very much Dan and SDNC/CCSDK teams!

Regards,

Ryan Goulding

On Tue, Feb 20, 2018 at 9:35 AM, VAN BRAKLE, TRACY L  wrote:

> CONGRATULATIONS RYAN !!!
>
> Tracy Van Brakle 
> AT Labs - Wireless Network Architecture and Design
> 732.420.3003  office
> 732.306.2387  cell
> 
> From: onap-discuss-boun...@lists.onap.org [onap-discuss-bounces@lists.
> onap.org] on behalf of TIMONEY, DAN
> Sent: Tuesday, February 20, 2018 9:32 AM
> To: onap-s...@lists.onap.org;  onap-discuss
> Subject: [onap-discuss] [ccsdk][sdnc] Congratulations to our newest
> committer - Ryan Goulding
>
> ***Security Advisory: This Message Originated Outside of AT ***
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
>
> CCSDK and SDNC team,
>
> It is with great pleasure that I announce that Ryan Goulding has been
> promoted to committer for the CCSDK and SDN projects.  Ryan has been a
> strong contributor to both our projects, and is also a strong contributor
> to OpenDaylight.  His expertise and hard work have been a huge asset to
> both our projects.
>
> Thank you, Ryan, for your many contributions!
>
> 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
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [E] Service Distribution and Service Deployment Issue on OOM Amsterdam release

2018-02-20 Thread Alexis de Talhouët

Hi, this issue is due to AAI model-loader component not working well at the 
time of the distribution. There is a window where model-loader tries to connect 
to sdc but fails because sdc is not yet up, hence model-loader is giving up. To 
fix this, bounce model-loader pod, re-deploy the service. Then all should be 
fine.

Alexis

> On Feb 20, 2018, at 10:49 AM, Thiruveedula, Bharath 
>  wrote:
> 
> Hi Vijayalakshmi,
> 
> Generally " Model-Version not found . " error is because of something wrong 
> in "model loader" in AAI. Check if model-loader container is up.
> 
> Are you running the OOM behind the proxy?
> 
> Best Regards
> Bharath T
> 
> 
> 
> On Sun, Feb 18, 2018 at 12:48 PM, Vijayalakshmi Hadimani 
> > wrote:
> Thanks Michael and Alexis for very detailed wiki and comprehensive demos .  
> 
>  
> 
> Continuing to Run Demo Vnf and DCAE Deployment on OOM Amsterdam release , I 
> am facing 2 Issues at Hand . I have tried rebuilding the pod and things 
> around it . but some how It is not helping .
> 
>  
> 
> Pls find the Onap-parameter.yaml attached .
> 
> The issue faced are Two .
> 
>  
> 
> a-   At the Time of deploying  the services below error is seen 
> .Indicating Model-Version not found .
> 
>  
> 
>  
> 
> 
> 
>  
> 
>  
> 
> b-  W.r.t to Service Distribution ,
> 
>   The artifcats are distributed to SO only  .It looks Like 
> there is no artifcats distribution happening between A . Any Pointer why 
> this could be happening and recommendation will be helpful .
> 
>  
> 
>  
> 
>  
> 
>  
> 
> 
> 
> ::DISCLAIMER::
> --
> The contents of this e-mail and any attachment(s) are confidential and 
> intended for the named recipient(s) only. E-mail transmission is not 
> guaranteed to be secure or error-free as information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses 
> in transmission. The e mail and its contents (with or without referred 
> errors) shall therefore not attach any liability on the originator or HCL or 
> its affiliates. Views or opinions, if any, presented in this email are solely 
> those of the author and may not necessarily reflect the views or opinions of 
> HCL or its affiliates. Any form of reproduction, dissemination, copying, 
> disclosure, modification, distribution and / or publication of this message 
> without the prior written consent of authorized representative of HCL is 
> strictly prohibited. If you have received this email in error please delete 
> it and notify the sender immediately. Before opening any email and/or 
> attachments, please check them for viruses and other defects.
> --
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw=O8fh9U8Fckd80BGFY5-_E1_3KnDPBdCVU17zX9uMrrQ=vQExGgI1FCnR5KLIwkrapYEJ3OEC12IIqWeqjKxbKTg=
>  
> 
> 
> 

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

Re: [onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

2018-02-20 Thread Kang Xi

Thanks. Then we pretty much have solved this problem. I’ll update the jira 
ticket accordingly.

Regards,
Kang

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Tuesday, February 20, 2018 11:11
To: Kang Xi ; FREEMAN, BRIAN D 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [integration] INT-261: Add standard utilities to 
all dockers (vim, ping, nslookup)

All the components in Heat already have ping-utils, vim and nslookup. Not sure 
about the Centos VMs for DCAE, need to check with Lusheng.

Marco

From: Kang Xi >
Date: Tuesday, February 20, 2018 at 11:02 AM
To: "PLATANIA, MARCO (MARCO)" 
>, BRIAN FREEMAN 
>
Cc: onap-discuss 
>
Subject: RE: [onap-discuss] [integration] INT-261: Add standard utilities to 
all dockers (vim, ping, nslookup)

Hi Marco,

I agree with you. Actually I did check the size and found the total is less 
than 5MB. Is there also an easy solution for heat?

Regards,
Kang

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Tuesday, February 20, 2018 10:58
To: Kang Xi >; FREEMAN, BRIAN D 
>
Cc: onap-discuss 
>
Subject: Re: [onap-discuss] [integration] INT-261: Add standard utilities to 
all dockers (vim, ping, nslookup)

Hi Kang,

Those tools don’t really require too much space in a docker image, so size 
shouldn’t be a problem. I don’t think we need to modify the docker images, we 
could create init containers in kubernetes that install those tools for the 
ONAP components that need them.

Marco

From: 
>
 on behalf of Kang Xi >
Date: Tuesday, February 20, 2018 at 10:38 AM
To: BRIAN FREEMAN >
Cc: onap-discuss 
>
Subject: [onap-discuss] [integration] INT-261: Add standard utilities to all 
dockers (vim, ping, nslookup)

Hi Brian, All,

We have a backlog jira ticket asking to install standard utilities to all 
dockers.
https://jira.onap.org/browse/INT-261

This issue was discussed at today’s Integration weekly meeting. Some concerns 
were raised that it would inflate the size and increate maintenance work for 
the production version as how to turn on/off installing those packages. Another 
question is that it might not be needed for all the dockers.

There is no doubt that having those tools will make debug and test more 
productive. Do you think it is possible to add the tools to a few most 
demanding dockers? If yes, please specify a list and I’ll follow up on this. 
Immediately I have the controller dockers in SDNC/APPC and mso docker in SO.

Regards,
Kang

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

Re: [onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

2018-02-20 Thread PLATANIA, MARCO (MARCO)

All the components in Heat already have ping-utils, vim and nslookup. Not sure 
about the Centos VMs for DCAE, need to check with Lusheng.

Marco

From: Kang Xi 
Date: Tuesday, February 20, 2018 at 11:02 AM
To: "PLATANIA, MARCO (MARCO)" , BRIAN FREEMAN 

Cc: onap-discuss 
Subject: RE: [onap-discuss] [integration] INT-261: Add standard utilities to 
all dockers (vim, ping, nslookup)

Hi Marco,

I agree with you. Actually I did check the size and found the total is less 
than 5MB. Is there also an easy solution for heat?

Regards,
Kang

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Tuesday, February 20, 2018 10:58
To: Kang Xi ; FREEMAN, BRIAN D 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [integration] INT-261: Add standard utilities to 
all dockers (vim, ping, nslookup)

Hi Kang,

Those tools don’t really require too much space in a docker image, so size 
shouldn’t be a problem. I don’t think we need to modify the docker images, we 
could create init containers in kubernetes that install those tools for the 
ONAP components that need them.

Marco

From: 
>
 on behalf of Kang Xi >
Date: Tuesday, February 20, 2018 at 10:38 AM
To: BRIAN FREEMAN >
Cc: onap-discuss 
>
Subject: [onap-discuss] [integration] INT-261: Add standard utilities to all 
dockers (vim, ping, nslookup)

Hi Brian, All,

We have a backlog jira ticket asking to install standard utilities to all 
dockers.
https://jira.onap.org/browse/INT-261

This issue was discussed at today’s Integration weekly meeting. Some concerns 
were raised that it would inflate the size and increate maintenance work for 
the production version as how to turn on/off installing those packages. Another 
question is that it might not be needed for all the dockers.

There is no doubt that having those tools will make debug and test more 
productive. Do you think it is possible to add the tools to a few most 
demanding dockers? If yes, please specify a list and I’ll follow up on this. 
Immediately I have the controller dockers in SDNC/APPC and mso docker in SO.

Regards,
Kang

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

Re: [onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

2018-02-20 Thread Kang Xi

Hi Marco,

I agree with you. Actually I did check the size and found the total is less 
than 5MB. Is there also an easy solution for heat?

Regards,
Kang

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Tuesday, February 20, 2018 10:58
To: Kang Xi ; FREEMAN, BRIAN D 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [integration] INT-261: Add standard utilities to 
all dockers (vim, ping, nslookup)

Hi Kang,

Those tools don’t really require too much space in a docker image, so size 
shouldn’t be a problem. I don’t think we need to modify the docker images, we 
could create init containers in kubernetes that install those tools for the 
ONAP components that need them.

Marco

From: 
>
 on behalf of Kang Xi >
Date: Tuesday, February 20, 2018 at 10:38 AM
To: BRIAN FREEMAN >
Cc: onap-discuss 
>
Subject: [onap-discuss] [integration] INT-261: Add standard utilities to all 
dockers (vim, ping, nslookup)

Hi Brian, All,

We have a backlog jira ticket asking to install standard utilities to all 
dockers.
https://jira.onap.org/browse/INT-261

This issue was discussed at today’s Integration weekly meeting. Some concerns 
were raised that it would inflate the size and increate maintenance work for 
the production version as how to turn on/off installing those packages. Another 
question is that it might not be needed for all the dockers.

There is no doubt that having those tools will make debug and test more 
productive. Do you think it is possible to add the tools to a few most 
demanding dockers? If yes, please specify a list and I’ll follow up on this. 
Immediately I have the controller dockers in SDNC/APPC and mso docker in SO.

Regards,
Kang

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

Re: [onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

2018-02-20 Thread PLATANIA, MARCO (MARCO)

Hi Kang,

Those tools don’t really require too much space in a docker image, so size 
shouldn’t be a problem. I don’t think we need to modify the docker images, we 
could create init containers in kubernetes that install those tools for the 
ONAP components that need them.

Marco

From:  on behalf of Kang Xi 

Date: Tuesday, February 20, 2018 at 10:38 AM
To: BRIAN FREEMAN 
Cc: onap-discuss 
Subject: [onap-discuss] [integration] INT-261: Add standard utilities to all 
dockers (vim, ping, nslookup)

Hi Brian, All,

We have a backlog jira ticket asking to install standard utilities to all 
dockers.
https://jira.onap.org/browse/INT-261

This issue was discussed at today’s Integration weekly meeting. Some concerns 
were raised that it would inflate the size and increate maintenance work for 
the production version as how to turn on/off installing those packages. Another 
question is that it might not be needed for all the dockers.

There is no doubt that having those tools will make debug and test more 
productive. Do you think it is possible to add the tools to a few most 
demanding dockers? If yes, please specify a list and I’ll follow up on this. 
Immediately I have the controller dockers in SDNC/APPC and mso docker in SO.

Regards,
Kang

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

Re: [onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

2018-02-20 Thread Josef Reisinger

Yes please +1 ... and add ngrep(1) too please


Mit freundlichen Grüßen / Kind regards
Josef Reisinger 
IBM Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter 
Geschäftsführung: Matthias Hartmann (Vorsitzender), Norbert Janzen, Stefan 
Lutz, Nicole Reimer, Dr. Klaus Seifert, Wolfgang Wendt 
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, 
HRB 14562 / WEEE-Reg.-Nr. DE 99369940 




From:   Kang Xi 
To: "FREEMAN, BRIAN D" 
Cc: onap-discuss 
Date:   20.02.2018 16:39
Subject:[onap-discuss] [integration] INT-261: Add standard 
utilities to all dockers (vim, ping, nslookup)
Sent by:onap-discuss-boun...@lists.onap.org



Hi Brian, All,
 
We have a backlog jira ticket asking to install standard utilities to all 
dockers.
https://jira.onap.org/browse/INT-261
 
This issue was discussed at today?s Integration weekly meeting. Some 
concerns were raised that it would inflate the size and increate 
maintenance work for the production version as how to turn on/off 
installing those packages. Another question is that it might not be needed 
for all the dockers.
 
There is no doubt that having those tools will make debug and test more 
productive. Do you think it is possible to add the tools to a few most 
demanding dockers? If yes, please specify a list and I?ll follow up on 
this. Immediately I have the controller dockers in SDNC/APPC and mso 
docker in SO. 
 
Regards,
Kang
 ___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss




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

[onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

2018-02-20 Thread Kang Xi

Hi Brian, All,

We have a backlog jira ticket asking to install standard utilities to all 
dockers.
https://jira.onap.org/browse/INT-261

This issue was discussed at today's Integration weekly meeting. Some concerns 
were raised that it would inflate the size and increate maintenance work for 
the production version as how to turn on/off installing those packages. Another 
question is that it might not be needed for all the dockers.

There is no doubt that having those tools will make debug and test more 
productive. Do you think it is possible to add the tools to a few most 
demanding dockers? If yes, please specify a list and I'll follow up on this. 
Immediately I have the controller dockers in SDNC/APPC and mso docker in SO.

Regards,
Kang

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

[onap-discuss] Canceled: [sdnc] Weekly SDNC project team meeting

2018-02-20 Thread TIMONEY, DAN

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:STANDARD
DTSTART:16010101T06
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T07
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="TIMONEY, DAN":MAILTO:dt5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="ARIA, LAL
 ENA":MAILTO:la5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="BOROKHOVI
 CH, MICHAEL":MAILTO:mich...@research.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="CHINTHAKA
 YALA, SHESHASHAILAVAS":MAILTO:sc2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="GUDISENA,
  VARUNESHWAR":MAILTO:vg4...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="GUPTA, AL
 OK":MAILTO:ag1...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="ISUKAPALL
 I, SASTRY":MAILTO:sas...@research.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="KUMAR, PR
 ASHANT":MAILTO:prashant.kum...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="LANDO, MI
 CHAEL":MAILTO:ml6...@intl.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="LANTHIER,
  STEPHEN":MAILTO:stephen.lanth...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="NGUYEN, T
 OAN T":MAILTO:tn2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="OBRIEN, F
 RANK MICHAEL":MAILTO:frank.obr...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=onap-disc
 u...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="REECE, CH
 RIS":MAILTO:cre...@awardsolutions.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="ROTUNDO, 
 AL":MAILTO:ar3...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="SILVERTHO
 RN, DANIEL":MAILTO:daniel.silverth...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="SPATSCHEC
 K, OLIVER":MAILTO:spat...@research.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="STILWELL,
  DAVE":MAILTO:ds6...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="TABEDZKI,
  RICHARD":MAILTO:rt0...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="TALASILA,
  MANOOP":MAILTO:talas...@research.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="THORPE, H
 ENRY E":MAILTO:ht1...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="TOFIGH, T
 OM":MAILTO:mt3...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="VAN BRAKL
 E, TRACY L":MAILTO:tv8...@att.com
DESCRIPTION;LANGUAGE=en-US:This event has been canceled:\n\nWhen: February 
 21\, 2018 at 9:00:00 AM EST (recurring)\nWhere: Zoom meeting - see notes f
 or logistics\n--\nONAP Meeting 6 is inviting you to a scheduled Zoom meeti
 ng.\n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/3308
 24945\n\nOr iPhone one-tap (US Toll
 ): +16465588656\,\,330824945# or +14086380968\,\,330824945#\n\nOr Telephon
 e:\nDial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)\n+1 855 8
 80 1246 (US Toll Free)\n+1 877 369 0926 (US Toll Free)\nMeeting ID: 330 82
 4 945\nInternational numbers available: https://zoom.us/zoomconference?m=r
 RItS256rDo_7UtkIznpz4jzZNmjTfbO\n\n
SUMMARY;LANGUAGE=en-US:Canceled: [sdnc] Weekly SDNC project team meeting
DTSTART;TZID=America/New_York:20180221T09
DTEND;TZID=America/New_York:20180221T093000
UID:FA0D73F0-6408-4E0B-B374-5E162E063BC0
RECURRENCE-ID;TZID=America/New_York:20180221T09
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180219T165207Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:2
LOCATION;LANGUAGE=en-US:Zoom meeting - see notes for logistics
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___

Re: [onap-discuss] [optfra] Weekly meeting on 2/19/2018

2018-02-20 Thread PUZHAVAKATH NARAYANAN, SHANKARANARAYANAN (SHANKARANARAYANAN)

Thanks for letting us know Dileep !

As a one off we could consider moving it to Wednesday (2/21) morning, but I’m 
not sure about the bridge availability given that there are other weekly 
meetings happening simultaneously. The other alternative is 11ET, Thursday 
2/22, after the TSC call. Can you please put a note on our wiki with these (and 
others which you think may work) options and ask for a preference.

Thanks,
Shankar

On Feb 16, 2018, at 9:43 AM, Ranganathan, Dileep 
> wrote:

Hi optfra team.

Do we have weekly meeting on 2/19/2018 as it is a holiday for many folks?
Does it make sense to consider another time for this particular instance of 
weekly meeting?

Thanks,
Dileep

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

Re: [onap-discuss] SDC VSP csar validation failed with error : null

2018-02-20 Thread Halfon Tal

Hi

Can you send me the CSAR you upload?
What version of SDC you are using? R1? R2?


Best regards
Tal Halfon

Development Manager @ Amdocs

P. +972 54 2213763

[cid:image001.png@01D2DC45.AD6F91B0]   [ONAP_logo_Sig]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Akula, Ramanjaneyul 
Reddy (Nokia - US/Irving)
Sent: Tuesday, February 20, 2018 4:40 PM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC VSP csar validation failed with error : null

Hi SDC Team,
Any hints would be highly appreciated.

Thanks in advance.

best regards,
Ramu


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Akula, Ramanjaneyul 
Reddy (Nokia - US/Irving)
Sent: Friday, February 16, 2018 9:47 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] SDC VSP csar validation failed with error : null

Hi SDC Team,
  I'm trying to upload the CSAR file to SDC as part of VSP creation.
Upload is successful.

However when I try to validate it, I see below error.


[cid:image004.png@01D3AA6C.42CE42C0]

And I tried to scan through all the error logs within SDC VM. And didn't get 
any clue out of it.

Would you please let me know if there is any offline tool to validate the CSAR 
file.


Thanks & best regards,
Ramu

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] SDC VSP csar validation failed with error : null

2018-02-20 Thread Akula, Ramanjaneyul Reddy (Nokia - US/Irving)

Hi SDC Team,
Any hints would be highly appreciated.

Thanks in advance.

best regards,
Ramu


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Akula, Ramanjaneyul 
Reddy (Nokia - US/Irving)
Sent: Friday, February 16, 2018 9:47 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] SDC VSP csar validation failed with error : null

Hi SDC Team,
  I'm trying to upload the CSAR file to SDC as part of VSP creation.
Upload is successful.

However when I try to validate it, I see below error.


[cid:image001.png@01D3AA26.5FE245A0]

And I tried to scan through all the error logs within SDC VM. And didn't get 
any clue out of it.

Would you please let me know if there is any offline tool to validate the CSAR 
file.


Thanks & best regards,
Ramu

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

[onap-discuss] [policy] Welcome to Liam Fallon

2018-02-20 Thread DRAGOSH, PAMELA L (PAM)

ONAP Community,

I would like to welcome Liam Fallon as a committer to the Policy project. Liam 
has been providing valuable
contributions to help the policy team with getting our code coverage above 80% 
in our policy/drools-applications.
He has also been valuable in providing help with wiki and general architecture 
direction.

Thanks!!

Pam Dragosh
ONAP Policy PTL
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ccsdk][sdnc] Congratulations to our newest committer - Ryan Goulding

2018-02-20 Thread VAN BRAKLE, TRACY L

CONGRATULATIONS RYAN !!!

Tracy Van Brakle 
AT Labs - Wireless Network Architecture and Design
732.420.3003  office
732.306.2387  cell

From: onap-discuss-boun...@lists.onap.org [onap-discuss-boun...@lists.onap.org] 
on behalf of TIMONEY, DAN
Sent: Tuesday, February 20, 2018 9:32 AM
To: onap-s...@lists.onap.org;  onap-discuss
Subject: [onap-discuss] [ccsdk][sdnc] Congratulations to our newest committer - 
Ryan Goulding

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

CCSDK and SDNC team,

It is with great pleasure that I announce that Ryan Goulding has been promoted 
to committer for the CCSDK and SDN projects.  Ryan has been a strong 
contributor to both our projects, and is also a strong contributor to 
OpenDaylight.  His expertise and hard work have been a huge asset to both our 
projects.

Thank you, Ryan, for your many contributions!

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

[onap-discuss] [ccsdk][sdnc] Congratulations to our newest committer - Ryan Goulding

2018-02-20 Thread TIMONEY, DAN

CCSDK and SDNC team,

It is with great pleasure that I announce that Ryan Goulding has been promoted 
to committer for the CCSDK and SDN projects.  Ryan has been a strong 
contributor to both our projects, and is also a strong contributor to 
OpenDaylight.  His expertise and hard work have been a huge asset to both our 
projects.

Thank you, Ryan, for your many contributions!

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

Re: [onap-discuss] Updated Invitation: [modeling] Project Bi-Weekly @ Every 2 weeks from 6am to 7am on Tuesday (PDT) (onap-discuss@lists.onap.org)

2018-02-20 Thread Vul, Alex

Is there a modeling subcommittee meeting today?

-Original Appointment-
From: ONAP Meetings and Events 
[mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com]
Sent: Tuesday, July 18, 2017 5:13 AM
To: ONAP Meetings and Events; onap-discuss@lists.onap.org; denghu...@huawei.com
Subject: [onap-discuss] Updated Invitation: [modeling] Project Bi-Weekly @ 
Every 2 weeks from 6am to 7am on Tuesday (PDT) (onap-discuss@lists.onap.org)
When: Tuesday, February 20, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://zoom.us/j/137904496

This event has been changed.
more details 
»

[modeling] Project Bi-Weekly
Changed: ONAP Meeting 5 is inviting you to a scheduled Zoom meeting.

Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/137904496
Or iPhone one-tap (US Toll): +14086380968,137904496# or +16465588656,137904496#
Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
Meeting ID: 137 904 496
International numbers available: 
https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a

When
Every 2 weeks from 6am to 7am on Tuesday Pacific Time

Where
Changed: https://zoom.us/j/137904496 
(map)

Calendar
onap-discuss@lists.onap.org

Who
•
kp...@linuxfoundation.org - creator

•
onap-discuss@lists.onap.org

•
denghu...@huawei.com

Going?   All events in this series:   
Yes
 - 
Maybe
 - 
No
more options 
»
Invitation from Google Calendar

You are receiving this courtesy email at the account 
onap-discuss@lists.onap.org because you are an attendee of this event.
To stop receiving future updates for this event, decline this event. 
Alternatively you can sign up for a Google account at 
https://www.google.com/calendar/ and control your notification settings for 
your entire calendar.
Forwarding this invitation could allow any recipient to modify your RSVP 
response. Learn 
More.
 << File: invite.ics >>  << File: ATT1.txt >>

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

Re: [onap-discuss] Working demo ?

2018-02-20 Thread Lars-Erik Helander

I does not sound like there is a working demo, that would suit my current
setup : ONAP deployed using OOM and master branch.

At this point I am only concerned about instantiating one or a few VNFs as
VMs/virtual-networks  on Openstack.

I have no problem of creating VNFs from scratch (write descriptors and
package as CSAR:s etc) as long as I can find the required information
somewhere:

Some questions that has popped up along my trials are:

   - How do you use the VNFSDK to create your own VNF CSAR?
   - A CSAR that has been uploaded to the VNFSDK marketplace, how is that
made available from within SDC when you create a service?
   - Given that you have a VF-C NSD and VNFD, what are the required steps
to package, onboard, ... until you have your VMs up an running, and what
are the ONAP "components" used within these steps.

I would be most grateful for answers to some or all of these questions.

/Lars


2018-02-20 0:49 GMT+01:00 Michael O'Brien :

> Sorry for not writing clearly – I was thinking in my head “onap” when I
> wrote oom
>
>
>
>Hi, There are a multiple levels of working state (onap up,
> onap+dcagegen2 up, onap+vnfs, and onap+dcaegen2+vnfs+closedloop)
>
>
>
>OOM will deploy all of onap except DCAE via master on any type of
> environment
>
>OOM will deploy all of onap including DCAE vi amsterdam and the heat
> side cloudify controller on an openstack environment
>
>ONAP (whether deployed via OOM or HEAT) will allow for VNF
> orchestration via SO with occasional bug workarounds in master/amsterdam
> only on openstack until SO/Multicloud brings in cloud-native VNF
> orchestration that is in the works.
>
>The amsterdam branch deploys DCAEGEN2 via OOM only on openstack using
> Alexis’s heatbridge between the two dcae controllers on both sides.  It
> last worked for me before the openlab IP reset last week up to the CDAP
> nodes – I fail partway through for now on lack of IPs
>
>I have not verified closed loop for 2 months.
>
>
>
>
>
> *From:* FREEMAN, BRIAN D [mailto:bf1...@att.com]
> *Sent:* Monday, February 19, 2018 11:32
> *To:* Michael O'Brien ; Lars-Erik Helander <
> leh...@gmail.com>; onap-discuss@lists.onap.org
>
> *Subject:* Re: [onap-discuss] Working demo ?
>
>
>
> Oom is not part of vnf orchestration so you might want to reword that
> Michael. Oom only sets up onap. Once onap is up oom is not involved in
> onboarding, instantiation or lcm of vnfs
>
> Brian
>
>
>
>
>
>
>
> Sent via the Samsung Galaxy S8, an AT 4G LTE smartphone
>
>
>
>
>
>  Original message 
>
> From: "OBRIEN, FRANK MICHAEL" 
>
> Date: 2/19/18 10:46 AM (GMT-05:00)
>
> To: Lars-Erik Helander , onap-discuss@lists.onap.org
>
> Subject: Re: [onap-discuss] Working demo ?
>
>
>
> Lars,
>
>Hi, There are a multiple levels of working state (onap up,
> onap+dcagegen2 up, onap+vnfs, and onap+dcaegen2+vnfs+closedloop)
>
>
>
>OOM will deploy all of onap except DCAE via master on any type of
> environment
>
>OOM will allow for VNF orchestration with occasional bug workarounds in
> master/amsterdam only on openstack until SO/Multicloud brings in
> cloud-native VNF orchestration that is in the works.
>
>The amsterdam branch deploys DCAEGEN2 via OOM only on openstack.  It
> last worked for me before the openlab IP reset last week.
>
>I have not verified closed loop for 2 months.
>
>/michael
>
>
>
>
>
> *From:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
> lists.onap.org ] *On Behalf Of *Lars-Erik
> Helander
> *Sent:* Monday, February 19, 2018 08:57
> *To:* onap-discuss@lists.onap.org
> *Subject:* [onap-discuss] Working demo ?
>
>
>
> Is there a working demo that could be used on a system deployed via OOM
> and master branch?
>
>
>
> /Lars
>
> 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] [E] SDC VSP csar validation failed with error : null

Re: [onap-discuss] [onap-tsc] [modeling] Beijing Release new functional requirements

Re: [onap-discuss] [onap-tsc] [modeling] Beijing Release new functional requirements

[onap-discuss] COE meeting of Feb 26, 2018 will be chair by Bin Hu or skipped. (was Re: Invitation: [coe] Weekly (updated Jan 12, 2018) @ Weekly from 10am to 11am on Tuesday from Tue Jan 16 to Tue Dec

[onap-discuss] vCPE: Matching VNF names with Services

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

Re: [onap-discuss] [Policy] Empty policies in Standalone mode

[onap-discuss] UUI health-check amsterdam

Re: [onap-discuss] [ccsdk][sdnc] Congratulations to our newest committer - Ryan Goulding

Re: [onap-discuss] [E] Service Distribution and Service Deployment Issue on OOM Amsterdam release

Re: [onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

Re: [onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

Re: [onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

Re: [onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

Re: [onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

[onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

[onap-discuss] Canceled: [sdnc] Weekly SDNC project team meeting

Re: [onap-discuss] [optfra] Weekly meeting on 2/19/2018

Re: [onap-discuss] SDC VSP csar validation failed with error : null

Re: [onap-discuss] SDC VSP csar validation failed with error : null

[onap-discuss] [policy] Welcome to Liam Fallon

Re: [onap-discuss] [ccsdk][sdnc] Congratulations to our newest committer - Ryan Goulding

[onap-discuss] [ccsdk][sdnc] Congratulations to our newest committer - Ryan Goulding

Re: [onap-discuss] Updated Invitation: [modeling] Project Bi-Weekly @ Every 2 weeks from 6am to 7am on Tuesday (PDT) (onap-discuss@lists.onap.org)

Re: [onap-discuss] Working demo ?

27 matches

Site Navigation

Mail list logo

Footer information