[onap-tsc] Casablanca release participation - Policy Framework

2018-06-06 Thread DRAGOSH, PAMELA L (PAM) 
Dear TSC,

This is to inform you that the Policy Framework project intends to participate 
on the Casablanca release.

Thanks,

Pamela Dragosh
Policy Framework PTL

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Review of Policy known vulnerability Analysis

2018-05-03 Thread DRAGOSH, PAMELA L (PAM) 
Yes Steve they are both removed.

I updated the Policy Vulnerability page.

https://wiki.onap.org/pages/viewpage.action?pageId=25437092

Thanks,

Pam

From: Stephen Terrill <stephen.terr...@ericsson.com>
Date: Wednesday, May 2, 2018 at 5:24 PM
To: "DRAGOSH, PAMELA L (PAM)" <pdrag...@research.att.com>
Cc: "onap-sec...@lists.onap.org" <onap-sec...@lists.onap.org>, onap-tsc 
<onap-tsc@lists.onap.org>
Subject: RE: Review of Policy known vulnerability Analysis

Hi Pam,

Thanks, good progress.   I see two issues that are “removing this dependency” 
“grizzly-http and commons-client – have these been removed?

BR,

Steve

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Thursday, April 26, 2018 5:23 PM
To: Stephen Terrill <stephen.terr...@ericsson.com>
Cc: onap-sec...@lists.onap.org; onap-tsc <onap-tsc@lists.onap.org>
Subject: Re: Review of Policy known vulnerability Analysis

Stephen,

Per your presentation today at the TSC, for Policy we have removed the last 2 
security issues from the codebase.

The code is delivered and I verified that nexus-iq has removed the 
identification of the vulnerability. We are going to do a round of testing 
today to verify functionality is still remaining and then close the JIRA’s. I 
will update the wiki when finished.

Thanks,

Pam

From: Stephen Terrill 
<stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>>
Date: Monday, April 2, 2018 at 3:22 PM
To: "DRAGOSH, PAMELA L (PAM)" 
<pdrag...@research.att.com<mailto:pdrag...@research.att.com>>
Cc: "onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>" 
<onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>>, onap-tsc 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
Subject: RE: Review of Policy known vulnerability Analysis

Hi Pam,

Thanks for the reply.  For the vulnerabilities that remain due to e.g. 
backwards compatibility, can we be clear about the exposure of the risk to ONAP 
in the impact analysis.

BR,

Steve

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Monday, April 02, 2018 1:31 PM
To: Stephen Terrill 
<stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>>
Cc: onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>; onap-tsc 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
Subject: Re: Review of Policy known vulnerability Analysis

Stephen,

We are introducing a change in functionality that bypasses this code in 
Beijing, but it is a late addition. We will need to support the use of this 
code for backwards compatibility until we can fully vet the new functionality 
works and we can switch to it completely to deprecate the other code. We hope 
that we can test and fix the new functionality over the next few weeks.

Pam


From: Stephen Terrill 
<stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>>
Date: Friday, March 30, 2018 at 3:39 PM
To: "DRAGOSH, PAMELA L (PAM)" 
<pdrag...@research.att.com<mailto:pdrag...@research.att.com>>
Cc: "onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>" 
<onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>>, onap-tsc 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
Subject: Review of Policy known vulnerability Analysis

Hi Pam,

I am reviewing the known vulnerability analysis for Policy 
(https://wiki.onap.org/pages/viewpage.action?pageId=25437092<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D25437092=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=WpF6UwvR-KYtHRoZjoCSMv1ydKuVWjHviBKuTK6xWE4=>
 ), thankyou for the analysis.


I had a question on “commons-client”, where the text indicates “We are building 
functionality that by-passes the code that uses this dependency into a new 
beijing template for control loops. We are targeting deprecation of the BRMS 
Gateway code in policy/engine over the next release or two”.  Is this something 
that is to be fixed in Beijing?

For Jacksonbind, please look at the example from MSB to assist you in your 
analysis.

BR,

Steve.


[csson]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=-6uwrGj9mHXm0kdNlB_a5x_YMWfVGMilUPjhhpwNuCI=>


STEPHEN TERRILL
Technology Specialist
POA Architecture and Solutions
Business Unit Digital Services

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>
www.ericsson.com<https://urldefense.proofpoint.com/v2/url?u=

Re: [onap-tsc] [Onap-arc] Casablanca use cases: Feedback received from EUAG (Service Providers) so far

2018-04-30 Thread DRAGOSH, PAMELA L (PAM) 
Alla,

For the Verizon request “Fine grained RBAC for deployment dashboardz’. The 
Policy Framework project can support this request via the use of the XACML PDP 
engine. What I request is that Verizon provide resources to the project to help 
facilitate this work for Casablanca.

In response to the hard coding of control loops, all these gaps and hardcoding 
was pointed out in Paris last year and a call for help was given. No one 
responded. If folks could contribute resources to Control Loop Sub Committee to 
help define and scope how to fix the gaps in control loops, then the community 
can help work towards getting this resolved.

Thanks,

