Skip to content

Exclude External hypervisor type during upgrade for System VM template checks #11435

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.

Sign up for GitHub

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
sureshanaparti merged 2 commits into from
Aug 15, 2025
Merged

Exclude External hypervisor type during upgrade for System VM template checks #11435

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b761c27
Exclude External hypervisor type during upgrade for System VM templat…
harikrishna-patnala Aug 12, 2025
0233a9a
Rename method
harikrishna-patnala Aug 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Exclude External hypervisor type during upgrade for System VM templat… 
…e checks
  • Loading branch information
@harikrishna-patnala
harikrishna-patnala committed Aug 12, 2025
commit b761c27cafabaf802ec156fe9279ed90d2893399
10 changes: 10 additions & 0 deletions engine/schema/src/main/java/com/cloud/dc/dao/ClusterDaoImpl.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,16 +168,26 @@ public List<HypervisorType> getAvailableHypervisorInZone(Long zoneId) {
.collect(Collectors.toList());
}

/**
* Returns distinct (HypervisorType, CPUArch) pairs from clusters in the given zone,
* excluding clusters with {@link HypervisorType#External}.
*
* @param zoneId the zone ID to filter by, or {@code null} to include all zones
* @return list of unique hypervisor type and CPU architecture pairs
*/
@Override
public List<Pair<HypervisorType, CPU.CPUArch>> listDistinctHypervisorsArchAcrossClusters(Long zoneId) {
Copy link
Copy Markdown
Contributor

@shwstppr shwstppr Aug 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel the method name should reflect the change to avoid confusion and wrong usage

Copy link
Copy Markdown
Member Author

@harikrishna-patnala harikrishna-patnala Aug 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shwstppr can you check the new changes with name change

SearchBuilder<ClusterVO> sb = createSearchBuilder();
sb.select(null, Func.DISTINCT_PAIR, sb.entity().getHypervisorType(), sb.entity().getArch());
sb.and("zoneId", sb.entity().getDataCenterId(), SearchCriteria.Op.EQ);
sb.and("hypervisorType", sb.entity().getHypervisorType(), SearchCriteria.Op.NEQ);
sb.done();
SearchCriteria<ClusterVO> sc = sb.create();
if (zoneId != null) {
sc.setParameters("zoneId", zoneId);
}
sc.setParameters("hypervisorType", HypervisorType.External);

final List<ClusterVO> clusters = search(sc, null);
return clusters.stream()
.map(c -> new Pair<>(c.getHypervisorType(), c.getArch()))
Expand Down
Loading