Allon Mureinik has posted comments on this change.
Change subject: core: Host shouldn't move to UP if it's already connected to
other pool
......................................................................
Patch Set 2: Code-Review+1
(1 comment)
Minor inline comments, please address.
....................................................
File
backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/InitVdsOnUpCommand.java
Line 221:
getStorageDomainDAO().getStorageDomainByTypeAndPool(storagePoolId,
StorageDomainType.Master);
Line 222: boolean masterDomainInactiveOrUnknown =
masterDomain.getStatus() == StorageDomainStatus.InActive
Line 223: || masterDomain.getStatus() ==
StorageDomainStatus.Unknown;
Line 224:
Line 225: VDSReturnValue returnValue =
ResourceManager.getInstance().runVdsCommand(VDSCommandType.ConnectStoragePool,
After discussing face-to-face, I understand the difference between
runVdsCommand and ResourceManager.getInstance().runVdsCommand.
However, this is not intuitive, and prone to be broken by a future developer
that will just "clean up" the code and revert it to a simple runVdsCommand call.
Please add a comment explaining WHY this was done, so we at least have SOME
protection.
Line 226: new
ConnectStoragePoolVDSCommandParameters(vds.getId(), storagePoolId,
Line 227: vds.getVdsSpmId(), masterDomain.getId(),
Line 228: storagePool.getmaster_domain_version()));
Line 229: if (!returnValue.getSucceeded()) {
--
To view, visit http://gerrit.ovirt.org/21095
To unsubscribe, visit http://gerrit.ovirt.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: Ifd3d8268516b010f7831b59bbc6331cfd70efec1
Gerrit-PatchSet: 2
Gerrit-Project: ovirt-engine
Gerrit-Branch: master
Gerrit-Owner: Liron Ar <[email protected]>
Gerrit-Reviewer: Allon Mureinik <[email protected]>
Gerrit-Reviewer: Liron Ar <[email protected]>
Gerrit-Reviewer: Roy Golan <[email protected]>
Gerrit-Reviewer: Tal Nisan <[email protected]>
Gerrit-Reviewer: oVirt Jenkins CI Server
Gerrit-HasComments: Yes
_______________________________________________
Engine-patches mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/engine-patches