Pam Dragosh
ONAP Policy PTL
Control Loop Sub Committee Chair


From:  on behalf of Alla Goldner 

Date: Monday, April 30, 2018 at 3:29 AM
To: "onap-usecase...@lists.onap.org" 
Cc: "onap-...@lists.onap.org" , 
"onap-disc...@lists.onap.org" , 
"onap-tsc@lists.onap.org" 
Subject: [Onap-arc] Casablanca use cases: Feedback received from EUAG (Service 
Providers) so far

Hi all,

For your information, please see below feedback on priorities of use 
cases/requirements received from Service Providers so far.
We will discuss these and additional requirements from Service Providers, 
attending the call.

Requirements from Verizon, in the order of priority: (architecture/modelling 
subcommittees and affected projects – please pay attention to relevant 
requirements in the list)


  *   Standards compliant on-boarding / orchestration interfaces

 *   SOL001 for Onboarding ( preferred )
 *   SOL003 for Or-Vnfm ( preferred )
 *   VNF Package certification & labelling
  *   Declarative model based orchestration
 *   TOSCA based orchestration of network services, along with 
Yang/Netconf/VES for automated configuration ( preferred )
 *   Model driven workflow orchestration for LCM
 *   Custom workflows via Apache Aria plugins ( preferred ) for Closed Loop 
& SA.
  *   Fine grained RBAC for deployment dashboard
 *   Ability to derive custom SDC & VID roles with fine grained attributes

*   Eg : Designer A cannot design services tagged to Designer B etc.
  *   Ability to deploy Geo-Redundant Highly available Network services
 *   GR part of network design requirement in SDC.
 *   Ability to orchestrate network services between multi-site / 
multi-region VIMs
  *   Geo-Redundant Highly available ONAP deployment
 *   Shared runtime catalogues across multi ONAP instances
*   Eg : ONAP B should be able to deploy NS designed by ONAP A etc.

And the corresponding questions:

  *   How many of the above requirements can be made available by readily 
tweaking existing code, with minimum efforts?
  *   How many would / can be scoped for future releases? if so, tentative 
timeline if any?
  *   Where & how can we help contributing to ONAP w.r.t above requirements?
Requirements and input on proposed use cases from Bell: (architecture/modelling 
subcommittees and affected projects – please pay attention to relevant 
requirements in the list)


  *   ONAP needs a more robust/generic implementation of functionality 
leveraged by existing use cases:
For example, there is still hard-coded logic just to make simple use cases work 
(such as Firewall closed loop)
-  A provider-specific closed-loop implementation is not possible at 
this time, as the hard-coded use case logic should be implemented generically.
-  We are going through that with a real use case - it can't be 
leveraged right now without significant code changes to APPC, SDNC, Policy and 
DCAE.

  *   Basic ONAP features which should be working reliably can be either 
incomplete, have been hardcoded or are still broken
Examples of such features:
-  SDC support for distribution of models/artifacts to multiple ONAP 
environments (development, testing, QA, production, etc.)
-  MultiVIM/Cloud's role is to abstract the VIM, currently SO does not 
leverage it, and no abstraction is built into it (it exposes directly the 
OpenStack model).
-  APPC's handling of events / actions from Policy is pretty much 
hardcoded for the use cases.
-  AAF is not or very lightly leveraged within the platform
There are much more – but in overall ONAP would benefit from improving existing 
features before building new, but partially working features.

  *   VNF Configuration support is quite important for pretty much every use 
cases – and isn’t well supported right now (aside initial/boot up 
configuration).
-  It is often the next operational need, right after any lifecycle 
management implementation
-  A model-driven approach to this leveraging standards-based / 
abstract configuration models, and the framework to derive device-specific 
configuration, as well as interpret

Re: [onap-tsc] Review of Policy known vulnerability Analysis

2018-04-26 Thread DRAGOSH, PAMELA L (PAM) 
Stephen,

Per your presentation today at the TSC, for Policy we have removed the last 2 
security issues from the codebase.

The code is delivered and I verified that nexus-iq has removed the 
identification of the vulnerability. We are going to do a round of testing 
today to verify functionality is still remaining and then close the JIRA’s. I 
will update the wiki when finished.

Thanks,

Pam

From: Stephen Terrill <stephen.terr...@ericsson.com>
Date: Monday, April 2, 2018 at 3:22 PM
To: "DRAGOSH, PAMELA L (PAM)" <pdrag...@research.att.com>
Cc: "onap-sec...@lists.onap.org" <onap-sec...@lists.onap.org>, onap-tsc 
<onap-tsc@lists.onap.org>
Subject: RE: Review of Policy known vulnerability Analysis

Hi Pam,

Thanks for the reply.  For the vulnerabilities that remain due to e.g. 
backwards compatibility, can we be clear about the exposure of the risk to ONAP 
in the impact analysis.

BR,

Steve

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Monday, April 02, 2018 1:31 PM
To: Stephen Terrill <stephen.terr...@ericsson.com>
Cc: onap-sec...@lists.onap.org; onap-tsc <onap-tsc@lists.onap.org>
Subject: Re: Review of Policy known vulnerability Analysis

