Re: [onap-discuss] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-14 Thread Chaker Al Hakim 
+1

From: onap-disc...@lists.onap.org [mailto:onap-disc...@lists.onap.org] On 
Behalf Of Catherine LEFEVRE
Sent: Sunday, October 14, 2018 4:06 PM
To: onap-tsc@lists.onap.org; onap-tsc-v...@lists.onap.org
Cc: onap-discuss ; Seshu m 
; TIMONEY, DAN 
Subject: Re: [onap-discuss] [onap-tsc] [TSC] Request API change waiver between 
SO and SDNC

Dear TSC Members (or proxy),

Thank you for your feedback.
If I did not miss any vote, 72% of TSC team has already approved the waiver.
We can conclude that the waiver has been granted.
· Andreas Geissler (DT)
· +1 Ranny Haiby, Nokia
· +1 Alexis de Talhouet , Bell Canada
· Chaker Al-Hakim, Huawei
· +1  Catherine Lefevre, AT
· +1 Eric Debeau, Orange
· +1 Jason Hunt, IBM
· +1 Srinivasa Addepalli, Intel
· +1 Murat Turpcu,turk telekom
· +1 Ning So, Reliance Jio
· Lingli Deng, CMCC
· +1 Alla Goldner, Amdocs
· +1 Bin Yang, Wind River
· Milind Jalwadi,, TechMahindra
· +1 Stephen Terrill, Ericsson
· +1 Susana Sabater, Vodafone
· +1 Viswa, Verizon
· Yan Chen, China Telecom
Many thanks & regards
Catherine
From: Lefevre, Catherine
Sent: Friday, October 12, 2018 12:41 PM
To: 'onap-tsc@lists.onap.org' 
mailto:onap-tsc@lists.onap.org>>; 
'onap-tsc-v...@lists.onap.org' 
mailto:onap-tsc-v...@lists.onap.org>>
Cc: 'onap-discuss' 
mailto:onap-disc...@lists.onap.org>>; 'Seshu m' 
mailto:seshu.kuma...@huawei.com>>; TIMONEY, DAN 
mailto:dt5...@att.com>>
Subject: RE: [onap-tsc] [TSC] Request API change waiver between SO and SDNC
Importance: High

Good morning Alexis,

Thank you for your leadership supporting the teams to progress quickly on this 
issue.
I am adding the TSC vote distro list in order to increase the visibility of 
this request.

TSC Members (or proxy)
Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
than Oct 13th End of your Day.
· Andreas Geissler (DT)
· Ranny Haiby, Nokia
· David Sauvageau, Bell Canada
· Chaker Al-Hakim, Huawei
· +1  Catherine Lefevre, AT
· Eric Debeau, Orange
· Jason Hunt, IBM
· Srinivasa Addepalli, Intel
· Murat Turpcu,turk telekom
· Ning So, Reliance Jio
· Lingli Deng, CMCC
· Alla Goldner, Amdocs
· Bin Yang, Wind River
· Milind Jalwadi,, TechMahindra
· Stephen Terrill, Ericsson
· Susana Sabater, Vodafone
· Viswa, Verizon
· Yan Chen, China Telecom
Many thanks & regards
Catherine

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: 
.https://gerrit.onap.org/r/#/c/67413/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_67413_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=c31OYuaPawMl_ySS_voXJQ=IRnORADhsIQatMiCFmpWYSg2RJ98PK3OBna5p6LFn8w=MlFEjJ27qgrsAF2_ZjsQRU5IFM7F9Z2E57BCD-A25FM=>

Regards,
Alexis


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3907): https://lists.onap.org/g/onap-tsc/message/3907
Mute This Topic: https://lists.onap.org/mt/27317325/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-14 Thread Catherine LEFEVRE 
Dear TSC Members (or proxy),

Thank you for your feedback.
If I did not miss any vote, 72% of TSC team has already approved the waiver.
We can conclude that the waiver has been granted.
·Andreas Geissler (DT)
·+1 Ranny Haiby, Nokia
·+1 Alexis de Talhouet , Bell Canada
·Chaker Al-Hakim, Huawei
·+1  Catherine Lefevre, AT
·+1 Eric Debeau, Orange
·+1 Jason Hunt, IBM
·+1 Srinivasa Addepalli, Intel
·+1 Murat Turpcu,turk telekom
·+1 Ning So, Reliance Jio
·Lingli Deng, CMCC
·+1 Alla Goldner, Amdocs
·+1 Bin Yang, Wind River
·Milind Jalwadi,, TechMahindra
·+1 Stephen Terrill, Ericsson
·+1 Susana Sabater, Vodafone
·+1 Viswa, Verizon
·Yan Chen, China Telecom
Many thanks & regards
Catherine
From: Lefevre, Catherine
Sent: Friday, October 12, 2018 12:41 PM
To: 'onap-tsc@lists.onap.org' ; 
'onap-tsc-v...@lists.onap.org' 
Cc: 'onap-discuss' ; 'Seshu m' 
; TIMONEY, DAN 
Subject: RE: [onap-tsc] [TSC] Request API change waiver between SO and SDNC
Importance: High

Good morning Alexis,

Thank you for your leadership supporting the teams to progress quickly on this 
issue.
I am adding the TSC vote distro list in order to increase the visibility of 
this request.

TSC Members (or proxy)
Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
than Oct 13th End of your Day.
·Andreas Geissler (DT)
·Ranny Haiby, Nokia
·David Sauvageau, Bell Canada
·Chaker Al-Hakim, Huawei
·+1  Catherine Lefevre, AT
·Eric Debeau, Orange
·Jason Hunt, IBM
·Srinivasa Addepalli, Intel
·Murat Turpcu,turk telekom
·Ning So, Reliance Jio
·Lingli Deng, CMCC
·Alla Goldner, Amdocs
·Bin Yang, Wind River
·Milind Jalwadi,, TechMahindra
·Stephen Terrill, Ericsson
·Susana Sabater, Vodafone
·Viswa, Verizon
·Yan Chen, China Telecom
Many thanks & regards
Catherine

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: 
.https://gerrit.onap.org/r/#/c/67413/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_67413_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=c31OYuaPawMl_ySS_voXJQ=IRnORADhsIQatMiCFmpWYSg2RJ98PK3OBna5p6LFn8w=MlFEjJ27qgrsAF2_ZjsQRU5IFM7F9Z2E57BCD-A25FM=>

Regards,
Alexis


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3906): https://lists.onap.org/g/onap-tsc/message/3906
Mute This Topic: https://lists.onap.org/mt/27260030/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-12 Thread Srini 
+1 (on API change)

Thanks
Srini


From: onap-tsc-v...@lists.onap.org [mailto:onap-tsc-v...@lists.onap.org] On 
Behalf Of Catherine LEFEVRE
Sent: Friday, October 12, 2018 3:41 AM
To: onap-tsc@lists.onap.org; onap-tsc-v...@lists.onap.org
Cc: onap-discuss ; Seshu m 
; TIMONEY, DAN 
Subject: Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between 
SO and SDNC
Importance: High

Good morning Alexis,

Thank you for your leadership supporting the teams to progress quickly on this 
issue.
I am adding the TSC vote distro list in order to increase the visibility of 
this request.

TSC Members (or proxy)
Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
than Oct 13th End of your Day.
·Andreas Geissler (DT)
·Ranny Haiby, Nokia
·David Sauvageau, Bell Canada
·Chaker Al-Hakim, Huawei
·+1  Catherine Lefevre, AT
·Eric Debeau, Orange
·Jason Hunt, IBM
·Srinivasa Addepalli, Intel
·Murat Turpcu,turk telekom
·Ning So, Reliance Jio
·Lingli Deng, CMCC
·Alla Goldner, Amdocs
·Bin Yang, Wind River
·Milind Jalwadi,, TechMahindra
·Stephen Terrill, Ericsson
·Susana Sabater, Vodafone
·Viswa, Verizon
·Yan Chen, China Telecom
Many thanks & regards
Catherine

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: 
.https://gerrit.onap.org/r/#/c/67413/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_67413_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=c31OYuaPawMl_ySS_voXJQ=IRnORADhsIQatMiCFmpWYSg2RJ98PK3OBna5p6LFn8w=MlFEjJ27qgrsAF2_ZjsQRU5IFM7F9Z2E57BCD-A25FM=>

Regards,
Alexis


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3897): https://lists.onap.org/g/onap-tsc/message/3897
Mute This Topic: https://lists.onap.org/mt/27271291/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-12 Thread Alexis de Talhouet 
+1 from me, obviously :)  - Proxy for David Sauvageau

> On Oct 12, 2018, at 8:34 AM, Ning So  wrote:
> 
> ＋1.
> 
> Ning So
> 
> 
>  Original Message 
> Subject: [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change 
> waiver between SO and SDNC
> From: Catherine LEFEVRE  <mailto:catherine.lefe...@intl.att.com>>
> Date: Oct 12, 2018, 5:43 AM
> To: onap-tsc@lists.onap.org 
> <mailto:onap-tsc@lists.onap.org>,onap-tsc-v...@lists.onap.org 
> <mailto:onap-tsc-v...@lists.onap.org>
> The e-mail below is from an external source. Please do not open attachments 
> or click links from an unknown or suspicious origin.
> 
> 
> Good morning Alexis,
>
> Thank you for your leadership supporting the teams to progress quickly on 
> this issue.
> I am adding the TSC vote distro list in order to increase the visibility of 
> this request.
>
> TSC Members (or proxy)
> Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
> than Oct 13th End of your Day.
> ·Andreas Geissler (DT)
> ·Ranny Haiby, Nokia
> ·David Sauvageau, Bell Canada
> ·Chaker Al-Hakim, Huawei
> ·+1  Catherine Lefevre, AT   
> ·Eric Debeau, Orange
> ·Jason Hunt, IBM
> ·Srinivasa Addepalli, Intel
> ·Murat Turpcu,turk telekom
> ·Ning So, Reliance Jio
> ·Lingli Deng, CMCC
> ·Alla Goldner, Amdocs
> ·Bin Yang, Wind River
> ·Milind Jalwadi,, TechMahindra
> ·Stephen Terrill, Ericsson
> ·Susana Sabater, Vodafone
> ·Viswa, Verizon
> ·Yan Chen, China Telecom
> Many thanks & regards
> Catherine
>
> From: onap-tsc@lists.onap.org <mailto:onap-tsc@lists.onap.org> 
> [mailto:onap-tsc@lists.onap.org <mailto:onap-tsc@lists.onap.org>] On Behalf 
> Of Alexis de Talhouet
> Sent: Friday, October 12, 2018 4:59 AM
> To: onap-tsc; onap-discuss
> Cc: Seshu m; TIMONEY, DAN
> Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC
>
> Hello TSC,
>
> As discussed during today’s meeting, an issue has been identified in the new 
> SO building block, introducing a regression in term of functionality from 
> previous release.
> PTLs from both projects acknowledge and agree with the required changes.
>
> Expected behaviour:
> Have the cloud owner / cloud region being retrievable from static 
> configuration file.
>
> Current behaviour:
> Cloud owner is hardcoded in the code, with no way to change it using config 
> file.
>
> API change requested:
> SDN-C: GENERIC-RESOURCE-API.yang
>
> Impact:
> This API change will allow SO to resolve the cloud owner from the config file 
> (similar to what we had in previous release), and to be able to use it with 
> the GR-API.
>
> Patches:
> SO:
> 1.  Use a property instead of hard coded value. (TBD)
> 2.  Push the changeset to allow it to be set on the north-bound 
> api.  (TBD)
> SDNC: 
> 1 Add cloud-owner definition: 
> .https://gerrit.onap.org/r/#/c/67413/ 
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_67413_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=c31OYuaPawMl_ySS_voXJQ=IRnORADhsIQatMiCFmpWYSg2RJ98PK3OBna5p6LFn8w=MlFEjJ27qgrsAF2_ZjsQRU5IFM7F9Z2E57BCD-A25FM=>
>
> Regards,
> Alexis
> 
> "Confidentiality Warning: This message and any attachments are intended only 
> for the use of the intended recipient(s), are confidential and may be 
> privileged. If you are not the intended recipient, you are hereby notified 
> that any review, re-transmission, conversion to hard copy, copying, 
> circulation or other use of this message and any attachments is strictly 
> prohibited. If you are not the intended recipient, please notify the sender 
> immediately by return email and delete this message and any attachments from 
> your system.
> 
> Virus Warning: Although the company has taken reasonable precautions to 
> ensure no viruses are present in this email. The company cannot accept 
> responsibility for any loss or damage arising from the use of this email or 
> attachment."
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3894): https://lists.onap.org/g/onap-tsc/message/3894
Mute This Topic: https://lists.onap.org/mt/27269787/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-12 Thread Ning So 
＋1.

