<!-- 
RSS generated by JIRA (9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1) at Sat Feb 10 06:02:09 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Akraino JIRA</title>
    <link>https://jira.akraino.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.5</version>
        <build-number>940005</build-number>
        <build-date>11-04-2023</build-date>
    </build-info>


<item>
            <title>[IEC-14] Create Jenkins job for running SEBA and PONSim on top of IEC</title>
                <link>https://jira.akraino.org/browse/IEC-14</link>
                <project id="10201" key="IEC">Integrated Edge Cloud</project>
                    <description>&lt;p&gt;At this moment there is an IEC Jenkins jobs to deploy all seba_on_arm usecase on top of IEC, which uses bbsim as a PON simulator.&lt;/p&gt;

&lt;p&gt;In the SEBA weekly meetings it was discussed about using PONSim as a simulator, in lack of actual PON hardware. It is also what Opencord uses for the SEBA releases.&lt;/p&gt;

&lt;p&gt;Since SEBA has yet to cleary define the HW and SW platform for running this usecase, we can start this effort in the context of IEC on our own in order to gain knowledge and fix potential problems on aarch64.&lt;/p&gt;</description>
                <environment></environment>
        <key id="10271">IEC-14</key>
            <summary>Create Jenkins job for running SEBA and PONSim on top of IEC</summary>
                <type id="10002" iconUrl="https://jira.akraino.org/secure/viewavatar?size=xsmall&amp;avatarId=10318&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://jira.akraino.org/images/icons/priorities/medium.svg">Medium</priority>
                        <status id="10001" iconUrl="https://jira.akraino.org/" description="">Done</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="ciprian.barbu.enea">Ciprian Barbu</assignee>
                                    <reporter username="ciprian.barbu.enea">Ciprian Barbu</reporter>
                        <labels>
                            <label>Release_2</label>
                    </labels>
                <created>Thu, 23 May 2019 12:57:35 +0000</created>
                <updated>Mon, 27 Apr 2020 12:18:54 +0000</updated>
                            <resolved>Mon, 27 Apr 2020 12:18:54 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="11226" author="ciprian.barbu.enea" created="Mon, 27 Apr 2020 12:18:47 +0000"  >&lt;p&gt;After a long gap since the work from last year, we now finally have Jenkins job running on the IEC project in Akraino Jenkins, for testing SEBA on top of IEC.&lt;/p&gt;

&lt;p&gt;For now, only jobs for the Fuel installer and only for baremetal PODs, since virtual PODs are running excruciatingly slow and are not reliable for running SEBA properly.&lt;/p&gt;

&lt;p&gt;Here is the corresponding change:&lt;br/&gt;
&lt;a href=&quot;https://gerrit.akraino.org/r/c/ci-management/+/3352&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://gerrit.akraino.org/r/c/ci-management/+/3352&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here is the view of the master job in Jenkins:&lt;br/&gt;
&lt;a href=&quot;https://jenkins.akraino.org/view/iec/job/iec-type2-fuel-baremetal-ubuntu1804-daily-master/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.akraino.org/view/iec/job/iec-type2-fuel-baremetal-ubuntu1804-daily-master/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here is the actual job that runs the tests:&lt;br/&gt;
&lt;a href=&quot;https://jenkins.akraino.org/view/iec/job/iec-type2-test-seba_on_arm-fuel-baremetal-ubuntu1804-daily-master/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.akraino.org/view/iec/job/iec-type2-test-seba_on_arm-fuel-baremetal-ubuntu1804-daily-master/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Note that these jobs could change names in the future.&lt;/p&gt;</comment>
                            <comment id="10312" author="ciprian.barbu.enea" created="Thu, 25 Jul 2019 14:21:52 +0000"  >&lt;p&gt;For achieving the purpose of this task, there were a number of tasks involved.&lt;/p&gt;

