Thursday, 2023-10-05

@dingo0:matrix.orgHi arneme worker nodes boot and install from the master controller node via netboot, that being said you would need to deploy AIO-DUPLEX02:40
@dingo0:matrix.orgwe always follwed https://docs.starlingx.io/r/stx.8.0/deploy/kubernetes/deployment-options.html02:40
@dingo0:matrix.org * we always followed https://docs.starlingx.io/r/stx.8.0/deploy/kubernetes/deployment-options.html02:40
@dingo0:matrix.orgbeing your a telecom, i would become familiar with the aio-duplex and the standard methods. while aio sounds nice, simplex is not something i would recommend for a production telecom environment, maybe lab testing however it is limiting in deployment options. Its best in my opinion to understand both and the flexibilities of each02:43
@dingo0:matrix.orgif you envision growing this stack to work in a 5G environment which it will do quite nicely regular is most likely the path you will want to pursue 02:45
@scott.little:matrix.org> <@brunomuniz:matrix.org> Now that we merged the commits into the `r/stx.8.0`, is there a manual process that needs to happen so the mirror is updated?17:44
Are you saying your changes aren't reflected in the Sept 30 build? https://mirror.starlingx.windriver.com/mirror/starlingx/rc/8.0/debian/monolithic/latest_build/
@scott.little:matrix.org> <@scott.little:matrix.org> Are you saying your changes aren't reflected in the Sept 30 build?   https://mirror.starlingx.windriver.com/mirror/starlingx/rc/8.0/debian/monolithic/latest_build/17:47
If you were expecting to see your changes under https://mirror.starlingx.windriver.com/mirror/starlingx/release/8.0.0/debian/monolithic/ ... then no... we'd have to decide as a community if it's worth creating a 8.0.1 or 8.1.0 release.
@brunomuniz:matrix.orgWell, I can test it in a fresh installation, but if we can trust the date of the file I'd say that my changes are not there. They merged on September 12 and the date from the file shows May 20 on the mirror.17:53
@scott.little:matrix.org> <@brunomuniz:matrix.org> Well, I can test it in a fresh installation, but if we can trust the date of the file I'd say that my changes are not there. They merged on September 12 and the date from the file shows May 20 on the mirror.17:58
hmmm, the latest build link didn't update despite the green build. While I investigate that, you can try ... https://mirror.starlingx.windriver.com/mirror/starlingx/rc/8.0/debian/monolithic/20230930T060059Z/
@scott.little:matrix.org> <@scott.little:matrix.org> hmmm, the latest build link didn't update despite the green build.   While I investigate that, you can try ... https://mirror.starlingx.windriver.com/mirror/starlingx/rc/8.0/debian/monolithic/20230930T060059Z/18:03
docker images failed to build ... https://mirror.starlingx.windriver.com/mirror/starlingx/rc/8.0/debian/monolithic/20230930T060059Z/logs/build-docker-images-stable.log.txt
@scott.little:matrix.org> <@scott.little:matrix.org> docker images failed to build ...  https://mirror.starlingx.windriver.com/mirror/starlingx/rc/8.0/debian/monolithic/20230930T060059Z/logs/build-docker-images-stable.log.txt18:03
Step 8/24 : RUN apt-get -y install snmp snmpd snmptrapd libpython2.7 python3 python3-dev python3-setuptools python-is-python3 postgresql-13 libsnmp-dev libjson-c-dev gcc make uuid-dev
@scott.little:matrix.orgUnable to locate package libpython2.718:04
@scott.little:matrix.org Failed to build stx-fm-subagent... Aborting18:04
@brunomuniz:matrix.org> <@scott.little:matrix.org> If you were expecting to see your changes under https://mirror.starlingx.windriver.com/mirror/starlingx/release/8.0.0/debian/monolithic/ ... then no... we'd have to decide as a community if it's worth creating a 8.0.1 or 8.1.0 release.18:37
That's also a question I have. Is there anything that triggers this process of analysis if a patch should be released (like the commit itself to the branch of a supported version)?
Or should someone make a case for a new patch release (on the Community call, for example)?

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!