bwsw edited a comment on issue #3839: FEATURE-3823: kvm agent hooks URL: https://github.com/apache/cloudstack/pull/3839#issuecomment-590793862 @DaanHoogland > As for the functionality I am still to understand a few things; How do administrators enter or change hooks? Do they have to go to the host? Is there a way to control the functionality of the management server? These are system-wide scripts, which are deployed based on certain logic implemented for a cloud, they are not per-user, per-vm, etc. The hooks are deployed to agents with Ansible or another way. After being deployed, they substitute the old ones, so it helps to upgrade transparently. Administrators never write hooks by themselves, they are implemented by cloud architectors/developers according to the cloud expected properties, which are beyond the logic implemented in ACS standard functionality. The hooks are activated in Agent with following options: ```ini # Libvirt XML transformer hook does XML-to-XML transformation which provider can use to add/remove/modify some # sort of attributes in Libvirt XML domain specification. agent.hooks.libvirt_vm_xml_transformer.script=libvirt-vm-xml-transformer.groovy agent.hooks.libvirt_vm_xml_transformer.method=transform # # The hook is called right after libvirt successfuly launched VM agent.hooks.libvirt_vm_on_start.script=libvirt-vm-state-change.groovy agent.hooks.libvirt_vm_on_start.method=onStart # # The hook is called right after libvirt successfuly stopped VM agent.hooks.libvirt_vm_on_stop.script=libvirt-vm-state-change.groovy agent.hooks.libvirt_vm_on_stop.method=onStop ``` Hope it clarifies things a little bit.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
