nebulous/optimiser-controller
Code Issues Proposed changes

Stop asking for upper bounds of machine resources

Browse Source 
Specify minimum requirements only, not upper bounds as
well.  (Specifying upper bounds was a workaround for when the
largest-possible machine was suggested by the broker, but that behavior
was changed.)

Change-Id: Iacee8baf2cef21b538ffbf12e4d262d2692bd8d8
This commit is contained in:
Rudi Schlatte 2024-04-23 10:26:04 +02:00
parent 44fea54890
commit aa47639a13
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
optimiser-controller/src/main/java/eu/nebulouscloud/optimiser/controller/NebulousAppDeployer.java
View File

@ -240,7 +240,7 @@ public class NebulousAppDeployer {
// ------------------------------------------------------------
// Extract node requirements
Map<String, List<Requirement>> componentRequirements = KubevelaAnalyzer.getClampedRequirements(kubevela);
Map<String, List<Requirement>> componentRequirements = KubevelaAnalyzer.getBoundedRequirements(kubevela);
Map<String, Integer> nodeCounts = KubevelaAnalyzer.getNodeCount(kubevela);
List<Requirement> controllerRequirements = getControllerRequirements(appUUID);
// // HACK: do this only when cloud id = nrec
@ -507,7 +507,7 @@ public class NebulousAppDeployer {
// ------------------------------------------------------------
// 1. Extract node requirements
Map<String, List<Requirement>> componentRequirements = KubevelaAnalyzer.getClampedRequirements(updatedKubevela);
Map<String, List<Requirement>> componentRequirements = KubevelaAnalyzer.getBoundedRequirements(updatedKubevela);
Map<String, Integer> componentReplicaCounts = KubevelaAnalyzer.getNodeCount(updatedKubevela);
Map<String, List<Requirement>> oldComponentRequirements = app.getComponentRequirements();