Stephen,

We are introducing a change in functionality that bypasses this code in 
Beijing, but it is a late addition. We will need to support the use of this 
code for backwards compatibility until we can fully vet the new functionality 
works and we can switch to it completely to deprecate the other code. We hope 
that we can test and fix the new functionality over the next few weeks.

Pam


From: Stephen Terrill 
<stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>>
Date: Friday, March 30, 2018 at 3:39 PM
To: "DRAGOSH, PAMELA L (PAM)" 
<pdrag...@research.att.com<mailto:pdrag...@research.att.com>>
Cc: "onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>" 
<onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>>, onap-tsc 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
Subject: Review of Policy known vulnerability Analysis

Hi Pam,

I am reviewing the known vulnerability analysis for Policy 
(https://wiki.onap.org/pages/viewpage.action?pageId=25437092<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D25437092=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=WpF6UwvR-KYtHRoZjoCSMv1ydKuVWjHviBKuTK6xWE4=>
 ), thankyou for the analysis.


I had a question on “commons-client”, where the text indicates “We are building 
functionality that by-passes the code that uses this dependency into a new 
beijing template for control loops. We are targeting deprecation of the BRMS 
Gateway code in policy/engine over the next release or two”.  Is this something 
that is to be fixed in Beijing?

For Jacksonbind, please look at the example from MSB to assist you in your 
analysis.

BR,

Steve.


[icsson]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=-6uwrGj9mHXm0kdNlB_a5x_YMWfVGMilUPjhhpwNuCI=>


STEPHEN TERRILL
Technology Specialist
POA Architecture and Solutions
Business Unit Digital Services

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>
www.ericsson.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com=DwQFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=E7aTSWbIw4jahsq7Td3GzRWuDLyQHPjTSedCVdI9S6M=>


