Hi Srini, Here is my concern as per the charter. 3.2.1 Project Decisions Making Process Technical and release decisions for a project should be made by consensus of that project’s Committers. If consensus cannot be reached, decisions are taken by majority vote of a project’s Committers. Committers may, by majority vote, delegate (or revoke delegation) of any portion of such decisions to an alternate open, documented, and traceable decision making process.
Although this technically meets the requirements of consensus among committers for a change of project scope, unless I missed something only the AAF committers from within AT&T were included in the conversations provided. My expectation was for there to be more inclusive documentation than that. The TSC will still need to vote on the approval of the scope change, which would include the addition of the new committers and repositories. My recommendation is that this should be done tomorrow as part of the M1 review. Best Regards, -kenny Kenny Paul, Technical Program Manager [email protected] 510.766.5945 > On Jan 16, 2018, at 4:00 PM, Addepalli, Srinivasa R > <[email protected]> wrote: > > Hi Kenny, > > Please see attached emails > > First email is confirmation from Ram (PTL of AAF) confirming the scope > change of AAF to include both certificate and secret management. > Second email is more discussion and conclusions related to security using HW > facilities. > > Thanks > Srini > > > > <> > <>From: Kenny Paul [mailto:[email protected]] > Sent: Tuesday, January 16, 2018 3:19 PM > To: Kamineni, Kiran K <[email protected]> > Cc: Addepalli, Srinivasa R <[email protected]>; Stephen Terrill > <[email protected]>; [email protected]; KOYA, RAMPRASAD > <[email protected]> > Subject: Re: [onap-tsc] Certificate and Secret Management Project to become > subproject of AAF > > Can someone point me to meeting minutes or an email thread where the PTL and > the existing committers of AAF accepted this as a subproject? > > > Best Regards, > -kenny > > Kenny Paul, Technical Program Manager > [email protected] <mailto:[email protected]> > 510.766.5945 > > > On Jan 16, 2018, at 11:43 AM, Kamineni, Kiran K <[email protected] > <mailto:[email protected]>> wrote: > > Hi Stephen, > > I have submitted the seed code repositories to Gildas and he has forwarded > those to the Linux foundation lawyer. > We are waiting for final confirmation from them about that before repository > creation. > > Regarding commiters and contributers. I have added this information > here:https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-ApplicationAuthorizationFramework > > <https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-ApplicationAuthorizationFramework> > > I have tentatively added myself and Girish from Techmahindra as committers > and Manjunath, Ning and Vamshi as contributors. > > I will be adding Jira epics and stories today to the AAF Jira. > > Thanks, > -- K i r a n > > From: Addepalli, Srinivasa R > Sent: Tuesday, January 16, 2018 11:36 AM > To: Stephen Terrill <[email protected] > <mailto:[email protected]>>; [email protected] > <mailto:[email protected]>; KOYA, RAMPRASAD <[email protected] > <mailto:[email protected]>>; Kamineni, Kiran K <[email protected] > <mailto:[email protected]>> > Subject: RE: [onap-tsc] Certificate and Secret Management Project to become > subproject of AAF > > + Kiran > > Hi Steve, > Kiran is working on adding contributors/committers. He is also working with > Gildas and LF on seed code approval. I would let Kiran to provide status. > > Thanks > Srini > > > From: Stephen Terrill [mailto:[email protected] > <mailto:[email protected]>] > Sent: Friday, January 12, 2018 1:37 AM > To: Addepalli, Srinivasa R <[email protected] > <mailto:[email protected]>>; [email protected] > <mailto:[email protected]>; KOYA, RAMPRASAD <[email protected] > <mailto:[email protected]>> > Subject: RE: [onap-tsc] Certificate and Secret Management Project to become > subproject of AAF > > Hi Srini, Ram, > > Thanks. Then we should quickly bring this back to the TSC for an vote on the > updated scope. I hope it can be done by email > > Looking at the definition though, I have the following comments: > https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project > <https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project> > > - Scope: in the certificate manager, I understood that it can be > create certificates, or go through to an external authority. > - Update the “architecture” to include the latest (see chris > presentation at the last TSC). > - I assume Srini that you and your team would be added as > contributors at least? > > BR, > > Steve > > From: Addepalli, Srinivasa R [mailto:[email protected] > <mailto:[email protected]>] > Sent: 11 January 2018 15:05 > To: Stephen Terrill <[email protected] > <mailto:[email protected]>>; [email protected] > <mailto:[email protected]> > Subject: RE: [onap-tsc] Certificate and Secret Management Project to become > subproject of AAF > > Scope of AAF is updated to include Secret Management and private key > security. Certificate management & Secure communication was already part of > the scope. > So, in summary, all the scope of CSM is now part of AAF scope. > > Thanks > Srini > > > From: Stephen Terrill [mailto:[email protected] > <mailto:[email protected]>] > Sent: Wednesday, January 10, 2018 10:36 PM > To: Addepalli, Srinivasa R <[email protected] > <mailto:[email protected]>>; [email protected] > <mailto:[email protected]> > Subject: RE: [onap-tsc] Certificate and Secret Management Project to become > subproject of AAF > > Hi Sri, Ram, > > Thanks for the update – this has been good work. > > Do we need to update the project scope for AAF, or did RAM consider it within > the existing scope? > > BR, > > Steve > > From: [email protected] > <mailto:[email protected]> > [mailto:[email protected] > <mailto:[email protected]>] On Behalf Of Addepalli, Srinivasa R > Sent: 11 January 2018 05:25 > To: [email protected] <mailto:[email protected]> > Subject: [onap-tsc] Certificate and Secret Management Project to become > subproject of AAF > > We (Intel and TM) have proposed ‘Certificate and Secret Management (CSM)’ as > a separate project for Beijing release. > Details are here: https://wiki.onap.org/pages/viewpage.action?pageId=16008548 > <https://wiki.onap.org/pages/viewpage.action?pageId=16008548>. > > Both architecture subcommittee and security subcommittee recommended us to > make it part of AAF for following reasons: > > - Contain projects explosion. > - Consolidate all security services in one project. > - Why AAF? - AAF is already providing authentication and authorization > services. > > Based on recommendation, we have approached AAF team. AAF team (thanks to > Ram, Jonathan, Sai and Sunil) accepted it to be part of AAF for Beijing > release. > All the scope of CSM is accepted by AAF team including certificate > management, secret management, HW key protection and Mutual TLS among ONAP > services. > > With this, we will remove CSM from the “Proposed Projects” and put it under > AAF. > > Please do let us know if there are any questions. > > Thanks > Intel & TM team (Original proposers of CSM) > > > > _______________________________________________ > ONAP-TSC mailing list > [email protected] <mailto:[email protected]> > https://lists.onap.org/mailman/listinfo/onap-tsc > <https://lists.onap.org/mailman/listinfo/onap-tsc> > > <Mail Attachment.eml><Mail Attachment.eml>
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
