Cellular Network Infrastructure » OsmoMGW

I have replaced state.in_stream.err_ts_counter and state.out_stream.err_ts_counter with libosmocore counters. There are still a couple more counters I think.

We have an approach for libosmocore counters: https://gerrit.osmocom.org/#/c/7396/ but we agreed not to merge it. We will go for rate counters instead that are much better alternative and also have better control interface support.

There is now an alternate patch that uses libosmocore rate counters:
https://gerrit.osmocom.org/7555 stats: use libosmocore rate counter for in/out_stream.err_ts_counter

Unfortunately the patch got reverted.

https://gerrit.osmocom.org/7891
https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/osmo-mgw/xUbuntu_17.04/i586

When looking at the OBS log I can see that there is some unexpected output. We need to check whats behind this and resubmit the patch when the error has been found.

lynxis: How can I retrieve the log from the build failure, I only added the link to the top build to the ticket. In order to pinpoint the problem, I need the logtext form the failure situation.

dexter: I've created a 32bit lxc container to test it.

The build problem under OBS was most likely a problem an integer size problem on the 32-bit build. I managed to reproduce the faulure under an 32 bit debian VM and fixed it. Here is the new version of the patch:

https://gerrit.osmocom.org/8086 stats: use libosmocore rate counter for in/out_stream.err_ts_counter

I have now replaced the counters that relate to packet/byte counting. See also:

https://gerrit.osmocom.org/#/c/osmo-mgw/+/9837 stats: replace packet statistic counters with libosmocore rate counters

As far as I can see we have now joined all relevant counters inside a rate counter group. Whats left is struct mgcp_conn_rtp.osmux.stats. I would suggest to fix this when osmux support is re-introduced. Until now this would only increase the confusion about osmux.