[
https://issues.apache.org/jira/browse/CLOUDSTACK-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615078#comment-14615078
]
ASF subversion and git services commented on CLOUDSTACK-8607:
-------------------------------------------------------------
Commit 31c6b14dd474e1c82b7377f97e9c84fac4b028b6 in cloudstack's branch
refs/heads/master from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=31c6b14 ]
Merge branch 'improvement/CLOUDSTACK-8607' change the host password on the host
itself via the updateHostPassword API
- Make sure the new password replaces the old one in the queue
- Updated the patch files for XenServer
- Updated the script path on LibvirtComputing class
- Adding update_host_passwd to VRScripts
- Add implementation to CitrixUpdateHostPasswordCommandWrapper
- Improve testUpdateHostPasswordCommand() unit test on
CitrixRequestWrapperTest
- Adding update_host_passwd.sh script
- Adding the host IP address as an instance variable on
UpdateHostPasswordCommand
- Improving the Unit Test (LibvirtComputingResourceTest) to get it covering
the new code
- Make sure doUpdateHostPassword() doesn't get called if flag is set to
false
- Do not update XenServer hosts if the cluster ID is not informed
This closes #559
> As an Operator I want to be able to change the host password on the host
> itself via the updateHostPassword API
> --------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8607
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8607
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, XenServer
> Reporter: Wilder Rodrigues
> Assignee: Wilder Rodrigues
> Fix For: 4.6.0
>
>
> 1. Change the API to offer a flag to decide to update the host or not
> - The default should be false
> - The flag is not mandatory
> 2. When the flag is informed and true, in case of communication error with
> the host we have to rollback the DB changes
> 3. In case of XenServer, do not allow single host update
> - Update shall be done only when the cluster ID is informed
> - It doesn't apply for KVM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
