Streamline Logging to be more useful for using the proto-kms

This aims at addressing issue #3 (closed)

Problem Description

Right now logging is happening in quite an unstructured way across multiple places, e.g.,

• not log-levels are being used
• the originating code part is not visible, except it is manually added to the log-message

Applied Changes

• move from go's log pkg to sirupsen/logrus
• add log-levels
• loglevel to be handed over during start of the pkg separately for the quantlum-layer and the proto-kms (using logrus instances)
• log.SetOutput(os.Stdout) to be set during boot, if log messages should not go to stdout
• log.SetFormatter() to be added
• use of log.SetReportCaller(true) to add origin code of the message to log-message in Trace level

kms/kms.go

@@ -7,10 +7,12 @@ package kms
 import (
 	"crypto/rand"
 	"encoding/binary"
-	"log"
+	"os"
 	"sync"
 	"time"
 
+	log "github.com/sirupsen/logrus"
+
 	pbETSI "code.fbi.h-da.de/danet/proto-kms/api/gen/proto/go/kmsetsi"
 	pbIC "code.fbi.h-da.de/danet/proto-kms/api/gen/proto/go/kmsintercom"
 	"code.fbi.h-da.de/danet/proto-kms/quantumlayer"
@@ -75,7 +77,7 @@ func NewEKMS(kmsName string, kmsUUID uuid.UUID) (newEKMS *EKMS) {
 func (kms *EKMS) AddQuantumElement(kmsUDPAddrr string) *QuantumElement {
 
 	//Get an emulated Quantumlayer
-	ql := quantumlayer.NewQuantumlayerEmuPRNG()
+	ql := quantumlayer.NewQuantumlayerEmuPRNG(os.Stdout, log.InfoLevel, false)
 	ql.Configure(kmsUDPAddrr)
 	ql.PowerOn()