[tp://www.ericsson.com/current_campaign]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_current-5Fcampaign=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=Li1HoXDppF_VyTDGmtsCYwCqQ2asI7s5LHmG9USB4bk=>

Legal entity: Ericsson España S.A, compay registration number ESA288568603. 
This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at 
www.ericsson.com/email_disclaimer<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_email-5Fdisclaimer=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=_9d1iQKBv7C70qCQckdHYFbCetguWZBkScYxIaXhOQE=>

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Control Loop Sub Committee Minutes from 4/24/2018

2018-04-25 Thread DRAGOSH, PAMELA L (PAM) 
ONAP,

The recording and minutes for the 4/25/2018 Control Loop Sub Committee meeting 
are here:

https://wiki.onap.org/display/DW/04-25-2018+Control+Loop+Sub+Committee+Weekly+Meeting

Briefly:

· Discussion on Beijing Testing Status

· Discussion on Policy Models – DCAE needs ability to query for models. 
CLAMP would like that stored in blueprint.

· Team discussed need for JIRA board to track action items and 
discussions needed for Casablanca functional requirements.

Thanks,

Pam Dragosh
ONAP Control Loop Sub Committee Chair

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Control Loop Sub Committee Minutes from 4/18/2018

2018-04-24 Thread DRAGOSH, PAMELA L (PAM) 
ONAP,

The recording and minutes for the 4/18/2018 Control Loop Sub Committee are 
located here:

https://wiki.onap.org/display/DW/04-18-2018+Control+Loop+Sub+Committee+Weekly+Meeting

Briefly:


· Discussion around the current status of Beijing Pairwise Testing. 
Thank you Ron Shachman and Alex Shatov for driving this work.

· Discussion around the Casablanca Auto Scale Out Use Case. Thank you 
to Scott Blandford for running this.

I would like to ask the TSC to encourage their team members to help start 
contributing to the committee. It seems the bulk of the work is being done by a 
small core group of folks within AT and our calls for help are not being 
answered by the other folks who are simply listening in on the meeting. There 
are opportunities to help with:


· Help defining functional requirements for Casablanca Control Loops

· Help with flow diagrams for all the scale out scenarios

· Help with defining a Common Actor API to simplify interaction between 
Policy/VID and the controllers.

· Help with taking notes/minutes for the meeting calls

Thanks,

Pam Dragosh
ONAP Control Loop Sub Committee Chair

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Review of Policy known vulnerability Analysis

2018-04-02 Thread DRAGOSH, PAMELA L (PAM) 
Stephen,

We are introducing a change in functionality that bypasses this code in 
Beijing, but it is a late addition. We will need to support the use of this 
code for backwards compatibility until we can fully vet the new functionality 
works and we can switch to it completely to deprecate the other code. We hope 
that we can test and fix the new functionality over the next few weeks.

Pam


From: Stephen Terrill <stephen.terr...@ericsson.com>
Date: Friday, March 30, 2018 at 3:39 PM
To: "DRAGOSH, PAMELA L (PAM)" <pdrag...@research.att.com>
Cc: "onap-sec...@lists.onap.org" <onap-sec...@lists.onap.org>, onap-tsc 
<onap-tsc@lists.onap.org>
Subject: Review of Policy known vulnerability Analysis

Hi Pam,

I am reviewing the known vulnerability analysis for Policy 
(https://wiki.onap.org/pages/viewpage.action?pageId=25437092<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D25437092=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=WpF6UwvR-KYtHRoZjoCSMv1ydKuVWjHviBKuTK6xWE4=>
 ), thankyou for the analysis.


I had a question on “commons-client”, where the text indicates “We are building 
functionality that by-passes the code that uses this dependency into a new 
beijing template for control loops. We are targeting deprecation of the BRMS 
Gateway code in policy/engine over the next release or two”.  Is this something 
that is to be fixed in Beijing?

For Jacksonbind, please look at the example from MSB to assist you in your 
analysis.

BR,

Steve.


[ricsson]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=-6uwrGj9mHXm0kdNlB_a5x_YMWfVGMilUPjhhpwNuCI=>


STEPHEN TERRILL
Technology Specialist
POA Architecture and Solutions
Business Unit Digital Services

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com
www.ericsson.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com=DwQFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=E7aTSWbIw4jahsq7Td3GzRWuDLyQHPjTSedCVdI9S6M=>


[ttp://www.ericsson.com/current_campaign]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_current-5Fcampaign=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=Li1HoXDppF_VyTDGmtsCYwCqQ2asI7s5LHmG9USB4bk=>

Legal entity: Ericsson España S.A, compay registration number ESA288568603. 
This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at 
www.ericsson.com/email_disclaimer<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_email-5Fdisclaimer=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=j8Gv-qzcAmG1BG1BuclfHzh7GfCbxaY5R60DavMb2rI=_9d1iQKBv7C70qCQckdHYFbCetguWZBkScYxIaXhOQE=>

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [Onap-usecasesub] Usecase subcommittee meeting 0f 19/03/2018 - the summary

2018-03-20 Thread DRAGOSH, PAMELA L (PAM) 
Ramki,

What exactly do you need to discuss with regards to the Policy Framework? Is 
this something that the Policy Framework team could discuss at our internal 
meeting?

Pam Dragosh
ONAP Policy PTL


From:  on behalf of Ramki Krishnan 

Date: Monday, March 19, 2018 at 8:23 PM
To: Alla Goldner , "onap-usecase...@lists.onap.org" 

Cc: "onap-tsc@lists.onap.org" 
Subject: Re: [onap-tsc] [Onap-usecasesub] Usecase subcommittee meeting 0f 
19/03/2018 - the summary

Hi Alla,

Can you please add “Distributed Policy Framework” as another topic?

--
Thanks,
Ramki

From: onap-usecasesub-boun...@lists.onap.org 
[mailto:onap-usecasesub-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Monday, March 19, 2018 11:56 AM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: [Onap-usecasesub] Usecase subcommittee meeting 0f 19/03/2018 - the 
summary

Hi all,

Thanks a lot to all meeting’s participants!

The following requirements were presented and will also be presented next week 
during our session at ONS (our session is on Monday, 1 pm – 2:30 pm)
1.Manual Scaling in, Auto scaling in/out
2.OSAM
3.Change Management

Additionally,


  1.  5G task force (Network Slicing, Optimization/OOF, PNF support leftovers)
  2.  Parviz Yegani ((Real Time Data Event Streaming & Processing ( RESP))
  3.  Any more?

Please send your presentations till this Thursday, the latest.

We also discussed the need to have f2f discussions for all related task forces 
during ONS, as there are many technical questions for the proposals, task force 
leads will send out emails inviting for such a discussions.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3C035.09C37340]

From: Alla Goldner
Sent: Sunday, March 18, 2018 4:54 PM
To: 'Vladimir Yanover (vyanover)' 
>; 
onap-usecase...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: RE: [onap-tsc] Agenda for the next Usecase subcommittee meeting 
(19/3/2018)

Hi Vladimir,

Fully agree,
I only received materials from Scott. Attached.

Others – please also try to distribute your materials in advance 9and upload to 
wiki).

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3C035.09C37340]

From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Sunday, March 18, 2018 4:52 PM
To: Alla Goldner >; 
onap-usecase...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: RE: [onap-tsc] Agenda for the next Usecase subcommittee meeting 
(19/3/2018)

Hello, Alla
Are there any materials? We will use the meetings time more efficiently if the 
presentations are available in advance.
Thanks
Vladimir

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, March 16, 2018 8:14 PM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc@lists.onap.org
Subject: [onap-tsc] Agenda for the next Usecase subcommittee meeting (19/3/2018)

Hi all,

The next meeting will be dedicated to review of your proposals for Casablanca, 
as a candidates to be presented during ONS/ONAP meeting.
The proposals will include leftovers from Beijing (those sub-features of 
scaling, Change management, HPA, PNF support which eventually will not be 
supported in Beijing) plus same requirements extensions for Casablanca plus new 
Casablanca proposals.

Those planning to bring proposals – please let me know so I can plan the time 
accordingly.

So far, I’ve received the following:


  1.  Scott Blandford (Manual Scaling in, Auto scaling in/out)
  2.  Sumithra Bhojan (OSAM)
  3.  Parviz Yegani (Real Time Data Event Streaming & Processing ( RESP)
  4.  Ajay Mahimkar (Change Management)

Additionally, 5G task force have expressed their intention to present on 
Network Slicing and on Optimization/OOF, as well as on PNF support leftovers.

Please correct me if I forgot to include some and if there will be additional 
proposals.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3C035.09C37340]

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

Re: [onap-tsc] [Onap-lf-announce] [it-infrastructure-alerts] ONAP environment maintenance 2018-02-08 @ 15:30 PDT (23:30 UTC)

2018-02-10 Thread DRAGOSH, PAMELA L (PAM) 
Yes – that works, thanks!!

Pam

From: Jessica Wagantall <jwagant...@linuxfoundation.org>
Date: Friday, February 9, 2018 at 2:39 PM
To: "DRAGOSH, PAMELA L (PAM)" <pdrag...@research.att.com>
Cc: "it-infrastructure-ale...@linuxfoundation.org" 
<it-infrastructure-ale...@linuxfoundation.org>, "onap-disc...@lists.onap.org" 
<onap-disc...@lists.onap.org>, "onap-lf-annou...@lists.onap.org" 
<onap-lf-annou...@lists.onap.org>, onap-tsc <onap-tsc@lists.onap.org>
Subject: Re: [Onap-lf-announce] [it-infrastructure-alerts] ONAP environment 
maintenance 2018-02-08 @ 15:30 PDT (23:30 UTC)

I have now upgraded both plugins now.

Can you please try again?

thanks a ton!
Jess

On Fri, Feb 9, 2018 at 11:38 AM, Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>> wrote:
Dear Pam,

The plugins are separate. I am working on upgrading them now, I think i can do 
it from the interface itself.

Just FYI, we are going to perform the 6.7.1 upgrade later today

Thanks a ton for your patience on this
Jess

On Fri, Feb 9, 2018 at 6:20 AM, DRAGOSH, PAMELA L (PAM) 
<pdrag...@research.att.com<mailto:pdrag...@research.att.com>> wrote:
Jessica,

Thanks, it is now possible to connect our local Eclipse environment to the 
sonar server which will help speed up clearing of issues. However, I did get 
this error with Eclipse Neon.3 Java version:

The following plugins do not meet the required minimum versions, please upgrade 
them on your SonarQube server:
  java (installed: 3.10, minimum: 4.0)
  javascript (installed: 2.10, minimum: 2.14)

I’m just wondering if 6.7.1 will be able to address that?

Thanks,

Pam

From: 
<onap-lf-announce-boun...@lists.onap.org<mailto:onap-lf-announce-boun...@lists.onap.org>>
 on behalf of Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Date: Thursday, February 8, 2018 at 8:42 PM
To: 
"it-infrastructure-ale...@linuxfoundation.org<mailto:it-infrastructure-ale...@linuxfoundation.org>"
 
<it-infrastructure-ale...@linuxfoundation.org<mailto:it-infrastructure-ale...@linuxfoundation.org>>,
 "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>, 
"onap-lf-annou...@lists.onap.org<mailto:onap-lf-annou...@lists.onap.org>" 
<onap-lf-annou...@lists.onap.org<mailto:onap-lf-annou...@lists.onap.org>>, 
onap-tsc <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
Subject: Re: [Onap-lf-announce] [it-infrastructure-alerts] ONAP environment 
maintenance 2018-02-08 @ 15:30 PDT (23:30 UTC)

Dear team, we have upgraded sonar from 5.4 -> 5.6.7 -> 6.0

We will be performing a following update to 6.7.1 soon.

Thanks!
Jess

On Thu, Feb 8, 2018 at 4:03 PM, Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>> wrote:
Dear team,

This upgrade is still going on.
Our team is working on the upgrade from 5.6.7 to 6.7 and then from 6.7 to 6.7.1

Thanks a lot for your patience.

Thanks!
Jess

On Thu, Feb 8, 2018 at 9:29 AM, Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>> wrote:
What: The Linux Foundation will be performing Sonar's upgrade once more (v6.7.1)

When: Thursday, Feb 8th @ 15:30 PDT

Why: Sonar needs to be upgraded to be able to get more functionality in place

Impact: Sonar will be unavailable for 1 hour during this maintenance

Notices will be posted to the mailing lists at the start and end of the 
maintenance.




___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [Onap-lf-announce] [it-infrastructure-alerts] ONAP environment maintenance 2018-02-08 @ 15:30 PDT (23:30 UTC)

2018-02-09 Thread DRAGOSH, PAMELA L (PAM) 
Jessica,

Thanks, it is now possible to connect our local Eclipse environment to the 
sonar server which will help speed up clearing of issues. However, I did get 
this error with Eclipse Neon.3 Java version:

The following plugins do not meet the required minimum versions, please upgrade 
them on your SonarQube server:
  java (installed: 3.10, minimum: 4.0)
  javascript (installed: 2.10, minimum: 2.14)

I’m just wondering if 6.7.1 will be able to address that?

Thanks,

Pam

From:  on behalf of Jessica Wagantall 

Date: Thursday, February 8, 2018 at 8:42 PM
To: "it-infrastructure-ale...@linuxfoundation.org" 
, "onap-disc...@lists.onap.org" 
, "onap-lf-annou...@lists.onap.org" 
, onap-tsc 
Subject: Re: [Onap-lf-announce] [it-infrastructure-alerts] ONAP environment 
maintenance 2018-02-08 @ 15:30 PDT (23:30 UTC)

Dear team, we have upgraded sonar from 5.4 -> 5.6.7 -> 6.0

We will be performing a following update to 6.7.1 soon.

Thanks!
Jess

On Thu, Feb 8, 2018 at 4:03 PM, Jessica Wagantall 
> wrote:
Dear team,

This upgrade is still going on.
Our team is working on the upgrade from 5.6.7 to 6.7 and then from 6.7 to 6.7.1

Thanks a lot for your patience.

Thanks!
Jess

On Thu, Feb 8, 2018 at 9:29 AM, Jessica Wagantall 
> wrote:
What: The Linux Foundation will be performing Sonar's upgrade once more (v6.7.1)

When: Thursday, Feb 8th @ 15:30 PDT

Why: Sonar needs to be upgraded to be able to get more functionality in place

Impact: Sonar will be unavailable for 1 hour during this maintenance

Notices will be posted to the mailing lists at the start and end of the 
maintenance.


___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] F2F Dec option "hands-on" missing

