https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-2069 controller <p>atomix.io has switched its implementation to Go and the Java implementation has been <a href="https://github.com/atomix/atomix-archive" class="external-link" target="_blank" rel="nofollow noopener">archived</a>.</p> <p>This is problematic, as the last release depends on an ancient Kryo version and upgrade requires API-incompatible changes.</p> <p>The code is licensed under APL2, so this should not be a problem.</p> <p>We only require atomix-storage and atomix-utils (as a dependency). Import atomix-archive.git/(storage/utils) into controller.git/third-party/atomix directory with full history, so that we have:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>/third-party // parent directory /third-party/atomix // parent directory /third-party/atomix/storage // code&amp;history from atomix-archive.git/storage /third-party/atomix/utils // code&amp;history from atomix-archive.git/utils</pre> </div></div> <p>In the controller repository.</p> CONTROLLER-2069

Import atomix-storage into controller.git

Task Medium Resolved Done Robert Varga Robert Varga pt Mon, 30 Jan 2023 19:27:18 +0000 Wed, 19 Apr 2023 21:12:53 +0000 Wed, 1 Mar 2023 23:39:35 +0000 7.0.5 clustering 0 3 <p>The results of conversation with LF iT is that we cannot import the history due to lack of Developer Certificate of Origin in all of the commits made to the atomix repo.<br/> Furtunately the inbound code scan done as part of the <a href="https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-25119" class="external-link" target="_blank" rel="nofollow noopener">LFIT issue</a> resulted in, quoteth:</p> <p> <br/> Here are the results from the open source license intake scan for atomix.</p> <p>LFN OpenDaylight - atomix-archive - License Intake Scan &amp; Analysis</p> <ul class="alternate" type="square"> <li>This intake scan is a static analysis of the source code in your repository. A dependency scan was not performed. Once a project is added to LFX <a href="https://security.lfx.linuxfoundation.org/" class="external-link" target="_blank" rel="nofollow noopener">https://security.lfx.linuxfoundation.org</a>, we can use SNYK to view a dependency scan for both licenses and vulnerabilities.</li> </ul> <p>Code Scanned: pulled 27-FEB-2023<br/> <a href="https://github.com/atomix/atomix-archive" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/atomix/atomix-archive</a></p> <ul class="alternate" type="square"> <li>only the following 2 directories were scanned:</li> <li><a href="https://github.com/atomix/atomix-archive/tree/master/storage" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/atomix/atomix-archive/tree/master/storage</a></li> <li><a href="https://github.com/atomix/atomix-archive/tree/master/utils" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/atomix/atomix-archive/tree/master/utils</a></li> </ul> <p>Project License: Top level project license was found: Apache 2.0</p> <p>SPDX license identifiers: License info was present in file headers, SPDX license identifiers were not found. I recommend that these be included in every source file header. <span class="error">&#91;see https://spdx.dev/ids&#93;</span></p> <p>Permissive licenses: Apache-2.0</p> <p>Copyleft licenses: None found</p> <p>Proprietary licenses: None found</p> <p>License conflicts: None found</p> <p>Binary / package files: None found</p> <p>Third party code / dependencies: None found</p> <ul class="alternate" type="square"> <li>NOTE: Open source licenses for any third party dependencies were not investigated as part of the intake scan, so not all potential license conflicts are reported here.</li> </ul> <p>Third party notice file: None found.</p> <p>SUMMARY FINDINGS: No license conflicts found. All code in the scanned directories is under the Apache 2.0 license. There should be no issues combining this code with your ODL project under the EPL-1.0 license. No information on third party dependencies was available.</p> <p>This means that while we do not get to import the git history, we are okay to import the code as-is.</p> Blocks CONTROLLER-2071 Development Rank 0|i0442n: