* The '0x' format was forgetting that an hexadecimal value can have a-f chars
* If someone wants to use a dedicated NSSAI_SD value, it is possible now
* For experimental purpose in cluster, SDR addresses can be provided for one config
- could be expended later on other conf files
Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>
- especially for plmn_list, will allow to be followed by an MCC/MNC in a
single line
- tightens regexes to match replacements more accurately, e.g., "val =
key" (instead of just searching for "key)
- no special rule for SD, which matches SD values (and not the SD
field). However, currently it is not possible to specify multiple SDs
(multiple SSTs was already not possible)
The loop passes over all keys. For plmn_list, there are subentries mcc,
mnc, mnc_length. The plmn_list if block assumes that the key is a dict,
which was not checked for, leading to a type error.
- Adding new templates for nFAPI in gNB and NR-UE images
- Better entrypoint for NR-UE (alignment on others)
- New Test method: StatsFromGenObject
- At deployment, image name, size and date are printed
- Initial scenario with 1 NR-UE and just ping operations
- Trigger new child sub-pipeline for L2-sim-5G tests
Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>
- install libasan in physim containers
- run physim containers with SYS_CAP_PTRACE capability
- remove static-libasan: not available in RHEL8:
The physims are tested in a container environment on top of RHEL8. To
my knowledge, no package provides the static ASan library there.
Therefore, remove it here to be able to run these tests.
This commit creates an intermediary build image for all eNB, gNB, UE,
nrUE, RU targets (ran-build) after the image containing all RAN
compilation dependencies (ran-base). Then, the corresponding target
container images are just copied from the ran-build.
The only exception is phySim, which is still compiled independently, as
the build_oai would otherwise put all compiled files into
phy_simulators/build instead of ran_build/build. We do this at this
state to avoid any inconsistencies.
This commit creates an intermediary build image for all eNB, gNB, UE,
nrUE, RU targets (ran-build) after the image containing all RAN
compilation dependencies (ran-base). Then, the corresponding target
container images are just copied from the ran-build.
luis_pereira87