ENGINEID of SNMP user is hardcoded, reusing default from a tutorial

[mbukatov]

Description

ENGINEID of SNMP user, which Tendrl uses to send SNMP trap messages, is hardcoded, reusing value mentioned in upstream SNMP example.

The value suggested by Tendrl Installation guide (search for Configure email/snmp source step there):

In receiving host machine:
yum install net-snmp
open file snmptrapd.conf
write below line inside file
authUser log <username of receiver>
createUser -e 8000000001020304 <user name of receiver> MD5 <md5 password> DES <des password>
Run command
snmptrapd -f -Lo -c snmptrapd.conf

And compare that with tutorial Configuring snmptrapd to receive SNMPv3 notifications:

A SNMPv3 TRAP
(for this, I'm making up an engineID to use: 0x8000000001020304)
In a /tmp/snmptrapd.conf file put:

And while the actual value is not the same, it seems that we may need to put more thought into this.

Additional Details

Manpage snmpd.conf(5) states:

The SNMPv3 protocol defines "engineIDs" that uniquely identify an agent. The string must
be consistent through time and should not change or conflict with another agent's engineID. Ever.

Version

Tendrl release v1.5.4

[r0h4n]

@GowthamShanmugam please look into this

@mbukatov any updates?