Ning So


 Original Message 
Subject: [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change 
waiver between SO and SDNC
From: Catherine LEFEVRE 
Date: Oct 12, 2018, 5:43 AM
To: onap-tsc@lists.onap.org,onap-tsc-v...@lists.onap.org

The e-mail below is from an external source. Please do not open attachments or 
click links from an unknown or suspicious origin.

Good morning Alexis,

Thank you for your leadership supporting the teams to progress quickly on this 
issue.
I am adding the TSC vote distro list in order to increase the visibility of 
this request.

TSC Members (or proxy)
Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
than Oct 13th End of your Day.
*Andreas Geissler (DT)
*Ranny Haiby, Nokia
*David Sauvageau, Bell Canada
*Chaker Al-Hakim, Huawei
*+1  Catherine Lefevre, AT
*Eric Debeau, Orange
*Jason Hunt, IBM
*Srinivasa Addepalli, Intel
*Murat Turpcu,turk telekom
*Ning So, Reliance Jio
*Lingli Deng, CMCC
*Alla Goldner, Amdocs
*Bin Yang, Wind River
*Milind Jalwadi,, TechMahindra
*Stephen Terrill, Ericsson
*Susana Sabater, Vodafone
*Viswa, Verizon
*Yan Chen, China Telecom
Many thanks & regards
Catherine

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: 
.https://gerrit.onap.org/r/#/c/67413/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_67413_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=c31OYuaPawMl_ySS_voXJQ=IRnORADhsIQatMiCFmpWYSg2RJ98PK3OBna5p6LFn8w=MlFEjJ27qgrsAF2_ZjsQRU5IFM7F9Z2E57BCD-A25FM=>

Regards,
Alexis

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s). 
are confidential and may be privileged. If you are not the intended recipient. 
you are hereby notified that any 
review. re-transmission. conversion to hard copy. copying. circulation or other 
use of this message and any attachments is 
strictly prohibited. If you are not the intended recipient. please notify the 
sender immediately by return email. 
and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. 
The company cannot accept responsibility for any loss or damage arising from 
the use of this email or attachment."

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3893): https://lists.onap.org/g/onap-tsc/message/3893
Mute This Topic: https://lists.onap.org/mt/27269787/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [E] Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-12 Thread Viswanath Kumar Skand Priya via Lists.Onap.Org 
+1 for API Waiver.

<http://www.verizon.com>

Viswanath Kumar Skand Priya
Senior Architect
Technology, Architecture & Planning



On Fri, Oct 12, 2018 at 4:10 PM Catherine LEFEVRE <
catherine.lefe...@intl.att.com> wrote:

