[onap-discuss] 答复: Question on VID

2017-06-04 Thread shentao 
Dear all

 

I’m going to build Usecase UI project to solve this problem.

I’ve listed all portal requirements of ONAP in Usecase UI Proposal. And
suggest portal functions which have not be implemented should build in this
project.

The project proposal described specific fuctions.
(https://wiki.onap.org/display/DW/Usecase+UI+Proposal+Template)

 

Usecase UI will provide GUI for operators and end-users from the point of
view of use cases.

As a whole project, Usecase UI requiremetns not only includes service design
and run-time management (resource, performance, fault, security,
configuration, etc.) for operators,

but also includes self-service management for end-users.

 

This project targets identifying all GUI requirements which operators and
end-users need ONAP to support, coordinating GUI parts of each ONAP
subsystem, filling the gaps for improving GUI functionalities for use case.

All GUI functionalities of ONAP system can be well showed to satisfy the
requirements from different customers.

 

Scope:

1.   The Designer Role:

l  Service design (implemented by SDC)

l  VNF onboarding (implemented by SDC)

l  Policy design (implemented by Policy Framework)

l  Closed Loop design (implemented by CLAMP)

2.   The Operator Role:

l  Service LCM (implemented by VID portal)

l  Inventory for services and resources (implemented by A)

l  Monitor system alarms (implemented by this project)

l  Alarm correlation (implemented by Holmes)

l  Show system performance (implemented by this project)

3.   The user Role: (Implemented by this project)

l  Provide model-based vCPE instance orchestration interface

l  Consume and interpret standard ONAP vCPE models

l  Call service orchestration systems to configure services and VNFs in the
core and at the edge

l  Use inventory systesm to determine currently defined inventory for core
and edge services

l  End-user self-service management UI of provisioned vCPE elements

 

 

Best regards,

Shentao

 

 

发件人: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com] 
发送时间: 2017年6月4日 19:05
收件人: Gaurav Gupta (c); ROSE, DANIEL V; shentao; dsha...@interwise.com;
eden.ro...@att.com; zahi.kapel...@att.com; HEMLI, AMICHAI; ANAPAN-LAVALLE,
HECTOR A
抄送: onap-discuss@lists.onap.org
主题: RE: [onap-discuss] Question on VID

 

Very valid point, Gaurav. ONAP has multiple GUIs and take this as a request
to TSC/community members to arrive at role definition for each GUI to ensure
that there’s no ambiguity and the same role calling to use more than one
GUI. If there’s such overlaps then we should get those sorted. 

 

thanks & regards,

Dhananjay Pavgi

Mobile : +91 98220 22264

cid:image002.png@01CE7323.F2727500   ONAP_logo_Sig

  www.techmahindra.com
Platinum Member. Visit :   http://www.onap.org 

 

From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gaurav Gupta (c)
Sent: Saturday, June 03, 2017 9:07 AM
To: ROSE, DANIEL V ; shentao ;
dsha...@interwise.com; eden.ro...@att.com; zahi.kapel...@att.com; HEMLI,
AMICHAI ; ANAPAN-LAVALLE, HECTOR A 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Question on VID

 

Daniel Rose 

 

I assumed that one of the Goal of ONAP is managing the Cloud Infra and
Service  easy for the Telco Operator  . 

 

As in traditional/conventional  Network infra environment Network Element
had their own EMS/NMS System and even if some functions of NE or all of the
NE even if virtualized , poses a problem for the operator to look at 2
Screen at least . 

a- EMS/NMS for NE and Service/KPI/Network Health Monitoring  

b-  Another for monitoring the health of  Virtualized environment   

 

Do you think - having  too many GUI's  would causes a lot of overhead unless
you are thinking of restricting each GUI to a specific Role .  

 

Do correct if I am missing something subtle .

with best regards 

gaurav 

  _  

From: onap-discuss-boun...@lists.onap.org
 on behalf of ROSE, DANIEL V

Sent: 02 June 2017 22:52
To: shentao; dsha...@interwise.com; eden.ro...@att.com;
zahi.kapel...@att.com; HEMLI, AMICHAI; ANAPAN-LAVALLE, HECTOR A
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Question on VID 

 

Hector do you know what kind of gui we have and where it is now?

 

Thanks,

Daniel Rose

ECOMP / ONAP

com.att.ecomp

732-420-7308

 

From: shentao [mailto:shen...@chinamobile.com] 
Sent: Friday, June 02, 2017 5:09 AM
To: ROSE, DANIEL V ; dsha...@interwise.com;
eden.ro...@att.com; zahi.kapel...@att.com; HEMLI, AMICHAI

Cc: onap-discuss@lists.onap.org
Subject: 答复: [onap-discuss] Question on VID

 

Hi, Daniel

 

Thanks for your reply.

I’m working to summarize portal requirements and want to confirm if VID is
going to provide a portal for service LCM

Re: [onap-discuss] (no subject)

2017-06-04 Thread FREEMAN, BRIAN D 
Did you change the password in 99-netconf.xml to the correct one for admin ?

Brian


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Abdelmuhaimen Seaudi
Sent: Sunday, June 04, 2017 5:39 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] (no subject)

Hi.

When I do a REST request on SDNC:
GET 
"http://SDNC:8282/restconf/operational/network-topology:network-topology/"

I get:
{
  "network-topology": {
"topology": [
  {
"topology-id": "topology-netconf",
"node": [
  {
"node-id": "controller-config",
"netconf-node-topology:host": "127.0.0.1",
"netconf-node-topology:port": 1830,
"netconf-node-topology:connection-status": "connecting"
  }
]
  }
]
  }
}

Why the node "controller-config" is stuck in "connecting" state ?


However, when I make same REST request on APPC:

GET 
"http://APPC:8282/restconf/operational/network-topology:network-topology/"

I get:
{
  "network-topology": {
"topology": [
  {
"topology-id": "topology-netconf",
"node": [
  {
"node-id": "controller-config",
"netconf-node-topology:host": "127.0.0.1",
"netconf-node-topology:connection-status": "connected",
"netconf-node-topology:available-capabilities": {
  "available-capability": [
"(config:aaa:authn:idmlight?revision=2015-12-04)aaa-idmlight",

  ]
},
"netconf-node-topology:unavailable-capabilities": {},
"netconf-node-topology:port": 1830


Thanks.

Abdelmuhaimen Seaudi, CCIE # 25265
Email: asea...@gmail.com
Skype: aseaudi
LinkedIn: 
www.linkedin.com/in/aseaudi
Telephone: +2012 84644 733

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

Re: [onap-discuss] YANG.XML format

2017-06-04 Thread Lando,Michael 
The current guide line is that the file be a valid xml and that the file ending 
be.xml.
No additional requirements/validations are done for this artifact.


BR,

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


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Law, Owen
Sent: Thursday, May 25, 2017 2:35 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] YANG.XML format

Hi ONAPers:

There is an option in SDC to add deployment artefacts as part of the service 
composition – is there a specific guideline on what format is needed for the 
YANG.XML  ?

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

Re: [onap-discuss] Missing artifact commons-logging:commons-logging:jar:1.2.1-SNAPSHOT

2017-06-04 Thread Lando,Michael 
hi, were you able to compile the project?
The dependency is hosted in this repo:

   apache-public
   Apache-Public
   https://repository.apache.org/content/groups/public/
   default


Which is defined in the pom for the sdc.



BR,

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


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Coquelin, Sebastien
Sent: Friday, May 26, 2017 12:13 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Missing artifact 
commons-logging:commons-logging:jar:1.2.1-SNAPSHOT

Sorry for the spam it is actually in the Apache snapshots repo here (Useful if 
you’re going to setup your own Nexus…)

https://repository.apache.org/content/groups/snapshots/commons-logging/commons-logging/1.2.1-SNAPSHOT/

Sébastien

From: 
>
 on behalf of "Coquelin, Sebastien" 
>
Date: Thursday, May 25, 2017 at 5:01 PM
To: "onap-discuss@lists.onap.org" 
>
Subject: [onap-discuss] Missing artifact 
commons-logging:commons-logging:jar:1.2.1-SNAPSHOT

Hi,

I am trying to build ONAP projects locally and I have several projects failing 
with a missing dependency.

For example, If I try to build SDC I get this error :

Could not find artifact commons-logging:commons-logging:jar:1.2.1-SNAPSHOT

The artifact is referenced here :
https://gerrit.onap.org/r/gitweb?p=sdc.git;a=blob;f=common-app-api/pom.xml#l174

The artifact does not seem to be present on Maven Central or ONAP Nexus… can 
anyone help ?

https://search.maven.org/#search|gav|1|g%3A%22commons-logging%22%20AND%20a%3A%22commons-logging%22
https://nexus.onap.org/#nexus-search;quick~commons-logging

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

Re: [onap-discuss] Unable to on-board VNF in SDC

2017-06-04 Thread Lando,Michael 
It looks like the onboarding component is not working correctly.
What dockers are you using? 1.1.0 snapshoot or the 1.0.0?


BR,

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


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Tuesday, May 30, 2017 6:20 PM
To: bharath thiruveedula ; Viswa KSP 
; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Unable to on-board VNF in SDC

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Ok, you will need to get the logs from the sdc be and fe for this so we can 
debug a bit further as something seems to not be working in there

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

From: bharath thiruveedula [mailto:bharath_...@hotmail.com]
Sent: Tuesday, May 30, 2017 10:54 AM
To: Viswa KSP >; 
onap-discuss@lists.onap.org; ROSE, DANIEL V 
>
Subject: RE: [onap-discuss] Unable to on-board VNF in SDC

Hi Daniel,
I am working with Viswa.
I tried the api directly, it shows the same service unavailable error.
Indeed all requests to sdc1/feProxy/onboarding-api endpoints giving the same 
error.
Regards
Bharath T
From: ROSE, DANIEL V
Sent: Tuesday, 30 May, 8:10 PM
Subject: RE: [onap-discuss] Unable to on-board VNF in SDC
To: Viswa KSP, onap-discuss@lists.onap.org
Cc: bharath_...@hotmail.com
Does the api shown in the error message work if you go to it directly?

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 Viswa KSP
Sent: Tuesday, May 30, 2017 10:37 AM
To: onap-discuss@lists.onap.org
Cc: bharath_...@hotmail.com
Subject: [onap-discuss] Unable to on-board VNF in SDC

Dear All,

We are facing issues while trying to on board a VNF in SDC Design view. When we 
browse to on-boarding tab of SDC, we are facing b
[Image]
elow error.

​
Health check seems to be good -> we are able to see all ONAP services up & 
running.

http://sdc.api.simpledemo.openecomp.org:8181/sdc1/rest/healthCheck

{ "sdcVersion": "1.1.0", "siteMode": "unknown", "componentsInfo": [ { 
"healthCheckComponent": "BE", "healthCheckStatus": "UP", "version": "1.1.0", 
"description": "OK" }, { "healthCheckComponent": "ES", "healthCheckStatus": 
"UP", "description": "OK" }, { "healthCheckComponent": "TITAN", 
"healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": 
"DE", "healthCheckStatus": "UP", "description": "OK" }, { 
"healthCheckComponent": "FE", "healthCheckStatus": "UP", "version": "1.1.0", 
"description": "OK" } ] }

Please let us know if we are missing something here.

BR,
Viswa

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

Re: [onap-discuss] Question on VID

2017-06-04 Thread Dhananjay Pavgi 
Very valid point, Gaurav. ONAP has multiple GUIs and take this as a request to 
TSC/community members to arrive at role definition for each GUI to ensure that 
there’s no ambiguity and the same role calling to use more than one GUI. If 
there’s such overlaps then we should get those sorted.

thanks & regards,
Dhananjay Pavgi
Mobile : +91 98220 22264
[cid:image002.png@01CE7323.F2727500]   [ONAP_logo_Sig]
www.techmahindra.com Platinum 
Member. Visit : http://www.onap.org

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gaurav Gupta (c)
Sent: Saturday, June 03, 2017 9:07 AM
To: ROSE, DANIEL V ; shentao ; 
dsha...@interwise.com; eden.ro...@att.com; zahi.kapel...@att.com; HEMLI, 
AMICHAI ; ANAPAN-LAVALLE, HECTOR A 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Question on VID


Daniel Rose



I assumed that one of the Goal of ONAP is managing the Cloud Infra and Service  
easy for the Telco Operator  .



As in traditional/conventional  Network infra environment Network Element had 
their own EMS/NMS System and even if some functions of NE or all of the NE even 
if virtualized , poses a problem for the operator to look at 2 Screen at least .

a- EMS/NMS for NE and Service/KPI/Network Health Monitoring

b-  Another for monitoring the health of  Virtualized environment

Do you think - having  too many GUI's  would causes a lot of overhead unless 
you are thinking of restricting each GUI to a specific Role .

Do correct if I am missing something subtle .
with best regards
gaurav

From: 
onap-discuss-boun...@lists.onap.org 
>
 on behalf of ROSE, DANIEL V >
Sent: 02 June 2017 22:52
To: shentao; dsha...@interwise.com; 
eden.ro...@att.com; 
zahi.kapel...@att.com; HEMLI, AMICHAI; 
ANAPAN-LAVALLE, HECTOR A
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Question on VID


Hector do you know what kind of gui we have and where it is now?



Thanks,

Daniel Rose

ECOMP / ONAP

com.att.ecomp

732-420-7308



From: shentao [mailto:shen...@chinamobile.com]
Sent: Friday, June 02, 2017 5:09 AM
To: ROSE, DANIEL V >; 
dsha...@interwise.com; 
eden.ro...@att.com; 
zahi.kapel...@att.com; HEMLI, AMICHAI 
>
Cc: onap-discuss@lists.onap.org
Subject: 答复: [onap-discuss] Question on VID



Hi, Daniel



Thanks for your reply.

I’m working to summarize portal requirements and want to confirm if VID is 
going to provide a portal for service LCM because it seems no description about 
GUI in VID proposal.

If VID provides a portal for service LCM, I agree with you that there is no 
necessary to build the same part in Usecase UI project.

Btw, as I understand appc provides NB APIs, but not gui. Does service lifecycle 
gui not exist in VID gui?





Best regards,

Shentao





发件人: ROSE, DANIEL V [mailto:dr6...@att.com]
发送时间: 2017年5月31日 4:14
收件人: shentao; dsha...@interwise.com; 
eden.ro...@att.com; 
zahi.kapel...@att.com; HEMLI, AMICHAI
抄送: onap-discuss@lists.onap.org
主题: RE: [onap-discuss] Question on VID



On the one hand, VID already has a portal integration.



To answer your questions in a more broad way I don’t think we want to go about 
creating GUIs for each specific use case (but I guess if the community does 
they can reply and keep me honest) and that is what I got as the output from a 
read of your project proposal. The idea in my opinion is to add capabilities to 
the platform. When you look at it that way I see 3 gui areas Service Design, 
Service Instantiation and Service Lifecycle. Service design is already covered 
by sdc and that project. Service Instantiation is covered by VID and service 
lifecycle is covered by appc gui, which may or may not be open sourced right 
now I am not sure but I am sure we would be ok with doing so if its not. Then 
if the release 1 use cases need enhancements t that we should implement them 
generically and any vnf can use it. I certainly don’t want to build the same 
thing for vcpe and volte!



Either way I don’t know what exactly your project is looking to do. Can you 
clarify your project proposal a bit so vi d can better work together with you?



Thanks,

Daniel Rose

ECOMP / ONAP

com.att.ecomp

732-420-7308



From:

[onap-discuss] (no subject)

2017-06-04 Thread Abdelmuhaimen Seaudi 
Hi.

When I do a REST request on SDNC:
GET "
http://SDNC:8282/restconf/operational/network-topology:network-topology/;

I get:
{
  "network-topology": {
"topology": [
  {
"topology-id": "topology-netconf",
"node": [
  {
"node-id": "controller-config",
"netconf-node-topology:host": "127.0.0.1",
"netconf-node-topology:port": 1830,
"netconf-node-topology:connection-status": "connecting"
  }
]
  }
]
  }
}

Why the node "controller-config" is stuck in "connecting" state ?


However, when I make same REST request on APPC:

GET "
http://APPC:8282/restconf/operational/network-topology:network-topology/;

I get:
{
  "network-topology": {
"topology": [
  {
"topology-id": "topology-netconf",
"node": [
  {
"node-id": "controller-config",
"netconf-node-topology:host": "127.0.0.1",
"netconf-node-topology:connection-status": "connected",
"netconf-node-topology:available-capabilities": {
  "available-capability": [

"(config:aaa:authn:idmlight?revision=2015-12-04)aaa-idmlight",

  ]
},
"netconf-node-topology:unavailable-capabilities": {},
"netconf-node-topology:port": 1830


Thanks.

Abdelmuhaimen Seaudi, CCIE # 25265
Email: asea...@gmail.com
Skype: aseaudi
LinkedIn: www.linkedin.com/in/aseaudi
Telephone: +2012 84644 733
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] SDNC throwing error Unauthorized for all rest calls

2017-06-04 Thread Tapan Majhi 
Destroying the container worked ☺
Thanks Brian

From: FREEMAN, BRIAN D [mailto:bf1...@att.com]
Sent: Saturday, June 03, 2017 5:57 PM
To: Tapan Majhi ; Ahmad, Munir ; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] SDNC throwing error Unauthorized for all rest calls

That file has the updated password K*U.

I would destroy the docker container and re-pull it.

Brian


From: MAJHI, TAPAN
Sent: Saturday, June 03, 2017 6:35 AM
To: FREEMAN, BRIAN D >; Ahmad, Munir 
>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] SDNC throwing error Unauthorized for all rest calls

No luck ☹
I took the latest file copied to the location you asked and tried. Still not 
able to login to the webportal of SDNC. And getting the same 401 Unauthorized 
error on rest calls.
Password should change or remains the same after this process ?

Regards,
Tapan M

From: FREEMAN, BRIAN D [mailto:bf1...@att.com]
Sent: Friday, June 02, 2017 6:32 PM
To: Tapan Majhi >; Ahmad, 
Munir >; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] SDNC throwing error Unauthorized for all rest calls

Not sure it will fix your problem but try recopying the idmlight.db.mv.db file 
from gerrit into /opt/opendaylight/current inside the container.

The file with the password is replaced during the container creation so this 
“should” reset it.

sdnc/oam/installation/sdnc/target/docker-stage/Dockerfile:COPY 
idmlight.db.mv.db /opt/opendaylight/current

Brian


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of MAJHI, TAPAN
Sent: Friday, June 02, 2017 8:42 AM
To: Ahmad, Munir >; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDNC throwing error Unauthorized for all rest calls

Tried restarting the container , issue remains the same.

For the webportal I am unable to login since it requires credential and the 
current credential is not working.

"admin" - "Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U"

Any idea where can we reset this password or which bundle in SDNC is 
responsible for the authentication functionality ?


Regards
Tapan m

From: Ahmad, Munir [mailto:munir.ah...@bell.ca]
Sent: Friday, June 02, 2017 5:59 PM
To: Tapan Majhi >; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDNC throwing error Unauthorized for all rest calls


Hi Tapan,

Did you try restarting the sdnc_controller_container? I would try to recreating 
the container if restart doesn’t fix it. You also can preload your VNF through 
API docs web portal here is the link to preload VNF topology.

http://localhost:8282/apidoc/explorer/index.html#!/VNF-API(2015-07-20)/preload_vnf_topology_operation_post_475

Thanks
Munir
From: 
>
 on behalf of Tapan Majhi 
>
Date: Friday, June 2, 2017 at 4:57 AM
To: "onap-discuss@lists.onap.org" 
>
Subject: [onap-discuss] SDNC throwing error Unauthorized for all rest calls

My working SDNC container suddenly started giving error for all the rest calls .

root@4712c8e7d331:/# curl -k -X POST -i -H "Content-Type: application/json" -H 
"Accept: application/json" -H "Authorization: Basic 
YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==" -H 
"X-TransactionId: 0a3f6713-ba96-4971-a6f8-c2da85a3176e" -H "X-FromAppId: API 
client" -H "Expect:" 
http://localhost:8181/restconf/operations/VNF-API:preload-vnf-topology-operation
 --data-binary @./req.json
HTTP/1.1 401 Unauthorized
Set-Cookie: rememberMe=deleteMe; Path=/restconf; Max-Age=0; Expires=Sun, 
01-Jun-2017 21:06:16 GMT
WWW-Authenticate: BASIC realm="application"
Content-Length: 0
Server: Jetty(8.1.15.v20140411)


Now I am not even able to login to the swagger with