Adding this to the Aug 3 agenda. Best Regards, -kenny
Kenny Paul, Technical Program Manager kp...@linuxfoundation.org 510.766.5945 > On Aug 1, 2017, at 5:07 AM, Lefevre, Catherine <cl6...@intl.att.com> wrote: > > Dear ONAP TSC, > > I fully understand the request about the seed code to be migrated to > *.onap.org <http://onap.org/>. > Nevertheless I want to bring to your attention that this request will require > significant effort (development, testing and infrastructure changes) > · Coordinate and update Maven dependencies and links > · Update namespaces as required > · Change the source code in order to align with *.onap.org > <http://onap.org/> for each impacted project > · Change the development scripts > · Review and update automated test cases > · Re-adjust the LF infrastructure accordingly, keeping the > org.openecomp version in place until the end of migration > That way each project can control the pace of migration from org.openecomp -> > org.onap : especially for the projects that are already based on the previous > naming. > · Review and re-adjust build jobs to be approved by CI-Management > project > · Create a temporary environment to perform the necessary code changes > · Plan the migration in order to avoid any drastic impact on the ONAP > community > · Recreate new docker images and stabilize the complete ONAP > Environment > · Etc. > > Based on past experience (moving from *.att.com <http://att.com/> to > *.openecomp.org <http://openecomp.org/>), this effort can take up to several > weeks until the ONAP release is completely stabilized > If we pursue in this direction then it is a major risk for our Amsterdam > release to be completed on time. > We will need to review the scope of ONAP R1 based on our resource capacity. > > Or we can develop a complete migration plan as part of our ONAP R1 commitments > And implement this migration in October as part of ONAP R2 preparation. > > Is it something we can discuss during our next TSC meeting? > > Thanks in advance for your consideration. > > Many thanks & regards > Catherine > > Catherine Lefèvre > AT&T Network and Shared Services > D2 Platform & Systems Development > AVP Software Development & Engineering > ECOMP/ONAP/RUBY/SPP > > > Phone: +32 2 418 49 22 > Mobile: +32 475 77 36 73 > catherine.lefe...@intl.att.com <mailto:catherine.lefe...@intl.att.com> > <> > TEXTING and DRIVING… It Can Wait > AT&T > BUROGEST OFFICE PARK SA > Avenue des Dessus-de-Lives, 2 > 5101 Loyers (Namur) > Belgium > > > NOTE: This email (or its attachments) contains information belonging to the > sender, which may be confidential. proprietary and/or legally privileged. The > information is intended only for the use of the individual(s) or entity(ies) > named above. If you are not the intended recipient, you are hereby notified > that any disclosure, distribution or taking of any action in reliance on the > content of this is strictly forbidden. If you have received this e-mail in > error please immediately notify the sender identified above > > _______________________________________________ > ONAP-TSC mailing list > ONAP-TSC@lists.onap.org <mailto:ONAP-TSC@lists.onap.org> > https://lists.onap.org/mailman/listinfo/onap-tsc > <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