> Good morning Alexis,
>
>
>
> Thank you for your leadership supporting the teams to progress quickly on
> this issue.
>
> I am adding the TSC vote distro list in order to increase the visibility
> of this request.
>
>
>
> TSC Members (or proxy)
>
> Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no
> later than *Oct 13th End of your Day*.
>
> ·Andreas Geissler (DT)
>
> ·Ranny Haiby, Nokia
>
> ·David Sauvageau, Bell Canada
>
> ·Chaker Al-Hakim, Huawei
>
> ·+1  Catherine Lefevre, AT
>
> ·Eric Debeau, Orange
>
> ·Jason Hunt, IBM
>
> ·Srinivasa Addepalli, Intel
>
> ·Murat Turpcu,turk telekom
>
> ·Ning So, Reliance Jio
>
> ·Lingli Deng, CMCC
>
> ·Alla Goldner, Amdocs
>
> ·Bin Yang, Wind River
>
> ·Milind Jalwadi,, TechMahindra
>
> ·Stephen Terrill, Ericsson
>
> ·Susana Sabater, Vodafone
>
> ·Viswa, Verizon
>
> ·Yan Chen, China Telecom
>
> Many thanks & regards
>
> Catherine
>
>
>
> *From:* onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org
> ] *On Behalf Of *Alexis de Talhouet
> *Sent:* Friday, October 12, 2018 4:59 AM
> *To:* onap-tsc; onap-discuss
> *Cc:* Seshu m; TIMONEY, DAN
> *Subject:* [onap-tsc] [TSC] Request API change waiver between SO and SDNC
>
>
>
> Hello TSC,
>
>
>
> As discussed during today’s meeting, an issue has been identified in the
> new SO building block, introducing a regression in term of functionality
> from previous release.
>
> PTLs from both projects acknowledge and agree with the required changes.
>
>
>
> *Expected behaviour:*
>
> Have the cloud owner / cloud region being retrievable from static
> configuration file.
>
>
>
> *Current behaviour:*
>
> Cloud owner is hardcoded in the code, with no way to change it using
> config file.
>
>
>
> *API change requested:*
>
> SDN-C: GENERIC-RESOURCE-API.yang
>
>
>
> *Impact:*
>
> This API change will allow SO to resolve the cloud owner from the config
> file (similar to what we had in previous release), and to be able to use it
> with the GR-API.
>
>
>
> *Patches*:
>
> SO:
>
> 1.  Use a property instead of hard coded value. (TBD)
>
> 2.  Push the changeset to allow it to be set on the
> north-bound api.  (TBD)
>
> SDNC:
>
> 1 Add cloud-owner definition: .
> https://gerrit.onap.org/r/#/c/67413/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_67413_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=c31OYuaPawMl_ySS_voXJQ=IRnORADhsIQatMiCFmpWYSg2RJ98PK3OBna5p6LFn8w=MlFEjJ27qgrsAF2_ZjsQRU5IFM7F9Z2E57BCD-A25FM=>
>
>
>
> Regards,
>
> Alexis
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3892): https://lists.onap.org/g/onap-tsc/message/3892
Mute This Topic: https://lists.onap.org/mt/27269169/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-12 Thread Catherine LEFEVRE 
Good morning Alexis,

Thank you for your leadership supporting the teams to progress quickly on this 
issue.
I am adding the TSC vote distro list in order to increase the visibility of 
this request.

TSC Members (or proxy)
Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
than Oct 13th End of your Day.
·Andreas Geissler (DT)
·Ranny Haiby, Nokia
·David Sauvageau, Bell Canada
·Chaker Al-Hakim, Huawei
·+1  Catherine Lefevre, AT
·Eric Debeau, Orange
·Jason Hunt, IBM
·Srinivasa Addepalli, Intel
·Murat Turpcu,turk telekom
·Ning So, Reliance Jio
·Lingli Deng, CMCC
·Alla Goldner, Amdocs
·Bin Yang, Wind River
·Milind Jalwadi,, TechMahindra
·Stephen Terrill, Ericsson
·Susana Sabater, Vodafone
·Viswa, Verizon
·Yan Chen, China Telecom
Many thanks & regards
Catherine

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] On Behalf Of Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: 
.https://gerrit.onap.org/r/#/c/67413/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_67413_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=c31OYuaPawMl_ySS_voXJQ=IRnORADhsIQatMiCFmpWYSg2RJ98PK3OBna5p6LFn8w=MlFEjJ27qgrsAF2_ZjsQRU5IFM7F9Z2E57BCD-A25FM=>

Regards,
Alexis


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3890): https://lists.onap.org/g/onap-tsc/message/3890
Mute This Topic: https://lists.onap.org/mt/27260030/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-11 Thread Yang Bin 
OK, I am ok with that, thanks for the explanation.

BTW, could you share some pointers w.r.t. the new BB, especially “With these 
new flows, at assignment stage, all the required ressources would get resolved 
by SDNC and stored in SDNC GR-API,” I would like to understand what the flow is 
at the assignment stage, and check if multicloud could help on that.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Alexis de Talhouet
Sent: Friday, October 12, 2018 10:18 AM
To: onap-tsc@lists.onap.org
Cc: onap-discuss; Seshu m; TIMONEY, DAN
Subject: Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

We re not trying to fulfill this requirement; although we are very aware of it. 
It is planned for Dublin, and won’t get in Casablanca; this is not the 
intention.
We’re not either changing any of the existing behaviour.
I’m not proposing any solution here, simply asking for an API waiver as we need 
to add a field in GR-API yang to get rid of the hard coded cloud owner in the 
new SO BB. The solution has been there before, it’s just lack of time before 
API freeze, and in this matter, introducing a regression.