2017-10-30 Thread DRAGOSH, PAMELA L (PAM) 
Kenny,

Myself and a few other folks are going to submit a combination presentation and 
panel discussion. We’d like 2 hours in order for a few presentations to begin 
with and then have hour for panel discussion. Is it possible to change or can 
we just wing it with the current version?

Sorry to be a pain.

Pam


From:  on behalf of Michael O'Brien 

Date: Monday, October 30, 2017 at 3:10 PM
To: Kenny Paul 
Cc: onap-discuss , onap-tsc 

Subject: [onap-tsc] F2F Dec option "hands-on" missing

Kenny,
   Hi, can we get the 3rd “hands-on” option returned to the f2f 
form – for today
 Thank you
  
https://www.surveymonkey.com/r/ZNDY6MV


Michael O’Brien
Amdocs Technology
16135955268
55268
[mdocs-a]

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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Amsterdam PTL Confidance Vote

2017-10-26 Thread DRAGOSH, PAMELA L (PAM) 
Kenny et all,

Question – is this confidence vote coming from my point of view of my project? 
Or from my point of view of Amsterdam overall??

Thanks,

Pam

From: linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com
When: 9:00 AM - 11:00 AM November 13, 2017
Subject: Amsterdam PTL Confidance Vote
Location: https://zoom.us/j/227871708


