Re: [opnfv-tech-discuss] API mismatch between Open-O and Compass

2016-12-21 Thread Yingjun Li
Good to know the Common Service (Keystone) is using OpenStack API V3. Thanks Yingjun From: Sukesh A C Sent: Tuesday, December 20, 2016 7:53 PM To: zhao.huab...@zte.com.cn; Gildas Lanilis Cc: narinder.gu...@canonical.com; Yingjun Li; denglin...@chinamobile.com; huangxiangyu; Thajudheen Rajak; Gao

Re: [opnfv-tech-discuss] API mismatch between Open-O and Compass

2016-12-20 Thread Sukesh A C
Hi Huabing, We use keystone identity v3 api(latest version in keystone) in open-o auth. Thanks, Sukesh. *** 本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了

Re: [opnfv-tech-discuss] API mismatch between Open-O and Compass

2016-12-20 Thread zhao.huabing
Hi Gildas, I guess you was asking the Common services, right? Currently Auth are using Keystone for auth implementation. But I think it's not the openst used as the vim by OPEN-O, but an independent one. @Sukeshu, Could you pls confirm that and the API version of Keystone used in Auth? Tha

Re: [opnfv-tech-discuss] API mismatch between Open-O and Compass

2016-12-20 Thread Gildas Lanilis
Thanks Victor that helps. FYI, we have a very tight timeline for OPERA. Scenario integration and Feature Freeze must be completed by Jan 13, 2017 (OPNVF MS5 milestone). Let Yingjun and myself know as you made progress. Thanks, Gildas From: Gaoweitao (Victor, MANO) Sent: Tuesday, December 20, 20

Re: [opnfv-tech-discuss] API mismatch between Open-O and Compass

2016-12-20 Thread Yingjun Li
Thanks for all your replies. Harry, I think currently you can only use OpenStack Mitaka for your integration testing. Then switch to Newton release after OPEN-O is Newton ready. Victor, please keep Harry, Gildas and me informed. Thanks Yingjun From: Gildas Lanilis Sent: Tuesday, December 20, 2

Re: [opnfv-tech-discuss] API mismatch between Open-O and Compass

2016-12-20 Thread Gildas Lanilis
Hi, Looping in Lingli (PTL for OPEN-O NFVO) and Huabing (PTL for OPEN-O SDNO). Lingli, Huabing, The question is in regard to the OPERA project (that OPEN-O approved back in August 2016). Is supporting OpenStack Newton API V3 part of the scope of Mercury Release? Thanks, Gildas From: Narinder

Re: [opnfv-tech-discuss] API mismatch between Open-O and Compass

2016-12-20 Thread Narinder Gupta
Yingjun, By default Juju will deploy to version 2 but we can switch to v3 in case other installers and applications are ready. As if today charm support both v2 and v3 but JOID is enabling v2. Thanks and Regards, Narinder Gupta (PMP) narinder.gu...@canonical.com Canonical, Ltd.

Re: [opnfv-tech-discuss] API mismatch between Open-O and Compass

2016-12-20 Thread Yingjun Li
Gildas Could you help answering Harry's question? OPEN-O 2 release will support OpenStack Newton, which means to support OS API v3. I guess the major parts involved in OpenStack API is NFVO and Common service. What is the OPEN-O plan to support the Newton API? Narinder, can you confirm that Ju

[opnfv-tech-discuss] API mismatch between Open-O and Compass

2016-12-19 Thread huangxiangyu
Hi Yingjun Currently , OpenStack Newton deployed by Compass use keystone API V3 instead of V2 . I assume there may be API mismatch when Open-O talk to OpenStack. Please check with Open-O developers if Open-O only support keystone V2. And if so, modification should be made in Open-O in