[
https://issues.apache.org/jira/browse/VCL-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Peeler updated VCL-366:
-----------------------------
Fix Version/s: (was: 2.3)
2.4
Moving to 2.4 - if even needed
> as needed add throttling to new vmware modules
> ----------------------------------------------
>
> Key: VCL-366
> URL: https://issues.apache.org/jira/browse/VCL-366
> Project: VCL
> Issue Type: Improvement
> Components: vcld (backend)
> Reporter: Aaron Peeler
> Fix For: 2.4
>
>
> This part two from the 2.2 release. Make use of the throttling variable
> within the new vmware modules.
> # Check to see if management node throttle is configured
> #get Throttle value from database if set
> my $xcat_throttle = 0;
> my $variable_name = $self->data->get_management_node_hostname() .
> "|xcat|throttle";
> if($self->data->is_variable_set($variable_name)){
> notify($ERRORS{'DEBUG'}, 0, "throttle is set for $variable_name");
> #fetch variable
> $xcat_throttle = $self->data->get_variable($variable_name);
> }
> else{
> notify($ERRORS{'DEBUG'}, 0, "throttle is not set for $variable_name");
> $xcat_throttle = 0;
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