This event has been changed.
more details 
»
Changed: Amsterdam PTL Confidance Vote
When

Changed: Mon Nov 13, 2017 6am – 8am Pacific Time

Where

https://zoom.us/j/227871708
 
(map)

Calendar

pdrag...@research.att.com

Who

•

kp...@linuxfoundation.org - creator

•

sw3...@att.com

•

denghu...@hotmail.com

•

kanagaraj.manic...@huawei.com

•

ml6...@intl.att.com

•

dtimo...@att.com

•

am8...@att.com

•

gg2...@att.com

•

l...@research.att.com

•

wangchen...@chinamobile.com

•

jf2...@att.com

•

stephen.terr...@ericsson.com

•

onap-tsc@lists.onap.org

•

Eman Gil

•

gn4...@intl.att.com

•

mp...@amdocs.com

•

david.sauvag...@bell.ca

•

zhao.huab...@zte.com.cn

•

ah0...@intl.att.com

•

pdrag...@research.att.com

•

denghu...@huawei.com

•

fu.guangr...@zte.com.cn

•

rx1...@att.com

•

es4...@att.com

•

gildas.lani...@huawei.com

•

helen.c...@huawei.com

•

sa...@research.att.com

•

Casey Cain

•

talas...@research.att.com

•

Philip Robb

•

rk5...@att.com

•

seshu.kuma...@huawei.com

•

lxin...@vmware.com

•

shen...@chinamobile.com

•

denglin...@chinamobile.com

•

Kristi Tan

•

lcayw...@linuxfoundation.org

•

Jill Lovato

•

Sarah Conway



Hi there,
ONAP Meeting 3 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/227871708
Or iPhone one-tap (US Toll): +14086380968,,227871708# or 
+16465588656,,227871708#
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: 227 871 708
International numbers available: 
https://zoom.us/zoomconference?m=KVVYvoPsmVc1-iR5MAAzXkGM_QvcVUy3





Going?   
Yes
 -

[onap-tsc] [onap-release] Problem with people creating JIRA's for unnecessary fixes

2017-10-12 Thread DRAGOSH, PAMELA L (PAM) 
Gildas and TSC,

