2017-03-28 12:30:28 +00:00
|
|
|
# osmo_gsm_tester: specifics for running a sysmoBTS
|
|
|
|
#
|
|
|
|
# Copyright (C) 2016-2017 by sysmocom - s.f.m.c. GmbH
|
|
|
|
#
|
|
|
|
# Author: Neels Hofmeyr <neels@hofmeyr.de>
|
|
|
|
#
|
|
|
|
# This program is free software: you can redistribute it and/or modify
|
2017-06-03 07:51:45 +00:00
|
|
|
# it under the terms of the GNU General Public License as
|
2017-03-28 12:30:28 +00:00
|
|
|
# published by the Free Software Foundation, either version 3 of the
|
|
|
|
# License, or (at your option) any later version.
|
|
|
|
#
|
|
|
|
# This program is distributed in the hope that it will be useful,
|
|
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
2017-06-03 07:51:45 +00:00
|
|
|
# GNU General Public License for more details.
|
2017-03-28 12:30:28 +00:00
|
|
|
#
|
2017-06-03 07:51:45 +00:00
|
|
|
# You should have received a copy of the GNU General Public License
|
2017-03-28 12:30:28 +00:00
|
|
|
# along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
2017-04-10 01:45:30 +00:00
|
|
|
import os
|
2017-05-22 18:16:03 +00:00
|
|
|
import pprint
|
2017-04-10 01:45:30 +00:00
|
|
|
from . import log, config, util, template, process
|
2017-03-28 12:30:28 +00:00
|
|
|
|
|
|
|
class SysmoBts(log.Origin):
|
|
|
|
suite_run = None
|
2017-05-18 17:31:44 +00:00
|
|
|
bsc = None
|
2017-03-28 12:30:28 +00:00
|
|
|
run_dir = None
|
2017-04-10 01:45:30 +00:00
|
|
|
inst = None
|
|
|
|
remote_inst = None
|
|
|
|
remote_env = None
|
|
|
|
remote_dir = None
|
|
|
|
|
|
|
|
REMOTE_DIR = '/osmo-gsm-tester'
|
|
|
|
BTS_SYSMO_BIN = 'osmo-bts-sysmo'
|
|
|
|
BTS_SYSMO_CFG = 'osmo-bts-sysmo.cfg'
|
2017-03-28 12:30:28 +00:00
|
|
|
|
|
|
|
def __init__(self, suite_run, conf):
|
fix and refactor logging: drop 'with', simplify
With the recent fix of the junit report related issues, another issue arose:
the 'with log.Origin' was changed to disallow __enter__ing an object twice to
fix problems, now still code would fail because it tries to do 'with' on the
same object twice. The only reason is to ensure that logging is associated with
a given object. Instead of complicating even more, implement differently.
Refactor logging to simplify use: drop the 'with Origin' style completely, and
instead use the python stack to determine which objects are created by which,
and which object to associate a log statement with.
The new way: we rely on the convention that each class instance has a local
'self' referencing the object instance. If we need to find an origin as a new
object's parent, or to associate a log message with, we traverse each stack
frame, fetching the first local 'self' object that is a log.Origin class
instance.
How to use:
Simply call log.log() anywhere, and it finds an Origin object to log for, from
the stack. Alternatively call self.log() for any Origin() object to skip the
lookup.
Create classes as child class of log.Origin and make sure to call
super().__init__(category, name). This constructor will magically find a parent
Origin on the stack.
When an exception happens, we first escalate the exception up through call
scopes to where ever it is handled by log.log_exn(). This then finds an Origin
object in the traceback's stack frames, no need to nest in 'with' scopes.
Hence the 'with log.Origin' now "happens implicitly", we can write pure natural
python code, no more hassles with scope ordering.
Furthermore, any frame can place additional logging information in a frame by
calling log.ctx(). This is automatically inserted in the ancestry associated
with a log statement / exception.
Change-Id: I5f9b53150f2bb6fa9d63ce27f0806f0ca6a45e90
2017-06-09 23:18:27 +00:00
|
|
|
super().__init__(log.C_RUN, self.BTS_SYSMO_BIN)
|
2017-03-28 12:30:28 +00:00
|
|
|
self.suite_run = suite_run
|
|
|
|
self.conf = conf
|
2017-04-10 01:45:30 +00:00
|
|
|
self.remote_env = {}
|
2017-04-28 14:13:03 +00:00
|
|
|
self.remote_user = 'root'
|
2017-03-28 12:30:28 +00:00
|
|
|
|
|
|
|
def start(self):
|
fix and refactor logging: drop 'with', simplify
With the recent fix of the junit report related issues, another issue arose:
the 'with log.Origin' was changed to disallow __enter__ing an object twice to
fix problems, now still code would fail because it tries to do 'with' on the
same object twice. The only reason is to ensure that logging is associated with
a given object. Instead of complicating even more, implement differently.
Refactor logging to simplify use: drop the 'with Origin' style completely, and
instead use the python stack to determine which objects are created by which,
and which object to associate a log statement with.
The new way: we rely on the convention that each class instance has a local
'self' referencing the object instance. If we need to find an origin as a new
object's parent, or to associate a log message with, we traverse each stack
frame, fetching the first local 'self' object that is a log.Origin class
instance.
How to use:
Simply call log.log() anywhere, and it finds an Origin object to log for, from
the stack. Alternatively call self.log() for any Origin() object to skip the
lookup.
Create classes as child class of log.Origin and make sure to call
super().__init__(category, name). This constructor will magically find a parent
Origin on the stack.
When an exception happens, we first escalate the exception up through call
scopes to where ever it is handled by log.log_exn(). This then finds an Origin
object in the traceback's stack frames, no need to nest in 'with' scopes.
Hence the 'with log.Origin' now "happens implicitly", we can write pure natural
python code, no more hassles with scope ordering.
Furthermore, any frame can place additional logging information in a frame by
calling log.ctx(). This is automatically inserted in the ancestry associated
with a log statement / exception.
Change-Id: I5f9b53150f2bb6fa9d63ce27f0806f0ca6a45e90
2017-06-09 23:18:27 +00:00
|
|
|
if self.bsc is None:
|
|
|
|
raise RuntimeError('BTS needs to be added to a BSC or NITB before it can be started')
|
|
|
|
log.log('Starting sysmoBTS to connect to', self.bsc)
|
|
|
|
self.run_dir = util.Dir(self.suite_run.trial.get_run_dir().new_dir(self.name()))
|
|
|
|
self.configure()
|
|
|
|
|
|
|
|
self.inst = util.Dir(os.path.abspath(self.suite_run.trial.get_inst(SysmoBts.BTS_SYSMO_BIN)))
|
|
|
|
lib = self.inst.child('lib')
|
|
|
|
if not os.path.isdir(lib):
|
|
|
|
raise log.Error('No lib/ in', self.inst)
|
|
|
|
if not self.inst.isfile('bin', SysmoBts.BTS_SYSMO_BIN):
|
|
|
|
raise log.Error('No osmo-bts-sysmo binary in', self.inst)
|
|
|
|
|
|
|
|
self.remote_dir = util.Dir(SysmoBts.REMOTE_DIR)
|
|
|
|
self.remote_inst = util.Dir(self.remote_dir.child(os.path.basename(str(self.inst))))
|
|
|
|
|
|
|
|
self.run_remote('rm-remote-dir', ('test', '!', '-d', SysmoBts.REMOTE_DIR, '||', 'rm', '-rf', SysmoBts.REMOTE_DIR))
|
|
|
|
self.run_remote('mk-remote-dir', ('mkdir', '-p', SysmoBts.REMOTE_DIR))
|
|
|
|
self.run_local('scp-inst-to-sysmobts',
|
|
|
|
('scp', '-r', str(self.inst), '%s@%s:%s' % (self.remote_user, self.remote_addr(), str(self.remote_inst))))
|
|
|
|
|
|
|
|
remote_run_dir = self.remote_dir.child(SysmoBts.BTS_SYSMO_BIN)
|
|
|
|
self.run_remote('mk-remote-run-dir', ('mkdir', '-p', remote_run_dir))
|
|
|
|
|
|
|
|
remote_config_file = self.remote_dir.child(SysmoBts.BTS_SYSMO_CFG)
|
|
|
|
self.run_local('scp-cfg-to-sysmobts',
|
|
|
|
('scp', '-r', self.config_file, '%s@%s:%s' % (self.remote_user, self.remote_addr(), remote_config_file)))
|
|
|
|
|
|
|
|
self.run_remote('reload-dsp-firmware', ('/bin/sh', '-c', '"cat /lib/firmware/sysmobts-v?.bit > /dev/fpgadl_par0 ; cat /lib/firmware/sysmobts-v?.out > /dev/dspdl_dm644x_0"'))
|
|
|
|
|
|
|
|
remote_lib = self.remote_inst.child('lib')
|
|
|
|
remote_binary = self.remote_inst.child('bin', 'osmo-bts-sysmo')
|
|
|
|
self.launch_remote('osmo-bts-sysmo',
|
|
|
|
('LD_LIBRARY_PATH=%s' % remote_lib,
|
|
|
|
remote_binary, '-c', remote_config_file, '-r', '1',
|
|
|
|
'-i', self.bsc.addr()),
|
|
|
|
remote_cwd=remote_run_dir)
|
2017-04-10 01:45:30 +00:00
|
|
|
|
|
|
|
def _process_remote(self, name, popen_args, remote_cwd=None):
|
|
|
|
run_dir = self.run_dir.new_dir(name)
|
2017-05-22 17:58:41 +00:00
|
|
|
return process.RemoteProcess(name, run_dir, self.remote_user, self.remote_addr(), remote_cwd,
|
2017-04-10 01:45:30 +00:00
|
|
|
popen_args)
|
|
|
|
|
|
|
|
def run_remote(self, name, popen_args, remote_cwd=None):
|
|
|
|
proc = self._process_remote(name, popen_args, remote_cwd)
|
|
|
|
proc.launch()
|
|
|
|
proc.wait()
|
|
|
|
if proc.result != 0:
|
fix and refactor logging: drop 'with', simplify
With the recent fix of the junit report related issues, another issue arose:
the 'with log.Origin' was changed to disallow __enter__ing an object twice to
fix problems, now still code would fail because it tries to do 'with' on the
same object twice. The only reason is to ensure that logging is associated with
a given object. Instead of complicating even more, implement differently.
Refactor logging to simplify use: drop the 'with Origin' style completely, and
instead use the python stack to determine which objects are created by which,
and which object to associate a log statement with.
The new way: we rely on the convention that each class instance has a local
'self' referencing the object instance. If we need to find an origin as a new
object's parent, or to associate a log message with, we traverse each stack
frame, fetching the first local 'self' object that is a log.Origin class
instance.
How to use:
Simply call log.log() anywhere, and it finds an Origin object to log for, from
the stack. Alternatively call self.log() for any Origin() object to skip the
lookup.
Create classes as child class of log.Origin and make sure to call
super().__init__(category, name). This constructor will magically find a parent
Origin on the stack.
When an exception happens, we first escalate the exception up through call
scopes to where ever it is handled by log.log_exn(). This then finds an Origin
object in the traceback's stack frames, no need to nest in 'with' scopes.
Hence the 'with log.Origin' now "happens implicitly", we can write pure natural
python code, no more hassles with scope ordering.
Furthermore, any frame can place additional logging information in a frame by
calling log.ctx(). This is automatically inserted in the ancestry associated
with a log statement / exception.
Change-Id: I5f9b53150f2bb6fa9d63ce27f0806f0ca6a45e90
2017-06-09 23:18:27 +00:00
|
|
|
log.ctx(proc)
|
|
|
|
raise log.Error('Exited in error')
|
2017-04-10 01:45:30 +00:00
|
|
|
|
|
|
|
def launch_remote(self, name, popen_args, remote_cwd=None):
|
|
|
|
proc = self._process_remote(name, popen_args, remote_cwd)
|
|
|
|
self.suite_run.remember_to_stop(proc)
|
|
|
|
proc.launch()
|
|
|
|
|
|
|
|
def run_local(self, name, popen_args):
|
|
|
|
run_dir = self.run_dir.new_dir(name)
|
|
|
|
proc = process.Process(name, run_dir, popen_args)
|
|
|
|
proc.launch()
|
|
|
|
proc.wait()
|
|
|
|
if proc.result != 0:
|
fix and refactor logging: drop 'with', simplify
With the recent fix of the junit report related issues, another issue arose:
the 'with log.Origin' was changed to disallow __enter__ing an object twice to
fix problems, now still code would fail because it tries to do 'with' on the
same object twice. The only reason is to ensure that logging is associated with
a given object. Instead of complicating even more, implement differently.
Refactor logging to simplify use: drop the 'with Origin' style completely, and
instead use the python stack to determine which objects are created by which,
and which object to associate a log statement with.
The new way: we rely on the convention that each class instance has a local
'self' referencing the object instance. If we need to find an origin as a new
object's parent, or to associate a log message with, we traverse each stack
frame, fetching the first local 'self' object that is a log.Origin class
instance.
How to use:
Simply call log.log() anywhere, and it finds an Origin object to log for, from
the stack. Alternatively call self.log() for any Origin() object to skip the
lookup.
Create classes as child class of log.Origin and make sure to call
super().__init__(category, name). This constructor will magically find a parent
Origin on the stack.
When an exception happens, we first escalate the exception up through call
scopes to where ever it is handled by log.log_exn(). This then finds an Origin
object in the traceback's stack frames, no need to nest in 'with' scopes.
Hence the 'with log.Origin' now "happens implicitly", we can write pure natural
python code, no more hassles with scope ordering.
Furthermore, any frame can place additional logging information in a frame by
calling log.ctx(). This is automatically inserted in the ancestry associated
with a log statement / exception.
Change-Id: I5f9b53150f2bb6fa9d63ce27f0806f0ca6a45e90
2017-06-09 23:18:27 +00:00
|
|
|
log.ctx(proc)
|
|
|
|
raise log.Error('Exited in error')
|
2017-03-28 12:30:28 +00:00
|
|
|
|
2017-05-22 17:58:41 +00:00
|
|
|
def remote_addr(self):
|
|
|
|
return self.conf.get('addr')
|
|
|
|
|
2017-03-28 12:30:28 +00:00
|
|
|
def configure(self):
|
2017-05-18 17:31:44 +00:00
|
|
|
if self.bsc is None:
|
|
|
|
raise RuntimeError('BTS needs to be added to a BSC or NITB before it can be configured')
|
2017-04-10 01:45:30 +00:00
|
|
|
|
|
|
|
self.config_file = self.run_dir.new_file(SysmoBts.BTS_SYSMO_CFG)
|
2017-03-28 12:30:28 +00:00
|
|
|
self.dbg(config_file=self.config_file)
|
|
|
|
|
|
|
|
values = { 'osmo_bts_sysmo': config.get_defaults('osmo_bts_sysmo') }
|
|
|
|
config.overlay(values, self.suite_run.config())
|
2017-05-18 17:31:44 +00:00
|
|
|
config.overlay(values, { 'osmo_bts_sysmo': { 'oml_remote_ip': self.bsc.addr() } })
|
2017-03-28 12:30:28 +00:00
|
|
|
config.overlay(values, { 'osmo_bts_sysmo': self.conf })
|
2017-05-22 18:16:03 +00:00
|
|
|
|
|
|
|
self.dbg('SYSMOBTS CONFIG:\n' + pprint.pformat(values))
|
2017-03-28 12:30:28 +00:00
|
|
|
|
|
|
|
with open(self.config_file, 'w') as f:
|
2017-04-10 01:45:30 +00:00
|
|
|
r = template.render(SysmoBts.BTS_SYSMO_CFG, values)
|
2017-03-28 12:30:28 +00:00
|
|
|
self.dbg(r)
|
|
|
|
f.write(r)
|
|
|
|
|
2017-05-18 17:31:44 +00:00
|
|
|
def conf_for_bsc(self):
|
|
|
|
values = config.get_defaults('bsc_bts')
|
2017-03-28 12:30:28 +00:00
|
|
|
config.overlay(values, config.get_defaults('osmo_bts_sysmo'))
|
|
|
|
config.overlay(values, self.conf)
|
|
|
|
self.dbg(conf=values)
|
|
|
|
return values
|
|
|
|
|
2017-05-18 17:31:44 +00:00
|
|
|
def set_bsc(self, bsc):
|
|
|
|
self.bsc = bsc
|
2017-03-28 12:30:28 +00:00
|
|
|
|
|
|
|
# vim: expandtab tabstop=4 shiftwidth=4
|