date:20170519

Re: [onap-discuss] [nexus] Missing com.github.sevntu.checkstyle:sevntu-checks artifact in ONAP Nexus

2017-05-19 Thread Alexis de Talhouët


> On May 19, 2017, at 11:10 AM, Andrew Grimberg  
> wrote:
> 
> First: requests to add proxies need to go to the helpdesk
> (helpd...@onap.org )

Ticket #40960 created.

> 
> Second: ONAP _already_ proxies ODL's release repository and the
> odl-third-party repository. We _will not_ proxy the 'public' repo from
> ODL as that's a repo group. If there is a specific repo that needs to be
> proxied that we're not currently proxying then we need to know what it
> is and the co-ords for adding the proxy.
> 
> You can easily see what repos are hosted or proxied by looking at
> https://nexus.onap.org/#view-repositories 
> .

Right… my bad. I haven’t seen that this particular repo was proxied. I 
understand the rational behind not proxying Public as being a group.

> 
> Third: Third party artifacts that do not have a maven repository should
> be thoroughly reviewed and assessed as to the actual need. We do not
> like hosting these sorts of things because it means we have to track
> upstream security announcements for such artifacts. It's far better to
> convince the upstream to either get a Maven repo available for people to
> utilize / proxy or to get their artifacts into Maven central.

Make sense, and we actually don’t need to go that route.

Thanks,
Alexis

