FreeBSD VM gets a UUID from host which informs where resource
disk locates. But that UUID string was not exposed from VM kernel,
as a result, the agent used a hard code "2:1:0" as the location of
resource disk. That should be updated after FreeBSD VM kernel
exposed UUID through "sysctl dev.storvsc" command.
But considering compatible with previous FreeBSD VM, the hard code
logic cannot be removed, and they are left there as a fallback.
* add testing for mountpoint, some refactoring
* fixed double space in mount string
* patch for ConfigProvider
* revert patch to original string.
* update documentation, add 'n' option for mountopts
* remove test argument
* More descriptive description in README, n to None
* minor var name changes for clarity
* spacing, missing self in get_mount_string
* mount_opts to mount_options
* add config option to writtet WaagentConf, minor style changes.
* mount options fix, is not Note
* add self to get_mount_string args
* self to function, not where it's called
* mount_options = output of function, not the function.
* get_mount_string returns with mount options/if not none
* forgot to remove part of the string
* instantiate resource disk handler, get_switch to get in conf.py
* Added config option to waagent.conf
* minor style fixes
* mountOpts is None change, and also added removed variable.
* revert changes to bin/waagent2.0
* reverted waagent2.0 to e8c641f
* config options added
* - Integrate RDMA handling
* - RDMA Integration
+ Fix syntax errors
+ Use the full distro name to differentiate properly between openSUSE
(which has currently no RDMA driver build) and SLES
* - RDMA integration
+ Do not stop the execution of the agent work flow by throwing an
exception if the RDMA handler is not specialized. Simply log an error
to indicate that the handler is not supported although it has been
configured with OS.EnableRDMA=y. The configuration in this case is in
error.
* - RDMA integration
+ Document he new OS.EnableRDMA configuration setting
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>
- 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
Hongjiang Zhang