Use the full path to shrink-pdfs.sh, so it works as expected when the
symlinks are not present. This is how pysim uses the publish/shrink
targets.
Fix for:
build/shrink-pdfs.sh _build/latex/osmopysim-usermanual.pdf
make: build/shrink-pdfs.sh: Command not found
Related: SYS#6380
Change-Id: Iba6e0e4932741adcb9e54e54eb7774716fb2e244
Group upload and publish closer together by moving the clean targets to
the bottom.
Related: SYS#6380
Change-Id: Id8b6ead89a2aeba28e9c55bcfde6564376e8418a
Describe what upload and publish do, it's not clear from the name of
these make targets.
Related: SYS#6380
Change-Id: Ic2ab9df2192912d20ede0241abe01e8d26a9afcc
Add a custom graphviz-filter.conf, so asciidoc instructs graphviz to
generate svgs.
Related: SYS#6380
Change-Id: Iee54012c41f554608b0915d707f7cf64bfbdc418
Generate svgs instead of pngs. Vector graphics have smaller file size
and don't look blurry when zooming into them.
Related: SYS#6380
Change-Id: I24f345a19adbc5abe41737233f89916996569ea8
Don't have a default value for OSMO_REPOSITORY, as this leads to manuals
getting uploaded to the wrong directory (publish) target and installed
to the wrong directory (install, uninstall).
Add checks to ensure the variable is set before using it in install and
uninstall.
Related: OS#5902
Change-Id: Ie21d58dd57a893a83f566eea464ab3eec82b67a4
Don't upload the manuals for master to "latest" anymore, this is
confusing given that we also refer to the most recent release as
"latest". Add the "master" directory to prepare a directory structure
where we can have manuals for each release:
osmo-hlr/
osmo-hlr/master/
osmo-hlr/master/osmohlr-usermanual.pdf
osmo-hlr/master/osmohlr-vty-reference.pdf
Related: OS#5902
Change-Id: Id090422afbd7b91ac78cc30e19372ac1c828cb6b
Add an editorconfig file so editors can figure out that the *.inc files
should be indented with tabs. At least neovim would use spaces
otherwise.
Change-Id: I93f8fa0c1f2721d12183f33f4a14e13b2deed80b
Add passage explaining basic visualisation of stat and rate counter items
with Netdata so user can start utilizing them without any special
configuration.
Related: OS#5671
Change-Id: I124503c3707bbe005abbfb4245abe2829c6ff57c
The files gb-nsw-{configuration-timer,configuration,maintenance} were
not actually chapters, but sub-chapters or sub-sub-chapters. This
breaks our general idea that all of those files are top-level chapters.
It also breaks asciidoc validation on Debian 11:
asciidoc: WARNING: gb-ns2-configuration.adoc: line 1: section title out of sequence: expected level 1, got level 2
asciidoc: WARNING: gb-ns2-maintenance.adoc: line 6: section title out of sequence: expected level 2, got level 3
the only place where they were used was the osmo-gbproxy manual, and
there in the exact sequenc in which I now merged them over here.
Change-Id: I3c618e5af61b376435f400ef9c64245cec2f9b73
... this can be included from the various user manuals to insert some
general language about the systemd service units we ship, and a few key
systemd commands to get users started.
Change-Id: I8b04047cbc4097676d69fad794bb3139c05a4a5f
Copied from osmo-bsc.git/doc/manuals/chapters/mgwpool.adoc, version from
Change-Id Id0d292506e8b2a888c8d7a682a38db80e9d0933a
Related: SYS#5987
Change-Id: Ieda0d4bfe6fc90da6e19c791d8ec2da89427ba3b
Both Synch. sequence and Training sequence are basically the same thing,
only the length is different. I guess this is why 3GPP TS 45.002 names
them differently. Let's mention them both to avoid confusion.
Change-Id: I092af5ef6b66f8bdbd46cc3ae0c77fd806f2fe27
This has been the port used historically in most existing deployments,
and it's the one already documented in the osmux section of user
manuals.
Change-Id: I9593e484a0df7cbfc3fa68f071246e3fb714bd4c
How and when socket statistics are generated is not immediately obvious.
Lets add some documentation about it.
Change-Id: Icb06b3934e9ea5f3526263dc8915bc3529a64324
Related: OS#5701
Remove this workaround, as we are not building for debian 8 anymore.
Related: OS#5223
Depends: osmo-ci Ibe7ba124557969df62798ba49c4489e9606c2341
Change-Id: I8285b8c483fe2d136b83946414587fc993d5f489
Introduce a new flag (1-bit field) indicating whether a VAMOS PDU
is for a _primary_ ('0'B) or for a _shadow_ ('1'B) timeslot. This
field shall be present only in the Uplink VAMOS PDUs, which unlike
the Downlink (AQPSK) PDUs are sent separately. This will simplify
routing of such PDUs in osmo-bts.
Change-Id: Ie00a12824938c6a65480bde1af364dcc9febb8f7
Related: SYS#4895, OS#4941, OS#4006
It's unclear why it was removed in I5fe6263ac666e41cbe34407f09e9023aafa57d2c
when common/chapters/glossary.adoc of this very same repository uses it.
Change-Id: Ib8d2f22450a84ed802b34845ad19a7af8d6b7968
We should use service-aliases and not the primary host name, as
that makes migration between machines hard.
Change-Id: Ie139a8cbf2aaa746c0edf6c90a567eb43bc51f45
Vilius Panevėžys