> 
> -Andy-
> 
> On 05/19/2017 06:35 AM, ROSE, DANIEL V wrote:
>> Andrew can LF add the odl repo? I don’t think we are supposed to add
>> 3^rd party repos right?
>> 
>> 
>> 
>> Daniel Rose
>> 
>> ECOMP / ONAP
>> 
>> com.att.ecomp
>> 
>> 732-420-7308
>> 
>> 
>> 
>> *From:*onap-discuss-boun...@lists.onap.org
>> [mailto:onap-discuss-boun...@lists.onap.org] *On Behalf Of *Alexis de
>> Talhouët
>> *Sent:* Friday, May 19, 2017 8:13 AM
>> *To:* onap-discuss@lists.onap.org
>> *Subject:* [onap-discuss] [nexus] Missing
>> com.github.sevntu.checkstyle:sevntu-checks artifact in ONAP Nexus
>> 
>> 
>> 
>> Hello,
>> 
>> 
>> My patches [1] are failing due to unresolved dependency: 
>> 
>> 
>> 14:47:28 [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check
>> (check-license) on project dblib-features: Execution check-license of
>> goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed:
>> Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.17 or one of
>> its dependencies could not be resolved: The following artifacts could
>> not be resolved:
>> com.github.sevntu.checkstyle:sevntu-checkstyle-maven-plugin:jar:1.21.0,
>> com.github.sevntu.checkstyle:sevntu-checks:jar:1.21.0: Failure to find
>> com.github.sevntu.checkstyle:sevntu-checkstyle-maven-plugin:jar:1.21.0
>> in https://nexus.onap.org/content/repositories/releases/
>> >  
>> >
>>  was
>> cached in the local repository, resolution will not be reattempted until
>> the update interval of releases has elapsed or updates are forced ->
>> [Help 1]
>> 
>> 
>> 
>> It seems that indeed, this is not present in ONAP’s Nexus public repo.
>> Indeed, this is coming from ODL, and it’s hosted in ODL’s public repo
>> [2]. Can we make this available in ONAP’s third-party repo, and/or proxy
>> ODL’s public's one?
>> 
>> 
>> 
>> Thanks,
>> 
>> Alexis
>> 
>> 
>> 
>> [1]: https://gerrit.onap.org/r/#/q/topic:features-parent\ 
>> 
>> >  
>> >
>> 
>> [2]: 
>> https://nexus.opendaylight.org/content/repositories/public/com/github/sevntu/checkstyle/
>>  
>> 
>> >  
>>

Re: [onap-discuss] [nexus] Missing com.github.sevntu.checkstyle:sevntu-checks artifact in ONAP Nexus

2017-05-19 Thread Andrew Grimberg

First: requests to add proxies need to go to the helpdesk
(helpd...@onap.org)

Second: ONAP _already_ proxies ODL's release repository and the
odl-third-party repository. We _will not_ proxy the 'public' repo from
ODL as that's a repo group. If there is a specific repo that needs to be
proxied that we're not currently proxying then we need to know what it
is and the co-ords for adding the proxy.

You can easily see what repos are hosted or proxied by looking at
https://nexus.onap.org/#view-repositories.

Third: Third party artifacts that do not have a maven repository should
be thoroughly reviewed and assessed as to the actual need. We do not
like hosting these sorts of things because it means we have to track
upstream security announcements for such artifacts. It's far better to
convince the upstream to either get a Maven repo available for people to
utilize / proxy or to get their artifacts into Maven central.

-Andy-

On 05/19/2017 06:35 AM, ROSE, DANIEL V wrote:
> Andrew can LF add the odl repo? I don’t think we are supposed to add
> 3^rd party repos right?
> 
>  
> 
> Daniel Rose
> 
> ECOMP / ONAP
> 
> com.att.ecomp
> 
> 732-420-7308
> 
>  
> 
> *From:*onap-discuss-boun...@lists.onap.org
> [mailto:onap-discuss-boun...@lists.onap.org] *On Behalf Of *Alexis de
> Talhouët
> *Sent:* Friday, May 19, 2017 8:13 AM
> *To:* onap-discuss@lists.onap.org
> *Subject:* [onap-discuss] [nexus] Missing
> com.github.sevntu.checkstyle:sevntu-checks artifact in ONAP Nexus
> 
>  
> 
> Hello,
> 
> 
> My patches [1] are failing due to unresolved dependency: 
> 
> 
> 14:47:28 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check
> (check-license) on project dblib-features: Execution check-license of
> goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed:
> Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.17 or one of
> its dependencies could not be resolved: The following artifacts could
> not be resolved:
> com.github.sevntu.checkstyle:sevntu-checkstyle-maven-plugin:jar:1.21.0,
> com.github.sevntu.checkstyle:sevntu-checks:jar:1.21.0: Failure to find
> com.github.sevntu.checkstyle:sevntu-checkstyle-maven-plugin:jar:1.21.0
> in https://nexus.onap.org/content/repositories/releases/
> 
>  was
> cached in the local repository, resolution will not be reattempted until
> the update interval of releases has elapsed or updates are forced ->
> [Help 1]
> 
>  
> 
> It seems that indeed, this is not present in ONAP’s Nexus public repo.
> Indeed, this is coming from ODL, and it’s hosted in ODL’s public repo
> [2]. Can we make this available in ONAP’s third-party repo, and/or proxy
> ODL’s public's one?
> 
>  
> 
> Thanks,
> 
> Alexis
> 
>  
> 
> [1]: https://gerrit.onap.org/r/#/q/topic:features-parent\
> 
> 
> [2]: 
> https://nexus.opendaylight.org/content/repositories/public/com/github/sevntu/checkstyle/
> 
> 
>  
> 
>  
> 
> 
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss
> 

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation



signature.asc
Description: OpenPGP digital signature
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

2017-05-19 Thread PLATANIA, MARCO (MARCO)

Hello Kedar,

This is what I received from Policy team about communication monitoring:

“The best way to monitor Policy during Closed Loop is to subscribe to our 
POLICY-CL-MGT topic (may have another name that is configurable).”

“With regards to the logs in the drools container, see 
$POLICY_HOME/logs/network.log.   I think that will capture all FW messages 
interaction, For the LB case, the REST interactions with AAI/MSO REST will go 
to the .out file, they are not captured yet in the network.log (it will at some 
point).”

If you need further assistance, please feel free to reach out to Policy team 
directly (some contacts here: 
https://wiki.onap.org/pages/viewpage.action?pageId=3246903 ).

Thanks,
Marco


From:  on behalf of Kedar Ambekar 

Date: Friday, May 19, 2017 at 8:37 AM
To: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Daniel, Marco,

It appears that the robot script run for demo.sh appc is more specific for vFW.

In case if vLB, as packetGenerator VM is part of different Heat stack, the 
robot script can’t find key vpg_name_0 in the dictionary. Also, I believe it 
will fail further for vpg_private_ip_1.

I gave a try by making below small changes (as APPC is not involved in vLB 
demo)  in demo_preload.robot as below.

Original :
${vpg_name_0}=Get From Dictionary${stack_info}vpg_name_0
${vpg_public_ip}=Get Server Ip${server_list}${stack_info}   
vpg_name_0network_name=public
${vpg_oam_ip}=Get From Dictionary${stack_info}vpg_private_ip_1
${appc}=Create Mount Point In APPC${vpg_name_0}${vpg_oam_ip}

Changed:
Declared a variable vpg_name_0 with the name of my packet generator VM from 
different stack.
Declared a variable vpg_public_ip with public IP of my packet generator VM from 
different stack.
${appc}=Create Mount Point In APPC${vpg_name_0}${vpg_public_ip}

With that, though I am not sure the impact of above change yet,  I could make 
the demo.sh appc step pass.

Now, can I know how to verify the closed control loop ? How to see messages 
exchanged on Message Bus for both the use cases ?

Appreciate some write-up on verification of both the cases !!

From: Kedar Ambekar
Sent: Friday, May 19, 2017 10:22 AM
To: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Thanks Catherine for the updated diagram, I could follow them.

Hi Daniel, Marco,

I am using Release-1.Here are my env parameters while running ONAP Heat 
template.

artifacts_version: 1.0.0
docker_version: 1.0-STAGING-latest
gerrit_branch: release-1.0.0


When I do demo.sh appc , I get 
“Dictionary does not contain key 'vpg_name_0'.”. The env file 
base_vlb_rackspace does not have this parameter. packet_gen_vlb_rackspace env 
file has this parameter though.

Here is my stack list.

[id:image002.png@01D2D0CA.C66625C0]


From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Friday, May 19, 2017 9:31 AM
To: PLATANIA, MARCO 
mailto:plata...@research.att.com>>; ROSE, DANIEL V 
mailto:dr6...@att.com>>; Kedar Ambekar 
mailto:ake...@techmahindra.com>>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Marco, Kedar,

I have updated the wiki page with the latest pictures.

Best regards
Catherine

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO
Sent: Friday, May 19, 2017 12:29 AM
To: ROSE, DANIEL V mailto:dr6...@att.com>>; Kedar Ambekar 
mailto:ake...@techmahindra.com>>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

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

I’m not familiar with preloading (Dan can cover that part), but for what 
regards the vLB demo flow, APP-C is not involved. During the closed loop, 
policy gets the VNF Id from AAI and provides this Id as argument of a 
CreateVF-Module request to MSO, which actually spins up the second DNS.

The figure in the wiki is outdated and should be replaced. Honeycomb isn’t used 
on the vLB VM.

Thanks,
Marco


From: "ROSE, DANIEL V" mailto:dr6...@att.com>>
Date: Thursday, May 18, 2017 at 6:09 PM
To: Kedar Ambekar mailto:ake...@techmahindra.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>, "PLATANIA, 
MARCO (MARCO)" mailto:plata...@research.att.com>>
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

you should be calling ./demo.sh appc . What branch of onap are you using? Release1?

Marco can answer questions about the actual demo closed loop better.

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-bou

Re: [onap-discuss] APPC questions

2017-05-19 Thread FREEMAN, BRIAN D

Thats part of the SDNC base so I forwarded the question on the SDNC team.

Brian

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Friday, May 19, 2017 9:54 AM
To: Ali, Shaheen ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] APPC questions

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
One of the big points of containers is it doesn't matter what the base os is 
running, only what the containers are running. I don't see why  you couldn't 
run the base os as all centos if you wanted for instance.

That said I appc can answer better but I don't see why appc couldn't run on 
mysql 5.7 its just a matter of upgrading (maybe even to mariadb)

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ali, Shaheen
Sent: Friday, May 19, 2017 9:40 AM
To: onap-discuss@lists.onap.org
Cc: Ali, Shaheen 
mailto:shaheen@centurylink.com>>
Subject: [onap-discuss] APPC questions

Hello Everyone,

We are exploring the APPC architecture and we have a few questions:

- Why is the base OS for APPC Ubuntu-Xenial (16.04)?
- Why is the MySQL server version 5.6?

I ask because according to MySQL web site, Ubuntu 16.04 does not support 5.6.  
I realize that APPC gets around this by running MySQL 5.6 in a Oracle Linux 
container.

However, I wonder why not just run MySQL 5.7 which is supported on Ubuntu 
16.04.  If 5.6 is really needed, why not base APPC on Ubuntu Trusty (14.04).  
Trusty supports MySQL 5.6.

Please help me understand these contradictory platform choices.

Thanks,

Shaheen
This communication is the property of CenturyLink and may contain confidential 
or privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please immediately notify the sender by reply e-mail and destroy all 
copies of the communication and any attachments.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] APPC questions

