Feature #2616
closedUpdate Prod and RnD sysmobts setups to 201705-testing
100%
Description
Nowadays the sysmobts in Rnd and the one in Prod setups of osmo-gsm-tester are running an old 201310. They should be re-flashed to use a new 201705-testing instead. It's better to do it once we move current 201705-nightly to testing because then we introduce the "gnutls" dependency to libosmocore and this way the SDK we install will already contain it in case we need it in the future.
Steps:
- Download latest 201705-testing image
- Flash it
- Configure it: look at steps in osmo-gsm-tester manual and wiki pages containing information about RnD and Prod setup details.
- Update the SDK in deb9build:/opt/poky There is already an ansible receipt for this (ask lynxis)
- Update contrib/jenkins-build-osmo-*-sysmo.sh in osmo-gsm-tester git repository to point to the new SDK. Maybe a good idea to have a symlink "latest" which points to latest version and use that one?
Updated by neels over 6 years ago
- Priority changed from Normal to High
since 201705 seems to be the version we want everyone to use, I guess it would be good to test this instead of 201310, and the prio is slightly raised.
Updated by laforge over 6 years ago
Hi Pau,
On Mon, Nov 06, 2017 at 03:05:02PM +0000, pespin [REDMINE] wrote:
Feature #2616: Update Prod and RnD sysmobts setups to 201705-testing
thanks for creating the ticket. Please try to make use of roh if you think
it is useful to you. In the end, updating a sysmoBTS is something he can for sure
do, while he cannot help you mcch with develpoment. So every hour you can spend
more on R&D tasks rather than updating BTSs is helping us. It's up to you,
if you think it makes sense.
Updated by pespin over 6 years ago
- Assignee changed from 55360 to roh
I think it makes sense for him to do it also because then we give somebody else than me the chance to setup/use/test the 201705 image and provide feedback on issues that I didn't see while preparing the new release.
roh I assign it to you, but we can discuss it if you need any help or have other stuff to do.
Updated by roh about 6 years ago
- removed the 1002 from the production tester temporarily
- flashed it with https://feeds.sysmocom.de/generic/sysmobts-v2/201705-testing/images/sysmobts-v2/sysmocom-core-image-sysmobts-v2-20180301172422.rootfs.ubi
- masking: systemctl mask osmo-nitb osmo-bts-sysmo osmo-pcu sysmobts-mgr
- configured it to the same fixed ip as before.
- placed it back in the tester.
- replaced the known ssh key for the bts on the tester.
next is the rnd system
Updated by roh about 6 years ago
same for the rnd system:
- removed
- flashed
- masked services
- fix ip config
- enable core dumps (on the prod. one too)
- placed back
- fixed ssh access.
about the buildsystem: i think i do not have access to those or know their setup. maybe its easier for you to do the updates there (SDK)
please test if everything works as expected.
Updated by pespin about 6 years ago
- Assignee changed from roh to lynxis
Assigning to lynxis as he's taking care of setting up the SDK with ansible. Have a look at verify-build-sdk job in sysmocom's jenkins to see how to download latest SDk available.
Updated by lynxis about 6 years ago
- Status changed from New to Resolved
- Assignee changed from lynxis to pespin
- % Done changed from 0 to 100
https://gerrit.osmocom.org/#/c/7124/ jenkins: use env POKY_VERSION POKY_PATH to find poky
https://gerrit.osmocom.org/#/c/7126/ jenkins: update poky version 2.3.2
I've also temporally updated the jenkins jobs using sed, so they are now working.