Please help me. I have people that are going outside my scrum and creating 
“BUGS” for sonar major/minor fixes. None of these are critical or identified 
during integration testing. It is past code freeze and RC0 and these are 
disruptive to the process for releasing code.

I have asked them to stop over the past 2 weeks but today I have 3 new JIRA’s 
to deal with. We are trying to get our artifacts released to meet RC0 
guidelines. At this point I don’t know what to do except to bring in the 
involvement of the TSC to get this behavior stopped.

While I appreciate the help, it would have been better for this work to be done 
months ago and not post code freeze. I’m also not sure what brought on this 
sudden interest in fixing sonar major/minor issues throughout policy project. 
None of these people have spoken to myself about working on policy, much less 
added themselves as contributors to the project.

What guidance is there for this?

Thanks,

Pam Dragosh
ONAP Policy PTL
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Control Loop Subcommittee Proposal

2017-10-11 Thread DRAGOSH, PAMELA L (PAM) 
Dear TSC,

I would like some guidance on the proposal for a Control Loop SubCommittee. 
This was discussed in Paris F2F at the Control Loop E2E Meeting. We identified 
a need for a subcommittee to help coordinate the efforts of supporting Control 
Loops across all the multitude of projects that are involved. Coordination 
between the project teams proved difficult to manage amongst themselves. Each 
Use Case for Amsterdam also had slightly different requirements for their 
respective Control Loops. There needs to be an overarching subcommittee that 
can manage this effort.

This is what I am proposing:

Name: Control Loop Subcommittee
Purpose: Coordinate the projects involved in implementation of Control Loop for 
the use cases in each release.
Expected Deliverables:

· Wiki – One-stop wiki page that can organize all the architectural and 
flow diagrams expected for the Use Cases targeted for a Release.

· Architectural Diagram – Work with Architecture Sub Committee to 
provide architecture diagrams for Control Loop Design, Instantiation and 
Runtime Execution.

· Flow Diagrams – Work with the relevant project teams to provide Flow 
Diagrams for creating Control Loops during Design Time Service Design and Flow 
Diagrams for Control Loop Runtime Instantiation and Execution.

· Model definition (In coordination with Modeling, VNFSDK, VNF 
Requirements Sub Committees) – Coordinate the models for VNF Vendor 
Recommendations for Control Loops, Models for DCAE Microservices, Models for 
Policy Configuration/Operational Control Loop Policies, etc.

· Project Requirements – Work with required Project teams to ensure 
commitments and deliverables for Control Loop Use Cases for a release. The Core 
teams are DCAE/CLAMP/Policy, but ultimately most projects are involved 
(APPC/VFC/SO/Dmaap/SDC/AAI to name a few).

· Integration Testing Requirements – Work with the integration test 
team to build E2E Testing Scripts for Control Loop Design, Instantiation and 
Runtime Execution

· Documentation Requirements – Work with the documentation team to 
build documentation on how the community can build, design and test Control 
Loops.
Starting Participants:
Pamela Dragosh – AT
Liam Fallon – Ericsson
Gervais-Martial Ngueko – AT
Guangrong Fu – ZTE
Grzegorz Tysczka – Orange
Patrick Liu - Huawei

Regards,

Pamela Dragosh
ONAP Policy PTL
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] More Help For Adding Committers

2017-08-18 Thread DRAGOSH, PAMELA L (PAM) 
Hey Kenny,

This is great thanks.

As a PTL, I personally feel it is important that committers aren’t just doing 
gerrit commits. But also show meritocracy in the following activities:

· actively participate in Weekly meetings

· respond to onap-discuss questions for that project

· actively help develop wiki information and respond to comments on 
wiki’s

· participate in gerrit reviews not just a submitter, but also review 
other submissions

· actively work with the PTL and other committers with planning for 
sprints, milestones, JIRA

All these items are just as important as someone who simply submits code, they 
ensure a healthy working team.

Thanks,

Pam Dragosh


From:  on behalf of Kenny Paul 

Date: Friday, August 18, 2017 at 2:11 AM
To: Ed Warnicke 
Cc: onap-tsc 
Subject: Re: [onap-tsc] More Help For Adding Committers

Hi Ed,
From the template:

Link(s) demonstrating the Contributor's established history of meritocratic 
contributions to the project:
(Typically this would be in the form of a gerrit query)


So assuming that the template is followed then, yes, that information should be 
provided :-)


Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

On Aug 17, 2017, at 6:48 PM, Ed Warnicke 
> wrote:

Could we add the history of meritocratic contribution via a link to a gerrit 
query for the proposed committers contributions to the repos of the project?

Ed

On Thu, Aug 17, 2017 at 6:40 PM, Kenny Paul 
> wrote:
In a further effort to both ease frustration of the PTLs and address general 
scalability concerns, I have created a template for adding new Committers to an 
ONAP project.
This template can be found by going to the Adding/Removing Committers to a 
Project
 page found under the Developer Best 
Practices
 section of the wiki.

