Re: [onap-discuss] [onap-tsc] Project Proposal: External SystemRegister

2017-05-17 Thread GILBERT, MAZIN E (MAZIN E) 
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, 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




原始邮件
发件人： ＜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, 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, and heartbeat detection of the 
system state.

For example, a user sent the authentic url, tenant, username and password of 
VIM to ESR. ESR try to connect the VIM with these information. After authentic 
succeed, ESR store these VIM information to A, do heartbeat detection for 
VIM status and present  the system status to user.



Best regards,

LiZi






原始邮件
发件人： ＜jpianigi...@juniper.net＞;
收件人：李滋00164331;
抄送人： ＜stephen.terr...@ericsson.com＞; 
＜onap-...@lists.onap.org＞; 
＜onap-discuss@lists.onap.org＞;
日 期 ：2017年05月16日 11:32
主 题 ：Re: [onap-tsc] Project Proposal: External System Register


Not clear what the

Re: [onap-discuss] [onap-tsc] Project Proposal: External SystemRegister

2017-05-17 Thread li.zi30 
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














原始邮件



发件人： ＜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, 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, and heartbeat detection of the 
system state. 

For example, a user sent the authentic url, tenant, username and password of 
VIM to ESR. ESR try to connect the VIM with these information. After authentic 
succeed, ESR store these VIM information to A, do heartbeat detection for 
VIM status and present  the system status to user. 

 

Best regards,

LiZi

 

 

 


原始邮件



发件人： ＜jpianigi...@juniper.net＞



收件人：李滋00164331



抄送人： ＜stephen.terr...@ericsson.com＞ ＜onap-...@lists.onap.org＞ 
＜onap-discuss@lists.onap.org＞



日 期 ：2017年05月16日 11:32



主 题 ：Re: [onap-tsc] Project Proposal: External System Register




 


Not clear what the business logic is.
 
 Sent from my iPhone




 On May 15, 2017, at 8:21 PM, "li.z...@zte.com.cn" ＜li.z...@zte.com.cn＞ wrote:


Hi Jacopo, Steve:

 

Actually, ESR has some business logic to deal with about external system, such 
as information verification,  which is out the scope of A When comes to the 
realization, ESR will be realized relying on A (store the external system 
data in A). 

 

Thanks,

LiZi

 

 

 

 

 




 



发件人： ＜jpianigi...@juniper.net＞



收件人： ＜stephen.terr...@ericsson.com＞李滋00164331   ＜onap-...@lists.onap.org＞ 
＜onap-discuss@lists.onap.org＞



日 期 ：2017年05月16日 01:19



主 题 ：RE: [onap-tsc] Project Proposal: External System Register




 


Hi,


I would agree with Steve about the need to limit overlap between subprojects


Jacopo  



From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
 Sent: Monday, May 15, 2017 10:10 AM
 To: li.z...@zte.com.cn onap-...@lists.onap.org onap-discuss@lists.onap.org
 Subject: Re: [onap-tsc] Project Proposal: External System Register




 


Hi,


 


While I agree with the need of the external elements to be registered, is there 
a reason for why we need a separate  register in addition to A? (note: I saw 
that Catherine   had a comment with a similar lines).  It may also relate to 
catalogue - LiZi, have you had a chance to chat with the A Project 
(https://wiki.onap.org/pages/viewpage.action?pageId=3246952).


 


Best Regards,


 


Steve.


 


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On

Re: [onap-discuss] [onap-tsc] Project Proposal: External SystemRegister

2017-05-16 Thread li.zi30 
Hi Daniel,





Just as you said what ONAP Operations manager care is " Platform Monitoring & 
healing: Monitor platform state, Platform health checks, fault tolerance and 
self-healing". It is about the ONAP system. And the ONAP Operations manager 
will not only check the state of platform, but also may influnce the lifecycle 
management.


The difference between ONAP Operations manager and ESR is that, ESR just care 
about the external system, such as VIM/VNFM/SDNC/EMS. And it will not has any 
influnce on the system lifecycle. It just check whether the external systems 
are reachable, and store the status. So that other components can determine 
whether the system is available based on the status.






Thanks,


LiZi















原始邮件



发件人： ＜dr6...@att.com＞
收件人：李滋00164331 ＜jpianigi...@juniper.net＞
抄送人： ＜onap-discuss@lists.onap.org＞ ＜onap-...@lists.onap.org＞
日 期 ：2017年05月16日 23:52
主 题 ：RE: [onap-discuss] [onap-tsc] Project Proposal: External SystemRegister







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, 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, and heartbeat detection of the 
system state. 

For example, a user sent the authentic url, tenant, username and password of 
VIM to ESR. ESR try to connect the VIM with these information. After authentic 
succeed, ESR store these VIM information to A, do heartbeat detection for 
VIM status and present  the system status to user. 

 

Best regards,

LiZi

 

 

 


原始邮件



发件人： ＜jpianigi...@juniper.net＞



收件人：李滋00164331



抄送人： ＜stephen.terr...@ericsson.com＞ ＜onap-...@lists.onap.org＞ 
＜onap-discuss@lists.onap.org＞



日 期 ：2017年05月16日 11:32



主 题 ：Re: [onap-tsc] Project Proposal: External System Register




 


Not clear what the business logic is.
 
 Sent from my iPhone




 On May 15, 2017, at 8:21 PM, "li.z...@zte.com.cn" ＜li.z...@zte.com.cn＞ wrote:


Hi Jacopo, Steve:

 

Actually, ESR has some business logic to deal with about external system, such 
as information verification,  which is out the scope of A When comes to the 
realization, ESR will be realized relying on A (store the external system 
data in A). 

 

Thanks,

LiZi

 

 

 

 

 




 



发件人： ＜jpianigi...@juniper.net＞



收件人： ＜stephen.terr...@ericsson.com＞李滋00164331   ＜onap-...@lists.onap.org＞ 
＜onap-discuss@lists.onap.org＞



日 期 ：2017年05月16日 01:19



主 题 ：RE: [onap-tsc] Project Proposal: External System Register




 


Hi,


I would agree with Steve about the need to limit overlap between subprojects


Jacopo  



From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
 Sent: Monday, May 15, 2017 10:10 AM
 To: li.z...@zte.com.cn onap-...@lists.onap.org onap-discuss@lists.onap.org
 Subject: Re: [onap-tsc] Project Proposal: External System Register




 


Hi,


 


While I agree with the need of the external elements to be registered, is there 
a reason for why we need a separate  register in addition to A? (note: I saw 
that Catherine   had a comment with a similar lines).  It may also relate to 
catalogue - LiZi, have you had a chance to chat with the A Project 
(https://wiki.onap.org/pages/viewpage.action?pageId=3246952).


 


Best Regards,


 


Steve.


 


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of li.z...@zte.com.cn
 Sent: 15 May 2017 04:32
 To: onap-...@lists.onap.org onap-discuss@lists.onap.org
 Subject: [onap-tsc] Project Proposal: External System Register


 

 


Dear ONAP TSC,


 


We would like to formally propose the External System Register project for ONAP.


 


ONAP components need to talk with external systems such as VIM/VNFM/SDNC/EMS to 
orchestrate a network service, for example, SO/VF-C need to talk with VIM to 
allocate resource and VNFMto deploy a VNF. So they should get the 
information of available external systems from a registry