-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fence_nutanix_ahv: Add fence agent support for Nutanix AHV Cluster #600
Conversation
This patch adds fence agent support for Nutanix AHV clusters. More specifically the initial support is aimed at AHV clusters that support Nutanix v4 APIs. V3 APIs are not supported. Signed off by <amir.eibagi@nutanix.com>
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-600/1/input |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good in general.
I've added some suggestions for improvements and fixes.
You should name the agent fence_nutanix_ahv to make it easy for users to identify that it might be the agent they're looking for without looking at the help text or manpage.
You have to run make xml-upload
and add the metadata to the PR.
The agent should be added to it's own %package/%description/%files sections in fence-agents.spec.in
.
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-600/2/input |
This patch adds fence agent support for Nutanix AHV clusters. More specifically the initial support is aimed at AHV clusters that support Nutanix v4 APIs. V3 APIs are not supported. Signed off by <amir.eibagi@nutanix.com>
3f9d80b
to
edb3ba3
Compare
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-600/3/input |
This patch adds fence agent support for Nutanix AHV clusters. More specifically the initial support is aimed at AHV clusters that support Nutanix v4 APIs. V3 APIs are not supported. Signed off by <amir.eibagi@nutanix.com>
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-600/4/input |
@oalbrigt Thank you for your review comments. I have addressed all of them. Please let me know if I have missed anything else. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few improvements needed.
This patch adds fence agent support for Nutanix AHV clusters. More specifically the initial support is aimed at AHV clusters that support Nutanix v4 APIs. V3 APIs are not supported. Signed off by <amir.eibagi@nutanix.com>
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-600/5/input |
This patch adds fence agent support for Nutanix AHV clusters. More specifically the initial support is aimed at AHV clusters that support Nutanix v4 APIs. V3 APIs are not supported. Signed off by <amir.eibagi@nutanix.com>
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-600/6/input |
retest this please |
Thank you for your review. I ran a few tests with the latest changes on a 3-node CentOS 9 stream, cluster setup. All basic power operations via fence_nutanix_ahv works fine. Also, tested stonith feature by failing a node to confirm that pacemaker successfully resets the failed node. Documenting the test output here. [root@vm2-auto ~]# fence_nutanix_ahv -a 10.101.63.173 -l admin -p Nutanix.123 -o list-status --ssl-insecure [root@vm2-auto ~]# fence_nutanix_ahv -a 10.101.63.173 -l admin -p Nutanix.123 -o list-status --filter="name eq 'TestVM1'" --ssl-insecure [root@vm2-auto ~]# fence_nutanix_ahv -a 10.101.63.173 -l admin -p Nutanix.123 -o on --plug='TestVM1' --ssl-insecure [root@vm2-auto ~]# fence_nutanix_ahv -a 10.101.63.173 -l admin -p Nutanix.123 -o reboot --plug='TestVM1' --ssl-insecure [root@vm2-auto ~]# fence_nutanix_ahv -a 10.101.63.173 -l admin -p Nutanix.123 -o list-status --filter="startswith(name, 'TestVM')" --ssl-insecure [root@vm2-auto ~]# fence_nutanix_ahv -a 10.101.63.173 -l admin -p Nutanix.123 -o off --plug='TestVM1' --ssl-insecure [root@vm2-auto ~]# fence_nutanix_ahv -a 10.101.63.173 -l admin -p Nutanix.123 -o list-status --filter="startswith(name, 'TestVM')" --ssl-insecure tail -f /var/log/pacemaker/pacemaker.log [root@node1 ~]# pcs status
Node List:
Full List of Resources:
|
@oalbrigt I have run some basic tests, including cluster node failure test. Please merge the pull request if you are comfortable with the tests. |
Thanks. |
This patch adds fence agent support for Nutanix AHV clusters. More specifically the initial support is aimed at AHV clusters that support Nutanix v4 APIs. V3 APIs are not supported.
Signed off by amir.eibagi@nutanix.com