Re: [onap-discuss] MultiVIM identity url and underlying VIM identity url, RE:08/15/17 - APPC/CDP-PAL/MultVIM - Touch Base 2

2017-08-21 Thread Xinhui Li 
+1

According to the past experience with ONAP demo set up, the inputs of the VID 
chat box are enumeration lists which we believe drawn by reading some 
configuration file or AAI.

Current design is Multi VIM/Cloud will use ESR for external system (e.g. 
openstack) registry. Let us ensure no conflict here.

Thanks,

Xinhui


From:  on behalf of "li.z...@zte.com.cn" 

Date: Monday, 21 August 2017 at 2:06 PM
To: "bin.y...@windriver.com" , "rx1...@att.com" 

Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] MultiVIM identity url and underlying VIM identity 
url, RE:08/15/17 - APPC/CDP-PAL/MultVIM - Touch Base 2


Hi Guys,



I found that you are talking about about the VIM information can be both 
inputed by ESR and VID. I feel confusing too. So hope this problem could be 
clarified at VID weekly meeting. The meeting information attaches bellow.



Thanks,

LiZi



[vid] Team ONAP5 Mon UTC 13:00 / China 21:00 / Eastern 09:00 / Pacific 
06:00<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D10782700&d=DwMGaQ&c=uilaK90D4TOVoH58JNXRgQ&r=14DWHoQdlEcTDc7RcGLzzkS0IMYLAIocLc5dNQRKqgk&m=TU8YL7AK6O1pSb6dR6NzEvzh-38noAZ1TEDgIIKSPDw&s=lh8ocsv_-EsvUJ_1hHLt8teWpX_J_2-QXMdKxZRXiBs&e=>
Monday

UTC 01:00 PM

China 09:00 PM

Eastern 09:00 AM

Pacific 06:00 AM


ONAP Meeting 5 is inviting you to a scheduled Zoom meeting.

Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/167433926<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_167433926&d=DwMGaQ&c=uilaK90D4TOVoH58JNXRgQ&r=14DWHoQdlEcTDc7RcGLzzkS0IMYLAIocLc5dNQRKqgk&m=TU8YL7AK6O1pSb6dR6NzEvzh-38noAZ1TEDgIIKSPDw&s=gY9Zsq4BIr0soCmrNfOw2IeumsfO--nuWdgPxdyKAkg&e=>

Or iPhone one-tap (US Toll): +14086380968,,167433926# or 
+16465588656,,167433926#

Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 167 433 926
International numbers available: 
https://zoom.us/zoomconference?m=mwsbUS78bJnISsV3I53VPekYg0oefEud<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_zoomconference-3Fm-3DmwsbUS78bJnISsV3I53VPekYg0oefEud&d=DwMGaQ&c=uilaK90D4TOVoH58JNXRgQ&r=14DWHoQdlEcTDc7RcGLzzkS0IMYLAIocLc5dNQRKqgk&m=TU8YL7AK6O1pSb6dR6NzEvzh-38noAZ1TEDgIIKSPDw&s=PUxe8bq1uCYMMLVzcszy9IzfO0LNl98T2ZxP1C1BEfE&e=>




原始邮件
发件人： ;
收件人： ; ; ; 
; ; ; ; 
; ; ; 
; ; ; 
; ; ; 
;李滋00164331; ; ; 
; ; ; ;
抄送人： ; ; ; 
; ;
日 期 ：2017年08月18日 10:20
主 题 ：RE: MultiVIM identity url and underlying VIM identity url, RE:08/15/17 - 
APPC/CDP-PAL/MultVIM - Touch Base 2


Hi Randa,

   That’s great. I like this approach.

   And the last point is not about APP-C to “support different  
types of cloud providers or different flavors of cloud” , My point is that 
there seems be some inconsistent between ESR and VID. I believe both of them 
provide portal to  register/input VIM’s information (identity 
url/username/password) and perhaps store those information differently, that 
might impact APP-C indirectly since eventually APP-C or policy will need to 
read these information. I saw Lizi (ESR PTL) had reached out  to VID team to 
sync with each other, so let’s see how this discrepancy being resolved. For 
now, we don’t have to worry about that too much.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: MAHER, RANDA [mailto:rx1...@att.com]
Sent: Friday, August 18, 2017 9:21 AM
To: Yang, Bin; Xinhui Li; SMITH, TYLER A; GUDISENA, VARUNESHWAR; ADDAGADA, 
SATISH; YOUNG, RYAN J; SEABOLT, SCOTT; KOYA, RAMPRASAD; HU, BIN; LEFEVRE, 
CATHERINE; 'marcus.willi...@intel.com'; VUL, ALEXANDER; HAY, AARON; DAVANGERE 
RAJASEKHAR, VEERENDRA;  NGUYEN, PHIL; BRADY, PATRICK D; WONNELL, SKIP; 
li.z...@zte.com.cn; Ethan Lynn; ANAPAN-LAVALLE, HECTOR A; FREEMAN, BRIAN D; 
MILLER, PAUL; VUL, ALEXANDER; av...@amdocs.com
Cc: DRAGOSH, PAM; GAO, CHENFEI; CHOU, JOSEPH Y; NGUEKO, GERVAIS-MARTIAL; 
FREEMAN, BRIAN D
Subject: RE: MultiVIM identity url and underlying VIM identity url, RE: 
08/15/17 - APPC/CDP-PAL/MultVIM - Touch Base 2

Hi Bin,
For tomorrow’s meeting , Ryan and Scott will step through how it works in APPC 
using an incoming request to illustrate the key points. I think that may be the 
 best way to approach this.  We will also record the session.

I have also invited Pam from Policy team to join the call, if she can make it, 
since for the vCPE use case, APPC will be triggered via Policy as part of the  
closed loop and in that scenario, the full url would be passed to APPC by 
Policy. Changes to the URL will impact Policy and I’m assuming the changes to 
AAI are already in discussions with that team.

I’m not sure I completely follow all your points below, but if you’re referring

Re: [onap-discuss] MultiVIM identity url and underlying VIM identity url, RE:08/15/17 - APPC/CDP-PAL/MultVIM - Touch Base 2

2017-08-20 Thread li.zi30 
Hi Guys,




I found that you are talking about about the VIM information can be both 
inputed by ESR and VID. I feel confusing too. So hope this problem could be 
clarified at VID weekly meeting. The meeting information attaches bellow.




Thanks,

LiZi




[vid] Team ONAP5 Mon UTC 13:00 / China 21:00 / Eastern 09:00 / Pacific 06:00

MondayUTC 01:00 PMChina 09:00 PMEastern 09:00 AMPacific 06:00 AM

ONAP Meeting 5 is inviting you to a scheduled Zoom meeting.


Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/167433926


Or iPhone one-tap (US Toll): +14086380968,,167433926# or 
+16465588656,,167433926#


Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 167 433 926
International numbers available: 
https://zoom.us/zoomconference?m=mwsbUS78bJnISsV3I53VPekYg0oefEud











原始邮件



发件人： 
收件人： 

   

 李滋00164331  


抄送人：
 
日 期 ：2017年08月18日 10:20
主 题 ：RE: MultiVIM identity url and underlying VIM identity url, RE:08/15/17 - 
APPC/CDP-PAL/MultVIM - Touch Base 2







Hi Randa,


 


   That’s great. I like this approach.


 


   And the last point is not about APP-C to “support different  
types of cloud providers or different flavors of cloud” , My point is that 
there seems be some inconsistent between ESR and VID. I believe both of them 
provide portal to  register/input VIM’s information (identity 
url/username/password) and perhaps store those information differently, that 
might impact APP-C indirectly since eventually APP-C or policy will need to 
read these information. I saw Lizi (ESR PTL) had reached out  to VID team to 
sync with each other, so let’s see how this discrepancy being resolved. For 
now, we don’t have to worry about that too much.


 


Best Regards,


Bin Yang,Solution Readiness Team,Wind River


Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189


Skype: yangbincs993



 



From: MAHER, RANDA [mailto:rx1...@att.com] 
 Sent: Friday, August 18, 2017 9:21 AM
 To: Yang, Bin Xinhui Li SMITH, TYLER A GUDISENA, VARUNESHWAR ADDAGADA, SATISH 
YOUNG, RYAN J SEABOLT, SCOTT KOYA, RAMPRASAD HU, BIN LEFEVRE, CATHERINE 
'marcus.willi...@intel.com' VUL, ALEXANDER HAY, AARON DAVANGERE RAJASEKHAR, 
VEERENDRA  NGUYEN, PHIL BRADY, PATRICK D WONNELL, SKIP li.z...@zte.com.cn Ethan 
Lynn ANAPAN-LAVALLE, HECTOR A FREEMAN, BRIAN D MILLER, PAUL VUL, ALEXANDER 
av...@amdocs.com
 Cc: DRAGOSH, PAM GAO, CHENFEI CHOU, JOSEPH Y NGUEKO, GERVAIS-MARTIAL FREEMAN, 
BRIAN D
 Subject: RE: MultiVIM identity url and underlying VIM identity url, RE: 
08/15/17 - APPC/CDP-PAL/MultVIM - Touch Base 2




 


Hi Bin,


For tomorrow’s meeting , Ryan and Scott will step through how it works in APPC 
using an incoming request to illustrate the key points. I think that may be the 
 best way to approach this.  We will also record the session.


 


I have also invited Pam from Policy team to join the call, if she can make it, 
since for the vCPE use case, APPC will be triggered via Policy as part of the  
closed loop and in that scenario, the full url would be passed to APPC by 
Policy. Changes to the URL will impact Policy and I’m assuming the changes to 
AAI are already in discussions with that team.


 


I’m not sure I completely follow all your points below, but if you’re referring 
to scope that would support different types of cloud providers or different  
flavors of cloud, etc..., then I agree with you, that is much larger challenge 
and taking it to architecture subcommittee may be the right place to start.


 


Thanks, Randa


 



From: Yang, Bin [mailto:bin.y...@windriver.com] 
 Sent: Wednesday, August 16, 2017 7:05 PM
 To: MAHER, RANDA  Xinhui Li  SMITH, TYLER 
A  GUDISENA, VARUNESHWAR   ADDAGADA, SATISH 
 YOUNG, RYAN J  SEABOLT, SCOTT  
KOYA, RAMPRASAD   HU, BIN  LEFEVRE, CATHERINE 
 'marcus.willi...@intel.com'  
VUL, ALEXANDER   HAY, AARON  DAVANGERE 
RAJASEKHAR, VEERENDRA  NGUYEN, PHIL   BRADY, 
PATRICK D  WONNELL, SKIP  li.z...@zte.com.cn 
Ethan Lynn  ANAPAN-LAVALLE, HECTOR A  
FREEMAN, BRIAN D   MILLER, PAUL  VUL, ALEXANDER 
 av...@amdocs.com
 Subject: RE: MultiVIM identity url and underlying VIM identity url, RE: 
08/15/17 - APPC/CDP-PAL/MultVIM - Touch Base 2




 


Hi Randa,


 


   It will helpful to understand the context if you could give the 
concrete example of “full URL”, “incoming request”  “additional version in the  
URL” .


   If the full URL is for accessing MultiVIM identity service like 
“http://msb.onap.org:80/api/multicloud/v0/{cloudowner}_{region}/identity/v3”,  
I think it is available from cloud-region of AAI, you don’t need do extra 
transforming, but just pass it to CDP-PAL.


 


Since the intention we support “backward compatible API” is to minimize the 
burden on APPC by making MultiVIM as transparent as possible,  I hope all 
stakeholders (MultiVIM,APPC, AAI, ESR, VID, etc.) coul