[RIC Platform] All Content FeedConfluence Syndication Feedhttps://wiki.o-ran-sc.orgRe: 2023-06-20 Release HFelix Klementtag:wiki.o-ran-sc.org,2009:comment-116459014-12024-03-27T17:32:23Z2024-03-27T17:32:23Z<div class="feed"> <p>
Comment <strong>added</strong> by <a href=" https://wiki.o-ran-sc.org/display/~fklement
">Felix Klement</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px 20px 10px 20px;">
<p>Hi, I also have this problem sometimes... I don't know why it happens, but restarting the gNB doesn't solve it.<br/>The quickest solution I have found is to uninstall and reinstall the k8s cluster with the ./uninstall and ./install commands.<br/>After that it "almost" always works.</p>
</div>
<div style="border-bottom: 1px solid #ddd; padding: 17px 20px 7px 20px;">
<strong>In reply to a comment by <a href=" /display/~taeyeongkim
"
class="url fn"
>김태영(공과대학 전기전자공학)</a>:</strong><br/>
<p>Hi everyone<br/>I followed demo video and completed to install even hello-world go xapp.</p><p>But when I tried again running e2sim docker, I couldn't connect to e2 termination of ricplt.</p><p>It had been in 'UNDER-RESET' state for a long time(10 hours).</p><p>Is there anyone who know about this problem and solution?</p><p><br/></p><p>Thanks:)</p><p><br/></p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-thumbnail" draggable="false" height="150" src="https://wiki.o-ran-sc.org/download/thumbnails/78217540/reset.PNG?version=1&modificationDate=1711557803827&api=v2" data-image-src="https://wiki.o-ran-sc.org/download/attachments/78217540/reset.PNG?version=1&modificationDate=1711557803827&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="116459011" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="reset.PNG" data-base-url="https://wiki.o-ran-sc.org" data-linked-resource-content-type="image/png" data-linked-resource-container-id="78217540" data-linked-resource-container-version="10" alt=""></span></p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" draggable="false" height="150" src="https://wiki.o-ran-sc.org/download/attachments/78217540/under%20reset.PNG?version=1&modificationDate=1711557804422&api=v2" data-image-src="https://wiki.o-ran-sc.org/download/attachments/78217540/under%20reset.PNG?version=1&modificationDate=1711557804422&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="116459012" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="under reset.PNG" data-base-url="https://wiki.o-ran-sc.org" data-linked-resource-content-type="image/png" data-linked-resource-container-id="78217540" data-linked-resource-container-version="10" alt=""></span></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/display/RICP/2023-06-20+Release+H?focusedCommentId=116459014#comment-116459014">View Online</a>
</div>
</div>Felix Klement2024-03-27T17:32:23ZRe: 2023-06-20 Release H김태영(공과대학 전기전자공학)tag:wiki.o-ran-sc.org,2009:comment-116459013-12024-03-27T16:43:40Z2024-03-27T16:43:40Z<div class="feed"> <p>
Comment <strong>added</strong> by <a href=" https://wiki.o-ran-sc.org/display/~taeyeongkim
">김태영(공과대학 전기전자공학)</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px 20px 10px 20px;">
<p>Hi everyone<br/>I followed demo video and completed to install even hello-world go xapp.</p><p>But when I tried again running e2sim docker, I couldn't connect to e2 termination of ricplt.</p><p>It had been in 'UNDER-RESET' state for a long time(10 hours).</p><p>Is there anyone who know about this problem and solution?</p><p><br/></p><p>Thanks:)</p><p><br/></p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-thumbnail" draggable="false" height="150" src="https://wiki.o-ran-sc.org/download/thumbnails/78217540/reset.PNG?version=1&modificationDate=1711557803827&api=v2" data-image-src="https://wiki.o-ran-sc.org/download/attachments/78217540/reset.PNG?version=1&modificationDate=1711557803827&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="116459011" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="reset.PNG" data-base-url="https://wiki.o-ran-sc.org" data-linked-resource-content-type="image/png" data-linked-resource-container-id="78217540" data-linked-resource-container-version="10" alt=""></span></p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" draggable="false" height="150" src="https://wiki.o-ran-sc.org/download/attachments/78217540/under%20reset.PNG?version=1&modificationDate=1711557804422&api=v2" data-image-src="https://wiki.o-ran-sc.org/download/attachments/78217540/under%20reset.PNG?version=1&modificationDate=1711557804422&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="116459012" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="under reset.PNG" data-base-url="https://wiki.o-ran-sc.org" data-linked-resource-content-type="image/png" data-linked-resource-container-id="78217540" data-linked-resource-container-version="10" alt=""></span></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/display/RICP/2023-06-20+Release+H?focusedCommentId=116459013#comment-116459013">View Online</a>
</div>
</div>김태영(공과대학 전기전자공학)2024-03-27T16:43:40Z2023-06-20 Release H > under reset.PNG김태영(공과대학 전기전자공학)tag:wiki.o-ran-sc.org,2009:attachment-116459012-12024-03-27T16:43:24Z2024-03-27T16:43:24Z<div class="feed"> <p>File
<b>attached</b> by
<a href=" https://wiki.o-ran-sc.org/display/~taeyeongkim
">김태영(공과대학 전기전자공학)</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>
<span class="aui-icon content-type-attachment-image" title="PNG File">PNG File</span> <a href="https://wiki.o-ran-sc.org/download/attachments/78217540/under%20reset.PNG?version=1&modificationDate=1711557804422&api=v2">under reset.PNG</a> <span class="smalltext">(23 kB)</span>
<br/>
</p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/pages/viewpageattachments.action?pageId=78217540">View Attachments</a>
</div>
</div>김태영(공과대학 전기전자공학)2024-03-27T16:43:24Z2023-06-20 Release H > reset.PNG김태영(공과대학 전기전자공학)tag:wiki.o-ran-sc.org,2009:attachment-116459011-12024-03-27T16:43:23Z2024-03-27T16:43:23Z<div class="feed"> <p>File
<b>attached</b> by
<a href=" https://wiki.o-ran-sc.org/display/~taeyeongkim
">김태영(공과대학 전기전자공학)</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>
<span class="aui-icon content-type-attachment-image" title="PNG File">PNG File</span> <a href="https://wiki.o-ran-sc.org/download/attachments/78217540/reset.PNG?version=1&modificationDate=1711557803827&api=v2">reset.PNG</a> <span class="smalltext">(84 kB)</span>
<br/>
</p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/pages/viewpageattachments.action?pageId=78217540">View Attachments</a>
</div>
</div>김태영(공과대학 전기전자공학)2024-03-27T16:43:23ZRe: 2022-05-24 Release Fsteve rattitag:wiki.o-ran-sc.org,2009:comment-116459007-12024-03-27T15:58:06Z2024-03-27T15:58:06Z<div class="feed"> <p>
Comment <strong>added</strong> by <a href=" https://wiki.o-ran-sc.org/display/~steve.ratti
">steve ratti</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px 20px 10px 20px;">
<p>how can i get this traffic steering xapp .</p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/display/RICP/2022-05-24+Release+F?focusedCommentId=116459007#comment-116459007">View Online</a>
</div>
</div>steve ratti2024-03-27T15:58:06ZRe: Anomaly Detection Use Casesteve rattitag:wiki.o-ran-sc.org,2009:comment-116459001-12024-03-27T15:06:05Z2024-03-27T15:06:05Z<div class="feed"> <p>
Comment <strong>added</strong> by <a href=" https://wiki.o-ran-sc.org/display/~steve.ratti
">steve ratti</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px 20px 10px 20px;">
<p>i am getting the same error now</p>
</div>
<div style="border-bottom: 1px solid #ddd; padding: 17px 20px 7px 20px;">
<strong>In reply to a comment by <a href=" /display/~leonardtan
"
class="url fn"
>Leo Zidane</a>:</strong><br/>
<p>I have built it successfully but when I do a push it has an error so anyone knows how to resolve it???</p><p><br/></p><p>root@<a href="http://leo-VirtualBox/home/leo/ric-app-hw/ad" class="external-link" rel="nofollow">leo-VirtualBox:/home/leo/ric-app-hw/ad#</a>docker build -t <a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a>:10002/o-ran-sc/ric-app-ad:0.0.2 .<br/>Sending build context to Docker daemon 20.89MB<br/>Step 1/15 : FROM frolvlad/alpine-miniconda3<br/>---> 9ca2d6f3bd4a<br/>Step 2/15 : RUN mkdir -p /opt/route/<br/>---> Using cache<br/>---> fe695a352526<br/>Step 3/15 : COPY --from=<a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a>:10002/o-ran-sc/bldr-alpine3-rmr:4.0.5 /usr/local/lib64/librmr* /usr/local/lib64/<br/>---> Using cache<br/>---> 4d63fdd9fd1a<br/>Step 4/15 : COPY --from=<a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a>:10002/o-ran-sc/bldr-alpine3-rmr:4.0.5 /usr/local/bin/rmr* /usr/local/bin/<br/>---> Using cache<br/>---> 8d3c38093076<br/>Step 5/15 : ENV LD_LIBRARY_PATH /usr/local/lib/:/usr/local/lib64<br/>---> Using cache<br/>---> be9abe16b846<br/>Step 6/15 : COPY local.rt /opt/route/local.rt<br/>---> Using cache<br/>---> 015ce0bdbc64<br/>Step 7/15 : ENV RMR_SEED_RT /opt/route/local.rt<br/>---> Using cache<br/>---> dd40800d0c06<br/>Step 8/15 : RUN apk update && apk add gcc musl-dev<br/>---> Using cache<br/>---> 8656cf7e6c15<br/>Step 9/15 : RUN pip install ricxappframe<br/>---> Using cache<br/>---> f84e4921c88b<br/>Step 10/15 : COPY setup.py /tmp<br/>---> Using cache<br/>---> c9d8fb04ebaa<br/>Step 11/15 : COPY LICENSE.txt /tmp/<br/>---> Using cache<br/>---> 4f37167802ec<br/>Step 12/15 : COPY ad/ /ad<br/>---> Using cache<br/>---> 31ff7f1275f4<br/>Step 13/15 : RUN pip install /tmp<br/>---> Using cache<br/>---> b1a93104cc46<br/>Step 14/15 : ENV PYTHONUNBUFFERED 1<br/>---> Using cache<br/>---> 7f8bc7470d22<br/>Step 15/15 : CMD PYTHONPATH=/<a href="http://ad/usr/lib/python3.7/site-packages/:$PYTHONPATH" class="external-link" rel="nofollow">ad:/usr/lib/python3.7/site-packages/:$PYTHONPATH</a> run-ad.py<br/>---> Using cache<br/>---> d6ad2450a2bc<br/>Successfully built d6ad2450a2bc<br/>Successfully tagged <a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a>:10002/o-ran-sc/ric-app-ad:0.0.2</p><p><br/>root@<a href="http://leo-VirtualBox/home/leo/ric-app-hw/ad" class="external-link" rel="nofollow">leo-VirtualBox:/home/leo/ric-app-hw/ad#</a> sudo docker push <a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a>:10002/o-ran-sc/ric-app-ad:0.0.1<br/>The push refers to repository [<a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a>:10002/o-ran-sc/ric-app-ad]<br/>5c54dab035e1: Preparing <br/>5d3e835823db: Preparing <br/>d4894aca3542: Preparing <br/>79e07d1323a3: Preparing <br/>52ae9c81f8d2: Preparing <br/>fd989337ff63: Waiting <br/>3d04cf930870: Waiting <br/>e10e73199034: Waiting <br/>376e7a9179e7: Waiting <br/>eaea412865da: Waiting <br/>b04280651494: Waiting <br/>c7ddd411f0cc: Waiting <br/>e2eb06d8af82: Waiting <br/><strong>unauthorized: access to the requested resource is not authorized</strong><br/>root@<a href="http://leo-VirtualBox/home/leo/ric-app-hw/ad" class="external-link" rel="nofollow">leo-VirtualBox:/home/leo/ric-app-hw/ad#</a></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/display/RICP/Anomaly+Detection+Use+Case?focusedCommentId=116459001#comment-116459001">View Online</a>
</div>
</div>steve ratti2024-03-27T15:06:05ZProject meetingsAbdul Wahid Wtag:wiki.o-ran-sc.org,2009:page-3605124-7422024-03-26T17:32:56Z2019-07-26T10:19:31Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.o-ran-sc.org/display/~wahidw
">Abdul Wahid W</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p class="auto-cursor-target"><style type='text/css'>/*<![CDATA[*/
div.rbtoc1711699270003 {padding: 0px;}
div.rbtoc1711699270003 ul {margin-left: 0px;}
div.rbtoc1711699270003 li {margin-left: 0px;padding-left: 0px;}
/*]]>*/</style><div class='toc-macro rbtoc1711699270003'>
<ul class='toc-indentation'>
<li><a href='#Projectmeetings-MeetingInfo'>Meeting Info</a></li>
<li><a href='#Projectmeetings-2024-03-26'>2024-03-26</a></li>
<li><a href='#Projectmeetings-2024-03-12'>2024-03-12</a></li>
<li><a href='#Projectmeetings-2024-02-13'>2024-02-13</a></li>
<li><a href='#Projectmeetings-2024-01-30'>2024-01-30</a></li>
<li><a href='#Projectmeetings-2024-01-16'>2024-01-16</a></li>
<li><a href='#Projectmeetings-2023-12-19demomeetinginsteadofthenormalprojectmeeting,sametimeslot'>2023-12-19 demo meeting instead of the normal project meeting, same time slot</a></li>
<li><a href='#Projectmeetings-2023-12-05'>2023-12-05</a></li>
<li><a href='#Projectmeetings-2023-11-21'>2023-11-21</a></li>
<li><a href='#Projectmeetings-2023-11-07'>2023-11-07</a></li>
<li><a href='#Projectmeetings-Oldermeetingminutes'>Older meeting minutes</a></li>
</ul>
</div></p><h1 class="auto-cursor-target" id="Projectmeetings-MeetingInfo">Meeting Info</h1><p><span style="color: rgb(23,43,77);">RIC project meetings are open to the public and held on Tuesdays at 2pm UTC (winter) and 1pm UTC (summer). </span><a href="https://www.timeanddate.com/time/map/" class="external-link" style="text-decoration: none;" rel="nofollow">World Time Zone Map</a></p><p><strong>Zoom 1 Info:</strong></p><ul><li>Join from PC, Mac, Linux, iOS, or Android: <a href="https://zoom.us/j/9644759813" class="external-link" rel="nofollow">https://zoom.us/j/9644759813</a></li><li>Meeting ID for dial-in: <strong>9644759813</strong></li></ul><div class="table-wrap"><table class="wrapped confluenceTable"><colgroup><col/><col/><col/></colgroup><tbody><tr><td colspan="1" class="confluenceTd">UTC-time</td><td colspan="1" class="confluenceTd">every 2nd Tuesday, check from <a href="https://lists.o-ran-sc.org/g/main/calendar" class="external-link" rel="nofollow">calendar</a> <strong><br/></strong></td><td colspan="1" class="confluenceTd"><p><a href="https://zoom.us/j/9644759813" class="external-link" rel="nofollow">https://zoom.us/j/9644759813</a></p></td></tr><tr><td colspan="1" class="confluenceTd">New York (EDT / UTC-4 during DST (-5 in the winter))</td><td colspan="1" class="confluenceTd">every 2nd Tuesday, check from <a href="https://lists.o-ran-sc.org/g/main/calendar" class="external-link" rel="nofollow">calendar</a></td><td colspan="1" class="confluenceTd">+1 669 900 6833 // +1 646 558 8656 // 855 880 1246 (Toll Free) // 877 369 0926 (Toll Free)</td></tr><tr><td colspan="1" class="confluenceTd">Paris (CEST / UTC+1 in the winter (+2 during DST))</td><td colspan="1" class="confluenceTd">every 2nd Tuesday, check from <a href="https://lists.o-ran-sc.org/g/main/calendar" class="external-link" rel="nofollow">calendar</a></td><td colspan="1" class="confluenceTd">+33 7 5678 4048 // +33 1 8288 0188 // 805 082 588 (Toll Free)</td></tr><tr><td colspan="1" class="confluenceTd">Beijing (CST / UTC+8)</td><td colspan="1" class="confluenceTd">every 2nd Tuesday, check from <a href="https://lists.o-ran-sc.org/g/main/calendar" class="external-link" rel="nofollow">calendar</a></td><td colspan="1" class="confluenceTd">+86 10 87833177 // +86 10 53876330 // 400 616 8835 (Toll Free) // 400 669 9381 (Toll Free)</td></tr><tr><td class="confluenceTd">Tokyo (JST / UTC+9) </td><td class="confluenceTd">every 2nd Tuesday, check from <a href="https://lists.o-ran-sc.org/g/main/calendar" class="external-link" rel="nofollow">calendar</a></td><td class="confluenceTd">+81 524 564 439 // +81 3 4578 1488 // 0 800 100 5040 (Toll Free)</td></tr><tr><td colspan="1" class="confluenceTd">Helsinki (EEST / UTC+2 in the winter (+3 during DST))</td><td colspan="1" class="confluenceTd">every 2nd Tuesday, check from <a href="https://lists.o-ran-sc.org/g/main/calendar" class="external-link" rel="nofollow">calendar</a></td><td colspan="1" class="confluenceTd"><p>+358 341092129</p></td></tr><tr><td colspan="1" class="confluenceTd">Delhi (IST // UTC +5:30</td><td colspan="1" class="confluenceTd">every 2nd Tuesday, check from <a href="https://lists.o-ran-sc.org/g/main/calendar" class="external-link" rel="nofollow">calendar</a></td><td colspan="1" class="confluenceTd">TODO</td></tr><tr><td colspan="1" class="confluenceTd"><p><br/></p><p>Other international numbers</p></td><td colspan="1" class="confluenceTd"><a style="text-decoration: none;" class="external-link" href="https://www.timeanddate.com/time/map/" rel="nofollow">World Time Zone Map</a></td><td colspan="1" class="confluenceTd"><p>International numbers available: <a style="text-decoration: none;" href="https://zoom.us/u/acyy3hylQi" class="external-link" rel="nofollow">https://zoom.us/u/acyy3hylQi</a></p></td></tr></tbody></table></div><h1 class="auto-cursor-target" id="Projectmeetings-2024-03-26"><span style="color: rgb(0,0,0);">2024-03-26</span></h1><p><span style="color: rgb(0,0,0);">Recording: <a href="https://zoom.us/rec/share/nVF6BQwAFhdQhRmybTeAmHfhdEOCC5pwBBBOosShtGFJLKrbUcWHc3fTBQBvahb4.ubwzld8isuEhYSqe" class="external-link" rel="nofollow">link to zoom recording</a><br/></span></p><ol><li>Every time: Check rule RC-4 (<a href="https://wiki.o-ran-sc.org/display/RICP/Release+criteria+checklist+template" rel="nofollow">link</a>) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. <a href="https://gerrit.o-ran-sc.org/r/q/projects:ric-plt+size:%253E249" class="external-link" rel="nofollow"><strong>link-to-reviews</strong></a> (<a href="https://gerrit-review.googlesource.com/Documentation/user-search.html" class="external-link" rel="nofollow">gerrit filter instructions</a> // <a class="external-link" href="https://bugs.chromium.org/p/gerrit/issues/detail?id=7886" rel="nofollow">gerrit t-shirt-sizing</a>).<ol><li>Last checked on (end of I release)<ol><li>TODO</li></ol></li></ol></li><li>every second time: Review <strong>code coverage stats</strong> and <strong>blocker code smells</strong><ol><li>We take a look at the two links in the beginning of this page: <a href="https://wiki.o-ran-sc.org/display/RICP/Code+coverage+reports" rel="nofollow">Code coverage reports</a>..</li><li>The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)</li><li>Thoralf did this last on 2023-12-14 as part of release notes: we did not do this this time</li></ol></li><li>Every time: Check if there are new bug reports in JIRA: <a href="https://jira.o-ran-sc.org/issues/?jql=project%20%3D%20RIC%20AND%20type%20%3D%20Bug%20and%20status%20!%3D%20done%20and%20createdDate%20%3E%20%272020-06-24%2000%3A00%27%20ORDER%20BY%20createdDate%20DESC" class="external-link" rel="nofollow">link</a><ol><li><strong><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1051" class="external-link" rel="nofollow">RIC-1051</a> </strong></strong>Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - <strong>To be checked by Himanshu</strong></li><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1049" class="external-link" rel="nofollow">RIC-1049</a></strong> apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04 - <strong>To be assigned to Sunil</strong></li><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1047" class="external-link" rel="nofollow">RIC-1047</a></strong> crash in E2T metric increment code </li><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1045" class="external-link" rel="nofollow">RIC-1045</a></strong> <span style="color: rgb(23,43,77);">A1 mediator is in crash loopback state for H-Release And I-Release</span> (HCL team can fix) <strong>→ DONE</strong> (was a mismatch between ric-dep and image versions)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1044" class="external-link" rel="nofollow">RIC-1044</a> Potential Missing Array Size Checks Leading to Crashes in e2mgr<strong> </strong></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1043" class="external-link" rel="nofollow">RIC-1043</a> <span style="color: rgb(23,43,77);">Crash in E2T buildPrometheusList Function</span> </li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1042" class="external-link" rel="nofollow">RIC-1042</a> Can't register xApp</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1041" class="external-link" rel="nofollow">RIC-1041</a> Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1031" class="external-link" rel="nofollow">RIC-1031</a> Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1032" class="external-link" rel="nofollow">RIC-1032</a> → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1025" class="external-link" rel="nofollow">RIC-1025</a> memory leak in routing manager</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1017" class="external-link" rel="nofollow">RIC-1017</a> xapp-frame - xapp-frame may not be able to successfully subscribe to messages</li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1016" class="external-link" rel="nofollow">RIC-1016</a> e2t sctp_params structure may not be initialized properly → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1015" class="external-link" rel="nofollow">RIC-1015</a> e2t too High default message size. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1014" class="external-link" rel="nofollow">RIC-1014</a> e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1013" class="external-link" rel="nofollow">RIC-1013</a> e2t e2term pod does not become ready. Possible stack/heap corruption </p></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1002" class="external-link" rel="nofollow">RIC-1002</a> (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) <strong>→ DONE</strong></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1001" class="external-link" rel="nofollow">RIC-1001</a> CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-965" class="external-link" rel="nofollow">RIC-965</a> RMR wormhole connections uses stale endpoints to make connections </li><li><a href="https://jira.o-ran-sc.org/browse/RIC-921" class="external-link" rel="nofollow">RIC-921</a> fix UT test case in e2mgr to stub time (leftover from review <a class="external-link" title="Follow link" href="https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493</a>)</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-915" rel="nofollow">RIC-915</a> dms_cli for installing xapp not working (raised by James)</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-905" rel="nofollow">RIC-905</a> new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-901" rel="nofollow">RIC-901</a> new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-896" class="external-link" rel="nofollow">RIC-896</a> xapps sending same msg type and sub id fails - details to be clarified</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-894" class="external-link" rel="nofollow">RIC-894</a> long idle period (days) causes RMR connection breaks</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-864" class="external-link" rel="nofollow">RIC-864</a> xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-857" rel="nofollow">RIC-857</a> sporadically RMR takes multiple minutes before being "ready"</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-852" class="external-link" rel="nofollow">RIC-852</a> Intermittent Issue with E2T: While setting up E2 setup request and response.</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-837" class="external-link" rel="nofollow">RIC-837</a> RMR is not forwarding messages from E2T to E2M</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-835" class="external-link" rel="nofollow">RIC-835</a> → 2021-12-07 no news from Viktor</li><li>fixed:<strong> <br/></strong></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">James: updates?</span></span><ol><li>2023-11-21<ol><li>was at OSC-OAI conference</li><li>could start using team accounts to test beds from Colosseum (NU) and ARA</li><li>discussed with Bimo (Taiwan lab) on pair-wise testing</li><li>discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.</li></ol></li><li>2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.</li><li>2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.</li><li>2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)</li><li>2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.</li><li>2024-03-26: Unavailable today.</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd"><span style="color: rgb(0,0,0);">Prashant's work in near-RT RIC(subteam-p)</span></span></span><ol><li>2023-08-22, 2023-09-26. 2023-11-07: could not participate</li><li>2024-02-13,2024-03-12,2024-03-26: no news</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Sunil updates (subteam-h)?</span></span><ol><li>2023-09-12: can give update next time. Maybe 2 or 3 items to work on.</li><li>2023-11-07: Not in the call today</li><li>2023-11-21: no updates. Difficult to find engineers working on this.</li><li>2024-01-16: <span style="color: rgb(0,0,0);">demo of xApp project additions in I release → Next time</span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">2024-01-16: re-evaluating RIC platform Jira items</span></li><li><span style="color: rgb(0,0,0);">2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860</span></li><li><span style="color: rgb(0,0,0);">2024-02-13: working on RIC subscription delete testing </span></li><li><span style="color: rgb(0,0,0);">2024-03-12: Implementation completed, facing issues in code submission.</span></li><li><span style="color: rgb(0,0,0);">2024-03-26: Working on <strong>RIC-1049</strong>, documentation will also be made.</span></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Subhash/Naman updates (subteam-s) ?</span></span><ol><li>2023-12-05: Naman gave an update on status of Samsung items</li><li>2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.</li><li>2024-01-30, 2024-02-13: no news, but still needs to work on <a href="https://jira.o-ran-sc.org/browse/RIC-1031" class="external-link" rel="nofollow">RIC-1031</a></li><li>2024-03-12: RIC-1031 - Needs more time to complete, To start working on A1 mediator integration with Non RealTime RIC</li><li>2024-03-26: Continuing on RIC-1031, Working on <span style="color: rgb(0,0,0);"><a href="https://jira.o-ran-sc.org/browse/RIC-1048" class="external-link" rel="nofollow">RIC-1048</a></span> (analysis on RMR scaling, design to be worked upon)</li></ol></li><li>Abhijit updates (subteam-ag) ?<ol><li>2023-10-24:<ol><li>Abhijit and James release new base image: <span style="color: rgb(0,0,0);">docker pull <a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a></span><span style="color: rgb(0,0,0);">:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder <a class="confluence-userlink user-mention" data-username="gabhijit" href="https://wiki.o-ran-sc.org/display/~gabhijit" data-linked-resource-id="67535006" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Abhijit Gadgil</a> </span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">no progress in review on the plain helm chart based deployment in <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743</a> → to be merged by <a class="confluence-userlink user-mention" data-username="czichy" href="https://wiki.o-ran-sc.org/display/~czichy" data-linked-resource-id="3604529" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Thoralf Czichy</a> <br/></span></li><li><span style="color: rgb(0,0,0);">1 and 2 of <strong>RIC-1004</strong> still be finailized this week. Rest to be moved to a new item.</span></li><li><span style="color: rgb(0,0,0);">Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme <em>and</em> confluence.</span></li></ol></li><li><span style="color: rgb(0,0,0);">2024-01-16, 2024-01-30: No news.</span></li><li><span style="color: rgb(0,0,0);">2024-02-13: continues work on xapp framework rust, incl. metric support</span></li><li><span style="color: rgb(0,0,0);">2024-03-12: No news.</span></li><li><span style="color: rgb(0,0,0);">2024-03-26: Implementation done , testing pending for <strong>xapp framework rust, incl. metric</strong> support</span></li></ol></li><li>Cap Gemini updates (subteam-cg)? <ol><li>We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024</li><li>2024-01-16: Ashish <span style="color: rgb(0,0,0);">presented the design of conflict manager, first phase: <a href="https://wiki.o-ran-sc.org/download/attachments/3605124/Conflict_Manager_Phase_1.pdf?api=v2" rel="nofollow">link to slideset</a></span></li><li><span style="color: rgb(0,0,0);">2024-03-26: unavailable.</span></li></ol></li><li>Himanshu (subteam-gs) would like to work on RIC-963<br/><ol><li class="e24Kjd">2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.</li><li class="e24Kjd">2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.</li><li class="e24Kjd">2024-03-12: Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working, length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.</li><li class="e24Kjd">2024-03-26: Assigned <strong>RIC-1043,1044,1047</strong>. Will provide updates next week. length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.</li></ol></li><li class="e24Kjd">Dhiraj (subteam-r)<br/><ol><li class="e24Kjd">2023-12-05: moved the IPv6 item to J release</li><li class="e24Kjd">2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.</li><li class="e24Kjd">2024-01-26: no news.</li></ol></li><li class="e24Kjd">Alexandre (subteam-utfpr)<br/><ol><li class="e24Kjd">2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001</li><li class="e24Kjd">2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf</li><li>2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised</li><li>2024-03-26: No news.</li></ol></li><li>Nokia (subteam-n)<ol><li class="e24Kjd">RIC-997 postponed to J</li><li class="e24Kjd">2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.</li></ol></li><li>ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.<ol><li>2024-03-26: New nomination awaited from TOC.</li></ol></li><li class="e24Kjd">J release<br/><ol><li class="e24Kjd"><span style="color: rgb(0,0,0);">2024-02-13: Naman's input</span><ol><li class="e24Kjd"><span style="color: rgb(0,0,0);">no Jira tickets yet, but woudl like to focus on </span><ol><li class="e24Kjd"><span style="color: rgb(0,0,0);">K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : <a href="https://jira.o-ran-sc.org/browse/RIC-1048" class="external-link" rel="nofollow">RIC-1048</a></span></li></ol></li></ol></li><li class="e24Kjd"><span style="color: rgb(0,0,0);">I release theme for near-rt RIC was "</span>RIC Platform Enhancements". What's it going to be for J?<ol><li class="e24Kjd">Thoralf's proposal based on current Jira list: <strong>"<span style="color: rgb(0,0,0);">Make the platform more robust in handling E2AP, conflicts and A1"</span></strong></li></ol></li><li class="e24Kjd">We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from <a href="https://wiki.o-ran-sc.org/display/RICP/Jira+usage+conventions" rel="nofollow">Jira usage conventions</a>.<ol><li><span class="ILfuVd"><span class="e24Kjd">committed (90% sure) and tentative (90...30% sure) items:<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-n-proposal%20or%20labels%20%3D%20subteam-n%20)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-n</a></span></span><span class="ILfuVd"><span class="e24Kjd">,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h-proposal%20or%20labels%20%3D%20subteam-h%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-h</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-p-proposal%20or%20labels%20%3D%20subteam-p%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-p</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-s-proposal%20or%20labels%20%3D%20subteam-s%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-s</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-utfpr-proposal%20or%20labels%20%3D%20subteam-utfpr)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-utfpr</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-ag-proposal%20or%20labels%20%3D%20subteam-ag%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-ag</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-cg-proposal%20or%20labels%20%3D%20subteam-cg%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-cg</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-r-proposal%20or%20labels%20%3D%20subteam-r%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-r</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-gs-proposal%20or%20labels%20%3D%20subteam-gs%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-gs</a><br/></span></span></li><li><span class="ILfuVd"><span class="e24Kjd">committed items only:<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-cg%20or%20labels%3Dsubteam-r%20or%20labels%3Dsubteam-gs)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">all teams (committed)</a><span> </span>and<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">all teams</a><span> </span>(committed + tentative).<br/></span></span></li><li><span class="ILfuVd"><span class="e24Kjd">items that are known to require work, but are currently not in J release:<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" rel="nofollow">link</a></span></span></li></ol></li></ol></li></ol><ol><li style="list-style-type: none;"><ol><li class="e24Kjd">input for release candidates: <a href="https://jira.o-ran-sc.org/browse/RIC-967?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-c%20or%20labels%3Dsubteam-cg)%20%20and%20labels%3D%20movedoutfromH%20%20and%20type%3DEpic%20%20and%20fixVersion%20in%20(H)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">leftovers</a> and <a href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" class="external-link" rel="nofollow">generally open items</a>, RSAC</li><li class="e24Kjd">Sprint dates<ol><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 1: Feb-19 to Mar-10</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 2: Mar-11 to Mar-31</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 3: Apr-1 to Apr-21</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)</span></li></ol></li></ol></li><li>RICAPP agenda: <a href="https://wiki.o-ran-sc.org/display/RICA/RICAPP+Meetings" rel="nofollow">RICAPP Meetings.</a></li></ol><p><br/></p><h1 class="auto-cursor-target" id="Projectmeetings-2024-03-12"><span style="color: rgb(0,0,0);">2024-03-12</span></h1><p><span style="color: rgb(0,0,0);">Recording: <strong><a href="https://zoom.us/rec/play/LnalGlP-2te3jLZgtaxh9K1UbCKpV997SvHRXXoVqOk-Pv-kBwQYx0xGte62av-BfTigfClbovrc3LQL.EtN-PyK2r5d23eE9?canPlayFromShare=true&from=share_recording_detail&continueMode=true&componentName=rec-play&originRequestUrl=https%3A%2F%2Fzoom.us%2Frec%2Fshare%2FxRJlKT8J5XHU4rZYOHo3-JZuGWDxV9IqXdh_MRMlF1ABMmkqz65Y_BY9SSPxyC79.nd-5F1uyVyJ3PhVP" class="external-link" rel="nofollow">link to zoom meeting</a></strong><br/></span></p><ol><li>Every time: Check rule RC-4 (<a href="https://wiki.o-ran-sc.org/display/RICP/Release+criteria+checklist+template" rel="nofollow">link</a>) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. <a class="external-link" href="https://gerrit.o-ran-sc.org/r/q/projects:ric-plt+size:%253E249" rel="nofollow"><strong>link-to-reviews</strong></a> (<a class="external-link" href="https://gerrit-review.googlesource.com/Documentation/user-search.html" rel="nofollow">gerrit filter instructions</a> // <a class="external-link" href="https://bugs.chromium.org/p/gerrit/issues/detail?id=7886" rel="nofollow">gerrit t-shirt-sizing</a>).<ol><li>Last checked on (end of I release)<ol><li>TODO</li></ol></li></ol></li><li>every second time: Review <strong>code coverage stats</strong> and <strong>blocker code smells</strong><ol><li>We take a look at the two links in the beginning of this page: <a href="https://wiki.o-ran-sc.org/display/RICP/Code+coverage+reports" rel="nofollow">Code coverage reports</a>..</li><li>The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)</li><li>Thoralf did this last on 2023-12-14 as part of release notes: we did not do this this time</li></ol></li><li>Every time: Check if there are new bug reports in JIRA: <a href="https://jira.o-ran-sc.org/issues/?jql=project%20%3D%20RIC%20AND%20type%20%3D%20Bug%20and%20status%20!%3D%20done%20and%20createdDate%20%3E%20%272020-06-24%2000%3A00%27%20ORDER%20BY%20createdDate%20DESC" class="external-link" rel="nofollow">link</a><ol><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1049" class="external-link" rel="nofollow">RIC-1049</a></strong> apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04</li><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1047" class="external-link" rel="nofollow">RIC-1047</a></strong> crash in E2T metric increment code </li><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1045" class="external-link" rel="nofollow">RIC-1045</a></strong> <span style="color: rgb(23,43,77);">A1 mediator is in crash loopback state for H-Release And I-Release</span> (HCL team can fix) <strong>→ DONE</strong> (was a mismatch between ric-dep and image versions)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1044" class="external-link" rel="nofollow">RIC-1044</a> Potential Missing Array Size Checks Leading to Crashes in e2mgr<strong> </strong></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1043" class="external-link" rel="nofollow">RIC-1043</a> <span style="color: rgb(23,43,77);">Crash in E2T buildPrometheusList Function</span> </li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1042" class="external-link" rel="nofollow">RIC-1042</a> Can't register xApp</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1041" class="external-link" rel="nofollow">RIC-1041</a> Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1031" class="external-link" rel="nofollow">RIC-1031</a> Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1032" class="external-link" rel="nofollow">RIC-1032</a> → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1025" class="external-link" rel="nofollow">RIC-1025</a> memory leak in routing manager</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1017" class="external-link" rel="nofollow">RIC-1017</a> xapp-frame - xapp-frame may not be able to successfully subscribe to messages</li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1016" class="external-link" rel="nofollow">RIC-1016</a> e2t sctp_params structure may not be initialized properly → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1015" class="external-link" rel="nofollow">RIC-1015</a> e2t too High default message size. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1014" class="external-link" rel="nofollow">RIC-1014</a> e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1013" class="external-link" rel="nofollow">RIC-1013</a> e2t e2term pod does not become ready. Possible stack/heap corruption </p></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1002" class="external-link" rel="nofollow">RIC-1002</a> (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) <strong>→ DONE</strong></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1001" class="external-link" rel="nofollow">RIC-1001</a> CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-965" class="external-link" rel="nofollow">RIC-965</a> RMR wormhole connections uses stale endpoints to make connections </li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-921" rel="nofollow">RIC-921</a> fix UT test case in e2mgr to stub time (leftover from review <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493" class="external-link" title="Follow link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493</a>)</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-915" rel="nofollow">RIC-915</a> dms_cli for installing xapp not working (raised by James)</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-905" rel="nofollow">RIC-905</a> new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-901" rel="nofollow">RIC-901</a> new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-896" class="external-link" rel="nofollow">RIC-896</a> xapps sending same msg type and sub id fails - details to be clarified</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-894" class="external-link" rel="nofollow">RIC-894</a> long idle period (days) causes RMR connection breaks</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-864" class="external-link" rel="nofollow">RIC-864</a> xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-857" rel="nofollow">RIC-857</a> sporadically RMR takes multiple minutes before being "ready"</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-852" class="external-link" rel="nofollow">RIC-852</a> Intermittent Issue with E2T: While setting up E2 setup request and response.</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-837" rel="nofollow">RIC-837</a> RMR is not forwarding messages from E2T to E2M</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-835" class="external-link" rel="nofollow">RIC-835</a> → 2021-12-07 no news from Viktor</li><li>fixed:<strong> <br/></strong></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">James: updates?</span></span><ol><li>2023-11-21<ol><li>was at OSC-OAI conference</li><li>could start using team accounts to test beds from Colosseum (NU) and ARA</li><li>discussed with Bimo (Taiwan lab) on pair-wise testing</li><li>discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.</li></ol></li><li>2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.</li><li>2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.</li><li>2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)</li><li>2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd"><span style="color: rgb(0,0,0);">Prashant's work in near-RT RIC(subteam-p)</span></span></span><ol><li>2023-08-22, 2023-09-26. 2023-11-07: could not participate</li><li>2024-02-13,2024-03-12: no news</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Sunil updates (subteam-h)?</span></span><ol><li>2023-09-12: can give update next time. Maybe 2 or 3 items to work on.</li><li>2023-11-07: Not in the call today</li><li>2023-11-21: no updates. Difficult to find engineers working on this.</li><li>2024-01-16: <span style="color: rgb(0,0,0);">demo of xApp project additions in I release → Next time</span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">2024-01-16: re-evaluating RIC platform Jira items</span></li><li><span style="color: rgb(0,0,0);">2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860</span></li><li><span style="color: rgb(0,0,0);">2024-02-13: working on RIC subscription delete testing </span></li><li><span style="color: rgb(0,0,0);">2024-03-12: Implementation completed, facing issues in code submission.</span></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Subhash/Naman updates (subteam-s) ?</span></span><ol><li>2023-12-05: Naman gave an update on status of Samsung items</li><li>2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.</li><li>2024-01-30, 2024-02-13: no news, but still needs to work on <a href="https://jira.o-ran-sc.org/browse/RIC-1031" class="external-link" rel="nofollow">RIC-1031</a></li><li>2024-03-12: RIC-1031 - Needs more time to complete, To start working on A1 mediator integration with Non RealTime RIC</li></ol></li><li>Abhijit updates (subteam-ag) ?<ol><li>2023-10-24:<ol><li>Abhijit and James release new base image: <span style="color: rgb(0,0,0);">docker pull <a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a></span><span style="color: rgb(0,0,0);">:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder <a class="confluence-userlink user-mention" data-username="gabhijit" href="https://wiki.o-ran-sc.org/display/~gabhijit" data-linked-resource-id="67535006" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Abhijit Gadgil</a> </span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">no progress in review on the plain helm chart based deployment in <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743</a> → to be merged by <a class="confluence-userlink user-mention" data-username="czichy" href="https://wiki.o-ran-sc.org/display/~czichy" data-linked-resource-id="3604529" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Thoralf Czichy</a> <br/></span></li><li><span style="color: rgb(0,0,0);">1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.</span></li><li><span style="color: rgb(0,0,0);">Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme <em>and</em> confluence.</span></li></ol></li><li><span style="color: rgb(0,0,0);">2024-01-16, 2024-01-30: No news.</span></li><li><span style="color: rgb(0,0,0);">2024-02-13: continues work on xapp framework rust, incl. metric support</span></li><li><span style="color: rgb(0,0,0);">2024-03-12: No news.</span></li></ol></li><li>Cap Gemini updates (subteam-cg)? <ol><li>We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024</li><li>2024-01-16: Ashish <span style="color: rgb(0,0,0);">presented the design of conflict manager, first phase: <a href="https://wiki.o-ran-sc.org/download/attachments/3605124/Conflict_Manager_Phase_1.pdf?api=v2" rel="nofollow">link to slideset</a></span></li></ol></li><li>Himanshu (subteam-gs) would like to work on RIC-963<br/><ol><li class="e24Kjd">2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.</li><li class="e24Kjd">2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.</li><li class="e24Kjd">2024-03-12: Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working, length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr.Good to raise JIRA.</li></ol></li><li class="e24Kjd">Dhiraj (subteam-r)<br/><ol><li class="e24Kjd">2023-12-05: moved the IPv6 item to J release</li><li class="e24Kjd">2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.</li></ol></li><li class="e24Kjd">Alexandre (subteam-utfpr)<br/><ol><li class="e24Kjd">2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001</li><li class="e24Kjd">2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf</li><li>2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised</li></ol></li><li>Nokia (subteam-n)<ol><li class="e24Kjd">RIC-997 postponed to J</li><li class="e24Kjd">2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.</li></ol></li><li>ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.</li><li class="e24Kjd">J release<br/><ol><li class="e24Kjd"><span style="color: rgb(0,0,0);">2024-02-13: Naman's input</span><ol><li class="e24Kjd"><span style="color: rgb(0,0,0);">no Jira tickets yet, but woudl like to focus on </span><ol><li class="e24Kjd"><span style="color: rgb(0,0,0);">K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : <a href="https://jira.o-ran-sc.org/browse/RIC-1048" class="external-link" rel="nofollow">RIC-1048</a></span></li></ol></li></ol></li><li class="e24Kjd"><span style="color: rgb(0,0,0);">I release theme for near-rt RIC was "</span>RIC Platform Enhancements". What's it going to be for J?<ol><li class="e24Kjd">Thoralf's proposal based on current Jira list: <strong>"<span style="color: rgb(0,0,0);">Make the platform more robust in handling E2AP, conflicts and A1"</span></strong></li></ol></li><li class="e24Kjd">We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from <a href="https://wiki.o-ran-sc.org/display/RICP/Jira+usage+conventions" rel="nofollow">Jira usage conventions</a>.<ol><li><span class="ILfuVd"><span class="e24Kjd">committed (90% sure) and tentative (90...30% sure) items:<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-n-proposal%20or%20labels%20%3D%20subteam-n%20)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-n</a></span></span><span class="ILfuVd"><span class="e24Kjd">,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h-proposal%20or%20labels%20%3D%20subteam-h%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-h</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-p-proposal%20or%20labels%20%3D%20subteam-p%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-p</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-s-proposal%20or%20labels%20%3D%20subteam-s%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-s</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-utfpr-proposal%20or%20labels%20%3D%20subteam-utfpr)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-utfpr</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-ag-proposal%20or%20labels%20%3D%20subteam-ag%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-ag</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-cg-proposal%20or%20labels%20%3D%20subteam-cg%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-cg</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-r-proposal%20or%20labels%20%3D%20subteam-r%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-r</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-gs-proposal%20or%20labels%20%3D%20subteam-gs%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-gs</a><br/></span></span></li><li><span class="ILfuVd"><span class="e24Kjd">committed items only:<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-cg%20or%20labels%3Dsubteam-r%20or%20labels%3Dsubteam-gs)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">all teams (committed)</a><span> </span>and<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">all teams</a><span> </span>(committed + tentative).<br/></span></span></li><li><span class="ILfuVd"><span class="e24Kjd">items that are known to require work, but are currently not in J release:<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" class="external-link" rel="nofollow">link</a></span></span></li></ol></li></ol></li></ol><ol><li style="list-style-type: none;"><ol><li class="e24Kjd">input for release candidates: <a href="https://jira.o-ran-sc.org/browse/RIC-967?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-c%20or%20labels%3Dsubteam-cg)%20%20and%20labels%3D%20movedoutfromH%20%20and%20type%3DEpic%20%20and%20fixVersion%20in%20(H)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">leftovers</a> and <a href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" class="external-link" rel="nofollow">generally open items</a>, RSAC</li><li class="e24Kjd">Sprint dates<ol><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 1: Feb-19 to Mar-10</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 2: Mar-11 to Mar-31</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 3: Apr-1 to Apr-21</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)</span></li></ol></li></ol></li><li>RICAPP agenda: <a href="https://wiki.o-ran-sc.org/display/RICA/RICAPP+Meetings" rel="nofollow">RICAPP Meetings.</a></li></ol><p><br/></p><h1 class="auto-cursor-target" id="Projectmeetings-2024-02-13"><span style="color: rgb(0,0,0);">2024-02-13</span></h1><p><span style="color: rgb(0,0,0);">Recording: <a href="https://zoom.us/rec/share/V3UVNwkxl-iG3O95U-gpU3AujC7GtWgyVWykEKQwGrnW3BjNOWp_IYg4E0OL8R00.ct0Z0omZDm85W0Xd" class="external-link" rel="nofollow">link to zoom recording</a><br/></span></p><ol><li>Every time: Check rule RC-4 (<a href="https://wiki.o-ran-sc.org/display/RICP/Release+criteria+checklist+template" rel="nofollow">link</a>) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. <a href="https://gerrit.o-ran-sc.org/r/q/projects:ric-plt+size:%253E249" class="external-link" rel="nofollow"><strong>link-to-reviews</strong></a> (<a href="https://gerrit-review.googlesource.com/Documentation/user-search.html" class="external-link" rel="nofollow">gerrit filter instructions</a> // <a class="external-link" href="https://bugs.chromium.org/p/gerrit/issues/detail?id=7886" rel="nofollow">gerrit t-shirt-sizing</a>).<ol><li>Last checked on (end of I release)<ol><li>TODO</li></ol></li></ol></li><li>every second time: Review <strong>code coverage stats</strong> and <strong>blocker code smells</strong><ol><li>We take a look at the two links in the beginning of this page: <a href="https://wiki.o-ran-sc.org/display/RICP/Code+coverage+reports" rel="nofollow">Code coverage reports</a>..</li><li>The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)</li><li>Thoralf did this last on 2023-12-14 as part of release notes: we did not do this this time</li></ol></li><li>Every time: Check if there are new bug reports in JIRA: <a href="https://jira.o-ran-sc.org/issues/?jql=project%20%3D%20RIC%20AND%20type%20%3D%20Bug%20and%20status%20!%3D%20done%20and%20createdDate%20%3E%20%272020-06-24%2000%3A00%27%20ORDER%20BY%20createdDate%20DESC" class="external-link" rel="nofollow">link</a><ol><li><strong>new <a href="https://jira.o-ran-sc.org/browse/RIC-1047" class="external-link" rel="nofollow">RIC-1047</a></strong> crash in E2T metric increment code </li><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1045" class="external-link" rel="nofollow">RIC-1045</a></strong> <span style="color: rgb(23,43,77);">A1 mediator is in crash loopback state for H-Release And I-Release</span> (HCL team can fix) <strong>→ DONE</strong> (was a mismatch between ric-dep and image versions)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1044" class="external-link" rel="nofollow">RIC-1044</a> Potential Missing Array Size Checks Leading to Crashes in e2mgr<strong> </strong></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1043" class="external-link" rel="nofollow">RIC-1043</a> <span style="color: rgb(23,43,77);">Crash in E2T buildPrometheusList Function</span> </li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1042" class="external-link" rel="nofollow">RIC-1042</a> Can't register xApp</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1041" class="external-link" rel="nofollow">RIC-1041</a> Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1031" class="external-link" rel="nofollow">RIC-1031</a> Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1032" class="external-link" rel="nofollow">RIC-1032</a> → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1025" class="external-link" rel="nofollow">RIC-1025</a> memory leak in routing manager</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1017" class="external-link" rel="nofollow">RIC-1017</a> xapp-frame - xapp-frame may not be able to successfully subscribe to messages</li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1016" class="external-link" rel="nofollow">RIC-1016</a> e2t sctp_params structure may not be initialized properly → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1015" class="external-link" rel="nofollow">RIC-1015</a> e2t too High default message size. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1014" class="external-link" rel="nofollow">RIC-1014</a> e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1013" class="external-link" rel="nofollow">RIC-1013</a> e2t e2term pod does not become ready. Possible stack/heap corruption </p></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1002" class="external-link" rel="nofollow">RIC-1002</a> (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1001" class="external-link" rel="nofollow">RIC-1001</a> CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-965" class="external-link" rel="nofollow">RIC-965</a> RMR wormhole connections uses stale endpoints to make connections </li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-921" rel="nofollow">RIC-921</a> fix UT test case in e2mgr to stub time (leftover from review <a title="Follow link" class="external-link" href="https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493</a>)</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-915" rel="nofollow">RIC-915</a> dms_cli for installing xapp not working (raised by James)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-905" class="external-link" rel="nofollow">RIC-905</a> new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-901" rel="nofollow">RIC-901</a> new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-896" rel="nofollow">RIC-896</a> xapps sending same msg type and sub id fails - details to be clarified</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-894" class="external-link" rel="nofollow">RIC-894</a> long idle period (days) causes RMR connection breaks</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-864" rel="nofollow">RIC-864</a> xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-857" class="external-link" rel="nofollow">RIC-857</a> sporadically RMR takes multiple minutes before being "ready"</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-852" class="external-link" rel="nofollow">RIC-852</a> Intermittent Issue with E2T: While setting up E2 setup request and response.</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-837" rel="nofollow">RIC-837</a> RMR is not forwarding messages from E2T to E2M</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-835" rel="nofollow">RIC-835</a> → 2021-12-07 no news from Viktor</li><li>fixed:<strong> <br/></strong></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">James: updates?</span></span><ol><li>2023-11-21<ol><li>was at OSC-OAI conference</li><li>could start using team accounts to test beds from Colosseum (NU) and ARA</li><li>discussed with Bimo (Taiwan lab) on pair-wise testing</li><li>discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.</li></ol></li><li>2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.</li><li>2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.</li><li>2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd"><span style="color: rgb(0,0,0);">Prashant's work in near-RT RIC(subteam-p)</span></span></span><ol><li>2023-08-22, 2023-09-26. 2023-11-07: could not participate</li><li>2024-02-13: no news</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Sunil updates (subteam-h)?</span></span><ol><li>2023-09-12: can give update next time. Maybe 2 or 3 items to work on.</li><li>2023-11-07: Not in the call today</li><li>2023-11-21: no updates. Difficult to find engineers working on this.</li><li>2024-01-16: <span style="color: rgb(0,0,0);">demo of xApp project additions in I release → Next time</span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">2024-01-16: re-evaluating RIC platform Jira items</span></li><li><span style="color: rgb(0,0,0);">2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860</span></li><li><span style="color: rgb(0,0,0);">2024-02-13: working on RIC subscription delete testing </span></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Subhash/Naman updates (subteam-s) ?</span></span><ol><li>2023-12-05: Naman gave an update on status of Samsung items</li><li>2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.</li><li>2024-01-30, 2024-02-13: no news, but still needs to work on <a href="https://jira.o-ran-sc.org/browse/RIC-1031" class="external-link" rel="nofollow">RIC-1031</a></li></ol></li><li>Abhijit updates (subteam-ag) ?<ol><li>2023-10-24:<ol><li>Abhijit and James release new base image: <span style="color: rgb(0,0,0);">docker pull <a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a></span><span style="color: rgb(0,0,0);">:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder <a class="confluence-userlink user-mention" data-username="gabhijit" href="https://wiki.o-ran-sc.org/display/~gabhijit" data-linked-resource-id="67535006" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Abhijit Gadgil</a> </span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">no progress in review on the plain helm chart based deployment in <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743</a> → to be merged by <a class="confluence-userlink user-mention" data-username="czichy" href="https://wiki.o-ran-sc.org/display/~czichy" data-linked-resource-id="3604529" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Thoralf Czichy</a> <br/></span></li><li><span style="color: rgb(0,0,0);">1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.</span></li><li><span style="color: rgb(0,0,0);">Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme <em>and</em> confluence.</span></li></ol></li><li><span style="color: rgb(0,0,0);">2024-01-16, 2024-01-30: No news.</span></li><li><span style="color: rgb(0,0,0);">2024-02-13: continues work on xapp framework rust, incl. metric support</span></li></ol></li><li>Cap Gemini updates (subteam-cg)? <ol><li>We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024</li><li>2024-01-16: Ashish <span style="color: rgb(0,0,0);">presented the design of conflict manager, first phase: <a href="https://wiki.o-ran-sc.org/download/attachments/3605124/Conflict_Manager_Phase_1.pdf?api=v2" rel="nofollow">link to slideset</a></span></li></ol></li><li>Himanshu (subteam-gs) would like to work on RIC-963<br/><ol><li class="e24Kjd">2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.</li><li class="e24Kjd">2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.</li></ol></li><li class="e24Kjd">Dhiraj (subteam-r)<br/><ol><li class="e24Kjd">2023-12-05: moved the IPv6 item to J release</li><li class="e24Kjd">2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over teh next weeks.</li></ol></li><li class="e24Kjd">Alexandre (subteam-utfpr)<br/><ol><li class="e24Kjd">2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001</li><li class="e24Kjd">2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf</li></ol></li><li>Nokia (subteam-n)<ol><li class="e24Kjd">RIC-997 postponed to J</li><li class="e24Kjd">2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.</li></ol></li><li class="e24Kjd">J release<br/><ol><li class="e24Kjd"><span style="color: rgb(0,0,0);">2024-02-13: Naman's input</span><ol><li class="e24Kjd"><span style="color: rgb(0,0,0);">no Jira tickets yet, but woudl like to focus on </span><ol><li class="e24Kjd"><span style="color: rgb(0,0,0);">K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : <a href="https://jira.o-ran-sc.org/browse/RIC-1048" class="external-link" rel="nofollow">RIC-1048</a></span></li></ol></li></ol></li><li class="e24Kjd"><span style="color: rgb(0,0,0);">I release theme for near-rt RIC was "</span>RIC Platform Enhancements". What's it going to be for J?<ol><li class="e24Kjd">Thoralf's proposal based on current Jira list: <strong>"<span style="color: rgb(0,0,0);">Make the platform more robust in handling E2AP, conflicts and A1"</span></strong></li></ol></li><li class="e24Kjd">We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from <a href="https://wiki.o-ran-sc.org/display/RICP/Jira+usage+conventions" rel="nofollow">Jira usage conventions</a>.<ol><li><span class="ILfuVd"><span class="e24Kjd">committed (90% sure) and tentative (90...30% sure) items:<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-n-proposal%20or%20labels%20%3D%20subteam-n%20)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-n</a></span></span><span class="ILfuVd"><span class="e24Kjd">,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h-proposal%20or%20labels%20%3D%20subteam-h%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-h</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-p-proposal%20or%20labels%20%3D%20subteam-p%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-p</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-s-proposal%20or%20labels%20%3D%20subteam-s%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-s</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-utfpr-proposal%20or%20labels%20%3D%20subteam-utfpr)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-utfpr</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-ag-proposal%20or%20labels%20%3D%20subteam-ag%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-ag</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-cg-proposal%20or%20labels%20%3D%20subteam-cg%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-cg</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-r-proposal%20or%20labels%20%3D%20subteam-r%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-r</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-gs-proposal%20or%20labels%20%3D%20subteam-gs%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-gs</a><br/></span></span></li><li><span class="ILfuVd"><span class="e24Kjd">committed items only:<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-cg%20or%20labels%3Dsubteam-r%20or%20labels%3Dsubteam-gs)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">all teams (committed)</a><span> </span>and<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">all teams</a><span> </span>(committed + tentative).<br/></span></span></li><li><span class="ILfuVd"><span class="e24Kjd">items that are known to require work, but are currently not in J release:<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" class="external-link" rel="nofollow">link</a></span></span></li></ol></li></ol></li></ol><ol><li style="list-style-type: none;"><ol><li class="e24Kjd">input for release candidates: <a href="https://jira.o-ran-sc.org/browse/RIC-967?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-c%20or%20labels%3Dsubteam-cg)%20%20and%20labels%3D%20movedoutfromH%20%20and%20type%3DEpic%20%20and%20fixVersion%20in%20(H)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">leftovers</a> and <a href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" class="external-link" rel="nofollow">generally open items</a>, RSAC</li><li class="e24Kjd">Sprint dates<ol><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 1: Feb-19 to Mar-10</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 2: Mar-11 to Mar-31</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 3: Apr-1 to Apr-21</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)</span></li></ol></li></ol></li><li>RICAPP agenda: <a href="https://wiki.o-ran-sc.org/display/RICA/RICAPP+Meetings" rel="nofollow">RICAPP Meetings.</a></li></ol><p><br/></p><h1 class="auto-cursor-target" id="Projectmeetings-2024-01-30"><span style="color: rgb(0,0,0);">2024-01-30</span></h1><p><span style="color: rgb(0,0,0);">Recording: <a href="https://zoom.us/rec/share/hed3PSHMSxnsVH-hiWUiXGVnIrbSXroh4ynS6Jh8p3ft3EDSyD4vhSyh_HWkae01.gZM-NXPYEvagtc2G" class="external-link" rel="nofollow">link to zoom recording</a><br/></span></p><ol><li>Every time: Check rule RC-4 (<a href="https://wiki.o-ran-sc.org/display/RICP/Release+criteria+checklist+template" rel="nofollow">link</a>) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. <a class="external-link" href="https://gerrit.o-ran-sc.org/r/q/projects:ric-plt+size:%253E249" rel="nofollow"><strong>link-to-reviews</strong></a> (<a href="https://gerrit-review.googlesource.com/Documentation/user-search.html" class="external-link" rel="nofollow">gerrit filter instructions</a> // <a href="https://bugs.chromium.org/p/gerrit/issues/detail?id=7886" class="external-link" rel="nofollow">gerrit t-shirt-sizing</a>).<ol><li>Last checked on 2023-09-26<ol><li>TODO</li></ol></li></ol></li><li>every second time: Review <strong>code coverage stats</strong> and <strong>blocker code smells</strong><ol><li>We take a look at the two links in the beginning of this page: <a href="https://wiki.o-ran-sc.org/display/RICP/Code+coverage+reports" rel="nofollow">Code coverage reports</a>..</li><li>The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)</li><li>Thoralf did this last on 2023-12-14 as part of release notes: we did not do this this time</li></ol></li><li>Every time: Check if there are new bug reports in JIRA: <a href="https://jira.o-ran-sc.org/issues/?jql=project%20%3D%20RIC%20AND%20type%20%3D%20Bug%20and%20status%20!%3D%20done%20and%20createdDate%20%3E%20%272020-06-24%2000%3A00%27%20ORDER%20BY%20createdDate%20DESC" class="external-link" rel="nofollow">link</a><ol><li>RIC-1045 <span style="color: rgb(23,43,77);">A1 mediator is in crash loopback state for H-Release And I-Release</span> (HCL team can fix </li><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1044" class="external-link" rel="nofollow">RIC-1044</a></strong> Potential Missing Array Size Checks Leading to Crashes in e2mgr<strong> </strong></li><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1043" class="external-link" rel="nofollow">RIC-1043</a> </strong><span style="color: rgb(23,43,77);">Crash in E2T buildPrometheusList Function</span><strong> </strong></li><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1042" class="external-link" rel="nofollow">RIC-1042</a></strong> Can't register xApp</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1041" class="external-link" rel="nofollow">RIC-1041</a> Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1031" class="external-link" rel="nofollow">RIC-1031</a> Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1032" class="external-link" rel="nofollow">RIC-1032</a> → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1025" class="external-link" rel="nofollow">RIC-1025</a> memory leak in routing manager</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1017" class="external-link" rel="nofollow">RIC-1017</a> xapp-frame - xapp-frame may not be able to successfully subscribe to messages</li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1016" class="external-link" rel="nofollow">RIC-1016</a> e2t sctp_params structure may not be initialized properly → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1015" class="external-link" rel="nofollow">RIC-1015</a> e2t too High default message size. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1014" class="external-link" rel="nofollow">RIC-1014</a> e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1013" class="external-link" rel="nofollow">RIC-1013</a> e2t e2term pod does not become ready. Possible stack/heap corruption </p></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1002" class="external-link" rel="nofollow">RIC-1002</a> (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1001" class="external-link" rel="nofollow">RIC-1001</a> CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-965" class="external-link" rel="nofollow">RIC-965</a> RMR wormhole connections uses stale endpoints to make connections </li><li><a href="https://jira.o-ran-sc.org/browse/RIC-921" class="external-link" rel="nofollow">RIC-921</a> fix UT test case in e2mgr to stub time (leftover from review <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493" title="Follow link" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493</a>)</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-915" rel="nofollow">RIC-915</a> dms_cli for installing xapp not working (raised by James)</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-905" rel="nofollow">RIC-905</a> new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-901" class="external-link" rel="nofollow">RIC-901</a> new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-896" class="external-link" rel="nofollow">RIC-896</a> xapps sending same msg type and sub id fails - details to be clarified</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-894" rel="nofollow">RIC-894</a> long idle period (days) causes RMR connection breaks</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-864" class="external-link" rel="nofollow">RIC-864</a> xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-857" rel="nofollow">RIC-857</a> sporadically RMR takes multiple minutes before being "ready"</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-852" class="external-link" rel="nofollow">RIC-852</a> Intermittent Issue with E2T: While setting up E2 setup request and response.</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-837" class="external-link" rel="nofollow">RIC-837</a> RMR is not forwarding messages from E2T to E2M</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-835" rel="nofollow">RIC-835</a> → 2021-12-07 no news from Viktor</li><li>fixed:<strong> <br/></strong></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">James: updates?</span></span><ol><li>2023-11-21<ol><li>was at OSC-OAI conference</li><li>could start using team accounts to test beds from Colosseum (NU) and ARA</li><li>discussed with Bimo (Taiwan lab) on pair-wise testing</li><li>discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.</li></ol></li><li>2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.</li><li>2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd"><span style="color: rgb(0,0,0);">Prashant's work in near-RT RIC(subteam-p)</span></span></span><ol><li>2023-08-22, 2023-09-26. 2023-11-07: could not participate</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Sunil updates (subteam-h)?</span></span><ol><li>2023-09-12: can give update next time. Maybe 2 or 3 items to work on.</li><li>2023-11-07: Not in the call today</li><li>2023-11-21: no updates. Difficult to find engineers working on this.</li><li>2024-01-16: <span style="color: rgb(0,0,0);">demo of xApp project additions in I release → Next time</span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">2024-01-16: re-evaluating RIC platform Jira items</span></li><li><span style="color: rgb(0,0,0);">2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860</span></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Naman updates (subteam-s) ?</span></span><ol><li>2023-12-05: Naman gave an update on status of Samsung items</li><li>2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.</li><li>2024-01-30: no news</li></ol></li><li>Abhijit updates (subteam-ag) ?<ol><li>2023-10-24:<ol><li>Abhijit and James release new base image: <span style="color: rgb(0,0,0);">docker pull <a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a></span><span style="color: rgb(0,0,0);">:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder <a class="confluence-userlink user-mention" data-username="gabhijit" href="https://wiki.o-ran-sc.org/display/~gabhijit" data-linked-resource-id="67535006" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Abhijit Gadgil</a> </span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">no progress in review on the plain helm chart based deployment in <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743</a> → to be merged by <a class="confluence-userlink user-mention" data-username="czichy" href="https://wiki.o-ran-sc.org/display/~czichy" data-linked-resource-id="3604529" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Thoralf Czichy</a> <br/></span></li><li><span style="color: rgb(0,0,0);">1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.</span></li><li><span style="color: rgb(0,0,0);">Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme <em>and</em> confluence.</span></li></ol></li><li><span style="color: rgb(0,0,0);">2024-01-16, 2024-01-30: No news.</span></li></ol></li><li>Cap Gemini updates (subteam-cg)? <ol><li>We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024</li><li>2024-01-16: Ashish <span style="color: rgb(0,0,0);">presented the design of conflict manager, first phase: <a href="https://wiki.o-ran-sc.org/download/attachments/3605124/Conflict_Manager_Phase_1.pdf?api=v2" rel="nofollow">link to slideset</a></span></li></ol></li><li>Himanshu (subteam-gs) would like to work on RIC-963<br/><ol><li class="e24Kjd">2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.</li><li class="e24Kjd">2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.</li></ol></li><li class="e24Kjd">Dhiraj (subteam-r)<br/><ol><li class="e24Kjd">2023-12-05: moved the IPv6 item to J release</li><li class="e24Kjd">2024-01-16: approval for changes to be commited now obtained. IPv6-related commits expected over teh next weeks.</li></ol></li><li class="e24Kjd">Alexandre (subteam-utfpr)<br/><ol><li class="e24Kjd">2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001</li><li class="e24Kjd">2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf</li></ol></li><li>Nokia (subteam-n)<ol><li class="e24Kjd">RIC-997 postponed to J</li></ol></li><li class="e24Kjd">J release<br/><ol><li class="e24Kjd"><strong><span style="color: rgb(0,0,0);">I release theme for near-rt RIC was "</span>RIC Platform Enhancements". What's it going to be for J?</strong></li><li class="e24Kjd">We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from <a href="https://wiki.o-ran-sc.org/display/RICP/Jira+usage+conventions" rel="nofollow">Jira usage conventions</a>.<ol><li><span class="ILfuVd"><span class="e24Kjd">committed (90% sure) and tentative (90...30% sure) items:<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-n-proposal%20or%20labels%20%3D%20subteam-n%20)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-n</a></span></span><span class="ILfuVd"><span class="e24Kjd">,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h-proposal%20or%20labels%20%3D%20subteam-h%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-h</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-p-proposal%20or%20labels%20%3D%20subteam-p%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-p</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-s-proposal%20or%20labels%20%3D%20subteam-s%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-s</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-utfpr-proposal%20or%20labels%20%3D%20subteam-utfpr)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-utfpr</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-ag-proposal%20or%20labels%20%3D%20subteam-ag%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-ag</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-cg-proposal%20or%20labels%20%3D%20subteam-cg%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-cg</a>,<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-r-proposal%20or%20labels%20%3D%20subteam-r%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">subteam-r</a>,<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-gs-proposal%20or%20labels%20%3D%20subteam-gs%20)%20%20and%20fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">subteam-gs</a><br/></span></span></li><li><span class="ILfuVd"><span class="e24Kjd">committed items only:<span> </span><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-cg%20or%20labels%3Dsubteam-r%20or%20labels%3Dsubteam-gs)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">all teams (committed)</a><span> </span>and<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=fixVersion%20in%20(J)%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" rel="nofollow">all teams</a><span> </span>(committed + tentative).<br/></span></span></li><li><span class="ILfuVd"><span class="e24Kjd">items that are known to require work, but are currently not in J release:<span> </span><a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" rel="nofollow">link</a></span></span></li></ol></li></ol></li></ol><ol><li style="list-style-type: none;"><ol><li class="e24Kjd">input for release candidates: <a href="https://jira.o-ran-sc.org/browse/RIC-967?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-c%20or%20labels%3Dsubteam-cg)%20%20and%20labels%3D%20movedoutfromH%20%20and%20type%3DEpic%20%20and%20fixVersion%20in%20(H)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">leftovers</a> and <a href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" class="external-link" rel="nofollow">generally open items</a>, RSAC</li><li class="e24Kjd">Sprint dates<ol><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 1: Feb-19 to Mar-10</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 2: Mar-11 to Mar-31</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 3: Apr-1 to Apr-21</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)</span></li><li><span style="color: rgb(0,0,0);">Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)</span></li></ol></li></ol></li><li>RICAPP agenda: <a href="https://wiki.o-ran-sc.org/display/RICA/RICAPP+Meetings" rel="nofollow">RICAPP Meetings.</a></li></ol><h1 class="auto-cursor-target" id="Projectmeetings-2024-01-16"><span style="color: rgb(0,0,0);">2024-01-16</span></h1><p><span style="color: rgb(0,0,0);">Recording: <a href="https://zoom.us/rec/share/-XKT3yFyCIzy8IcU2q88DeASdVX1D4jSETktE2kkvycNzTrVwz43Dk7WjaNmclto.oDrJfzqJLZSgouAn" class="external-link" rel="nofollow">link to zoom recording</a><br/></span></p><ol><li>Every time: Check rule RC-4 (<a href="https://wiki.o-ran-sc.org/display/RICP/Release+criteria+checklist+template" rel="nofollow">link</a>) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. <a class="external-link" href="https://gerrit.o-ran-sc.org/r/q/projects:ric-plt+size:%253E249" rel="nofollow"><strong>link-to-reviews</strong></a> (<a class="external-link" href="https://gerrit-review.googlesource.com/Documentation/user-search.html" rel="nofollow">gerrit filter instructions</a> // <a class="external-link" href="https://bugs.chromium.org/p/gerrit/issues/detail?id=7886" rel="nofollow">gerrit t-shirt-sizing</a>).<ol><li>Last checked on 2023-09-26<ol><li>TODO</li></ol></li></ol></li><li>every second time: Review <strong>code coverage stats</strong> and <strong>blocker code smells</strong><ol><li>We take a look at the two links in the beginning of this page: <a href="https://wiki.o-ran-sc.org/display/RICP/Code+coverage+reports" rel="nofollow">Code coverage reports</a>..</li><li>The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)</li><li>Thoralf did this last on 2023-12-14 as part of release notes: we did not do this this time</li></ol></li><li>Every time: Check if there are new bug reports in JIRA: <a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=project%20%3D%20RIC%20AND%20type%20%3D%20Bug%20and%20status%20!%3D%20done%20and%20createdDate%20%3E%20%272020-06-24%2000%3A00%27%20ORDER%20BY%20createdDate%20DESC" rel="nofollow">link</a><ol><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1041" class="external-link" rel="nofollow">RIC-1041</a> </strong>Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation</li><li><strong><a href="https://jira.o-ran-sc.org/browse/RIC-1031" class="external-link" rel="nofollow">RIC-1031</a></strong><strong> </strong>Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1032" class="external-link" rel="nofollow">RIC-1032</a> → RIC-1035 - we cpontinue with this under RIC-1035 (discussed with Abhijit in the project meeting)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1025" class="external-link" rel="nofollow">RIC-1025</a> memory leak in routing manager</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1017" class="external-link" rel="nofollow">RIC-1017</a> xapp-frame - xapp-frame may not be able to successfully subscribe to messages</li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1016" class="external-link" rel="nofollow">RIC-1016</a> e2t sctp_params structure may not be initialized properly → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1015" class="external-link" rel="nofollow">RIC-1015</a> e2t too High default message size. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1014" class="external-link" rel="nofollow">RIC-1014</a> e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1013" class="external-link" rel="nofollow">RIC-1013</a> e2t e2term pod does not become ready. Possible stack/heap corruption </p></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1002" class="external-link" rel="nofollow">RIC-1002</a> (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1001" class="external-link" rel="nofollow">RIC-1001</a> <strong>CVE-2023-41627</strong> RMR service should verify route tables - Alexandre will take a look</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-991" class="external-link" rel="nofollow">RIC-991</a> <strong>CVE-2023-40997</strong> RMR related (not a duplicate) - Alexandre will take a look → <strong>DONE</strong></li><li><span style="color: rgb(0,0,0);"><a href="https://jira.o-ran-sc.org/browse/RIC-989" class="external-link" rel="nofollow">RIC-989</a></span> <strong>CVE-2023-40998</strong> RMR (minor) security issue - Alexandre will take a look → <strong>DONE</strong></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-965" class="external-link" rel="nofollow">RIC-965</a> RMR wormhole connections uses stale endpoints to make connections </li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-921" rel="nofollow">RIC-921</a> fix UT test case in e2mgr to stub time (leftover from review <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493" class="external-link" title="Follow link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493</a>)</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-915" rel="nofollow">RIC-915</a> dms_cli for installing xapp not working (raised by James)</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-905" rel="nofollow">RIC-905</a> new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-901" rel="nofollow">RIC-901</a> new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-896" class="external-link" rel="nofollow">RIC-896</a> xapps sending same msg type and sub id fails - details to be clarified</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-894" class="external-link" rel="nofollow">RIC-894</a> long idle period (days) causes RMR connection breaks</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-864" rel="nofollow">RIC-864</a> xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-857" rel="nofollow">RIC-857</a> sporadically RMR takes multiple minutes before being "ready"</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-852" rel="nofollow">RIC-852</a> Intermittent Issue with E2T: While setting up E2 setup request and response.</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-837" rel="nofollow">RIC-837</a> RMR is not forwarding messages from E2T to E2M</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-835" rel="nofollow">RIC-835</a> → 2021-12-07 no news from Viktor</li><li>fixed:<strong> RIC-991, RIC-989<br/></strong></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">James: updates?</span></span><ol><li><s>2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.</s></li><li><s>2023-09-26: This was presented in TOC (See <a href="https://wiki.o-ran-sc.org/download/attachments/78217260/Pairwise%20Tests%20and%20Lab%20Status.pptx?api=v2" rel="nofollow">link</a>). Cases relevant for near-RT RIC:</s><ol><li><s>ODU-high and near-RT RIC (currently using stub).</s></li><li><s>near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)</s></li><li><s>near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)</s></li><li><s>James will check with Sunil on issues he has with the test cases</s></li><li><s>ArgoCD used by Taiwan lab in some ONAP SMO case and the engineers there where wondering if something similar could be done with OSC.</s></li></ol></li><li><s>2023-10-24</s><ol><li><s>updates from O-RAN f-2-f:</s><ol><li><s>nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)</s></li><li><s>OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.</s><ol><li><s>see demo "oai-osc-ric-demo.mp4" in <a href="https://wiki.o-ran-sc.org/display/EV/Material+for+O-RAN+October+f2f+in+Phoenix" rel="nofollow">link</a> and the demo session recording on the O-RAN web site (thoralf-todo)</s></li><li><s>more discussion coming at the joint OSC/OAI workshop in Boston</s></li></ol></li><li><s>session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.</s></li></ol></li><li><s>OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)</s></li></ol></li><li><s> 2023-11-07</s><ol><li><s>James is working with Taiwan lab on making sure we have good coverage</s></li></ol></li><li>2023-11-21<ol><li>was at OSC-OAI conference</li><li>could start using team accounts to test beds from Colosseum (NU) and ARA</li><li>discussed with Bimo (Taiwan lab) on pair-wise testing</li><li>discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.</li></ol></li><li>2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd"><span style="color: rgb(0,0,0);">Prashant's work in near-RT RIC(subteam-p)</span></span></span><ol><li>2023-08-22, 2023-09-26. 2023-11-07: could not participate</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Sunil updates (subteam-h)?</span></span><ol><li>2023-09-12: can give update next time. Maybe 2 or 3 items to work on.</li><li>2023-11-07: Not in the call today</li><li>2023-11-21: no updates. Difficult to find engineers working on this.</li><li>2024-01-16: <span style="color: rgb(0,0,0);">demo of xApp project additions in I release → Next time</span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">2024-01-16: re-evaluating RIC platform Jira items</span></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Subhash/Naman updates (subteam-s) ?</span></span><ol><li><s>2023-08-29: no news, other than Naman working on the operator implementation.</s></li><li><s>2023-09-12:</s><ol><li><s>We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.</s></li><li><s>Thoralf to figure out a way to start A1 mediator standalone for CI testing</s><ol><li><s>Thoralf sent instructions to John → DONE</s></li></ol></li><li><s>current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.</s></li><li><s>Naman also works on the operator implementation</s></li></ol></li><li><s>2023-09-26: </s><br/><ol><li><s>kubernetes operator new repo needed or not?</s><ol><li><s>xapp deployment → appmgr or ricdms</s></li><li><s>ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.</s></li></ol></li><li><s>What happened to kserve adapter? → Subhash can check.</s></li></ol></li><li><s>2023-11-07</s><ol><li><s>Naman presented his k8s operator work. Naman used Kubebuilder</s></li><li><s>still working on operator to deploy RIC platform</s></li></ol></li><li><s>2023-11-21:</s><ol><li><s>k8s operator commits - needs to be finalized.</s></li></ol></li><li>2023-12-05: Naman gave an update on status of Samsung items</li><li>2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.</li></ol></li><li>Abhijit updates (subteam-ag) ?<ol><li>2023-10-24:<ol><li>Abhijit and James release new base image: <span style="color: rgb(0,0,0);">docker pull <a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a></span><span style="color: rgb(0,0,0);">:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder <a class="confluence-userlink user-mention" data-username="gabhijit" href="https://wiki.o-ran-sc.org/display/~gabhijit" data-linked-resource-id="67535006" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Abhijit Gadgil</a> </span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">no progress in review on the plain helm chart based deployment in <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743</a> → to be merged by <a class="confluence-userlink user-mention" data-username="czichy" href="https://wiki.o-ran-sc.org/display/~czichy" data-linked-resource-id="3604529" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Thoralf Czichy</a> <br/></span></li><li><span style="color: rgb(0,0,0);">1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.</span></li><li><span style="color: rgb(0,0,0);">Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme <em>and</em> confluence.</span></li></ol></li><li><span style="color: rgb(0,0,0);">2024-01-16 No news.</span></li></ol></li><li>Cap Gemini updates (subteam-cg)? <ol><li><span style="color: rgb(0,0,0);">2023-11-07: </span><span style="color: rgb(0,0,0);">after discussions on the topic we would like to proceed with</span><ol><li><p><s>Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.</s></p></li><li><p><s>Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well.</s></p></li><li>discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024</li></ol></li><li><strong>2024-01-16: Ashish <span style="color: rgb(0,0,0);">presented the design of conflict manager, first phase: <a href="https://wiki.o-ran-sc.org/download/attachments/3605124/Conflict_Manager_Phase_1.pdf?api=v2" rel="nofollow">link to slideset</a></span></strong></li></ol></li><li>Himanshu (subteam-gs) would like to work on RIC-963<br/><ol><li class="e24Kjd"><s>2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".</s></li><li class="e24Kjd"><s>2023-11-07: addressing review comments of <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681</a> tomorrow. Then we should be able to merge this.</s></li><li class="e24Kjd"><s>2023-11-21: as discussed in teh beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.</s></li><li class="e24Kjd">2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.</li><li class="e24Kjd"><strong>2024-01-16: </strong>RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.</li></ol></li><li class="e24Kjd">Dhiraj (subteam-r)<br/><ol><li class="e24Kjd">2023-12-05: moved the IPv6 item to J release</li><li class="e24Kjd">2024-01-16: approval for changes to be commited now obtained. IPv6-related commits expected over teh next weeks.</li></ol></li><li class="e24Kjd">Alexandre (subteam-utfpr)<br/><ol><li class="e24Kjd">2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001</li><li class="e24Kjd">2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf</li></ol></li><li>Nokia (subteam-n)<ol><li class="e24Kjd">RIC-997 postponed to J</li></ol></li><li class="e24Kjd">J release<br/><ol><li class="e24Kjd">We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from <a href="https://wiki.o-ran-sc.org/display/RICP/Jira+usage+conventions" rel="nofollow">Jira usage conventions</a>.<ol><li class="e24Kjd">Example Nokia J release: <a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-n-proposal%20or%20labels%20%3D%20subteam-n%20)%20%20and%20fixVersion%20in%20(J)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">link</a></li></ol></li></ol></li></ol><ol><li style="list-style-type: none;"><ol><li class="e24Kjd">input for release candidates: <a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-c%20or%20labels%3Dsubteam-cg)%20%20and%20labels%3D%20movedoutfromH%20%20and%20type%3DEpic%20%20and%20fixVersion%20in%20(H)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">left ov</a><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-cg%20or%20labels%3Dsubteam-r%20or%20labels%3Dsubteam-gs)%20%20and%20labels%3D%20movedoutfromI%20%20and%20type%3DEpic%20%20and%20fixVersion%20in%20(I)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">left overs</a><a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-c%20or%20labels%3Dsubteam-cg)%20%20and%20labels%3D%20movedoutfromH%20%20and%20type%3DEpic%20%20and%20fixVersion%20in%20(H)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">ers</a> and <a href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" class="external-link" rel="nofollow">generally open items</a>, RSAC</li><li class="e24Kjd">Sprint dates<ol><li>TODO - general timeframe: Jan-June 2024</li></ol></li></ol></li></ol><p><br/></p><ol><li>RICAPP agenda: <a href="https://wiki.o-ran-sc.org/display/RICA/RICAPP+Meetings" rel="nofollow">RICAPP Meetings.</a></li></ol><p><br/></p><h1 class="auto-cursor-target" id="Projectmeetings-2023-12-19demomeetinginsteadofthenormalprojectmeeting,sametimeslot"><span style="color: rgb(0,0,0);">2023-12-19 <a href="https://wiki.o-ran-sc.org/display/RICP/2023-12-19+Release+I" rel="nofollow">demo meeting</a> instead of the normal project meeting, same time slot</span></h1><h1 class="auto-cursor-target" id="Projectmeetings-2023-12-05"><span style="color: rgb(0,0,0);">2023-12-05</span></h1><p><span style="color: rgb(0,0,0);">Recording: <a href="https://zoom.us/rec/share/Ra_3205PG0U2lmG5rsY1B1w2ixCgq-o-D2W1h0vhZaSDa8Edq0Xvy6mPOJe729Im.bQp3hawLogj0ctV6" class="external-link" rel="nofollow">link to zoom recording</a> <br/></span></p><ol><li>Every time: Check rule RC-4 (<a href="https://wiki.o-ran-sc.org/display/RICP/Release+criteria+checklist+template" rel="nofollow">link</a>) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. <a class="external-link" href="https://gerrit.o-ran-sc.org/r/q/projects:ric-plt+size:%253E249" rel="nofollow"><strong>link-to-reviews</strong></a> (<a href="https://gerrit-review.googlesource.com/Documentation/user-search.html" class="external-link" rel="nofollow">gerrit filter instructions</a> // <a class="external-link" href="https://bugs.chromium.org/p/gerrit/issues/detail?id=7886" rel="nofollow">gerrit t-shirt-sizing</a>).<ol><li>Last checked on 2023-09-26<ol><li> <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11898" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11898</a> OK (simple alarms, but we created <a href="https://jira.o-ran-sc.org/browse/RIC-1028" class="external-link" rel="nofollow">RIC-1028</a> for a more general test mock framework)</li><li><a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743?usp=search" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743</a> OK, since deployment acts as test</li><li><a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/12025?usp=search" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/12025</a> ok, lots of code, but very generic. Naman will try to add test case</li><li><a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/12032?usp=search" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/12032</a> OK, only go.sum file</li><li><a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11895?usp=search" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11895</a> OK (simple alarms, but we created <a href="https://jira.o-ran-sc.org/browse/RIC-1028" class="external-link" rel="nofollow">RIC-1028</a> for a more general test mock framework)</li></ol></li></ol></li><li>every second time: Review <strong>code coverage stats</strong> and <strong>blocker code smells</strong><ol><li>We take a look at the two links in the beginning of this page: <a href="https://wiki.o-ran-sc.org/display/RICP/Code+coverage+reports" rel="nofollow">Code coverage reports</a>..</li><li>The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)</li><li>Thoralf did this last on 2023-05-23: we did not do this this time</li></ol></li><li>Every time: Check if there are new bug reports in JIRA: <a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=project%20%3D%20RIC%20AND%20type%20%3D%20Bug%20and%20status%20!%3D%20done%20and%20createdDate%20%3E%20%272020-06-24%2000%3A00%27%20ORDER%20BY%20createdDate%20DESC" rel="nofollow">link</a><ol><li><a href="https://jira.o-ran-sc.org/browse/RIC-1025" class="external-link" rel="nofollow">RIC-1025</a> memory leak in routing manager</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1017" class="external-link" rel="nofollow">RIC-1017</a> xapp-frame - xapp-frame may not be able to successfully subscribe to messages</li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1016" class="external-link" rel="nofollow">RIC-1016</a> e2t sctp_params structure may not be initialized properly → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1015" class="external-link" rel="nofollow">RIC-1015</a> e2t too High default message size. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1014" class="external-link" rel="nofollow">RIC-1014</a> e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1013" class="external-link" rel="nofollow">RIC-1013</a> e2t e2term pod does not become ready. Possible stack/heap corruption </p></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1002" class="external-link" rel="nofollow">RIC-1002</a> (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1001" class="external-link" rel="nofollow">RIC-1001</a> <strong>CVE-2023-41627</strong> RMR service should verify route tables - Alexandre will take a look</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-991" class="external-link" rel="nofollow">RIC-991</a> <strong>CVE-2023-40997</strong> RMR related (not a duplicate) - Alexandre will take a look</li><li><span style="color: rgb(0,0,0);"><a href="https://jira.o-ran-sc.org/browse/RIC-989" class="external-link" rel="nofollow">RIC-989</a></span> <strong>CVE-2023-40998</strong> RMR (minor) security issue - Alexandre will take a look</li><li><s><a href="https://jira.o-ran-sc.org/browse/RIC-972" class="external-link" rel="nofollow">RIC-972</a> (Naman) URL for A1 mediator to align with spec. → CLOSED</s></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-965" class="external-link" rel="nofollow">RIC-965</a> RMR wormhole connections uses stale endpoints to make connections </li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-921" rel="nofollow">RIC-921</a> fix UT test case in e2mgr to stub time (leftover from review <a class="external-link" title="Follow link" href="https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493</a>)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-915" class="external-link" rel="nofollow">RIC-915</a> dms_cli for installing xapp not working (raised by James)</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-905" rel="nofollow">RIC-905</a> new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-901" class="external-link" rel="nofollow">RIC-901</a> new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-896" class="external-link" rel="nofollow">RIC-896</a> xapps sending same msg type and sub id fails - details to be clarified</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-894" rel="nofollow">RIC-894</a> long idle period (days) causes RMR connection breaks</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-864" class="external-link" rel="nofollow">RIC-864</a> xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-857" rel="nofollow">RIC-857</a> sporadically RMR takes multiple minutes before being "ready"</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-852" class="external-link" rel="nofollow">RIC-852</a> Intermittent Issue with E2T: While setting up E2 setup request and response.<ol><li>2021-12-21: Trying to get bandwidth for this during F release.</li></ol></li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-837" rel="nofollow">RIC-837</a> RMR is not forwarding messages from E2T to E2M</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-835" class="external-link" rel="nofollow">RIC-835</a> → 2021-12-07 no news from Viktor</li><li>fixed:<strong> <br/></strong></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">James: updates?</span></span><ol><li>2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.</li><li>2023-09-26: This was presented in TOC (See <a href="https://wiki.o-ran-sc.org/download/attachments/78217260/Pairwise%20Tests%20and%20Lab%20Status.pptx?api=v2" rel="nofollow">link</a>). Cases relevant for near-RT RIC:<ol><li>ODU-high and near-RT RIC (currently using stub).</li><li>near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)</li><li>near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)</li><li>James will check with Sunil on issues he has with the test cases</li><li>ArgoCD used by Taiwan lab in some ONAP SMO case and the engineers there where wondering if something similar could be done with OSC.</li></ol></li><li>2023-10-24<ol><li>updates from O-RAN f-2-f:<ol><li>nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)</li><li>OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.<ol><li>see demo "oai-osc-ric-demo.mp4" in <a href="https://wiki.o-ran-sc.org/display/EV/Material+for+O-RAN+October+f2f+in+Phoenix" rel="nofollow">link</a> and the demo session recording on the O-RAN web site (thoralf-todo)</li><li>more discussion coming at the joint OSC/OAI workshop in Boston</li></ol></li><li>session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.</li></ol></li><li>OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)</li></ol></li><li> 2023-11-07<ol><li>James is working with Taiwan lab on making sure we have good coverage</li></ol></li><li>2023-11-21<ol><li>was at OSC-OAI conference</li><li>could start using team accounts to test beds from Colosseum (NU) and ARA</li><li>discussed with Bimo (Taiwan lab) on pair-wise testing</li><li>discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.</li></ol></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd"><span style="color: rgb(0,0,0);">Prashant's work in near-RT RIC(subteam-p)</span></span></span><ol><li>2023-08-22, 2023-09-26. 2023-11-07: could not participate</li><li>2024-01-16</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Sunil updates (subteam-h)?</span></span><ol><li>2023-09-12: can give update next time. Maybe 2 or 3 items to work on.</li><li>2023-11-07: Not in the call today</li><li>2023-11-21: no updates. Difficult to find engineers working on this.</li><li>2024-01-16: no news. Wants to re-valuate tickets (earlier assigned to HCL).</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Subhash/Naman updates (subteam-s) ?</span></span><ol><li>2023-08-29: no news, other than Naman working on the operator implementation.</li><li>2023-09-12:<ol><li>We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.</li><li>Thoralf to figure out a way to start A1 mediator standalone for CI testing<ol><li>Thoralf sent instructions to John → DONE</li></ol></li><li>current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.</li><li>Naman also works on the operator implementation</li></ol></li><li>2023-09-26: <br/><ol><li>kubernetes operator new repo needed or not?<ol><li>xapp deployment → appmgr or ricdms</li><li>ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.</li></ol></li><li>What happened to kserve adapter? → Subhash can check.</li></ol></li><li>2023-11-07<ol><li>Naman presented his k8s operator work. Naman used Kubebuilder</li><li>still working on operator to deploy RIC platform</li></ol></li><li>2023-11-21:<ol><li>k8s operator commits - needs to be finalized.</li></ol></li><li>2023-12-05: Naman gave an update on status of Samsung items</li></ol></li><li>Abhijit updates (subteam-ag) ?<ol><li>2023-10-24:<ol><li>Abhijit and James release new base image: <span style="color: rgb(0,0,0);">docker pull <a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a></span><span style="color: rgb(0,0,0);">:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder <a class="confluence-userlink user-mention" data-username="gabhijit" href="https://wiki.o-ran-sc.org/display/~gabhijit" data-linked-resource-id="67535006" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Abhijit Gadgil</a> </span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">no progress in review on the plain helm chart based deployment in <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743</a> → to be merged by <a class="confluence-userlink user-mention" data-username="czichy" href="https://wiki.o-ran-sc.org/display/~czichy" data-linked-resource-id="3604529" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Thoralf Czichy</a> <br/></span></li><li><span style="color: rgb(0,0,0);"><s>Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it → most assigned to Nokia</s><br/></span></li><li><span style="color: rgb(0,0,0);">1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.</span></li><li><span style="color: rgb(0,0,0);">Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme <em>and</em> confluence.</span></li></ol></li></ol></li><li>Cap Gemini updates (subteam-cg)? <ol><li><span style="color: rgb(0,0,0);">2023-11-07: </span><span style="color: rgb(0,0,0);">after discussions on the topic we would like to proceed with</span><ol><li><p>Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.</p></li><li><p>Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well.</p></li><li>discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024</li><li>TODO-thoralf-to-ask-Gunja-to-present- Thoralf</li></ol></li></ol></li><li>Himanshu (subteam-gs) would like to work on RIC-963<br/><ol><li class="e24Kjd">2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".</li><li class="e24Kjd">2023-11-07: addressing review comments of <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681</a> tomorrow. Then we should be able to merge this.</li><li class="e24Kjd">2023-11-21: as discussed in teh beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.</li><li class="e24Kjd">2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.</li></ol></li><li class="e24Kjd">Dhiraj (subteam-r)<br/><ol><li class="e24Kjd"><s>2023-08-22:</s><ol><li class="e24Kjd"><s>checking compliance/license issues</s></li><li class="e24Kjd"><s>How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).</s></li></ol></li><li class="e24Kjd"><s>2023-08-29:</s><ol><li class="e24Kjd"><s>got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes</s></li></ol></li><li class="e24Kjd"><p><s>2023-11-07</s></p><ol><li class="e24Kjd"><p><s>license topic still be discussed. Was working on an other project for last months</s></p></li></ol></li><li class="e24Kjd">2023-12-05: moved the IPv6 item to J release</li></ol></li><li class="e24Kjd">Alexandre (subteam-utfpr)<br/><ol><li class="e24Kjd">2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001</li><li class="e24Kjd">2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf</li></ol></li><li>Nokia (subteam-n)<ol><li class="e24Kjd">RIC-997 postponed to J</li></ol></li><li class="e24Kjd">Demo<ol><li class="e24Kjd">We will use the project meeting slot for the demos</li><li class="e24Kjd">Naman to demo k8s operator deployment of platform (xapp part already done) and also A1 creating a policy.</li><li class="e24Kjd"><span style="color: rgb(51,153,102);">Adding support for DU in E2T/E2M/RNIB - >thoralf can do if not Gunja.<br/></span></li></ol></li><li class="e24Kjd">I release content<ol><li class="e24Kjd">we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from <a href="https://wiki.o-ran-sc.org/display/RICP/Jira+usage+conventions" rel="nofollow">Jira usage conventions</a>.</li></ol></li></ol><ol><li style="list-style-type: none;"><ol><li class="e24Kjd">input for release candidates: <a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-c%20or%20labels%3Dsubteam-cg)%20%20and%20labels%3D%20movedoutfromH%20%20and%20type%3DEpic%20%20and%20fixVersion%20in%20(H)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">left overs</a> and <a href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" class="external-link" rel="nofollow">generally open items</a>, RSAC</li><li class="e24Kjd">Sprint dates<ol><li>Sprint I release dev sprint 1: Aug-21 to Sep-10</li><li>Sprint I release dev sprint 2: Sep-11 to Oct-1</li><li>Sprint I release dev sprint 3: Oct-2 to Oct-22</li><li>Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)</li><li>Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)</li></ol></li><li>Plan (v03 as of 2023-08-18):<ol><li>I release plan moved to <a href="https://wiki.o-ran-sc.org/display/REL/I+Release#IRelease-Near-Real-timeRANIntelligentControllerPlatform(E2Interface)(RICPLT)" rel="nofollow">I release page</a>.</li><li>Thoralf will start generating images next week (Dec-11 - Dec-13)</li></ol></li></ol></li><li>RICAPP agenda: <a href="https://wiki.o-ran-sc.org/display/RICA/RICAPP+Meetings" rel="nofollow">RICAPP Meetings.</a></li></ol><h1 class="auto-cursor-target" id="Projectmeetings-2023-11-21"><span style="color: rgb(0,0,0);">2023-11-21</span></h1><p><span style="color: rgb(0,0,0);">Recording: <a href="https://zoom.us/rec/share/RHqKsr5w-UtnsPsL2K_SwSNLCdskADl3ZzJgpQIYzOkIE1HaB9X6yUVrZLMbwTA9.PmwTGpIfAt2QewuV" class="external-link" rel="nofollow">link to zoom recording</a><br/></span></p><ol><li>Every time: Check rule RC-4 (<a href="https://wiki.o-ran-sc.org/display/RICP/Release+criteria+checklist+template" rel="nofollow">link</a>) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. <a class="external-link" href="https://gerrit.o-ran-sc.org/r/q/projects:ric-plt+size:%253E249" rel="nofollow"><strong>link-to-reviews</strong></a> (<a class="external-link" href="https://gerrit-review.googlesource.com/Documentation/user-search.html" rel="nofollow">gerrit filter instructions</a> // <a class="external-link" href="https://bugs.chromium.org/p/gerrit/issues/detail?id=7886" rel="nofollow">gerrit t-shirt-sizing</a>).<ol><li>Last checked on 2023-09-26<ol><li> TODO</li></ol></li></ol></li><li>every second time: Review <strong>code coverage stats</strong> and <strong>blocker code smells</strong><ol><li>We take a look at the two links in the beginning of this page: <a href="https://wiki.o-ran-sc.org/display/RICP/Code+coverage+reports" rel="nofollow">Code coverage reports</a>..</li><li>The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)</li><li>Thoralf did this last on 2023-05-23: we did not do this this time</li></ol></li><li>Every time: Check if there are new bug reports in JIRA: <a href="https://jira.o-ran-sc.org/issues/?jql=project%20%3D%20RIC%20AND%20type%20%3D%20Bug%20and%20status%20!%3D%20done%20and%20createdDate%20%3E%20%272020-06-24%2000%3A00%27%20ORDER%20BY%20createdDate%20DESC" class="external-link" rel="nofollow">link</a><ol><li><a href="https://jira.o-ran-sc.org/browse/RIC-1025" class="external-link" rel="nofollow">RIC-1025</a> memory leak in routing manager</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1017" class="external-link" rel="nofollow">RIC-1017</a> xapp-frame - xapp-frame may not be able to successfully subscribe to messages</li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1016" class="external-link" rel="nofollow">RIC-1016</a> e2t sctp_params structure may not be initialized properly → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1015" class="external-link" rel="nofollow">RIC-1015</a> e2t too High default message size. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1014" class="external-link" rel="nofollow">RIC-1014</a> e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1013" class="external-link" rel="nofollow">RIC-1013</a> e2t e2term pod does not become ready. Possible stack/heap corruption </p></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1002" class="external-link" rel="nofollow">RIC-1002</a> (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1001" class="external-link" rel="nofollow">RIC-1001</a> RMR service should verify route tables - Alexandre will take a look</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-991" class="external-link" rel="nofollow">RIC-991</a> RMR related (not a duplicate) - Alexandre will take a look</li><li><span style="color: rgb(0,0,0);"><a href="https://jira.o-ran-sc.org/browse/RIC-989" class="external-link" rel="nofollow">RIC-989</a></span> RMR (minor) security issue - Alexandre will take a look</li><li><s><a href="https://jira.o-ran-sc.org/browse/RIC-972" class="external-link" rel="nofollow">RIC-972</a> (Naman) URL for A1 mediator to align with spec. → CLOSED</s></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-965" class="external-link" rel="nofollow">RIC-965</a> RMR wormhole connections uses stale endpoints to make connections </li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-921" rel="nofollow">RIC-921</a> fix UT test case in e2mgr to stub time (leftover from review <a title="Follow link" class="external-link" href="https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493</a>)</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-915" rel="nofollow">RIC-915</a> dms_cli for installing xapp not working (raised by James)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-905" class="external-link" rel="nofollow">RIC-905</a> new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-901" rel="nofollow">RIC-901</a> new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-896" rel="nofollow">RIC-896</a> xapps sending same msg type and sub id fails - details to be clarified</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-894" rel="nofollow">RIC-894</a> long idle period (days) causes RMR connection breaks</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-864" rel="nofollow">RIC-864</a> xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-857" rel="nofollow">RIC-857</a> sporadically RMR takes multiple minutes before being "ready"</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-852" rel="nofollow">RIC-852</a> Intermittent Issue with E2T: While setting up E2 setup request and response.<ol><li>2021-12-21: Trying to get bandwidth for this during F release.</li></ol></li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-837" rel="nofollow">RIC-837</a> RMR is not forwarding messages from E2T to E2M</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-835" class="external-link" rel="nofollow">RIC-835</a> → 2021-12-07 no news from Viktor</li><li>fixed:<strong> <br/></strong></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">James: updates?</span></span><ol><li><s>2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.</s></li><li><s>2023-09-26: This was presented in TOC (See <a href="https://wiki.o-ran-sc.org/download/attachments/78217260/Pairwise%20Tests%20and%20Lab%20Status.pptx?api=v2" rel="nofollow">link</a>). Cases relevant for near-RT RIC:</s><ol><li><s>ODU-high and near-RT RIC (currently using stub).</s></li><li><s>near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)</s></li><li><s>near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)</s></li><li><s>James will check with Sunil on issues he has with the test cases</s></li><li><s>ArgoCD used by Taiwan lab in some ONAP SMO case and the engineers there where wondering if something similar could be done with OSC.</s></li></ol></li><li><s>2023-10-24</s><ol><li><s>updates from O-RAN f-2-f:</s><ol><li><s>nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)</s></li><li><s>OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.</s><ol><li><s>see demo "oai-osc-ric-demo.mp4" in <a href="https://wiki.o-ran-sc.org/display/EV/Material+for+O-RAN+October+f2f+in+Phoenix" rel="nofollow">link</a> and the demo session recording on the O-RAN web site (thoralf-todo)</s></li><li><s>more discussion coming at the joint OSC/OAI workshop in Boston</s></li></ol></li><li><s>session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.</s></li></ol></li><li><s>OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)</s></li></ol></li><li><s> 2023-11-07</s><ol><li><s>James is working with Taiwan lab on making sure we have good coverage</s></li></ol></li><li>2023-11-21<ol><li>was at OSC-OAI conference</li><li>could start using team accounts to test beds from Colosseum (NU) and ARA</li><li>discussed with Bimo (Taiwan lab) on pair-wise testing</li><li>discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.</li></ol></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd"><span style="color: rgb(0,0,0);">Prashant's work in near-RT RIC(subteam-p)</span></span></span><ol><li>2023-08-22, 2023-09-26. 2023-11-07: could not participate</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Sunil updates (subteam-h)?</span></span><ol><li><s>2023-09-12: can give update next time. Maybe 2 or 3 items to work on.</s></li><li><s>2023-11-07: Not in the call today</s></li><li>2023-11-21: no updates. Difficult to find engineers working on this.</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Subhash/Naman updates (subteam-s) ?</span></span><ol><li><s>2023-08-29: no news, other than Naman working on the operator implementation.</s></li><li><s>2023-09-12:</s><ol><li><s>We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.</s></li><li><s>Thoralf to figure out a way to start A1 mediator standalone for CI testing</s><ol><li><s>Thoralf sent instructions to John → DONE</s></li></ol></li><li><s>current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.</s></li><li><s>Naman also works on the operator implementation</s></li></ol></li><li><s>2023-09-26: </s><br/><ol><li><s>kubernetes operator new repo needed or not?</s><ol><li><s>xapp deployment → appmgr or ricdms</s></li><li><s>ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.</s></li></ol></li><li><s>What happened to kserve adapter? → Subhash can check.</s></li></ol></li><li><s>2023-11-07</s><ol><li><s>Naman presented his k8s operator work. Naman used Kubebuilder</s></li><li><s>still working on operator to deploy RIC platform</s></li></ol></li><li>2023-11-21:<ol><li>k8s operator commits - needs to be finalized.</li></ol></li></ol></li><li>Abhijit updates (subteam-ag) ?<ol><li>2023-10-24:<ol><li>Abhijit and James release new base image: <span style="color: rgb(0,0,0);">docker pull <a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a></span><span style="color: rgb(0,0,0);">:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder <a class="confluence-userlink user-mention" data-username="gabhijit" href="https://wiki.o-ran-sc.org/display/~gabhijit" data-linked-resource-id="67535006" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Abhijit Gadgil</a> </span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">no progress in review on the plain helm chart based deployment in <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743</a> → to be merged by <a class="confluence-userlink user-mention" data-username="czichy" href="https://wiki.o-ran-sc.org/display/~czichy" data-linked-resource-id="3604529" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">Thoralf Czichy</a> <br/></span></li><li><span style="color: rgb(0,0,0);"><s>Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it → most assigned to Nokia</s><br/></span></li><li><span style="color: rgb(0,0,0);">1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.</span></li><li><span style="color: rgb(0,0,0);">Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme <em>and</em> confluence.</span></li></ol></li></ol></li><li>Cap Gemini updates (subteam-cg)? <ol><li><span style="color: rgb(0,0,0);">2023-11-07: </span><span style="color: rgb(0,0,0);">after discussions on the topic we would like to proceed with</span><ol><li><p>Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.</p></li><li><p>Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well.</p></li><li>discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024</li><li>TODO-thoralf-to-ask-Gunja-to-present- Thoralf</li></ol></li></ol></li><li>Himanshu (subteam-gs) would like to work on RIC-963<br/><ol><li class="e24Kjd">2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".</li><li class="e24Kjd">2023-11-07: addressing review comments of <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681</a> tomorrow. Then we should be able to merge this.</li><li class="e24Kjd">2023-11-21: as discussed in the beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.</li></ol></li><li class="e24Kjd">Dhiraj (subteam-r)<br/><ol><li class="e24Kjd"><s>2023-08-22:</s><ol><li class="e24Kjd"><s>checking compliance/license issues</s></li><li class="e24Kjd"><s>How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).</s></li></ol></li><li class="e24Kjd"><s>2023-08-29:</s><ol><li class="e24Kjd"><s>got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes</s></li></ol></li><li class="e24Kjd"><p>2023-11-07</p><ol><li class="e24Kjd"><p>license topic still be discussed. Was working on an other project for last months</p></li></ol></li></ol></li><li class="e24Kjd">Alexandre (subteam-utfpr)<br/><ol><li class="e24Kjd">2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001</li><li class="e24Kjd">2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf</li></ol></li><li>Nokia (subteam-n)<ol><li class="e24Kjd">.RIC-997 likely being postponed.</li></ol></li><li class="e24Kjd">I release content</li></ol><ol><li style="list-style-type: none;"><ol><li class="e24Kjd">we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from <a href="https://wiki.o-ran-sc.org/display/RICP/Jira+usage+conventions" rel="nofollow">Jira usage conventions</a>.</li><li class="e24Kjd">input for release candidates: <a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-c%20or%20labels%3Dsubteam-cg)%20%20and%20labels%3D%20movedoutfromH%20%20and%20type%3DEpic%20%20and%20fixVersion%20in%20(H)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">left overs</a> and <a href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" class="external-link" rel="nofollow">generally open items</a>, RSAC</li><li class="e24Kjd">Sprint dates<ol><li>Sprint I release dev sprint 1: Aug-21 to Sep-10</li><li>Sprint I release dev sprint 2: Sep-11 to Oct-1</li><li>Sprint I release dev sprint 3: Oct-2 to Oct-22</li><li>Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)</li><li>Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)</li></ol></li><li>Plan (v03 as of 2023-08-18):<ol><li>I release plan moved to <a href="https://wiki.o-ran-sc.org/display/REL/I+Release#IRelease-Near-Real-timeRANIntelligentControllerPlatform(E2Interface)(RICPLT)" rel="nofollow">I release page</a>.</li></ol><ol><li><p><br/></p></li></ol></li></ol></li><li>RICAPP agenda: <a href="https://wiki.o-ran-sc.org/display/RICA/RICAPP+Meetings" rel="nofollow">RICAPP Meetings.</a></li></ol><h1 class="auto-cursor-target" id="Projectmeetings-2023-11-07"><span style="color: rgb(0,0,0);">2023-11-07</span></h1><p><span style="color: rgb(0,0,0);">Recording: <a href="https://zoom.us/rec/share/-kiWAMbncsLF-jwPc7E7u3IIiW3bzziEBvSFqgtwEQ_J26KX5JS5hZbg8Oj6b8_7.Raxou644hLE7QJ1B" class="external-link" rel="nofollow">link to zoom recording</a><br/></span></p><ol><li>Every time: Check rule RC-4 (<a href="https://wiki.o-ran-sc.org/display/RICP/Release+criteria+checklist+template" rel="nofollow">link</a>) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. <a class="external-link" href="https://gerrit.o-ran-sc.org/r/q/projects:ric-plt+size:%253E249" rel="nofollow"><strong>link-to-reviews</strong></a> (<a href="https://gerrit-review.googlesource.com/Documentation/user-search.html" class="external-link" rel="nofollow">gerrit filter instructions</a> // <a href="https://bugs.chromium.org/p/gerrit/issues/detail?id=7886" class="external-link" rel="nofollow">gerrit t-shirt-sizing</a>).<ol><li>Last checked on 2023-09-26<br/><ol><li><a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681</a> ok, (not yet merged)</li><li><a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11889" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11889</a> ok. included test cases</li><li><a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/11999" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/11999</a> actually small changes, but as this is generated code, no need for test cases. Actually hand-written code is coming in another review together with test code.</li></ol></li></ol></li><li>every second time: Review <strong>code coverage stats</strong> and <strong>blocker code smells</strong><ol><li>We take a look at the two links in the beginning of this page: <a href="https://wiki.o-ran-sc.org/display/RICP/Code+coverage+reports" rel="nofollow">Code coverage reports</a>..</li><li>The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)</li><li>Thoralf did this last on 2023-05-23: we did not do this this time</li></ol></li><li>Every time: Check if there are new bug reports in JIRA: <a class="external-link" href="https://jira.o-ran-sc.org/issues/?jql=project%20%3D%20RIC%20AND%20type%20%3D%20Bug%20and%20status%20!%3D%20done%20and%20createdDate%20%3E%20%272020-06-24%2000%3A00%27%20ORDER%20BY%20createdDate%20DESC" rel="nofollow">link</a><ol><li><a href="https://jira.o-ran-sc.org/browse/RIC-1017" class="external-link" rel="nofollow">RIC-1017</a> xapp-frame - xapp-frame may not be able to successfully subscribe to messages</li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1016" class="external-link" rel="nofollow">RIC-1016</a> e2t sctp_params structure may not be initialized properly → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1015" class="external-link" rel="nofollow">RIC-1015</a> e2t too High default message size. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1014" class="external-link" rel="nofollow">RIC-1014</a> e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia</p></li><li><p><a href="https://jira.o-ran-sc.org/browse/RIC-1013" class="external-link" rel="nofollow">RIC-1013</a> e2t e2term pod does not become ready. Possible stack/heap corruption </p></li><li><s><a href="https://jira.o-ran-sc.org/browse/RIC-1009" class="external-link" rel="nofollow">RIC-1009</a> E2Mgr API can be improperly invoked → TODO-thoralf-converted-this-to-Epic</s></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1002" class="external-link" rel="nofollow">RIC-1002</a> (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-1001" class="external-link" rel="nofollow">RIC-1001</a> RMR service should verify route tables - Alexandre will take a look</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-991" class="external-link" rel="nofollow">RIC-991</a> RMR related (not a duplicate) - Alexandre will take a look</li><li><span style="color: rgb(0,0,0);"><a href="https://jira.o-ran-sc.org/browse/RIC-989" class="external-link" rel="nofollow">RIC-989</a></span> RMR (minor) security issue - Alexandre will take a look</li><li><s><a href="https://jira.o-ran-sc.org/browse/RIC-972" class="external-link" rel="nofollow">RIC-972</a> (Naman) URL for A1 mediator to align with spec. → CLOSED</s></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-965" class="external-link" rel="nofollow">RIC-965</a> RMR wormhole connections uses stale endpoints to make connections </li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-921" rel="nofollow">RIC-921</a> fix UT test case in e2mgr to stub time (leftover from review <a class="external-link" href="https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493" title="Follow link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493</a>)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-915" class="external-link" rel="nofollow">RIC-915</a> dms_cli for installing xapp not working (raised by James)</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-905" class="external-link" rel="nofollow">RIC-905</a> new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-901" class="external-link" rel="nofollow">RIC-901</a> new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-896" class="external-link" rel="nofollow">RIC-896</a> xapps sending same msg type and sub id fails - details to be clarified</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-894" class="external-link" rel="nofollow">RIC-894</a> long idle period (days) causes RMR connection breaks</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-864" rel="nofollow">RIC-864</a> xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-857" rel="nofollow">RIC-857</a> sporadically RMR takes multiple minutes before being "ready"</li><li><a href="https://jira.o-ran-sc.org/browse/RIC-852" class="external-link" rel="nofollow">RIC-852</a> Intermittent Issue with E2T: While setting up E2 setup request and response.<ol><li>2021-12-21: Trying to get bandwidth for this during F release.</li></ol></li><li><a href="https://jira.o-ran-sc.org/browse/RIC-837" class="external-link" rel="nofollow">RIC-837</a> RMR is not forwarding messages from E2T to E2M</li><li><a class="external-link" href="https://jira.o-ran-sc.org/browse/RIC-835" rel="nofollow">RIC-835</a> → 2021-12-07 no news from Viktor</li><li>fixed:<strong> <s>RIC-972</s><br/></strong></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">James: updates?</span></span><ol><li>2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.</li><li>2023-09-26: This was presented in TOC (See <a href="https://wiki.o-ran-sc.org/download/attachments/78217260/Pairwise%20Tests%20and%20Lab%20Status.pptx?api=v2" rel="nofollow">link</a>). Cases relevant for near-RT RIC:<ol><li>ODU-high and near-RT RIC (currently using stub).</li><li>near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)</li><li>near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)</li><li>James will check with Sunil on issues he has with the test cases</li><li>ArgoCD used by Taiwan lab in some ONAP SMO case and the engineers there where wondering if something similar could be done with OSC.</li></ol></li><li>2023-10-24<ol><li>updates from O-RAN f-2-f:<ol><li>nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)</li><li>OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.<ol><li>see demo "oai-osc-ric-demo.mp4" in <a href="https://wiki.o-ran-sc.org/display/EV/Material+for+O-RAN+October+f2f+in+Phoenix" rel="nofollow">link</a> and the demo session recording on the O-RAN web site (thoralf-todo)</li><li>more discussion coming at the joint OSC/OAI workshop in Boston</li></ol></li><li>session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.</li></ol></li><li>OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)</li></ol></li><li> 2023-11-07<ol><li>James is working with Taiwan lab on making sure we have good coverage</li></ol></li></ol></li><li><span class="ILfuVd"><span class="e24Kjd"><span style="color: rgb(0,0,0);">Prashant's work in near-RT RIC(subteam-p)</span></span></span><ol><li>2023-08-22, 2023-09-26. 2023-11-07: could not participate</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Sunil updates (subteam-h)?</span></span><ol><li>2023-09-12: can give update next time. Maybe 2 or 3 items to work on.</li><li>2023-11-07: Not in the call today</li></ol></li><li><span class="ILfuVd"><span class="e24Kjd">Subhash/Naman updates (subteam-s) ?</span></span><ol><li>2023-08-29: no news, other than Naman working on the operator implementation.</li><li>2023-09-12:<ol><li>We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.</li><li>Thoralf to figure out a way to start A1 mediator standalone for CI testing<ol><li>Thoralf sent instructions to John → DONE</li></ol></li><li>current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.</li><li>Naman also works on the operator implementation</li></ol></li><li>2023-09-26: <br/><ol><li>kubernetes operator new repo needed or not?<ol><li>xapp deployment → appmgr or ricdms</li><li>ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.</li></ol></li><li>What happened to kserve adapter? → Subhash can check.</li></ol></li><li>2023-11-07<ol><li>Naman presented his k8s operator work. Naman used Kubebuilder</li><li>still working on operator to deploy RIC platform</li></ol></li></ol></li><li>Abhijit updates (subteam-ag) ?<ol><li>2023-10-24:<ol><li>Abhijit and James release new base image: <span style="color: rgb(0,0,0);">docker pull <a href="http://nexus3.o-ran-sc.org" class="external-link" rel="nofollow">nexus3.o-ran-sc.org</a></span><span style="color: rgb(0,0,0);">:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0</span><strong><span style="color: rgb(0,0,0);"><br/></span></strong></li><li><span style="color: rgb(0,0,0);">no progress in review on the plain helm chart based deployment in <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743</a> </span></li><li><span style="color: rgb(0,0,0);">Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it.</span></li></ol></li></ol></li><li>Cap Gemini updates (subteam-cg)? <ol><li><strong><span style="color: rgb(0,0,0);">2023-11-07: </span></strong><span style="color: rgb(0,0,0);">after discussions on the topic we would like to proceed with</span><ol><li><p><strong>Phase1: </strong>Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.</p></li><li><p><strong>Phase2: </strong>E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well. TODO-discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation</p></li><li>TODO-thoralf-to-ask-Gunja-to-present</li></ol></li></ol></li><li>Himanshu (subteam-gs) would like to work on RIC-963<br/><ol><li class="e24Kjd">2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".</li><li class="e24Kjd">2023-11-07: addressing review comments of <a href="https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681" class="external-link" rel="nofollow">https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681</a> tomorrow. Then we should be able to merge this.</li></ol></li><li class="e24Kjd">Dhiraj (subteam-r)<br/><ol><li class="e24Kjd">2023-08-22:<ol><li class="e24Kjd">checking compliance/license issues</li><li class="e24Kjd">How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).</li></ol></li><li class="e24Kjd">2023-08-29:<ol><li class="e24Kjd">got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes</li></ol></li><li class="e24Kjd"><p>2023-11-07</p><ol><li class="e24Kjd"><p>license topic still be discussed. Was working on an other project for last months</p></li></ol></li></ol></li><li class="e24Kjd">Alexandre (subteam-utfpr)<br/><ol><li class="e24Kjd">2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001</li><li class="e24Kjd">2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf</li></ol></li><li>Nokia (subteam-n)<ol><li class="e24Kjd">...</li></ol></li><li class="e24Kjd">I release content</li></ol><ol><li style="list-style-type: none;"><ol><li class="e24Kjd">we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from <a href="https://wiki.o-ran-sc.org/display/RICP/Jira+usage+conventions" rel="nofollow">Jira usage conventions</a>.</li><li class="e24Kjd">input for release candidates: <a href="https://jira.o-ran-sc.org/issues/?jql=(labels%20%3D%20subteam-h%20or%20labels%20%3D%20subteam-n%20or%20labels%3Dsubteam-utfpr%20or%20labels%3Dsubteam-ag%20or%20labels%20%3D%20subteam-s%20or%20labels%3D%20subteam-p%20or%20labels%3Dsubteam-c%20or%20labels%3Dsubteam-cg)%20%20and%20labels%3D%20movedoutfromH%20%20and%20type%3DEpic%20%20and%20fixVersion%20in%20(H)%20%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20and%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22" class="external-link" rel="nofollow">left overs</a> and <a href="https://jira.o-ran-sc.org/issues/?jql=((labels%20not%20in%20(subteam-p)%20AND%20labels%20not%20in%20(subteam-cg)%20AND%20labels%20not%20in%20(subteam-ag)%20AND%20labels%20not%20in%20(subteam-h)%20AND%20labels%20not%20in%20(subteam-s)%20AND%20labels%20not%20in%20(subteam-utfpr)%20AND%20labels%20not%20in%20(subteam-n)%20)%20or%20labels%20is%20EMPTY)%20AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20AND%20status%20!%3D%20done%20AND%20type%20%3D%20epic%20and%20fixVersion%20in%20(ZZZ_future)%20ORDER%20BY%20priority%20DESC" class="external-link" rel="nofollow">generally open items</a>, RSAC</li><li class="e24Kjd">Sprint dates<ol><li>Sprint I release dev sprint 1: Aug-21 to Sep-10</li><li>Sprint I release dev sprint 2: Sep-11 to Oct-1</li><li>Sprint I release dev sprint 3: Oct-2 to Oct-22</li><li>Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)</li><li>Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)</li></ol></li><li>Plan (v03 as of 2023-08-18):<ol><li>I release plan moved to <a href="https://wiki.o-ran-sc.org/display/REL/I+Release#IRelease-Near-Real-timeRANIntelligentControllerPlatform(E2Interface)(RICPLT)" rel="nofollow">I release page</a>.</li></ol></li></ol></li><li>RICAPP agenda: <a href="https://wiki.o-ran-sc.org/display/RICA/RICAPP+Meetings" rel="nofollow">RICAPP Meetings.</a></li></ol><h1 class="auto-cursor-target" style="color: rgb(0,0,0);" id="Projectmeetings-Oldermeetingminutes">Older meeting minutes</h1><p class="auto-cursor-target">check from here: <a href="https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20873969">Project meetings (old)</a></p><div><br/></div><div><br/></div>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/display/RICP/Project+meetings">View Online</a>
·
<a href="https://wiki.o-ran-sc.org/pages/diffpagesbyversion.action?pageId=3605124&revisedVersion=742&originalVersion=741">View Changes Online</a>
</div>
</div>Abdul Wahid W2019-07-26T10:19:31ZRe: xApp Framework for Python (xapp-frame-py)steve rattitag:wiki.o-ran-sc.org,2009:comment-116458190-12024-03-26T16:55:57Z2024-03-26T16:55:57Z<div class="feed"> <p>
Comment <strong>added</strong> by <a href=" https://wiki.o-ran-sc.org/display/~steve.ratti
">steve ratti</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px 20px 10px 20px;">
<p>ok thanks let me check it </p>
</div>
<div style="border-bottom: 1px solid #ddd; padding: 17px 20px 7px 20px;">
<strong>In reply to a comment by <a href=" /display/~wahidw
"
class="url fn"
>Abdul Wahid W</a>:</strong><br/>
<p>I think you can refer to the hw-python implementation here - <a class="external-link" href="https://gerrit.o-ran-sc.org/r/gitweb?p=ric-app/hw-python.git;a=summary" rel="nofollow">https://gerrit.o-ran-sc.org/r/gitweb?p=ric-app/hw-python.git;a=summary</a></p><p>More details with <a class="confluence-userlink user-mention" data-username="singh.sunil" href="https://wiki.o-ran-sc.org/display/~singh.sunil" data-linked-resource-id="20874812" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">SUNIL SINGH</a> </p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20873778&focusedCommentId=116458190#comment-116458190">View Online</a>
</div>
</div>steve ratti2024-03-26T16:55:57ZRe: xApp Framework for Python (xapp-frame-py)steve rattitag:wiki.o-ran-sc.org,2009:comment-116458189-12024-03-26T16:49:18Z2024-03-26T16:49:18Z<div class="feed"> <p>
Comment <strong>added</strong> by <a href=" https://wiki.o-ran-sc.org/display/~steve.ratti
">steve ratti</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px 20px 10px 20px;">
<p>hi can you tell how you are using the xapp framework for the customization of xapp</p><p>of is there any tutorial to develop the xapp in python framework </p>
</div>
<div style="border-bottom: 1px solid #ddd; padding: 17px 20px 7px 20px;">
<strong>In reply to a comment by <a href=" /display/~ericcheng09
"
class="url fn"
>imhusky@live.com</a>:</strong><br/>
<p>Hi</p><p>I am building my xapps using this framework and wondering whether xapps could communicate with other components in RIC (subscription manager, routing manager, etc.)? </p><p><br/></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20873778&focusedCommentId=116458189#comment-116458189">View Online</a>
</div>
</div>steve ratti2024-03-26T16:49:18ZRe: xApp Framework for Python (xapp-frame-py)Abdul Wahid Wtag:wiki.o-ran-sc.org,2009:comment-116458186-12024-03-26T14:42:10Z2024-03-26T14:42:10Z<div class="feed"> <p>
Comment <strong>added</strong> by <a href=" https://wiki.o-ran-sc.org/display/~wahidw
">Abdul Wahid W</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px 20px 10px 20px;">
<p>I think you can refer to the hw-python implementation here - <a class="external-link" href="https://gerrit.o-ran-sc.org/r/gitweb?p=ric-app/hw-python.git;a=summary" rel="nofollow">https://gerrit.o-ran-sc.org/r/gitweb?p=ric-app/hw-python.git;a=summary</a></p><p>More details with <a class="confluence-userlink user-mention" data-username="singh.sunil" href="https://wiki.o-ran-sc.org/display/~singh.sunil" data-linked-resource-id="20874812" data-linked-resource-version="1" data-linked-resource-type="userinfo" data-base-url="https://wiki.o-ran-sc.org">SUNIL SINGH</a> </p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20873778&focusedCommentId=116458186#comment-116458186">View Online</a>
</div>
</div>Abdul Wahid W2024-03-26T14:42:10ZRe: xApp Framework for Python (xapp-frame-py)steve rattitag:wiki.o-ran-sc.org,2009:comment-116458178-12024-03-26T11:23:52Z2024-03-26T11:23:52Z<div class="feed"> <p>
Comment <strong>added</strong> by <a href=" https://wiki.o-ran-sc.org/display/~steve.ratti
">steve ratti</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px 20px 10px 20px;">
<p>hi everyine is there any video where i can learn how to developed the xapp in pythin framework</p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20873778&focusedCommentId=116458178#comment-116458178">View Online</a>
</div>
</div>steve ratti2024-03-26T11:23:52ZRe: Introduction and guidesWanda Guotag:wiki.o-ran-sc.org,2009:comment-116457482-12024-03-25T22:02:38Z2024-03-25T22:02:38Z<div class="feed"> <p>
Comment <strong>added</strong> by <a href=" https://wiki.o-ran-sc.org/display/~dustin12138
">Wanda Guo</a>
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px 20px 10px 20px;">
<p>Hi O-RAN SC community, </p><p>I tried to install the near-RT RIC following the latest guide, and I ran into a problem when I ran the script install_k8s_and_helm.sh. </p><p><br/></p><p>Currently, <span style="color: rgb(31,35,40);">the legacy Kubernetes package repositories (</span><code class="notranslate" style=""><a href="http://apt.kubernetes.io" class="external-link" rel="nofollow">apt.kubernetes.io</a></code><span style="color: rgb(31,35,40);"><span> </span>and<span> </span></span><code class="notranslate" style=""><a href="http://yum.kubernetes.io" class="external-link" rel="nofollow">yum.kubernetes.io</a></code><span style="color: rgb(31,35,40);">, also known as<span> </span></span><code class="notranslate" style=""><a href="http://packages.cloud.google.com" class="external-link" rel="nofollow">packages.cloud.google.com</a></code><span style="color: rgb(31,35,40);">) have been shut down (removed) as of 2024-03-04. The link to the announcement is here: <a class="external-link" href="https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/" rel="nofollow">https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/</a>. The old version of Kubernetes used in the script is no longer in the new repo, so I cannot run the provided script without errors, even if I ran their mitigation code. </span><span style="color: rgb(31,35,40);">So, is there a newer version of the installation guide or the script that addresses this problem?</span></p><p><br/></p><p><span style="color: rgb(31,35,40);">Thanks for your help!</span></p><p><br/></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.o-ran-sc.org/display/RICP/Introduction+and+guides?focusedCommentId=116457482#comment-116457482">View Online</a>
</div>
</div>Wanda Guo2024-03-25T22:02:38Z