Background:
SO and SDNC added respectively new Building Blocks and support for GR-API, in 
order to avoir having to perform the manual preload step. With these new flows, 
at assignment stage, all the required ressources would get resolved by SDNC and 
stored in SDNC GR-API, so at creation stage, all SO has to do is query SDNC to 
gets the resources to use, and proceed with creation.
What was uncover late is SO new BBs are using a hard coded cloud owner. The 
change is simply to allow having that cloud owner configurable. It is a 
small/quick fix in order to provide somewhat of a feature parity between former 
SO flow and new SO flows.

I’m asking the TSC for an API waiver as we're pass API freeze and this is an 
API change, in some ways.  If you want to discuss more in detail that 
functionality, I’ll be happy to explain over a meeting.
My intention is to have a quick turnaround on the API change waiver request. I 
hope TSC will be able to see the urgency in that matter, given RC0, so we don’t 
debate too much on a requirement, as as stated before, we’re not trying to 
fulfil any; simply to fix a regression.

Thanks,
Alexis

On Oct 11, 2018, at 9:04 PM, Yang Bin 
mailto:bin.y...@windriver.com>> wrote:
Hi Alexis, Dan,

   I am not sure if you are aware the ONAP functional requirement 
about the “Centralized Representation and Consistent Identification of Cloud 
Regions In 
ONAP<https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP>”
 
https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP

   The functional requirement consists of 2 important changes:
1, remove any hardcoded/redundant representation of a single cloud region, the 
hard-coded cloud-sites in SO configuration file is exactly what is  targeting 
to be refactored. Now this part is on track of pairwise testing between 
SO/MultiCloud .
2, apply the usage of ID of a cloud region in a consistent way , the agreement 
is that the composite keys: {cloud-owner}/{cloud-region-id} will be applied 
whenever ONAP component wants to refer to a cloud region. This part requires 
the API changes between VID/SO/SDNC and other related projects. It is  a 
stretch goal in Casablanca, perhaps we can get it done in Dublin Release.

   I do believe both of 2 changes above might be related to your 
proposal. I would like to discuss a little bit about the issue and your 
proposal so that maybe we can come up with more comprehensive/consistent 
solution to get things (API changes) done at one time.

   If you don’t mind, we can start with several questions:
   1, why should the Cloud-Owner be provisioned to SDNC with 
REST-API?
I guess your proposal is to provision the “Cloud Owner” instead of having it 
being hard-coded . I agree with you that it should not be hard-coded, but why 
should the Cloud-Owner be provisioned to SDNC with REST-API?
IMHO, “Cloud-Owner” (and the cloud-region-id ) should be selected either by 
user via VID portal or by OOF according to policy. In that case, the ID  of the 
selected cloud region ({cloud-owner}/{cloud-region-id} ) should be passed to 
SO/SDNC/etc. through rest API.

2, Will SDNC use the ID  of the selected cloud region to retrieve information 
from AAI?
   This question is to help me understand what the interactions are 
between SDNC and AAI

3, Will SDNC use the ID  of the selected cloud region to retrieve information 
from underlying VIM/Cloud instance (e.g. OpenStack instance)?
   This qu

Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-11 Thread Alexis de Talhouet 
We re not trying to fulfill this requirement; although we are very aware of it. 
It is planned for Dublin, and won’t get in Casablanca; this is not the 
intention.
We’re not either changing any of the existing behaviour.
I’m not proposing any solution here, simply asking for an API waiver as we need 
to add a field in GR-API yang to get rid of the hard coded cloud owner in the 
new SO BB. The solution has been there before, it’s just lack of time before 
API freeze, and in this matter, introducing a regression.

Background:
SO and SDNC added respectively new Building Blocks and support for GR-API, in 
order to avoir having to perform the manual preload step. With these new flows, 
at assignment stage, all the required ressources would get resolved by SDNC and 
stored in SDNC GR-API, so at creation stage, all SO has to do is query SDNC to 
gets the resources to use, and proceed with creation.
What was uncover late is SO new BBs are using a hard coded cloud owner. The 
change is simply to allow having that cloud owner configurable. It is a 
small/quick fix in order to provide somewhat of a feature parity between former 
SO flow and new SO flows.

I’m asking the TSC for an API waiver as we're pass API freeze and this is an 
API change, in some ways.  If you want to discuss more in detail that 
functionality, I’ll be happy to explain over a meeting.
My intention is to have a quick turnaround on the API change waiver request. I 
hope TSC will be able to see the urgency in that matter, given RC0, so we don’t 
debate too much on a requirement, as as stated before, we’re not trying to 
fulfil any; simply to fix a regression.

