osmo-gsm-manuals[master]: Describe how to run multiple instances of osmo-nitb and osmo...

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.

Neels Hofmeyr gerrit-no-reply at lists.osmocom.org
Sun Dec 25 01:17:11 UTC 2016


Patch Set 1: Code-Review-1

(16 comments)

Apologies, I'm very nitpicky on docs and English. I find that it's written quite well, but I still had a lot of two cents to add. It might have been faster to just edit myself...

https://gerrit.osmocom.org/#/c/1497/1/OsmoBTS/chapters/configuration.adoc
File OsmoBTS/chapters/configuration.adoc:

Line 186: It is possible to run multiple instances of *osmo-bts* on one and the same
we usually mark binaries with backticks in the manuals

  `osmo-bts`

though this isn't really a binary (would be `osmo-bts-foo`). So actually I guess we'd write

  OsmoBTS

instead.


Line 190: Since usually a BTS instance comes included with its individual PCU instance,
included is a bit misleading. maybe like this?

  Since usually a BTS instance runs in conjunction with a dedicated PCU instance,


Line 191: the socket-path between PCU and BTS has to be individualized as well. It is
The English don't use word-joining or wordjoining like Germans do. Rather say

  socket path

Instead of "individualized...as well" I'd say

  has to be distinguished between the two running instances.


Line 201: The VTY can be bound to a free ip-address from the loopback range:
drop the hyphen, and maybe IP should be capitalized?

  IP address

and maybe tweak as

  can be bound to any IP address available on the system,
  e.g. to a free IP address from the loopback range:


https://gerrit.osmocom.org/#/c/1497/1/OsmoNITB/chapters/running.adoc
File OsmoNITB/chapters/running.adoc:

Line 65: Running multiple instances of *osmo-nitb* is possible if all interfaces (vty,
backtick

  `osmo-nitb`

Capitalize "VTY" and "OML"?


Line 66: oml) are separated using the appropriate configuration options. The ip based
"IP" ?


Line 68: processes, the user has to bind those services to specific but different 
2x whitespace errors at end of line


Line 69: ip-addresses.
IP addresses


Line 71: The VTY and the control interface can be bind to ip-addresses from the loopback
"For example,..." / "bound" / "IP addresses"


Line 74: .Example: Binding VTY and control interface to a specific ip-address
IP address


Line 82: The OML interface also needs be separated by binding it to different ip
"needs to be" / "IP"


Line 84: address range here since the address we binding on has to be reachable (from
rather

  Usually, it is not possible [...] since the OML interface needs to be reachable by an external BTS.

(with osmo-bts-trx or on a sysmoBTS NITB config, it is quite possible to run both osmo-bts and osmo-nitb on the same box.)


Line 85: outside) to the bts. If only one ethernet interface is available, subdevices
a rare case where the English do hyphenate:

  sub-devices

...why do I know stuff like this !?!?


Line 86: with different ip addresses can be created.
IP


Line 88: .Example: Binding OML to a specific ip-address
IP address


Line 94: NOTE: Depending on the application it is necessary to have different ARFCN,
comma after 'application' / include the word 'settings' somewhere, e.g. at the end of the sentence.


-- 
To view, visit https://gerrit.osmocom.org/1497
To unsubscribe, visit https://gerrit.osmocom.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I69adeef85adda6f08b31b7d176f51e16968c1435
Gerrit-PatchSet: 1
Gerrit-Project: osmo-gsm-manuals
Gerrit-Branch: master
Gerrit-Owner: dexter <pmaier at sysmocom.de>
Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Gerrit-HasComments: Yes



More information about the gerrit-log mailing list