The members of the TSC are closely scrutinizing these types of requests. If you 
have a Contributor that has earned the right to be a Committer, and you have 
not already received a direct email from me indicating that your request has 
been submitted to the TSC for approval, I strongly recommend that you make use 
of the template and follow the process it outlines.

Hopefully this should make things run a bit smoother for all.

Please let me know if you have any questions.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945


___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc


___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Policy Framework Project Proposal

2017-05-16 Thread DRAGOSH, PAMELA L (PAM) 
Sven,

We have submitted the proposal already to the tsc as of 5/11 – Phil Robb marked 
it with that date. We hope to hear from the TSC within the next week or so to 
determine if it is accepted.

Since we are not officially accepted yet, let’s keep our comments on the wiki 
page itself right now. At issue is the organization of the code/projects.

Thanks,

Pam

From: <onap-tsc-boun...@lists.onap.org> on behalf of Sven van der Meer 
<sven.van.der.m...@ericsson.com>
Date: Tuesday, May 16, 2017 at 8:13 AM
To: "onap-tsc@lists.onap.org" <onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Policy Framework Project Proposal

Thanks a lot Pam!

I have added Ericsson contributors. We are currently discussion committers as 
well (hopefully finalising that in the next few days).

Two questions:
-  When do you plan to submit the proposal?
-  What is your preferred method of commenting/contributing to your 
proposal? (editing Wiki, commenting Wiki, email, …)

Thanks
/sven

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: 15 May 2017 13:58
To: Sven van der Meer <sven.van.der.m...@ericsson.com>; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Policy Framework Project Proposal

Hi Sven,

We look forward to working with Ericsson and other companies on the Policy 
Framework.

There is a place for your policy infrastructure. We have long envisioned the 
Policy Framework to be extendable to support multiple PDP Engines, languages, 
and extensions such as conflict mitigation.

Please feel free to add your team as contributors to start, I believe the “who 
should be” a committer status is something that will be worked out as the 
project gets assessed/approved by the TSC.

Thanks,

Pam

Pamela Dragosh
Lead Inventive Scientist
ONAP Policy
AT Research
pdrag...@research.att.com<mailto:pdrag...@research.att.com>



From: <onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>> 
on behalf of Sven van der Meer 
<sven.van.der.m...@ericsson.com<mailto:sven.van.der.m...@ericsson.com>>
Date: Monday, May 15, 2017 at 5:40 AM
To: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Policy Framework Project Proposal

Dear Pam!

We would like to strongly support your proposal for a policy framework and 
actively contribute to it. Our main work over the past years is in Adaptive 
Policies and we are prepared to contribute our APEX policy infrastructure to 
ONAP, plus underling work on policy languages (a DSL approach), conflict 
mitigation and context, policy continuum (translation/transformation/refinement 
between arbitrary domains), and the seamless execution of different policy 
models.

At the moment we are looking into providing our policy instrumentation as 
either a set of engines in the PDP package or as a system covering some aspects 
of PDP, PEP, and PAP – providing a complimentary alternative to any existing 
policy code in the packages. Does that make sense?

Furthermore, we would like to contribute to the overall ONAP discussion on 
policy frameworks as a precursor for specifications and later code.

We have a few publications in the area, which might help to understand our 
background. For instance, the group “APEX: Adaptive Policy” (the telecom policy 
group there, not the bio/agricultural groups ☺) on ResearchGate.net contains a 
number of papers on control loops (5G Summit) and engine (APEX for autonomic 
anomaly detection using Ericsson’s COMPA control loop, running last year in 
North America):
-  https://www.researchgate.net/project/Apex-Adaptive-Policy

There is more work in other areas I can point you to if you are interested, for 
instance the IETF SUPA information model and 5G management requirements from 
European projects.

My main question then is: how do we best engage with your team and the 
proposal? And is there a place for our policy infrastructure?

Thanks
/sven


[icsson]<http://www.ericsson.com/>


SVEN VAN DER MEER Dr.-Ing.
Master Engineer
NM Lab

Ericsson
Ericsson Software Campus, Athlone, Co. Westmeath
N37 PV44, Ireland
Phone +353 90 6462011
Mobile +353 87 1953797
sven.van.der.m...@erisccon.com<mailto:sven.van.der.m...@erisccon.com>
www.ericsson.com<http://www.ericsson.com>


[tp://www.ericsson.com/current_campaign]<http://www.ericsson.com/current_campaign>

Legal entity: LMI, registered office in Dublin. This Communication is 
Confidential. We only send and receive email on the basis of the terms set out 
at www.ericsson.com/email_disclaimer<http://www.ericsson.com/email_disclaimer>




From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of DRAGOSH, PAMELA L (PAM)
Sent: 11 May 2017 13:58
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>

[onap-tsc] Policy Framework Project Proposal

2017-05-11 Thread DRAGOSH, PAMELA L (PAM) 
Hello Committee Members,

I would like to submit the following project proposal:

https://wiki.onap.org/display/DW/Policy+Framework+Project+Proposal

Regards,

Pam

Pamela Dragosh
Lead Inventive Scientist
ONAP Policy
AT Research
pdrag...@research.att.com


___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc