forked from ablecloud-team/ablestack-cloud
-
Notifications
You must be signed in to change notification settings - Fork 0
bronto merge #28
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
Merged
Dajeong-Park
merged 20 commits into
Dajeong-Park:ablestack-bronto
from
ablecloud-team:ablestack-bronto
Aug 31, 2021
Merged
bronto merge #28
Dajeong-Park
merged 20 commits into
Dajeong-Park:ablestack-bronto
from
ablecloud-team:ablestack-bronto
Aug 31, 2021
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tup-data… (apache#5187) * Added ability to create schemas only when using cloudstack-setup-databases * Renamed var name * Added a check for passing --schema-only and --deploy-as together/. * Moved validation to appropriate method * Moved description * fixed whitespace
…ache#4570) * Externalize KVM Agent's option to change migration thread timeout * Update javadoc Co-authored-by: GutoVeronezi <[email protected]>
Co-authored-by: SadiJr <[email protected]>
* ui: Go back for delete actions before querying async job * Prevent redirecting if failed
…oad balancing. (apache#1257) * CLOUDSTACK-9175: [VMware DRS] Adding new host to DRS cluster does not participate in load balancing. Summary: When a new host is added to a cluster, Cloudstack doesn't create all the port groups (created by cloudstack earlier in other hosts) present in the cluster. Since the new host doesn't have all the necessary networking port groups of cloudstack, it is not eligible to participate in DRS load balancing or HA. Solution: When adding a host to the cluster in Cloudstack, use VMware API to find the list of unique port groups on a previously added host (older host in the cluster) if exists and then create them on the new host. * Added few checks for cluster details
* Added support for removing unused port groups on VMWare * Fixed error handling around unavailable portgroup name * Review changes, defaulting glovbal var to false, added warning to description, changed if statement. * Cleanup unused network port groups on all the hosts. Co-authored-by: Suresh Kumar Anaparti <[email protected]> Co-authored-by: nicolas <[email protected]>
…ms (apache#5364) * server: allow destroy volumes which attach to a expunged vm * server: recover volume which is attached to a removed vm
…e volume operations. (apache#5377) Worker VM tags are missed for few cloned VMs in VMware, and so these are skipped when tracking / cleaning up of Worker VMs. Adding proper Worker VM tags to these VMs would make them trackable from CloudStack.
* server: improve attach volume in specific cases When a VM is in stopped state and host for it is not found then server skips sending AttachCommand to hypervisor. Change tries to improve this case and finds a suitable host in the VM's cluster when volume is not in a HOST scope pool. Signed-off-by: Abhishek Kumar <[email protected]> * typo Co-authored-by: sureshanaparti <[email protected]> Co-authored-by: sureshanaparti <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR 설명
이 PR은 ...
변경 구분
기능/개선 규모 또는 버그 심각도
기능/개선 규모
버그 심각도
스크린샷
테스트 방법 및 결과