&lt;p&gt;As a foreword, I initially started experimenting with PONSim using IEC 3 nodes clusters, first on x86 and then arm64. So here are the different issues/tasks that needed to be solved.&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Enable PONSim to run successfully on 3 nodes clusters. The were 2 issues here, one with genie-policy running on all nodes, even if it should only work on the master, and another one where the mininet pod would sometimes be scheduled to another node than the ponsimv2 components (e.g. rg). The following commit fixes this until we can make it upstream &lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt;.&lt;/li&gt;
	&lt;li&gt;Build PONSim and other related&#160;components for arm64. The Docker images resulted have been pushed to a temporary location on Dockerhub, but I will push them to the iecedge hub as soon as possible. The ponsim_3node_arm64 branch in iecedge/helm-charts shows the images changed and their location &lt;span class=&quot;error&quot;&gt;&amp;#91;2&amp;#93;&lt;/span&gt;&#160;&lt;/li&gt;
	&lt;li&gt;Installation scripts for PONSim. I tried to reuse the tools from upstream opencord, so I made this gerrit change &lt;span class=&quot;error&quot;&gt;&amp;#91;3&amp;#93;&lt;/span&gt;. This uses the opencord/automation-tools repo to deploy SEBA-in-a-Box. Since our Jenkins jobs already deploy SEBA, I decided to bypass the SEBA installation steps from automation-tools by faking the completion of the corresponding Makefile targets (this consists of touching various files in a temporary directory). It was also necessary to make the scripts use the iecedge/helm-charts version, previously described. It&apos;s worth noting that the installation script must be run on the K8S master.&lt;/li&gt;
	&lt;li&gt;Tests scripts for SEBA-in-a-Box. As with the install script, this phase uses the tools and testing framework from upstream, namley opencord/cord-tester. I referred to SIAB Opencord Jenkins jobs &lt;span class=&quot;error&quot;&gt;&amp;#91;4&amp;#93;&lt;/span&gt;. The test scripts are run in a Docker container &lt;span class=&quot;error&quot;&gt;&amp;#91;5&amp;#93;&lt;/span&gt;, specifically built for running cord-tester SIAB robot tests. The resulting change for IEC is pending &lt;span class=&quot;error&quot;&gt;&amp;#91;6&amp;#93;&lt;/span&gt;&#160;but should be merged soon.&lt;/li&gt;
	&lt;li&gt;JJB related work. This consists of defining a new step in the pipeline, iec-test-{use_case}-*. For now we only have seba_on_arm use_case, which means only one such test job, for each combination of {installer} and {os}. The gerrit change is pending &lt;span class=&quot;error&quot;&gt;&amp;#91;7&amp;#93;&lt;/span&gt;&#160;and needs review from ci-management team.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Unfortunately there is still some work to be done. During the time spent experimenting with SEBA-in-a-Box and PONSim I&apos;ve identified a number of issues, both specific to virtual pods and arm64. I will create new Jira cards to document and keep track of them. This means I cannot successfully run the test jobs in Jenkins, not unless we solve the arm64 issues and possibly move to baremetal deployment pods.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://github.com/iecedge/helm-charts/commit/561dfcff4e363bdc0b01e04a987c90a8c491c85f&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/iecedge/helm-charts/commit/561dfcff4e363bdc0b01e04a987c90a8c491c85f&lt;/a&gt;&lt;br/&gt;
 &lt;span class=&quot;error&quot;&gt;&amp;#91;2&amp;#93;&lt;/span&gt;&#160;&lt;a href=&quot;https://github.com/iecedge/helm-charts/tree/ponsim_3node_arm64&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/iecedge/helm-charts/tree/ponsim_3node_arm64&lt;/a&gt;&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;3&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://gerrit.akraino.org/r/#/c/iec/+/1131/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://gerrit.akraino.org/r/#/c/iec/+/1131/&lt;/a&gt;&lt;br/&gt;
 &lt;span class=&quot;error&quot;&gt;&amp;#91;4&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://jenkins.opencord.org/view/SIAB/job/seba-in-a-box-build-test-latest/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opencord.org/view/SIAB/job/seba-in-a-box-build-test-latest/&lt;/a&gt;&lt;br/&gt;
 &lt;span class=&quot;error&quot;&gt;&amp;#91;5&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://hub.docker.com/r/iecedge/cord-tester/tags&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://hub.docker.com/r/iecedge/cord-tester/tags&lt;/a&gt;&lt;br/&gt;
 &lt;span class=&quot;error&quot;&gt;&amp;#91;6&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://gerrit.akraino.org/r/#/c/iec/+/1215/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://gerrit.akraino.org/r/#/c/iec/+/1215/&lt;/a&gt;&lt;br/&gt;
 &lt;span class=&quot;error&quot;&gt;&amp;#91;7&amp;#93;&lt;/span&gt;&#160;&lt;a href=&quot;https://gerrit.akraino.org/r/#/c/ci-management/+/1243/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://gerrit.akraino.org/r/#/c/ci-management/+/1243/&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="10641">IEC-22</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                        <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10105" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i000l3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>