https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 https://jira.akraino.org/browse/REC-73 Radio Edge Cloud <p>This test case will test versions supported in the blueprint for various sub-components such as (shown here as an example) THIS IS A CI/CD test requirement</p> <p>Get specific versions from packages.yaml. In the absence of a specific version #, the latest version of that package is used (and should just be ignored as we are only testing for those specifically indicated.)</p> <p>(some examples....</p> <p><font color="#172b4d">·        </font><font color="#333333">CentOS 7.6 with LTS Kernel 4.14</font></p> <p><font color="#172b4d">·        </font><font color="#333333">Docker 19.03.2</font></p> <p><font color="#172b4d">·        </font><font color="#333333">Kubernetes 1.16.0</font></p> <p><font color="#172b4d">·        </font><font color="#000000">DANM 4.0</font></p> <p><font color="#172b4d">·        </font><font color="#000000">Ceph 12.2</font></p> <p><font color="#172b4d">·        </font><font color="#333333">Helm 2.14.3</font></p> <p><font color="#172b4d">·        </font><font color="#000000">CPU-Pooler 0.3</font></p> <p><font color="#172b4d">·        </font><font color="#000000">Prometheus 2.11</font></p> <p><font color="#172b4d">·        </font><font color="#000000">Elasticsearch 6.7</font></p> <p><font color="#172b4d">·        </font><font color="#000000">Fluentd 1.6</font></p> <p><font color="#172b4d">·        </font><font color="#000000">Ironic 10.1.4</font></p> <p><font color="#172b4d">·        </font><font color="#000000">Keystone 13.0.2 )</font></p> REC-73

Develop Test Case to Test Versions of Blueprint Sub-components

Task Medium To Do Unresolved Naga Sugguna Deepak Kataria Tue, 19 Nov 2019 21:29:36 +0000 Fri, 3 Jan 2020 21:19:36 +0000 0 4 <p>While that might work for the REC blueprint, it is not generic enough for all blueprints.<br/> The “packages.yaml” file is something we would expect other blueprints to contain, and other blueprints don’t use RPM’s for deployment in most cases.<br/> Are you aware where packages.yaml resides for the REC blueprint?</p> <p>I could not make anything from above comment.</p> <p>What I am expecting is <br/> 1) an absolute file path of a file which mentions component and version<br/> 2) structure of the file one example line is "python=3.6"</p> <p>In that case BluVal automation can read that file and check for expected versions. Please understand all the blueprint owners supposed to use the same file location and structure, then only BluVal can really use this file.</p> <p> </p> <p> </p> <p>(per <a href="https://jira.akraino.org/secure/ViewProfile.jspa?name=saku.chydenius" class="user-hover" rel="saku.chydenius">saku.chydenius</a>):</p> <p>Packages.yaml does not end up into the ISO image. Main reason is that the image itself contains more precise data of what packages, versions and dependencies were actually installed. Given file can be included easily via ta/manifest:product-manifest.spec if required:<br/> • <a href="https://gerrit.akraino.org/r/gitweb?p=ta/manifest.git;a=blob;f=product-manifest.spec;hb=refs/heads/master" class="external-link" target="_blank" rel="nofollow noopener">https://gerrit.akraino.org/r/gitweb?p=ta/manifest.git;a=blob;f=product-manifest.spec;hb=refs/heads/master</a></p> <p>There is more precise list of all included packages per Jenkins build available here (but not included in the ISO nor in the inner QCOW2 image):<br/> • <a href="https://logs.akraino.org/production/vex-yul-akraino-jenkins-prod-1/ta-ci-build-amd64/264/work/results/rpmlists/rpmdata.json" class="external-link" target="_blank" rel="nofollow noopener">https://logs.akraino.org/production/vex-yul-akraino-jenkins-prod-1/ta-ci-build-amd64/264/work/results/rpmlists/rpmdata.json</a></p> <p>Naga needs the following:</p> <p>1) Name of yaml file containing the list and versioning of all require components: File name is: packages.ini</p> <p>2) Location:</p> <p>Talk to Nokia folks to see if packages.yaml end up in the ISO, otherwise, use version in Gerrit</p> <p> </p> <p>I think we should confirm that the supported version in the blueprint is installed.</p> <p>Do we strictly match for versions exactly matched here.</p> <p>Eg. Docker <font color="#333333">19.03.2</font>, test makes sure that version 19~ or 19.03~ or strict 19.03.2?</p> Development Rank 0|i002r0: