Bynar
Bynar copied to clipboard
Server remediation as a service
main.rs::287 -- OperationInfo struct created with device_id set to 0. This will then create an operation entry in the device that doesn't correspond to any device and will essentially be...
add_or_update_operation() needs to be called to a) evaluate and set the completed/done time b) track other operations like diskadd, disk remove etc for each hardware that is remediated.
It would be nice if there was a database column to show how long a scan took which could help identify machines where bynar is crashing or taking forever.
Since the ByNar is running as binary (agent) in the system, what happens on the following scenario? - Kernel panic - System rebooted, not up? - Someone stopped the agent...
The provided platforms (Slack and JIRA) can be used if owner meets requirements. Possible to develop adapters for notification services that allow user to either develop, or send constructed .json...
Write some protobuf API's for hp ticket integration
https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Managing%20Volumes/#replace-brick Have bynar take these steps to swap a disk for glusterfs. The volume type will need to be ascertained before following the appropriate set of steps.
Exposing the database over the api will allow others to integrate easier.
Testing bynar is challenging to say the least. If possible I wonder if a virtual machine could be created that allows integration testing to be performed over and over to...
I was checking out this today: https://docs.rs/hdd/0.10.0/hdd/ and this might actually be better at identifying disks than udev. I've seen linux get into situations where udev drops the device from...