[jira] [Updated] (CLOUDSTACK-2696) default value of cluster.memory.allocated.capacity.notificationthreshold is getting set to 0.75 instead of taking value from Global parameter cluster.memory.alloca

2013-05-27 Thread prashant kumar mishra (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

prashant kumar mishra updated CLOUDSTACK-2696:
--

Attachment: logs.rar

 default value of cluster.memory.allocated.capacity.notificationthreshold  is 
 getting set to 0.75 instead of taking value from Global parameter 
 cluster.memory.allocated.capacity.notificationthreshold
 

 Key: CLOUDSTACK-2696
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2696
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, UI
Affects Versions: 4.2.0
Reporter: prashant kumar mishra
 Fix For: 4.2.0

 Attachments: logs.rar


 Steps to reproduce
 ---
 1- set global parameter 
 cluster.memory.allocated.capacity.notificationthreshold to some value say 
 0.2
 2-Set cluster level parameter 
 cluster.memory.allocated.capacity.notificationthreshold to space
 Expected
 --
 cluster.memory.allocated.capacity.notificationthreshold should be set to 
 0.2(global parameter)
 Actual
 ---
 cluster.memory.allocated.capacity.notificationthreshold is getting set to 
 0.75,DB shows NULL in value field
 DB
 --
 mysql select * from cluster_details;
 +++-+---+
 | id | cluster_id | name| 
 value |
 +++-+---+
 |  1 |  1 | cpuOvercommitRatio  | 
 1.0   |
 |  2 |  1 | memoryOvercommitRatio   | 
 1.0   |
 |  3 |  2 | cpuOvercommitRatio  | 
 1.0   |
 |  4 |  2 | memoryOvercommitRatio   | 
 1.0   |
 |  5 |  1 | cluster.cpu.allocated.capacity.disablethreshold | 
 NULL  |
 |  6 |  2 | cluster.cpu.allocated.capacity.disablethreshold | 
 NULL  |
 |  7 |  1 | cluster.memory.allocated.capacity.disablethreshold  | 
 NULL  |
 |  8 |  1 | cluster.cpu.allocated.capacity.notificationthreshold| 
 0.85  |
 |  9 |  2 | cluster.cpu.allocated.capacity.notificationthreshold| 
 NULL  |
 | 10 |  2 | cluster.memory.allocated.capacity.disablethreshold  | 
 0.85  |
 | 11 |  2 | cluster.memory.allocated.capacity.notificationthreshold | 
 NULL  |
 +++-+---+

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (CLOUDSTACK-2696) default value of cluster.memory.allocated.capacity.notificationthreshold is getting set to 0.75 instead of taking value from Global parameter cluster.memory.alloca

2013-05-27 Thread prashant kumar mishra (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

prashant kumar mishra updated CLOUDSTACK-2696:
--

Attachment: (was: logs.rar)

 default value of cluster.memory.allocated.capacity.notificationthreshold  is 
 getting set to 0.75 instead of taking value from Global parameter 
 cluster.memory.allocated.capacity.notificationthreshold
 

 Key: CLOUDSTACK-2696
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2696
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, UI
Affects Versions: 4.2.0
Reporter: prashant kumar mishra
 Fix For: 4.2.0

 Attachments: logs.rar


 Steps to reproduce
 ---
 1- set global parameter 
 cluster.memory.allocated.capacity.notificationthreshold to some value say 
 0.2
 2-Set cluster level parameter 
 cluster.memory.allocated.capacity.notificationthreshold to space
 Expected
 --
 cluster.memory.allocated.capacity.notificationthreshold should be set to 
 0.2(global parameter)
 Actual
 ---
 cluster.memory.allocated.capacity.notificationthreshold is getting set to 
 0.75,DB shows NULL in value field
 DB
 --
 mysql select * from cluster_details;
 +++-+---+
 | id | cluster_id | name| 
 value |
 +++-+---+
 |  1 |  1 | cpuOvercommitRatio  | 
 1.0   |
 |  2 |  1 | memoryOvercommitRatio   | 
 1.0   |
 |  3 |  2 | cpuOvercommitRatio  | 
 1.0   |
 |  4 |  2 | memoryOvercommitRatio   | 
 1.0   |
 |  5 |  1 | cluster.cpu.allocated.capacity.disablethreshold | 
 NULL  |
 |  6 |  2 | cluster.cpu.allocated.capacity.disablethreshold | 
 NULL  |
 |  7 |  1 | cluster.memory.allocated.capacity.disablethreshold  | 
 NULL  |
 |  8 |  1 | cluster.cpu.allocated.capacity.notificationthreshold| 
 0.85  |
 |  9 |  2 | cluster.cpu.allocated.capacity.notificationthreshold| 
 NULL  |
 | 10 |  2 | cluster.memory.allocated.capacity.disablethreshold  | 
 0.85  |
 | 11 |  2 | cluster.memory.allocated.capacity.notificationthreshold | 
 NULL  |
 +++-+---+

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira