Re: [onap-discuss] Beijing M1: Status of functional requirements

2018-01-21 Thread Alla Goldner 
Hi Mazin,

Sure, we will add this information to the description.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D392EC.566F2CA0]

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Sunday, January 21, 2018 3:15 PM
To: Alla Goldner 
Cc: onap-...@lists.onap.org P ; 
onap-...@lists.onap.org; onap-discuss@lists.onap.org; 
onap-usecase...@lists.onap.org
Subject: Re: [onap-discuss] Beijing M1: Status of functional requirements

Thanks Alla. That is great progress, and appreciate the hard work by everyone.
Have the software architectures worked on the detailed designs of those 
requirements
with the PTLs to ensure nothing is lost in translation?

Can you add to the website the services that will be tested to evaluate 
completions of those requirements.

Mazin




On Jan 18, 2018, at 1:08 PM, Alla Goldner 
mailto:alla.gold...@amdocs.com>> wrote:

Hi all,

As per today’s M1 dedicated TSC meeting and outcomes of the work done by 
Usecase subcommittee along with relevant PTLs,

Here is the most updated status of the functional requirements: 
https://wiki.onap.org/display/DW/Beijing+Functional+Requirements<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Beijing-2BFunctional-2BRequirements&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=7VBK7vn4mMMbbTBo_UbIrby0L3gd_KvI_MskXwqLW-k&s=oTidhLg49Z6O_9zviXx3fusoAmFtnvgaAJ1TYwIbm3I&e=>

1.   Thus, we assume, the following functional requirements are part of 
Beijing Release scope:

a.   HPA
b.  Change Management
c.   Manual scaling
d.  PNF support

All, please indicate if you see any issues with that.

2.   Auto scaling status: APPC, CLAMP and Policy could not commit due to 
lack of resources.

All, please indicate in case some additional resources can be dedicated from 
your side to help the above mentioned projects with Auto scaling requirement 
support.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=7VBK7vn4mMMbbTBo_UbIrby0L3gd_KvI_MskXwqLW-k&s=IayIFfpFwRaM2wxAHs8JbwKxe9_7ufbotiJ9jkkxtrE&e=>
___
onap-discuss mailing list
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=7VBK7vn4mMMbbTBo_UbIrby0L3gd_KvI_MskXwqLW-k&s=Y63nXwhDh5uYEaYn9pj-mMgdhOa5KZzTbaZj3NWvzgg&e=

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Beijing M1: Status of functional requirements

2018-01-21 Thread GILBERT, MAZIN E (MAZIN E) 
Thanks Alla. That is great progress, and appreciate the hard work by everyone.
Have the software architectures worked on the detailed designs of those 
requirements
with the PTLs to ensure nothing is lost in translation?

Can you add to the website the services that will be tested to evaluate 
completions of those requirements.

Mazin




On Jan 18, 2018, at 1:08 PM, Alla Goldner 
mailto:alla.gold...@amdocs.com>> wrote:

Hi all,

As per today’s M1 dedicated TSC meeting and outcomes of the work done by 
Usecase subcommittee along with relevant PTLs,

Here is the most updated status of the functional requirements: 
https://wiki.onap.org/display/DW/Beijing+Functional+Requirements

1.   Thus, we assume, the following functional requirements are part of 
Beijing Release scope:

a.   HPA
b.  Change Management
c.   Manual scaling
d.  PNF support

All, please indicate if you see any issues with that.

2.   Auto scaling status: APPC, CLAMP and Policy could not commit due to 
lack of resources.

All, please indicate in case some additional resources can be dedicated from 
your side to help the above mentioned projects with Auto scaling requirement 
support.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=7VBK7vn4mMMbbTBo_UbIrby0L3gd_KvI_MskXwqLW-k&s=Y63nXwhDh5uYEaYn9pj-mMgdhOa5KZzTbaZj3NWvzgg&e=

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

[onap-discuss] Beijing M1: Status of functional requirements

2018-01-18 Thread Alla Goldner 
Hi all,

As per today's M1 dedicated TSC meeting and outcomes of the work done by 
Usecase subcommittee along with relevant PTLs,

Here is the most updated status of the functional requirements: 
https://wiki.onap.org/display/DW/Beijing+Functional+Requirements


1.   Thus, we assume, the following functional requirements are part of 
Beijing Release scope:


a.   HPA

b.  Change Management

c.   Manual scaling

d.  PNF support

All, please indicate if you see any issues with that.


2.   Auto scaling status: APPC, CLAMP and Policy could not commit due to 
lack of resources.

All, please indicate in case some additional resources can be dedicated from 
your side to help the above mentioned projects with Auto scaling requirement 
support.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D39097.AC5F6230]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

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