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
Adding reboot action for os_server_action module #62828
Conversation
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
The test
|
Build succeeded (third-party-check pipeline).
|
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.
There's also a soft reboot option but that works only when a VM is in an ACTIVE state and that case can be easily covered by the generic reboot module.
Actually a VM might be purposefully unreachable from the controller network, but still manageable from Openstack, so the use-case for soft rebooting is still valid, according to me.
For instance, a module argument like reboot_type
could be offered and set to SOFT
by default. In that case, the VM state should be ACTIVE beforehand.
|
||
cloud.compute.post( | ||
_action_url(server.id), | ||
json={'reboot': {'type': 'HARD'}}) |
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.
Do we really want a default and only "hard" reboot ?
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.
That's right. Added soft reboot as default and new argument reboot_type
.
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.
shipit
Thanks for submitting patch for Openstack Ansible modules! |
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.
Because we moved Openstack Ansible modules to Openstack repositories, please submit all changes from openstack modules to Openstack Gerrit: https://review.opendev.org/#/q/project:openstack/ansible-collections-openstack Thanks for your contribution and sorry for inconvienience.
@sshnaidm does that require a CLA? I know openstacksdk requires a CLA to send fixes, so I'm carrying local patches since I can't get the CLA signed. To date, I've been able to send fixes to the openstack ansible modules since no CLA is required for ansible contributions. |
@jamescassell yes, you are right, all Openstack contributions require License Agreement to be signed. |
@gabicrisan Thanks for the contribution. Closing as per above. |
SUMMARY
This enables the reboot action within the os_server_action module. Since there are two types of reboot actions currently supported by Openstack API, a new argument
reboot_type
has been added in order to be able to select between these two options. The action is defaulted to soft reboot.Reboot states references: https://docs.openstack.org/api-ref/compute/?expanded=reboot-server-reboot-action-detail
ISSUE TYPE
COMPONENT NAME
reboot action for os_server_action module
ADDITIONAL INFORMATION