While the hard coded values may reflect best practice values, we should allow a parameterize the check so a user can specify their own tolerance levels.
This impacts EQS/CI.
[DEBUG PASSED ] 10.111.1.56: File permisssions correct for /var/log/eucalyptus
[DEBUG PASSED ] 10.111.1.56: NC service running
[DEBUG PASSED ] 10.111.1.56: libvirt service running
[DEBUG PASSED ] 10.111.5.183: CLC service running
[DEBUG PASSED ] 10.111.5.183: No services in DISABLED
[DEBUG PASSED ] 10.111.5.183: No services in BROKEN
[DEBUG PASSED ] 10.111.5.183: No services in NOTREADY
[DEBUG PASSED ] 10.111.5.183: Was able to access postgres DB
[DEBUG PASSED ] 10.111.5.183: DB size smaller than 3GB
[DEBUG PASSED ] 10.111.5.183: /var/lib/eucalyptus is less than 85% full
[DEBUG FAILED ] 10.111.5.183: Less than 2GB of memory available. Consider stop other process on this host
Total passed: 25
Total failed: 1
Disconnecting from 10.111.5.183... done.
Disconnecting from 10.111.1.56... done.
[DEBUG RESULTS ] Name: DebugCloudController Passed: 7 Failed: 1
[DEBUG RESULTS ] Name: DebugNodeController Passed: 2 Failed: 0
[DEBUG RESULTS ] Name: FilePermissions Passed: 4 Failed: 0
[DEBUG RESULTS ] Name: CheckPorts Passed: 10 Failed: 1
[DEBUG RESULTS ] Name: DebugClusterController Passed: 1 Failed: 0
[DEBUG RESULTS ] Name: EucalyptusSosReports Passed: 11 Failed: 0
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE
Currently some debug checks are comparing actual resources to a hard coded value, such as memory usage (https://github.com/eucalyptus/calyptos/blob/master/calyptos/plugins/debugger/debug_cloud_controller.py#L74).
While the hard coded values may reflect best practice values, we should allow a parameterize the check so a user can specify their own tolerance levels.
This impacts EQS/CI.