Cannot identify which machine sends the data if we run >1 NS2 connected to NS1

[sonata-nfv]

Cannot identify which machine sends the data if we run >1 NS2 connected to NS1

[mmiiot]

WIMMS is the <machine_name> , it is a placeholder.
WIMMS has to be replaced by the company wide unique machine identifier.

You can subscribe e.g. from
machine simulator: WIMMS1/EM63/ActCntPrt/
or real physical machine: IMM2/EM63/ActCntPrt/

or data from additional iot sensors integrated in IMM2:
IMM2/sensorX/tempY

[mpeuster]

Ahhhhhhhh ... got it! Perfect.

Than I can make it configurable in the Docker container of the VNF and everything is fine. Many thanks for the clarification.

I'll adapt the Prometheus Exporter VNF as well so that the machine name is correctly translated into a label for the recorded data. That is not the case right now. Then we should be able to easily visualize data for individual machines.

[mmiiot]

Question: Can we set it via FMP before instantiation (during machine adding process) of NS2 and can we manipulate it later via FMP?

[mpeuster]

Puh hard to say for the real SP. We should somehow. I am adding an environment variable MACHINE_NAME to the Docker container (the same as we did for other config options already).

I am focusing on the emulator version of the pilot (NetSoft) right now, but we should be able to set this variable in the K8s case as well.