Mserver
is a generic test image. The image contains a rich set of
iptools and some servers;
The mserver
image is used to start PODs. Example;
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: mserver
spec:
selector:
matchLabels:
app: mserver
template:
metadata:
labels:
app: mserver
spec:
containers:
- name: mserver
image: registry.nordix.org/cloud-native/mserver:latest
securityContext:
privileged: true
ports:
- name: mconnect
containerPort: 5001
- name: ctraffic
containerPort: 5003
- name: mconnect-udp
protocol: UDP
containerPort: 5001
- name: ctraffic-udp
protocol: UDP
containerPort: 5003
- name: "http"
containerPort: 80
- name: "kahttp"
containerPort: 8080
- name: "kahttps"
containerPort: 8443
- name: "sctpt"
protocol: SCTP
containerPort: 6000
The default test requires that mconnect.xz
and ctraffic.gz
release
files are downloaded to $ARCHIVE
or $HOME/Downloads
.
./mserver.sh # help printout
log=/tmp/$USER/xcluster.log
./mserver.sh test > $log
The kahttp test requires that kahttp.xz
(and optionally
server.crt
) is downloaded to $ARCHIVE
or $HOME/Downloads
.
./mserver.sh test kahttp > $log
The sctpt test requires nfqlb
(for build of sctpt
only).
$($XCLUSTER ovld sctp)/sctp.sh nfqlb_download
./mserver.sh test sctpt > $log
The parameters to the servers can be specified in environment variables. The defaults are;
MCONNECT_PARAMS="-udp -address [::]:5001"
CTRAFFIC_PARAMS="-udp -address [::]:5003"
KAHTTP_PARAMS="-address :8080 -https_addr :8443"
Because of multihoming the sctpt
configuration is a bit
different. The parameters can be specified, but not
--addr
. Instead the interfaces can be specified. Defaults;
SCTPT_INTERFACES=eth0
SCTPT_PARAMS="--log=5 --port=6000"
For multihoming two interfaces should be specified;
SCTPT_INTERFACES=net1,net2
Prerequisites;
-
mconnect.xz
,ctraffic.gz
andkahttp.xz
downloaded -
kahttp cloned
-
nfqueue-loadbalancer downloaded
$($XCLUSTER ovld sctp)/sctp.sh nfqlb_download
./mserver.sh mkimage