<!-- 
RSS generated by JIRA (9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1) at Sat Feb 10 06:02:20 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-37] [IEC][SEBA] Move to the new SEBA version in CI</title>
                <link>https://jira.akraino.org/browse/IEC-37</link>
                <project id="10201" key="IEC">Integrated Edge Cloud</project>
                    <description>&lt;p&gt;The work for upgrading our IEC SEBA version for arm64 to the latest stable is nearly complete. For this effort we have employed the use of upstream Opencord tools for deploying SEBA (specifically SEBA-in-a-Box), by means of forking the automation-tools and helm-charts repositories from Opencord. The longer term goal is to also integrate arm64 support in upstream, so that forking is not necessary, but that is another subject.&lt;/p&gt;

&lt;p&gt;Currently, the Akraino CI still uses the old version of SEBA in the corresponding job:&lt;br/&gt;
&lt;a href=&quot;https://jenkins.akraino.org/view/iec/job/iec-type2-install-seba_on_arm-fuel-virtual-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-install-seba_on_arm-fuel-virtual-ubuntu1804-daily-master/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We need to complete the switch to the new version by modifying the installation script:&lt;br/&gt;
&lt;a href=&quot;https://gerrit.akraino.org/r/gitweb?p=iec.git;a=blob;f=src/use_cases/seba_on_arm/install/install.sh;h=f489c03278d4ce7b1ba407371fec93b4d84ea4c5;hb=HEAD&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://gerrit.akraino.org/r/gitweb?p=iec.git;a=blob;f=src/use_cases/seba_on_arm/install/install.sh;h=f489c03278d4ce7b1ba407371fec93b4d84ea4c5;hb=HEAD&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The method used instead will be the same proposed in my previous change (WIP) which installed PONSim:&lt;br/&gt;
&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;

&lt;p&gt;The main difference to this gerrit change will be that we will no longer assume SEBA has been previously installed by some other means, and instead we will explicitly rely on the installation script to deploy SEBA, specifically this slightly altered version of SEBA-in-a-Box which, compared to the established meaning in Opencord, is able to run on 3-node clusters running the IEC platform.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11284">IEC-37</key>
            <summary>[IEC][SEBA] Move to the new SEBA version in CI</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="catiov">Catalin Iova</assignee>
                                    <reporter username="ciprian.barbu.enea">Ciprian Barbu</reporter>
                        <labels>
                    </labels>
                <created>Tue, 31 Mar 2020 16:18:07 +0000</created>
                <updated>Mon, 29 Jun 2020 10:45:35 +0000</updated>
                            <resolved>Fri, 26 Jun 2020 12:53:45 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="11307" author="ciprian.barbu.enea" created="Mon, 29 Jun 2020 10:45:35 +0000"  >&lt;p&gt;At the same time with switching to the new SEBA version in CI we moved away from virtual PODs because they simply don&apos;t have the processing power to successfully deploy SEBA in a predictable manner.&lt;/p&gt;</comment>
                            <comment id="11303" author="catiov" created="Fri, 26 Jun 2020 12:53:39 +0000"  >&lt;p&gt;Updates done:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jenkins.akraino.org/view/iec/job/iec-type2-install-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-install-seba_on_arm-fuel-baremetal-ubuntu1804-daily-master/&lt;/a&gt;&lt;/p&gt;

&lt;p&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;</comment>
                            <comment id="11175" author="ciprian.barbu.enea" created="Tue, 31 Mar 2020 16:22:41 +0000"  >&lt;p&gt;One other useful information, the Akraino CI defines two executors for the IEC project, both representing virtual aarch64 PODs. These PODs might not meet the requirements for successfully deploying and running SEBA, a baremetal POD is highly recommeneded.&lt;/p&gt;

&lt;p&gt;But until we solve this we will have to make due with the virtual PODs. In the interest of making this integration seamless, I would also recommend experimenting in the sandbox first.&lt;/p&gt;

&lt;p&gt;There are some instructions here: &lt;a href=&quot;https://docs.releng.linuxfoundation.org/en/latest/jenkins-sandbox.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://docs.releng.linuxfoundation.org/en/latest/jenkins-sandbox.html&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="11026">IEC-27</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="11386">IEC-49</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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|i003rw:</customfieldvalue>

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