Thanks,
Alexis

> On Oct 11, 2018, at 9:04 PM, Yang Bin  wrote:
> 
> Hi Alexis, Dan,
>
>I am not sure if you are aware the ONAP functional requirement 
> about the “Centralized Representation and Consistent Identification of Cloud 
> Regions In ONAP” 
> https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP
>
>The functional requirement consists of 2 important changes:
> 1, remove any hardcoded/redundant representation of a single cloud region, 
> the hard-coded cloud-sites in SO configuration file is exactly what is  
> targeting to be refactored. Now this part is on track of pairwise testing 
> between SO/MultiCloud .
> 2, apply the usage of ID of a cloud region in a consistent way , the 
> agreement is that the composite keys: {cloud-owner}/{cloud-region-id} will be 
> applied whenever ONAP component wants to refer to a cloud region. This part 
> requires the API changes between VID/SO/SDNC and other related projects. It 
> is  a stretch goal in Casablanca, perhaps we can get it done in Dublin 
> Release.
>
>I do believe both of 2 changes above might be related to your 
> proposal. I would like to discuss a little bit about the issue and your 
> proposal so that maybe we can come up with more comprehensive/consistent 
> solution to get things (API changes) done at one time.
>
>If you don’t mind, we can start with several questions:
>1, why should the Cloud-Owner be provisioned to SDNC with 
> REST-API?
> I guess your proposal is to provision the “Cloud Owner” instead of having it 
> being hard-coded . I agree with you that it should not be hard-coded, but why 
> should the Cloud-Owner be provisioned to SDNC with REST-API?
> IMHO, “Cloud-Owner” (and the cloud-region-id ) should be selected either by 
> user via VID portal or by OOF according to policy. In that case, the ID  of 
> the selected cloud region ({cloud-owner}/{cloud-region-id} ) should be passed 
> to SO/SDNC/etc. through rest API.
>
> 2, Will SDNC use the ID  of the selected cloud region to retrieve information 
> from AAI?
>This question is to help me understand what the interactions 
> are between SDNC and AAI
>
> 3, Will SDNC use the ID  of the selected cloud region to retrieve information 
> from underlying VIM/Cloud instance (e.g. OpenStack instance)?
>This question would help me understand if there is interaction 
> between SDNC and underlying VIM/Cloud instance
>
> Thanks
>
> Best Regards,
> Bin Yang,Solution Engineering Team,Wind River
> ONAP Multi-VIM/Cloud PTL
> Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
> Skype: yangbincs993
>
> From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
> Alexis de Talhouet
> Sent: Friday, October 12, 2018 4:59 AM
> To: onap-tsc; onap-discuss
> Cc: Seshu m; TIMONEY, DAN
> Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC
>
> Hello TSC,
>
> As discussed during today’s meeting, an issue has been identified in the new 
> SO building block, introdu

Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-11 Thread Yang Bin 
Hi Alexis, Dan,

I am trying to understand the changes of the patch:
https://gerrit.onap.org/r/#/c/67413/1/generic-resource-api/model/src/main/yang/GENERIC-RESOURCE-API.yang

If I am not get it wrong, this changes of this patch is only to add 
“cloud-owner” as part of SDNC rest API  with witch SO will have to provide the 
“cloud owner” along with “aic-cloud-region”?In that case I do think this is 
the reasonable change and consistent to the functional requirement of 
“consistent ID of cloud regions”.

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Yang Bin
Sent: Friday, October 12, 2018 9:04 AM
To: onap-tsc@lists.onap.org; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hi Alexis, Dan,

   I am not sure if you are aware the ONAP functional requirement 
about the “Centralized Representation and Consistent Identification of Cloud 
Regions In 
ONAP<https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP>”
 
https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP

   The functional requirement consists of 2 important changes:
1, remove any hardcoded/redundant representation of a single cloud region, the 
hard-coded cloud-sites in SO configuration file is exactly what is  targeting 
to be refactored. Now this part is on track of pairwise testing between 
SO/MultiCloud .
2, apply the usage of ID of a cloud region in a consistent way , the agreement 
is that the composite keys: {cloud-owner}/{cloud-region-id} will be applied 
whenever ONAP component wants to refer to a cloud region. This part requires 
the API changes between VID/SO/SDNC and other related projects. It is  a 
stretch goal in Casablanca, perhaps we can get it done in Dublin Release.

   I do believe both of 2 changes above might be related to your 
