Update Xen RA to use xl instead of the deprecated xm #440
Conversation
|
Yes, I'd also prefer if the RA stayed compatible with both xl and xm. (That would allow us to keep updating on older releases as well.) |
|
Updated to fall back to using xm if xl is not available |
|
Thanks! Let's just hope that xl really has the same semantics as xm. |
|
The syntax seems to be the same (from some quick testing I did), but there could probably be subtle differences in semantics. But I think that can be true of any version upgrade.. I guess we'll see. :) |
|
After talking to people more knowledgeable about Xen, it turns out that migrating from the xm tools to xl is decidedly non-trivial: xl doesn't have any concept of Managed Domains, which means that xl list fails if the vm is not running. The best solution seems to be to make people migrate to the VirtualDomain RA rather than trying to get the Xen RA to work with xl. |
|
I wonder why did Xen replace xm with xl then. It's a pain to manage dropping features which were working. |
|
Yes. :( |
The xm command line tool has been deprecated in favor of the xl toolstack. For more information, see: - http://wiki.xen.org/wiki/MigrationGuideToXen4.1 - http://wiki.xen.org/wiki/XL#Upgrading_from_xend Use xl if available, else fall back on using xm.
Clean up trailing whitespace, and don't use ! as heredoc delimiter as some editors don't handle it properly.
|
Updated with proper quoting around name parameter in call to $xentool create. |
|
Now that there is a passing ocft test for this updated agent, any chance of merging? |
|
Yes, sure, thanks! |
Update Xen RA to use xl instead of the deprecated xm
|
Thanks! |
First commit replaces the use of the xm command line tool with xl.
For more details, see:
Also comes with a second commit which cleans up trailing whitespace in the RA.