fix(docker): fixes when generating the templates for gNB conf files

* 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>
This commit is contained in:
Raphael Defosseux
2022-09-21 10:52:05 +02:00
parent 18ead40b84
commit 0dff2c9bc3
3 changed files with 20 additions and 22 deletions
+6 -1
View File
@@ -20,9 +20,14 @@ if [[ -v USE_SA_NFAPI_VNF ]]; then cp $PREFIX/etc/gnb.sa.nfapi.vnf.conf $PREFIX/
if [[ -v USE_VOLUMED_CONF ]]; then cp $PREFIX/etc/mounted.conf $PREFIX/etc/gnb.conf; fi
# Defualt Parameters
GNB_ID=${GNB_ID:-0xe00}
GNB_ID=${GNB_ID:-e00}
USE_FQDN=${USE_FQDN:-false}
AMF_FQDN=${AMF_FQDN:-oai-amf-svc}
# if you explicitly want to use an SD, it should be added in the docker-compose or the helm chart
# if you want to support more than 1 NSSAI, then you need to mount a more-complex conf file
if [[ -v NSSAI_SST ]] && [[ -v NSSAI_SD ]] then
NSSAI_SST=$NSSAI_SST" , sd = "$NSSAI_SD
fi
# Resolve AMF FQDN
if ($USE_FQDN); then AMF_IP_ADDRESS=(`getent hosts $AMF_FQDN | awk '{print $1}'`); fi