Hi,
Regarding Network Function Change management, my understanding of the situation
is as follows.
1. At the Beijing F2F the summary that occurred was that no one questioned the
need of the functionality, nor the interest of the participants do drive it,
however the question was on the deliverables. It was concluded that the to
realize this functionality it was not separate code, but code in several
projects. We concluded that there should be an email discussion on the way
forward.
2. Oliver initiated the discussion proposing several approaches we could follow.
2a. A project gathering requirements
2b. The architecture committee
2c. Consider this as a use case and identify the needs in the use case
sub-committee.
3. I had proposed the use-case sub-committee approach.
- We need a way foreward with such features that span several projects
- There is a team that interest to drive this topic, so we need to
facilitate the path
- The discussion around the use-cases has to been to derive the needs
that would be appreciated by the projects
There was no further comment nor objection to this. My proposal is that for
the sake of clarity for the team desiring to progress change management, we
bring this topic up after the rest of the project approvals and vote. My
proposed vote would be:
- "Does the TSC agree that the change management functionality is progressed as
a use case where the expected outcome of the use case discussion in the
use-case sub-commiteee is to identify and explain the needs of the projects in
order to support change management functionality".
Best Regards,
Steve.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of ROSE, DANIEL V
Sent: 21 June 2017 16:44
To: SPATSCHECK, OLIVER <[email protected]>; Phil Robb
<[email protected]>
Cc: onap-tsc <[email protected]>
Subject: Re: [onap-tsc] Special (and longer) TSC meeting this Thursday 6/22/17
I believe there was an email from Stephen T saying the network fuction change
mgmt. team could go off and make use cases so hopefully some other tsc members
can weigh in and we can make a decision.
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of SPATSCHECK, OLIVER
Sent: Wednesday, June 21, 2017 10:40 AM
To: Phil Robb <[email protected]>
Cc: onap-tsc <[email protected]>
Subject: Re: [onap-tsc] Special (and longer) TSC meeting this Thursday 6/22/17
*** Security Advisory: This Message Originated Outside of AT&T ***.
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Phil,
I thought we decided to pursue: " • Network Function Change Management”
as a use case in the use case sub committee instead of a project when we were
in Beijing. Do we have to discuss this again? Please advice so I can make sure
the correct experts will dial in.
Thx
Oliver
> On Jun 21, 2017, at 3:16 AM EDT, Phil Robb <[email protected]> wrote:
>
> Hello ONAP TSC Members:
>
> We've been unable to get adequate response from TSC members in the Doodle
> poll to determine when we could hold extra TSC meetings to close on the
> remaining project proposals that would like to participate in Release-1.
>
> Given the urgency of holding these reviews so that development teams can
> actually get to work coding, we are going to hold a special TSC meeting on
> Thursday morning during our regular TSC meeting slot, and we are extending
> the meeting to two hours this week so that we can get through all of the
> proposals.
>
> Please look for an updated calendar event to this affect.
>
> The agenda, including the order for each Project Creation Review is on the
> TSC Meeting Wiki here:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_TSC-2BMeeting-2BResources&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=PXUIufLo7FbnyzeFuMKlDoU-6k9WVXTciteWZ2L79wQ&s=hh6Jnd0_UnkYcQf1OMtvbQ_9PLwnAgc0Ek2XYOP-z9A&e=
>
>
> As we did before, one TSC member is responsible to "sheperd" the project
> proposals that fall in their domain. Please review the list on the agenda,
> identify the projects that you are to be shepherding, and reach out to the
> project contact to ensure they are available to present, *and* ensure that
> there are no outstanding questions/issues from the rest of the TSC that have
> not been addressed in the project proposals.
>
> Let's try very hard to get through all of the remaining proposals on
> Thursday. If that doesn't work, then we will need to call another special
> meeting (probably on Friday) to close on all of them.
>
> Thanks in advance for your help with this. We have project teams *unable* to
> work until the TSC completes these reviews.
>
> Best,
>
> Phil.
>
>
> --
> Phil Robb
> Executive Director, OpenDaylight Project
> VP Operations - Networking & Orchestration, The Linux Foundation
> (O) 970-229-5949
> (M) 970-420-4292
> Skype: Phil.Robb
> _______________________________________________
> ONAP-TSC mailing list
> [email protected]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=m9Kks2xE5W3_0JTf6yJDnEuTUF2hMt9hz0dh9cQ3pG4&s=SAKmpkar1vXIHYgRw9hb0fSzfgzgsdNjYnNmz03j7gw&e=
>
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=PXUIufLo7FbnyzeFuMKlDoU-6k9WVXTciteWZ2L79wQ&s=6edJvc-CkTdWXskTcb5hAY388Av5psqzFOoPpfkCl5k&e=
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc
