Hello Kenny, If I may I think that “micro” repos are a better way to handle code in a CI/CD world. Let’s take two examples:
* SO: SO has (roughly) one project into ONAP git but delivers 13 containers. That means that 1 code change that should affect only one of the containers will rebuild the 13 containers so it’s __hard__ to debug at the end. * SDC: SDC has 21 repos (if I’m not mistaken) and delivers 13 containers also. That mean that 1 code change that should affect only one of the containers __should__ rebuild 1 containers. I assume that some repos could be merged together but not that much IMHO. So for me a good practice is: * This “folder” / code produce 1 container --> it should be a project into gerrit * This “folder” / code is a common foundation for several containers --> it should be a project into gerrit and we should have a __clear__ (automated) policy on how to upgrade the upstream components. It will create a lot of git repositories but with small responsibility which is IMHO a good way for microservices. Regards, --- Sylvain Desbureaux De : <onap-...@lists.onap.org> au nom de Kenny Paul <kp...@linuxfoundation.org> Date : dimanche 7 juillet 2019 à 21:15 À : "onap-tsc@lists.onap.org" <onap-tsc@lists.onap.org>, "onap-...@lists.onap.org" <onap-...@lists.onap.org> Cc : 'Shalom Berman' <shal...@amdocs.com>, 'Avi Gaffa' <avraham.ga...@amdocs.com> Objet : Re: [Onap-arc] [onap-tsc] New SDC repositories request This reply is targeted at the TSC Members more than anything else. I am unsure why in ONAP we have a perceived need to continually create new repos within a project with the exact same set of committers over and over This isn’t behavior typically seen in other OSS projects. As I mentioned in Paris, this is pretty much worse practice<https://wiki.onap.org/display/DW/Repository+Management+FAQ?preview=/51282601/51282604/repo%20growth.png>. The issue with repo proliferation seems to be pretty pervasive My only guess that this behavior may be a holdover from a closed source development model. In January we had 250 active repos and now we have 282. That is a rate of more than one new repo per week. Bottom line, repos aren’t free. Each one means incremental ongoing work for release engineering, incremental ongoing maintenance and the more repos a project has the more difficult it becomes for someone new to onboard to that project, effectively strangling contributor diversity. I believe y’all should be trying to get a better understanding of why we need to add a repo a week. -kenny From: onap-tsc@lists.onap.org <onap-tsc@lists.onap.org> On Behalf Of Ofir Sonsino Sent: Sunday, July 7, 2019 4:07 AM To: onap-tsc@lists.onap.org; onap-...@lists.onap.org Cc: 'Shalom Berman' <shal...@amdocs.com>; 'Avi Gaffa' <avraham.ga...@amdocs.com> Subject: Re: [onap-tsc] New SDC repositories request Hi Catherine, Thank you for replying. You’re right we can’t guarantee it will be part of Frankfurt release at this stage, but I’d still like to allow the teams to make their contribution meanwhile. Giving the code will be delivered to dedicated repositories, we’ll be able to choose whether to include the artifacts in Frankfurt release, or exclude them if there’s a need to. I’m looking forward to architecture subcommittee feedback; @Arc, please note this is more about internal SDC rather than cross ONAP architecture. @Kenny, committers should be same as main SDC repository: https://git.onap.org/sdc/tree/INFO.yaml Best regards, Ofir From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> [mailto:onap-tsc@lists.onap.org] On Behalf Of Kenny Paul Sent: Tuesday, July 02, 2019 7:19 PM To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> Cc: 'Shalom Berman' <shal...@amdocs.com<mailto:shal...@amdocs.com>>; 'Avi Gaffa' <avraham.ga...@amdocs.com<mailto:avraham.ga...@amdocs.com>> Subject: Re: [onap-tsc] New SDC repositories request SDC already has 21 repos. Are the permissions on the ones proposed for a different set of committers than the others? -kenny From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> On Behalf Of Catherine LEFEVRE Sent: Tuesday, July 2, 2019 12:17 AM To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> Cc: Shalom Berman <shal...@amdocs.com<mailto:shal...@amdocs.com>>; Avi Gaffa <avraham.ga...@amdocs.com<mailto:avraham.ga...@amdocs.com>> Subject: Re: [onap-tsc] New SDC repositories request Good morning Ofir, At this stage, we cannot really confirm that this feature will be part or not of the Frankfurt release. Nevertheless, looking at the feature’s details, it seems to be required to fix the DB synchronization issue Can we get the buying from the ONAP Architecture Team? Many thanks and regards Catherine From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> [mailto:onap-tsc@lists.onap.org] On Behalf Of Sonsino, Ofir Sent: Monday, June 24, 2019 3:42 PM To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> Cc: Shalom Berman <shal...@amdocs.com<mailto:shal...@amdocs.com>>; Avi Gaffa <avraham.ga...@amdocs.com<mailto:avraham.ga...@amdocs.com>> Subject: [onap-tsc] New SDC repositories request ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Dear TSC, I’d like to ask for your approval for creating 2 SDC repositories as follow: * sdc/type-management * sdc/type-management-plugin In favor of the type management feature in SDC that is detailed here: https://wiki.onap.org/display/DW/SDC+Type+Management<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_SDC-2BType-2BManagement&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=c31OYuaPawMl_ySS_voXJQ&m=fnXTE1PpmK9FI5TBB5R4h7V_FjaLCI4WPnA54msuSpo&s=3j_FIAFC26lTEBqmMX0KowNbjENS-NvBtiQeRPlKOJA&e=> This to be a part of SDC Frankfurt release. Thanks, Ofir Sonsino Project Technical Lead, SDC AT&T Network Application Development · NetCom Tel Aviv | Tampa | Atlanta | New Jersey |Chicago ··········································································· Office: +972 (3) 5451417 Mobile: +972 (52) 4377782 E-mail: ofir.sons...@intl.att.com<mailto:ofir.sons...@intl.att.com> _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5190): https://lists.onap.org/g/onap-tsc/message/5190 Mute This Topic: https://lists.onap.org/mt/32389899/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
