The Agent will monitor for more recent versions and update itself
(without impacting the installed version). If the new Agent fails
(in a very bad way or consistently), the code rolls back to the prior
version.
Signed-off-by: Brendan Dixon <brendand@microsoft.com>
* formatting fixes, update error text, remove unused imports
* modify error logic to use host plugin upload as a fallback
* initial commit for host plugin work
* adds the vmAgentLog api
* code review feedback
* update loopback detection to use SIOCGIFFLAGS and IFF_LOOPBACK; add unit tests
* adds a check for the wireserver ip, and if it does exist then skip the dhcp lookup and route manipulation; adds unit tests
* ensure the first selected interface is the primary, which is that with the default route; adds unit tests
* parse the wireserver from the dhcp leases file on disk; distro-specific, this is the ubuntu implementation; adds unit tests
* unit test fixes, python 3 changes
* code review feedback
* - Support package upgrade in for the RDMA driver
+ A different version of the rdma driver may need to be installed when
a VM gets rebooted as it may be deployed on different HW that has a
different firmware version
* - RDMA support driver upgrades
+ Code style changes
+ Turns out the module in question cannot be removed with "rmmod" and we
need to reboot the system if the driver is already loaded and a package
upgrade is needed. Implemented this condition
* - RDMAHandler
+ Add additional logging
- correct scvmm references
- add unit tests for scvmm detection
- ensure all matching devices are mounted and examined for scvmm configuration
- exit once vmm startup script is found and executed
- fixes#185
* - RDMA support
+ SUSE specific implementation to install the RDMA kernel module
* - RDMA specialization for SUSE
+ Some code tidy up
* - SUSE RDMA loader
+ Adjust imports to new structure of modules in project
+ Fix typo
+ Log success
+ Best effort package detection
This will treat interface names such as 'lo:1' as loopback
as well. The ultimate solution is to use sysfs+procfs in this
method to check the flags and find the ipv4 addr. However sticking
to an extended check for now.
Fixes#188.
brendandixon