[MCOL-251] does columnstore need to issue snmp traps? Created: 2016-07-07  Updated: 2023-10-26  Resolved: 2016-10-26

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.0.2
Fix Version/s: 1.0.4

Type: New Feature Priority: Minor
Reporter: David Hill (Inactive) Assignee: David Hill (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
PartOf
is part of MCOL-280 Beta issues Closed
Sprint: 2016-19, 2016-20, 2016-21

 Description   

The current version of MariaDB Columnstore issues snmptraps, which is used to inform remote control centers of an issue with the system. This is there because it was in InfiniDB. It was in InfiniDB when the software design was to be running on a dedicated appliance.
When InfiniDB was converted to be a software only product, this functionality remained.

The question is, does this functionality of being able to generate snmptraps from columnstore need to be kept?

1 item of note, the issuing of local alarms is tied to issuing for a trap. So if we decide to remove the snmptrap functionality, the logic of sending alarms will need to be changed.

Also removing the snmptrap functionality altogether will simple our source tree and build process.

 Comments   
Comment by David Hill (Inactive) [ 2016-07-13 ]

it was agreed that the snmptrap functionality would be moved from columnstore.

Comment by David Hill (Inactive) [ 2016-10-10 ]

Changes being made:

1. remove the issuing of snmptrapds
2. which will removing the luanching of snmptrapd
3. remove the snmptrap prompts in postConfigure
4. change code to issue alarms directly and not have it based on the trap being issued first
5. last but not least, remove all references to the snmp libraries and divorce Columnstore from having snmp libraries as build and install dependencies.

This is actively being worked now in MCOL-251 repo

Comment by David Hill (Inactive) [ 2016-10-10 ]

code changes are completed...

1. Issue alarms without snmptraps
2. change code that referenced the term snmpmanager to alarmmanager
3. removed code for snmpmanager and add alarmmanager under oamapps
4. removed the build and install dependencies for net-snmp
5. snmptrapd not being started and prompt removed from postConfigure

ready for review in enegine mcol-251... a lot of files were changed

Comment by David Hill (Inactive) [ 2016-10-10 ]

How to test:

1. make sure you can build with net-snmp-devel
2. make sure you can install without net-snmp
3. run postConfigure and make sure the snmptrapd part is removed
4. check ma getsystemi and make sure the snmptrapd is no longer there
5. stopsystem and run getsystemi and check that alarms are being issue from the summary

Comment by David Hill (Inactive) [ 2016-10-10 ]

Assign to review, let me know if its reviewable based on the knowledge of OAM

Comment by Ben Thompson (Inactive) [ 2016-10-11 ]

Review done, looks good, confirmed build/install.

Comment by David Hill (Inactive) [ 2016-10-26 ]

tested, no snmptrap daemon is now loaded and alarms are functional

Generated at Thu Feb 08 02:19:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.