Do SDN Configuration Changes Get Reviewed Differently? An Empirical Study at TELUS

preprint OA: closed CC-BY-4.0
📄 Open PDF Full text JSON View at publisher

Abstract

Abstract Configuration files are crucial in Software-Defined Networking (SDN) as they define policies required for the dynamic and safe management of large-scale network traffic. Frequent changes to these files can indicate adaptability and responsiveness but may also suggest instability or frequent reconfiguration needs, due to the intricate dependencies between network components and the risk of misconfigurations that can affect network performance and security. This complexity introduced by these configuration changes poses significant challenges, complicating both the development and review processes. Managing and reviewing these changes effectively is essential to ensure that the network remains robust, secure, and optimized, making it crucial to understand and address the difficulties associated with configuration files in SDN context. This paper presents the results of a study conducted in collaboration with our industrial partner, a telecom company providing SDN-based solutions, to investigate the specific challenges related to the review of configuration files compared to traditional development and documentation files. We analyze 8,495 GitLab Merge Requests (MRs) from five configuration-centric projects. Using both quantitative and qualitative methods, we compare configuration MRs with development and documentation MRs, and examine differences between configuration bug-related and non-bug-related MRs. Our findings show that configuration-dominant MRs (more than 50% of the files are configuration) receive significantly less review participation and activity than development MRs, with less consistent quality and more questions raised. However, configuration-inclusive MRs (less than 50% configuration files) show better review quality and alignment with development standards, featuring more suggestions and evaluations. When compared to documentation MRs, both configuration-dominant and configuration-inclusive MRs exhibit higher review activity and engagement, take longer to review, and are more frequently self-managed. Configuration-dominant bug-related MRs demonstrate significantly higher review activity, engagement, and approval, emphasizing technical accuracy and achieving high-quality ratings. Configuration-inclusive bug-related MRs related to bugs show consistent review quality similar to non-bug-related MRs. The main contributions of the paper are: a comprehensive quantitative and qualitative comparison of reviews on configuration and traditional files, and an assessment of the impact of bugs in configuration files on the review process. These contributions give practitioners valuable insights to identify inefficiencies that reduce participation and effectiveness in configuration reviews in SDN context, while highlighting areas for improving review practices.
Full text 13,816 characters · extracted from preprint-html · click to expand
Do SDN Configuration Changes Get Reviewed Differently? An Empirical Study at TELUS | Research Square window.SnipcartSettings = { analytics: { enabled: false } }; (function() { var accessVector = localStorage.getItem('access_vector') || ''; window.dataLayer = window.dataLayer || []; if (accessVector) { window.dataLayer.push({ user: { profile: { profileInfo: { snid: accessVector } } } }); } })(); (function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);})(window,document,'script','dataLayer','GTM-K279D39R'); Browse Preprints In Review Journals COVID-19 Preprints AJE Video Bytes Research Tools Research Promotion AJE Professional Editing AJE Rubriq About Preprint Platform In Review Editorial Policies Our Team Advisory Board Help Center Sign In Submit a Preprint Cite Share Download PDF Research Article Do SDN Configuration Changes Get Reviewed Differently? An Empirical Study at TELUS Samah Kansab, Henri Aïdasso, Francis Bordeleau, Ali Tizghadam This is a preprint; it has not been peer reviewed by a journal. https://doi.org/ 10.21203/rs.3.rs-7263416/v1 This work is licensed under a CC BY 4.0 License Status: Posted Version 1 posted You are reading this latest preprint version Abstract Configuration files are crucial in Software-Defined Networking (SDN) as they define policies required for the dynamic and safe management of large-scale network traffic. Frequent changes to these files can indicate adaptability and responsiveness but may also suggest instability or frequent reconfiguration needs, due to the intricate dependencies between network components and the risk of misconfigurations that can affect network performance and security. This complexity introduced by these configuration changes poses significant challenges, complicating both the development and review processes. Managing and reviewing these changes effectively is essential to ensure that the network remains robust, secure, and optimized, making it crucial to understand and address the difficulties associated with configuration files in SDN context. This paper presents the results of a study conducted in collaboration with our industrial partner, a telecom company providing SDN-based solutions, to investigate the specific challenges related to the review of configuration files compared to traditional development and documentation files. We analyze 8,495 GitLab Merge Requests (MRs) from five configuration-centric projects. Using both quantitative and qualitative methods, we compare configuration MRs with development and documentation MRs, and examine differences between configuration bug-related and non-bug-related MRs. Our findings show that configuration-dominant MRs (more than 50% of the files are configuration) receive significantly less review participation and activity than development MRs, with less consistent quality and more questions raised. However, configuration-inclusive MRs (less than 50% configuration files) show better review quality and alignment with development standards, featuring more suggestions and evaluations. When compared to documentation MRs, both configuration-dominant and configuration-inclusive MRs exhibit higher review activity and engagement, take longer to review, and are more frequently self-managed. Configuration-dominant bug-related MRs demonstrate significantly higher review activity, engagement, and approval, emphasizing technical accuracy and achieving high-quality ratings. Configuration-inclusive bug-related MRs related to bugs show consistent review quality similar to non-bug-related MRs. The main contributions of the paper are: a comprehensive quantitative and qualitative comparison of reviews on configuration and traditional files, and an assessment of the impact of bugs in configuration files on the review process. These contributions give practitioners valuable insights to identify inefficiencies that reduce participation and effectiveness in configuration reviews in SDN context, while highlighting areas for improving review practices. Software Configuration Software-Defined Networking (SDN) Merge Request Code Review DevOps Full Text Additional Declarations The authors declare no competing interests. Cite Share Download PDF Status: Posted Version 1 posted You are reading this latest preprint version Research Square lets you share your work early, gain feedback from the community, and start making changes to your manuscript prior to peer review in a journal. As a division of Research Square Company, we’re committed to making research communication faster, fairer, and more useful. We do this by developing innovative software and high quality services for the global research community. Our growing team is made up of researchers and industry professionals working together to solve the most critical problems facing scientific publishing. Also discoverable on Platform About Our Team In Review Editorial Policies Advisory Board Help Center Resources Author Services Accessibility API Access RSS feed Manage Cookie Preferences © Research Square 2026 | ISSN 2693-5015 (online) Privacy Policy Terms of Service Do Not Sell My Personal Information {"props":{"pageProps":{"initialData":{"identity":"rs-7263416","acceptedTermsAndConditions":true,"allowDirectSubmit":true,"archivedVersions":[],"articleType":"Research Article","associatedPublications":[],"authors":[{"id":493829328,"identity":"fafa2307-af7d-4c4d-96a9-e5af0c6b6986","order_by":0,"name":"Samah Kansab","email":"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAZAAAAAyAQMAAABI0h/eAAAABlBMVEX///8AAABVwtN+AAAACXBIWXMAAA7EAAAOxAGVKw4bAAABB0lEQVRIie2Qu2rDMABFbyg0i4pXQyD+BZlAMvThX5ExuIsF2eot2boIsvozFAyGbgYNHdI0qyAdPGULGApd2qFyPBbR0KmDziIkONyDAIfjn3IBsO68BOhN/9Scr8xTEGCw7O7kPKVVvyvB4yZ+nyMNZp46NKC7ceRt7huGt3FkUegLL0cFsvCpSGcUdD8hPl+blcPEtkLB5YggH0iNqW+UWPhXnaJiYQtbHctPo0Ry9/xhlNeF8LYnZWFToHllVrJY1lm3UjOCU5hi1jB9rK4JTROpswfKaBIKzdcFoyoUtS2Ml3uSJ7cmrGrar7tguNrKts1VMFzayvpP6GE/XhwOh8PxJ74ByTxbMqteknoAAAAASUVORK5CYII=","orcid":"","institution":"","correspondingAuthor":true,"prefix":"","firstName":"Samah","middleName":"","lastName":"Kansab","suffix":""},{"id":493829329,"identity":"6124146e-00ec-4d42-90d6-fe24c71b5a42","order_by":1,"name":"Henri Aïdasso","email":"","orcid":"","institution":"","correspondingAuthor":false,"prefix":"","firstName":"Henri","middleName":"","lastName":"Aïdasso","suffix":""},{"id":493829330,"identity":"333f4c42-2620-4654-8661-3b98803f75db","order_by":2,"name":"Francis Bordeleau","email":"","orcid":"","institution":"","correspondingAuthor":false,"prefix":"","firstName":"Francis","middleName":"","lastName":"Bordeleau","suffix":""},{"id":493829331,"identity":"98daec00-6d8d-48cb-b031-1f25e0692603","order_by":3,"name":"Ali Tizghadam","email":"","orcid":"","institution":"","correspondingAuthor":false,"prefix":"","firstName":"Ali","middleName":"","lastName":"Tizghadam","suffix":""}],"badges":[],"createdAt":"2025-07-31 14:39:45","currentVersionCode":1,"declarations":{"humanSubjects":false,"vertebrateSubjects":false,"conflictsOfInterestStatement":false,"humanSubjectEthicalGuidelines":false,"humanSubjectConsent":false,"humanSubjectClinicalTrial":false,"humanSubjectCaseReport":false,"vertebrateSubjectEthicalGuidelines":false},"doi":"10.21203/rs.3.rs-7263416/v1","doiUrl":"https://doi.org/10.21203/rs.3.rs-7263416/v1","draftVersion":[],"editorialEvents":[],"editorialNote":"","failedWorkflow":false,"files":[{"id":88129695,"identity":"82d6e8bb-7cb1-44da-a05d-a7276cfbe0a6","added_by":"auto","created_at":"2025-08-01 18:31:31","extension":"pdf","order_by":1,"title":"","display":"","copyAsset":false,"role":"manuscript-pdf","size":627408,"visible":true,"origin":"","legend":"","description":"","filename":"archVFEMSEconfigpaper.pdf","url":"https://assets-eu.researchsquare.com/files/rs-7263416/v1_covered_950d2b60-e582-4660-b46c-de8f882262c5.pdf"}],"financialInterests":"The authors declare no competing interests.","formattedTitle":"\u003cp\u003eDo SDN Configuration Changes Get Reviewed Differently? An Empirical Study at TELUS\u003c/p\u003e","fulltext":[],"fulltextSource":"","fullText":"","funders":[],"hasAdminPriorityOnWorkflow":false,"hasManuscriptDocX":false,"hasOptedInToPreprint":true,"hasPassedJournalQc":"","hasAnyPriority":true,"hideJournal":true,"highlight":"","institution":"École de Technologie Supérieure","isAcceptedByJournal":false,"isAuthorSuppliedPdf":true,"isDeskRejected":"","isHiddenFromSearch":false,"isInQc":false,"isInWorkflow":false,"isPdf":true,"isPdfUpToDate":true,"isWithdrawnOrRetracted":false,"journal":{"display":true,"email":"[email protected]","identity":"researchsquare","isNatureJournal":false,"hasQc":true,"allowDirectSubmit":true,"externalIdentity":"","sideBox":"","snPcode":"","submissionUrl":"/submission","title":"Research Square","twitterHandle":"researchsquare","acdcEnabled":true,"dfaEnabled":false,"editorialSystem":"","reportingPortfolio":"","inReviewEnabled":false,"inReviewRevisionsEnabled":true},"keywords":"Software Configuration, Software-Defined Networking (SDN), Merge Request, Code Review, DevOps","lastPublishedDoi":"10.21203/rs.3.rs-7263416/v1","lastPublishedDoiUrl":"https://doi.org/10.21203/rs.3.rs-7263416/v1","license":{"name":"CC BY 4.0","url":"https://creativecommons.org/licenses/by/4.0/"},"manuscriptAbstract":"\u003cp\u003eConfiguration files are crucial in Software-Defined Networking (SDN) as they define policies required for the dynamic and safe management of large-scale network traffic. Frequent changes to these files can indicate adaptability and responsiveness but may also suggest instability or frequent reconfiguration needs, due to the intricate dependencies between network components and the risk of misconfigurations that can affect network performance and security. This complexity introduced by these configuration changes poses significant challenges, complicating both the development and review processes. Managing and reviewing these changes effectively is essential to ensure that the network remains robust, secure, and optimized, making it crucial to understand and address the difficulties associated with configuration files in SDN context. This paper presents the results of a study conducted in collaboration with our industrial partner, a telecom company providing SDN-based solutions, to investigate the specific challenges related to the review of configuration files compared to traditional development and documentation files. We analyze 8,495 GitLab Merge Requests (MRs) from five configuration-centric projects. Using both quantitative and qualitative methods, we compare configuration MRs with development and documentation MRs, and examine differences between configuration bug-related and non-bug-related MRs. Our findings show that configuration-dominant MRs (more than 50% of the files are configuration) receive significantly less review participation and activity than development MRs, with less consistent quality and more questions raised. However, configuration-inclusive MRs (less than 50% configuration files) show better review quality and alignment with development standards, featuring more suggestions and evaluations. When compared to documentation MRs, both configuration-dominant and configuration-inclusive MRs exhibit higher review activity and engagement, take longer to review, and are more frequently self-managed. Configuration-dominant bug-related MRs demonstrate significantly higher review activity, engagement, and approval, emphasizing technical accuracy and achieving high-quality ratings. Configuration-inclusive bug-related MRs related to bugs show consistent review quality similar to non-bug-related MRs. The main contributions of the paper are: a comprehensive quantitative and qualitative comparison of reviews on configuration and traditional files, and an assessment of the impact of bugs in configuration files on the review process. These contributions give practitioners valuable insights to identify inefficiencies that reduce participation and effectiveness in configuration reviews in SDN context, while highlighting areas for improving review practices.\u003c/p\u003e","manuscriptTitle":"Do SDN Configuration Changes Get Reviewed Differently? An Empirical Study at TELUS","msid":"","msnumber":"","nonDraftVersions":[{"code":1,"date":"2025-08-01 18:23:23","doi":"10.21203/rs.3.rs-7263416/v1","editorialEvents":[{"type":"communityComments","content":0}],"status":"published","journal":{"display":true,"email":"[email protected]","identity":"researchsquare","isNatureJournal":false,"hasQc":true,"allowDirectSubmit":true,"externalIdentity":"","sideBox":"","snPcode":"","submissionUrl":"/submission","title":"Research Square","twitterHandle":"researchsquare","acdcEnabled":true,"dfaEnabled":false,"editorialSystem":"","reportingPortfolio":"","inReviewEnabled":false,"inReviewRevisionsEnabled":true}}],"origin":"","ownerIdentity":"77d1e436-6a2e-4122-9999-aab2ad4cdb8e","owner":[],"postedDate":"August 1st, 2025","published":true,"recentEditorialEvents":[],"rejectedJournal":[],"revision":"","amendment":"","status":"posted","subjectAreas":[],"tags":[],"updatedAt":"2025-08-01T18:23:23+00:00","versionOfRecord":[],"versionCreatedAt":"2025-08-01 18:23:23","video":"","vorDoi":"","vorDoiUrl":"","workflowStages":[]},"version":"v1","identity":"rs-7263416","journalConfig":"researchsquare"},"__N_SSP":true},"page":"/article/[identity]/[[...version]]","query":{"redirect":"/article/rs-7263416","identity":"rs-7263416","version":["v1"]},"buildId":"8U1c8b4HqxoKbykW_rLl7","isFallback":false,"isExperimentalCompile":false,"dynamicIds":[84888],"gssp":true,"scriptLoader":[]}

Text is read by the "Ask this paper" AI Q&A widget below. Extraction quality varies by source — PMC NXML preserves structure cleanly, OA-HTML may include some navigation residue, and OA-PDF can have broken hyphenation. The publisher copy (via DOI) is the canonical version.

My notes (saved in your browser only)

Ask this paper AI returns verbatim quotes from the full text · source: preprint-html

Answers must be backed by verbatim quotes from this paper's full text. Hallucinated quotes are dropped automatically; if no verbatim passage answers the question, we say so. How this works

Citation neighborhood (no data yet)

We don't have any in-corpus citations linked to this paper yet. This is a recent paper (2025) — citers typically take a year or two to land, and the OpenAlex reference graph may still be filling in.

Source provenance

europepmc
last seen: 2026-05-20T01:45:00.602351+00:00
unpaywall
last seen: 2026-05-29T02:00:03.542394+00:00
License: CC-BY-4.0