2017-05-19 Thread ROSE, DANIEL V

One of the big points of containers is it doesn't matter what the base os is 
running, only what the containers are running. I don't see why  you couldn't 
run the base os as all centos if you wanted for instance.

That said I appc can answer better but I don't see why appc couldn't run on 
mysql 5.7 its just a matter of upgrading (maybe even to mariadb)

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ali, Shaheen
Sent: Friday, May 19, 2017 9:40 AM
To: onap-discuss@lists.onap.org
Cc: Ali, Shaheen 
Subject: [onap-discuss] APPC questions

Hello Everyone,

We are exploring the APPC architecture and we have a few questions:

- Why is the base OS for APPC Ubuntu-Xenial (16.04)?
- Why is the MySQL server version 5.6?

I ask because according to MySQL web site, Ubuntu 16.04 does not support 5.6.  
I realize that APPC gets around this by running MySQL 5.6 in a Oracle Linux 
container.

However, I wonder why not just run MySQL 5.7 which is supported on Ubuntu 
16.04.  If 5.6 is really needed, why not base APPC on Ubuntu Trusty (14.04).  
Trusty supports MySQL 5.6.

Please help me understand these contradictory platform choices.

Thanks,

Shaheen

This communication is the property of CenturyLink and may contain confidential 
or privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please immediately notify the sender by reply e-mail and destroy all 
copies of the communication and any attachments.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] APPC questions

2017-05-19 Thread Ali, Shaheen

Hello Everyone,

We are exploring the APPC architecture and we have a few questions:

- Why is the base OS for APPC Ubuntu-Xenial (16.04)?
- Why is the MySQL server version 5.6?