proposal. I would like to discuss a little bit about the issue and your 
proposal so that maybe we can come up with more comprehensive/consistent 
solution to get things (API changes) done at one time.

   If you don’t mind, we can start with several questions:
   1, why should the Cloud-Owner be provisioned to SDNC with 
REST-API?
I guess your proposal is to provision the “Cloud Owner” instead of having it 
being hard-coded . I agree with you that it should not be hard-coded, but why 
should the Cloud-Owner be provisioned to SDNC with REST-API?
IMHO, “Cloud-Owner” (and the cloud-region-id ) should be selected either by 
user via VID portal or by OOF according to policy. In that case, the ID  of the 
selected cloud region ({cloud-owner}/{cloud-region-id} ) should be passed to 
SO/SDNC/etc. through rest API.

2, Will SDNC use the ID  of the selected cloud region to retrieve information 
from AAI?
   This question is to help me understand what the interactions are 
between SDNC and AAI

3, Will SDNC use the ID  of the selected cloud region to retrieve information 
from underlying VIM/Cloud instance (e.g. OpenStack instance)?
   This question would help me understand if there is interaction 
between SDNC and underlying VIM/Cloud instance

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: .https://gerrit.onap.org/r/#/c/67413/

Regards,
Alexis


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this

Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-11 Thread Yang Bin 
Hi Alexis, Dan,

   I am not sure if you are aware the ONAP functional requirement 
about the “Centralized Representation and Consistent Identification of Cloud 
Regions In 
ONAP<https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP>”
 
https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP

   The functional requirement consists of 2 important changes:
1, remove any hardcoded/redundant representation of a single cloud region, the 
hard-coded cloud-sites in SO configuration file is exactly what is  targeting 
to be refactored. Now this part is on track of pairwise testing between 
SO/MultiCloud .
2, apply the usage of ID of a cloud region in a consistent way , the agreement 
is that the composite keys: {cloud-owner}/{cloud-region-id} will be applied 
whenever ONAP component wants to refer to a cloud region. This part requires 
the API changes between VID/SO/SDNC and other related projects. It is  a 
stretch goal in Casablanca, perhaps we can get it done in Dublin Release.

   I do believe both of 2 changes above might be related to your 
proposal. I would like to discuss a little bit about the issue and your 
proposal so that maybe we can come up with more comprehensive/consistent 
solution to get things (API changes) done at one time.

   If you don’t mind, we can start with several questions:
   1, why should the Cloud-Owner be provisioned to SDNC with 
REST-API?
I guess your proposal is to provision the “Cloud Owner” instead of having it 
being hard-coded . I agree with you that it should not be hard-coded, but why 
should the Cloud-Owner be provisioned to SDNC with REST-API?
IMHO, “Cloud-Owner” (and the cloud-region-id ) should be selected either by 
user via VID portal or by OOF according to policy. In that case, the ID  of the 
selected cloud region ({cloud-owner}/{cloud-region-id} ) should be passed to 
SO/SDNC/etc. through rest API.

2, Will SDNC use the ID  of the selected cloud region to retrieve information 
from AAI?
   This question is to help me understand what the interactions are 
between SDNC and AAI

3, Will SDNC use the ID  of the selected cloud region to retrieve information 
from underlying VIM/Cloud instance (e.g. OpenStack instance)?
   This question would help me understand if there is interaction 
between SDNC and underlying VIM/Cloud instance

Thanks

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: .https://gerrit.onap.org/r/#/c/67413/

Regards,
Alexis


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3882): https://lists.onap.org/g/onap-tsc/message/3882
Mute This Topic: https://lists.onap.org/mt/27260030/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-11 Thread Alexis de Talhouet 
Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound api.  
(TBD)
SDNC: 
1 Add cloud-owner definition: .https://gerrit.onap.org/r/#/c/67413/ 


Regards,
Alexis
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#3878): https://lists.onap.org/g/onap-tsc/message/3878
Mute This Topic: https://lists.onap.org/mt/27260030/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-