I ask because according to MySQL web site, Ubuntu 16.04 does not support 5.6.  
I realize that APPC gets around this by running MySQL 5.6 in a Oracle Linux 
container.

However, I wonder why not just run MySQL 5.7 which is supported on Ubuntu 
16.04.  If 5.6 is really needed, why not base APPC on Ubuntu Trusty (14.04).  
Trusty supports MySQL 5.6.

Please help me understand these contradictory platform choices.

Thanks,

Shaheen


This communication is the property of CenturyLink and may contain confidential 
or privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please immediately notify the sender by reply e-mail and destroy all 
copies of the communication and any attachments.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] SDC portal is not accessible with 502 error

2017-05-19 Thread Ajay.Priyadarshi

Hi,

On SDC Cassandra is UP. The communication issues among all containers (all 
residing in same vm)

(Backend Health check)
root@vm1-sdc:/data/logs/BE/ASDC/ASDC-BE# curl 
http://localhost:8080/sdc2/rest/healthCheck  


Error 503 


HTTP ERROR: 503
Problem accessing /sdc2/rest/healthCheck. Reason:
Service Unavailable
http://eclipse.org/jetty";>Powered by Jetty:// 
9.3.15.v20161220



There are highlighted  beans which have not been initialized, so kindly suggest 
the possible reasons for failed initialization of these beans.

2017-05-19T12:41:19.007Z|||main||ASDC-BE||ERROR|o.s.web.context.ContextLoader||ActivityType=,
 Desc=
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED


Does any script or doc available for validating all necessary services for each 
kind of vm, which could help debugging.

Regards,
Ajay

From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: 18 May 2017 20:50
To: EMPOROPULO, VITALIY; Aayush Bhatnagar; Ajay Priyadarshi; EFRAT, ELHAY; 
onap-discuss@lists.onap.org; Ning So; Robert Pippert
Subject: RE: SDC portal is not accessible with 502 error

Aayush,

There is kind of a story already for this 
https://jira.onap.org/browse/COMMON-12?filter=-2
if you want to track that or add some details

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of EMPOROPULO, VITALIY
Sent: Thursday, May 18, 2017 11:10 AM
To: aayush.bhatna...@ril.com; 
ajay.priyadar...@ril.com; EFRAT, ELHAY 
mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org; 
ning...@ril.com; 
robert.pipp...@ril.com
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Aayush,

It is obviously not a good way to use containers, and is definitely going to 
change.

To my understanding, running all of the SDC containers in a single VM was a 
quick and easy solution for automating SDC deployment in ONAP. From that point 
it will evolve to proper (Micro)services, with independent scaling-out of 
components, load balancing and service lookup as a means of HA and fault 
tolerance, etc.

Regards,
Vitaliy

From: aayush.bhatna...@ril.com 
[mailto:aayush.bhatna...@ril.com]
Sent: Thursday, May 18, 2017 17:38
To: Vitaliy Emporopulo 
mailto:vitaliy.emporop...@amdocs.com>>; 
ajay.priyadar...@ril.com; Elhay Efrat 
mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org; 
ning...@ril.com; 
robert.pipp...@ril.com
Subject: RE: SDC portal is not accessible with 502 error

Thanks for the update Vitaliy.

The requirement of running on the same host is something which has been done by 
design, or will it change in the future.

Why I ask this question is the fact that once we try to execute HA and Fault 
Tolerant scenarios for individual ONAP components (inclusive of the SDC), the 
hosts may change.

Regards

Aayush


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Vitaliy Emporopulo
Sent: 18 May 2017 18:41
To: Ajay Priyadarshi; Elhay Efrat; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Ajay,

Currently a SDC setup expects all of its containers to run on the same host 
(virtual or physical), and access each other via the host's IP address or 
hostname visible inside the containers. This is possible using 
container-to-host port binding.

Apparently, a SDC container cannot reach the others via 172.16.74.83. On the 
other hand, it looks like the BE identifies itself as 10.0.3.1 (see

Re: [onap-discuss] [nexus] Missing com.github.sevntu.checkstyle:sevntu-checks artifact in ONAP Nexus

2017-05-19 Thread ROSE, DANIEL V

Andrew can LF add the odl repo? I don’t think we are supposed to add 3rd party 
repos right?

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Friday, May 19, 2017 8:13 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [nexus] Missing 
com.github.sevntu.checkstyle:sevntu-checks artifact in ONAP Nexus

Hello,

My patches [1] are failing due to unresolved dependency:

14:47:28 [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (check-license) on 
project dblib-features: Execution check-license of goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed: Plugin 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17 or one of its 
dependencies could not be resolved: The following artifacts could not be 
resolved: 
com.github.sevntu.checkstyle:sevntu-checkstyle-maven-plugin:jar:1.21.0, 
com.github.sevntu.checkstyle:sevntu-checks:jar:1.21.0: Failure to find 
com.github.sevntu.checkstyle:sevntu-checkstyle-maven-plugin:jar:1.21.0 in 
https://nexus.onap.org/content/repositories/releases/
 was cached in the local repository, resolution will not be reattempted until 
the update interval of releases has elapsed or updates are forced -> [Help 1]

It seems that indeed, this is not present in ONAP’s Nexus public repo. Indeed, 
this is coming from ODL, and it’s hosted in ODL’s public repo [2]. Can we make 
this available in ONAP’s third-party repo, and/or proxy ODL’s public's one?

Thanks,
Alexis

[1]: 
https://gerrit.onap.org/r/#/q/topic:features-parent\
[2]: 
https://nexus.opendaylight.org/content/repositories/public/com/github/sevntu/checkstyle/


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

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

2017-05-19 Thread ROSE, DANIEL V

Come to think of it you might be right, after all if there is no appc, why do 
we need to run appc mount ☺ try just skipping it!

Thanks,

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO
Sent: Friday, May 19, 2017 9:22 AM
To: Kedar Ambekar ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

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

You can monitor messages that the VNF sends to the DCAE collector via the 
collector web page: 
http://:3904/events/unauthenticated.SEC_MEASUREMENT_OUTPUT/group1/C1?timeout=5000

Please use the appropriate DCAE collector public IP address. For what regards 
the messages exchanged by DCAE and Policy, and Policy and APP-C/AAI/MSO, I 
forwarded your question to other people in our team. I hope I can get back to 
you soon with a detailed answer.

Regarding the demo.sh script, Dan knows it better and can provide further 
details on that.

Thanks,
Marco


From: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Kedar Ambekar 
mailto:ake...@techmahindra.com>>
Date: Friday, May 19, 2017 at 8:37 AM
To: "onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Daniel, Marco,

It appears that the robot script run for demo.sh appc is more specific for vFW.

In case if vLB, as packetGenerator VM is part of different Heat stack, the 
robot script can’t find key vpg_name_0 in the dictionary. Also, I believe it 
will fail further for vpg_private_ip_1.

I gave a try by making below small changes (as APPC is not involved in vLB 
demo)  in demo_preload.robot as below.

Original :
${vpg_name_0}=Get From Dictionary${stack_info}vpg_name_0
${vpg_public_ip}=Get Server Ip${server_list}${stack_info}   
vpg_name_0network_name=public
${vpg_oam_ip}=Get From Dictionary${stack_info}vpg_private_ip_1
${appc}=Create Mount Point In APPC${vpg_name_0}${vpg_oam_ip}

Changed:
Declared a variable vpg_name_0 with the name of my packet generator VM from 
different stack.
Declared a variable vpg_public_ip with public IP of my packet generator VM from 
different stack.
${appc}=Create Mount Point In APPC${vpg_name_0}${vpg_public_ip}

With that, though I am not sure the impact of above change yet,  I could make 
the demo.sh appc step pass.

Now, can I know how to verify the closed control loop ? How to see messages 
exchanged on Message Bus for both the use cases ?

Appreciate some write-up on verification of both the cases !!

From: Kedar Ambekar
Sent: Friday, May 19, 2017 10:22 AM
To: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Thanks Catherine for the updated diagram, I could follow them.

Hi Daniel, Marco,

I am using Release-1.Here are my env parameters while running ONAP Heat 
template.

artifacts_version: 1.0.0
docker_version: 1.0-STAGING-latest
gerrit_branch: release-1.0.0


When I do demo.sh appc , I get 
“Dictionary does not contain key 'vpg_name_0'.”. The env file 
base_vlb_rackspace does not have this parameter. packet_gen_vlb_rackspace env 
file has this parameter though.

Here is my stack list.

[id:image002.png@01D2D0CA.C66625C0]


From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Friday, May 19, 2017 9:31 AM
To: PLATANIA, MARCO 
mailto:plata...@research.att.com>>; ROSE, DANIEL V 
mailto:dr6...@att.com>>; Kedar Ambekar 
mailto:ake...@techmahindra.com>>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Marco, Kedar,

I have updated the wiki page with the latest pictures.

Best regards
Catherine

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO
Sent: Friday, May 19, 2017 12:29 AM
To: ROSE, DANIEL V mailto:dr6...@att.com>>; Kedar Ambekar 
mailto:ake...@techmahindra.com>>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

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

I’m not familiar with preloading (Dan can cover that part), b

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

2017-05-19 Thread PLATANIA, MARCO (MARCO)

Kedar,

You can monitor messages that the VNF sends to the DCAE collector via the 
collector web page: 
http://:3904/events/unauthenticated.SEC_MEASUREMENT_OUTPUT/group1/C1?timeout=5000

Please use the appropriate DCAE collector public IP address. For what regards 
the messages exchanged by DCAE and Policy, and Policy and APP-C/AAI/MSO, I 
forwarded your question to other people in our team. I hope I can get back to 
you soon with a detailed answer.

Regarding the demo.sh script, Dan knows it better and can provide further 
details on that.

Thanks,
Marco


From:  on behalf of Kedar Ambekar 

Date: Friday, May 19, 2017 at 8:37 AM
To: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Daniel, Marco,

It appears that the robot script run for demo.sh appc is more specific for vFW.

In case if vLB, as packetGenerator VM is part of different Heat stack, the 
robot script can’t find key vpg_name_0 in the dictionary. Also, I believe it 
will fail further for vpg_private_ip_1.

I gave a try by making below small changes (as APPC is not involved in vLB 
demo)  in demo_preload.robot as below.

Original :
${vpg_name_0}=Get From Dictionary${stack_info}vpg_name_0
${vpg_public_ip}=Get Server Ip${server_list}${stack_info}   
vpg_name_0network_name=public
${vpg_oam_ip}=Get From Dictionary${stack_info}vpg_private_ip_1
${appc}=Create Mount Point In APPC${vpg_name_0}${vpg_oam_ip}

Changed:
Declared a variable vpg_name_0 with the name of my packet generator VM from 
different stack.
Declared a variable vpg_public_ip with public IP of my packet generator VM from 
different stack.
${appc}=Create Mount Point In APPC${vpg_name_0}${vpg_public_ip}

With that, though I am not sure the impact of above change yet,  I could make 
the demo.sh appc step pass.

Now, can I know how to verify the closed control loop ? How to see messages 
exchanged on Message Bus for both the use cases ?

Appreciate some write-up on verification of both the cases !!

From: Kedar Ambekar
Sent: Friday, May 19, 2017 10:22 AM
To: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Thanks Catherine for the updated diagram, I could follow them.

Hi Daniel, Marco,

I am using Release-1.Here are my env parameters while running ONAP Heat 
template.

artifacts_version: 1.0.0
docker_version: 1.0-STAGING-latest
gerrit_branch: release-1.0.0


When I do demo.sh appc , I get 
“Dictionary does not contain key 'vpg_name_0'.”. The env file 
base_vlb_rackspace does not have this parameter. packet_gen_vlb_rackspace env 
file has this parameter though.

Here is my stack list.

[id:image002.png@01D2D0CA.C66625C0]


From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Friday, May 19, 2017 9:31 AM
To: PLATANIA, MARCO 
mailto:plata...@research.att.com>>; ROSE, DANIEL V 
mailto:dr6...@att.com>>; Kedar Ambekar 
mailto:ake...@techmahindra.com>>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Marco, Kedar,

I have updated the wiki page with the latest pictures.

Best regards
Catherine

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO
Sent: Friday, May 19, 2017 12:29 AM
To: ROSE, DANIEL V mailto:dr6...@att.com>>; Kedar Ambekar 
mailto:ake...@techmahindra.com>>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

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

I’m not familiar with preloading (Dan can cover that part), but for what 
regards the vLB demo flow, APP-C is not involved. During the closed loop, 
policy gets the VNF Id from AAI and provides this Id as argument of a 
CreateVF-Module request to MSO, which actually spins up the second DNS.

The figure in the wiki is outdated and should be replaced. Honeycomb isn’t used 
on the vLB VM.

Thanks,
Marco


From: "ROSE, DANIEL V" mailto:dr6...@att.com>>
Date: Thursday, May 18, 2017 at 6:09 PM
To: Kedar Ambekar mailto:ake...@techmahindra.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>, "PLATANIA, 
MARCO (MARCO)" mailto:plata...@research.att.com>>
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

you should be calling ./demo.sh appc . What branch of onap are you using? Release1?

Marco can answer questions about the actual demo closed loop better.

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

2017-05-19 Thread Kedar Ambekar

Hi Daniel, Marco,

It appears that the robot script run for demo.sh appc is more specific for vFW.

In case if vLB, as packetGenerator VM is part of different Heat stack, the 
robot script can’t find key vpg_name_0 in the dictionary. Also, I believe it 
will fail further for vpg_private_ip_1.

I gave a try by making below small changes (as APPC is not involved in vLB 
demo)  in demo_preload.robot as below.

Original :
${vpg_name_0}=Get From Dictionary${stack_info}vpg_name_0
${vpg_public_ip}=Get Server Ip${server_list}${stack_info}   
vpg_name_0network_name=public
${vpg_oam_ip}=Get From Dictionary${stack_info}vpg_private_ip_1
${appc}=Create Mount Point In APPC${vpg_name_0}${vpg_oam_ip}

Changed:
Declared a variable vpg_name_0 with the name of my packet generator VM from 
different stack.
Declared a variable vpg_public_ip with public IP of my packet generator VM from 
different stack.
${appc}=Create Mount Point In APPC${vpg_name_0}${vpg_public_ip}

With that, though I am not sure the impact of above change yet,  I could make 
the demo.sh appc step pass.

Now, can I know how to verify the closed control loop ? How to see messages 
exchanged on Message Bus for both the use cases ?

Appreciate some write-up on verification of both the cases !!

From: Kedar Ambekar
Sent: Friday, May 19, 2017 10:22 AM
To: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Thanks Catherine for the updated diagram, I could follow them.

Hi Daniel, Marco,

I am using Release-1.Here are my env parameters while running ONAP Heat 
template.

artifacts_version: 1.0.0
docker_version: 1.0-STAGING-latest
gerrit_branch: release-1.0.0


When I do demo.sh appc , I get 
“Dictionary does not contain key 'vpg_name_0'.”. The env file 
base_vlb_rackspace does not have this parameter. packet_gen_vlb_rackspace env 
file has this parameter though.

Here is my stack list.

[cid:image002.png@01D2D0CA.C66625C0]


From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Friday, May 19, 2017 9:31 AM
To: PLATANIA, MARCO 
mailto:plata...@research.att.com>>; ROSE, DANIEL V 
mailto:dr6...@att.com>>; Kedar Ambekar 
mailto:ake...@techmahindra.com>>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Marco, Kedar,

I have updated the wiki page with the latest pictures.

Best regards
Catherine

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO
Sent: Friday, May 19, 2017 12:29 AM
To: ROSE, DANIEL V mailto:dr6...@att.com>>; Kedar Ambekar 
mailto:ake...@techmahindra.com>>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

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

I’m not familiar with preloading (Dan can cover that part), but for what 
regards the vLB demo flow, APP-C is not involved. During the closed loop, 
policy gets the VNF Id from AAI and provides this Id as argument of a 
CreateVF-Module request to MSO, which actually spins up the second DNS.

The figure in the wiki is outdated and should be replaced. Honeycomb isn’t used 
on the vLB VM.

Thanks,
Marco


From: "ROSE, DANIEL V" mailto:dr6...@att.com>>
Date: Thursday, May 18, 2017 at 6:09 PM
To: Kedar Ambekar mailto:ake...@techmahindra.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>, "PLATANIA, 
MARCO (MARCO)" mailto:plata...@research.att.com>>
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

you should be calling ./demo.sh appc . What branch of onap are you using? Release1?

Marco can answer questions about the actual demo closed loop better.

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Thursday, May 18, 2017 8:44 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Daniel,

Thanks for reply !


1.   In zip file uploaded, I had base_vlb_rackspace and 
dnsscaling_rackspace files.

2.   I did demo.sh preload for 
K-demoVLB-Module.

3.   In Add VF Module, I cho

[onap-discuss] [nexus] Missing com.github.sevntu.checkstyle:sevntu-checks artifact in ONAP Nexus

2017-05-19 Thread Alexis de Talhouët

Hello,

My patches [1] are failing due to unresolved dependency: 

14:47:28 [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (check-license) on 
project dblib-features: Execution check-license of goal 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed: Plugin 
org.apache.maven.plugins:maven-checkstyle-plugin:2.17 or one of its 
dependencies could not be resolved: The following artifacts could not be 
resolved: 
com.github.sevntu.checkstyle:sevntu-checkstyle-maven-plugin:jar:1.21.0, 
com.github.sevntu.checkstyle:sevntu-checks:jar:1.21.0: Failure to find 
com.github.sevntu.checkstyle:sevntu-checkstyle-maven-plugin:jar:1.21.0 in 
https://nexus.onap.org/content/repositories/releases/ was cached in the local 
repository, resolution will not be reattempted until the update interval of 
releases has elapsed or updates are forced -> [Help 1]

It seems that indeed, this is not present in ONAP’s Nexus public repo. Indeed, 
this is coming from ODL, and it’s hosted in ODL’s public repo [2]. Can we make 
this available in ONAP’s third-party repo, and/or proxy ODL’s public's one?

Thanks,
Alexis

[1]: https://gerrit.onap.org/r/#/q/topic:features-parent\ 

[2]: 
https://nexus.opendaylight.org/content/repositories/public/com/github/sevntu/checkstyle/
 



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

[onap-discuss] 答复: Re: [onap-tsc] Project Proposal: ExternalSystemRegister

2017-05-19 Thread li.zi30

Hi Mazin,





Thanks for you suggestion. Yes, there are certain levels of repetition of 
technology and algorithms between ESR and A&AI.  And there're also some area 
A&AI haven't covered in its scope such as the registration and health check of 
external system, the model definition of VNFM and EMS. I will contact with A&AI 
team to figure out how to address these issues and the potential of cooperation 
.




Thanks,

LiZi











原始邮件



发件人： ＜ma...@research.att.com＞
收件人：李滋00164331
抄送人： ＜avi.chap...@amdocs.com＞ ＜onap-discuss@lists.onap.org＞ 
＜onap-...@lists.onap.org＞
日 期 ：2017年05月17日 19:42
主 题 ：Re: [onap-tsc] [onap-discuss]   Project Proposal: 
ExternalSystemRegister





LiZi,  
Thanks for putting the proposal together. The TSC will be continuing a review 
cycle over the next 2 weeks.

I realize the difference and the need of having a system register for external 
communications, 

but the question is whether this should be a separate project that may cause 
further dilution. 

If the technology and the algorithms used for supporting ESR are similar to 
others like those

used in A&AI, but the type of data is different then I don’t see the need for 
separate systems.
 
I can see many situations like life cycle management of VNFs using closed loop 
automation where

doing post health checks are critical after repairing a failure. So having both 
platform and external system 

data available in one place are key.
 
In general, the TSC will look very closely on projects that need merger to help 
unify the community

and strengthen the developer ecosystem. You are getting good feedback from the 
community and 

I suggest you look closer.
 
Regards,

Mazin

 
On May 17, 2017, at 5:31 AM, li.z...@zte.com.cn wrote:
 


Hi Avi,
 
ESR will not only store and manage configuration of VIM, but also the 
configuration of VNFM/SDNC/EMS. It  provides a service to centralized 
management of the information of different kinds of external systems. And it 
will be used by SO/SDC/VF-C etc.

When comes to multi-vim, we suggest that multi-vim using ESR as a dependency 
component, obtaining the connect  information and status of VIM from ESR. For 
this point, we can have a further discussion.

 


Best regards,


LiZi


 


 


 


 


___ ONAP-TSC mailing list 
onap-...@lists.onap.org 
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=5FX921RLo79NTx7tKLHbXyljepFXw2thQpj9A1brOP0&s=_OpHzCu-kDteWkDZA7f3ajsdoETVzQ2k4RKRj-9SF8w&e=
 

 








发件人： ＜avi.chap...@amdocs.com＞

收件人： ＜dr6...@att.com＞李滋00164331  ＜jpianigi...@juniper.net＞

抄送人： ＜onap-discuss@lists.onap.org＞  ＜onap-...@lists.onap.org＞

日 期 ：2017年05月17日 00:31

主 题 ：RE: [onap-tsc] [onap-discuss] Project Proposal: External SystemRegister


 




Hi,


 


Reading the project scope it seems to me a real time configuration repository 
for external system location and credential specifically for VIM.


Probably this should be part of the multi-vim project which should own and 
manage this configuration.


 


I assume that  the component which is used for  storing/managing this 
configuration can be shared across different projects and/or might offered to  
be  a service  which any component can use.


 


Avi,


 


 




From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of ROSE, DANIEL V Sent: Tuesday, May 16, 2017 6:51 PM To: 
li.z...@zte.com.cn jpianigi...@juniper.net Cc: onap-discuss@lists.onap.org 
onap-...@lists.onap.org Subject: Re: [onap-tsc] [onap-discuss] Project 
Proposal: External System Register




 


I have to agree with Jacopo and Steve, that’s not business logic that’s basic 
endpoint health checking.


 


So to clarify on my and their inputs, it still seems like to me that the entire 
scope of this project is covered by some combination of A&AI, ONAP OM  or MSB 
depending  on who you ask / how you look at it.


 


ONAP Operations manager in particular mentions (Which seems to cover most of 
your stuff.)


 


·  Platform Monitoring & healing: Monitor platform state, Platform health 
checks, fault tolerance and self-healing


 


Can you please work with someone like David Sauvageau on that project to be 
sure you have no overlap?


 


Thanks,


Daniel Rose


ECOMP / ONAP


com.att.ecomp


732-420-7308


 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of li.z...@zte.com.cn 
Sent: Tuesday, May 16, 2017 12:49 AM To: jpianigi...@juniper.net Cc: 
onap-discuss@lists.onap.org onap-...@lists.onap.org Subject: Re: [onap-discuss] 
[onap-tsc] Project Proposal: External System Register


 



Hi Jacopo,


 


Thanks for your quick response. The business logic can be information 
verification before store the data to A&AI, and heartbeat detection of the 
system state. 


For example, a user sent the authentic url, ten

Re: [onap-discuss] [nexus] Missing com.github.sevntu.checkstyle:sevntu-checks artifact in ONAP Nexus

Re: [onap-discuss] [nexus] Missing com.github.sevntu.checkstyle:sevntu-checks artifact in ONAP Nexus

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Re: [onap-discuss] APPC questions

Re: [onap-discuss] APPC questions

[onap-discuss] APPC questions

Re: [onap-discuss] SDC portal is not accessible with 502 error

Re: [onap-discuss] [nexus] Missing com.github.sevntu.checkstyle:sevntu-checks artifact in ONAP Nexus

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

[onap-discuss] [nexus] Missing com.github.sevntu.checkstyle:sevntu-checks artifact in ONAP Nexus

[onap-discuss] 答复: Re: [onap-tsc] Project Proposal: ExternalSystemRegister

13 matches

Site Navigation

Mail list logo

Footer information