[jira] [Updated] (CLOUDSTACK-9697) Better error message on UI user if tries to shrink the VM ROOT volume size
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9697: - Summary: Better error message on UI user if tries to shrink the VM ROOT volume size (was: Better error message user if tries to shrink the VM ROOT volume size) > Better error message on UI user if tries to shrink the VM ROOT volume size > -- > > Key: CLOUDSTACK-9697 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9697 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.9.1.0 > > > If a user tries to shrink the size of the root volume of a VM, the operation > fails with an error > Going from existing size of 10737418240 to size of 8589934592 would shrink > the volume.Need to sign off by supplying the shrinkok parameter with value of > true. > Instead, the UI can simply not allow shrink operation on the ROOT volume. > Throw a more user friendly message > "Shrink operation on ROOT volume not supported" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CLOUDSTACK-9697) Better error message on UI user if tries to shrink the VM ROOT volume size
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9697: - Description: If a user tries to shrink the size of the root volume of a VM, the operation fails with an error Going from existing size of 10737418240 to size of 8589934592 would shrink the volume.Need to sign off by supplying the shrinkok parameter with value of true. Instead, the UI can simply not allow shrink operation on the ROOT volume. Throw a more user friendly message on the UI "Shrink operation on ROOT volume not supported" was: If a user tries to shrink the size of the root volume of a VM, the operation fails with an error Going from existing size of 10737418240 to size of 8589934592 would shrink the volume.Need to sign off by supplying the shrinkok parameter with value of true. Instead, the UI can simply not allow shrink operation on the ROOT volume. Throw a more user friendly message "Shrink operation on ROOT volume not supported" > Better error message on UI user if tries to shrink the VM ROOT volume size > -- > > Key: CLOUDSTACK-9697 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9697 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.9.1.0 > > > If a user tries to shrink the size of the root volume of a VM, the operation > fails with an error > Going from existing size of 10737418240 to size of 8589934592 would shrink > the volume.Need to sign off by supplying the shrinkok parameter with value of > true. > Instead, the UI can simply not allow shrink operation on the ROOT volume. > Throw a more user friendly message on the UI > "Shrink operation on ROOT volume not supported" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CLOUDSTACK-9718) Revamp the dropdown showing lists of hosts available for migration in a Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9718: - Status: Reviewable (was: In Progress) > Revamp the dropdown showing lists of hosts available for migration in a Zone > > > Key: CLOUDSTACK-9718 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9718 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.10.0.0 > > Attachments: MigrateInstance-SeeHosts-Search.PNG, > MigrateInstance-SeeHosts.PNG > > > There are a couple of issues: > 1. When looking for the possible hosts for migration, not all are displayed. > 2. If there is a large number of hosts, then the drop down showing is not > easy to use. > To fix this, propose to change the view to a list view which will show the > hosts in a list view with radio button. Additionally have a search option > where the hostname can be searched in this list to make it more usable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9675) Cloudstack Metrics: Miscellaneous bug fixes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9675: - Status: Reviewable (was: In Progress) > Cloudstack Metrics: Miscellaneous bug fixes > --- > > Key: CLOUDSTACK-9675 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9675 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.7.1 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.9.0 > > > There are a number of issues in cloudstack metrics feature > 1. Goto Zone metrics or Hosts metrics. NUmerical values are not listed under > Mem Usage and Mem Allocation columns. Instead 'NaN' is displayed. > 2. Create a Windows instance on a Xen cluster. No IOPS data is generated or > shown in the Disk Usage Tab for that Instance. > 3. Changing storage.overprovisioning factor should cause changed values in > storage metrics. This doesnt happen currently. > 4. Allocated memory is not correctly calculated on Hosts Metrics page for a > xen server with multiple instances. > 5. List of Virtual Machines will be incorrect if the number is greater than > the default.page.size. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9700) Allow user to Register/Copy templates to multiple zones at the same time
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9700: - Attachment: RegisterTemplate-multiselect-error.PNG RegisterTemplate-multiselect.PNG CopyTemplate-WithSearchZone.PNG CopyTemplate-multiplezones.PNG Snapshots showing CopyTemplate new dialog and search functionality RegisterTemplate UI (Add in Templates) with multi select option as well as error conditions. > Allow user to Register/Copy templates to multiple zones at the same time > > > Key: CLOUDSTACK-9700 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9700 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template, UI >Affects Versions: 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.10.0.0 > > Attachments: CopyTemplate-WithSearchZone.PNG, > CopyTemplate-multiplezones.PNG, RegisterTemplate-multiselect-error.PNG, > RegisterTemplate-multiselect.PNG > > > A user can currently copy or register a template with only one zone at a > time. > The idea of this feature is to allow the user to allow copying or registering > of one template to multiple zones at the same time. > Both the UI and API need changes in this case. The UI for the destination > zone is currently a drop down. It can be a multi-select box. > The APIs need to accept destination zone as an array instead of a single ID. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9718) Revamp the dropdown showing lists of hosts available for migration in a Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9718: - Attachment: MigrateInstance-SeeHosts-Search.PNG MigrateInstance-SeeHosts.PNG New screen showing up all hosts that are available for migration. Also shows the CPU utilization & Memory used parameters per host. Second attachment shows the hosts based on keyword search > Revamp the dropdown showing lists of hosts available for migration in a Zone > > > Key: CLOUDSTACK-9718 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9718 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.10.0.0 > > Attachments: MigrateInstance-SeeHosts-Search.PNG, > MigrateInstance-SeeHosts.PNG > > > There are a couple of issues: > 1. When looking for the possible hosts for migration, not all are displayed. > 2. If there is a large number of hosts, then the drop down showing is not > easy to use. > To fix this, propose to change the view to a list view which will show the > hosts in a list view with radio button. Additionally have a search option > where the hostname can be searched in this list to make it more usable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9699) Metrics: Add a global setting to enable/disable Metrics view
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9699: - Attachment: metrics-enabled.PNG metrics-disabled.PNG enable-metrics-flag.PNG The enable.metrics global setting. View when the flag is false. View when the flag is true. > Metrics: Add a global setting to enable/disable Metrics view > > > Key: CLOUDSTACK-9699 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9699 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.10.0.0 > > Attachments: enable-metrics-flag.PNG, metrics-disabled.PNG, > metrics-enabled.PNG > > > The Metrics view for each type of entity basically fires APIs and calculates > required values on the client end. For e.g. to display memory usage etc at > the zone level, it will fetch all zones. For each zone it will fetch > pods->cluster->host->VMs > For a very large Cloudstack installation this will have a major impact on the > performance. > Ideally, there should be an API which calculates all this in the backend and > the UI should simply show the values. However, for the time, introduce a > global setting called enable.metrics which will be set to false. This will > cause the metrics button not to be shown on any of the pages. > If the Admin changes this to true, then the button will be visible and > Metrics functionality will work as usual. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9700) Allow user to Register/Copy templates to multiple zones at the same time
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9700: - Fix Version/s: (was: 4.9.1.0) 4.10.0.0 > Allow user to Register/Copy templates to multiple zones at the same time > > > Key: CLOUDSTACK-9700 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9700 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template, UI >Affects Versions: 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.10.0.0 > > > A user can currently copy or register a template with only one zone at a > time. > The idea of this feature is to allow the user to allow copying or registering > of one template to multiple zones at the same time. > Both the UI and API need changes in this case. The UI for the destination > zone is currently a drop down. It can be a multi-select box. > The APIs need to accept destination zone as an array instead of a single ID. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9718) Revamp the dropdown showing lists of hosts available for migration in a Zone
Rashmi Dixit created CLOUDSTACK-9718: Summary: Revamp the dropdown showing lists of hosts available for migration in a Zone Key: CLOUDSTACK-9718 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9718 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.9.0, 4.8.0, 4.7.0 Reporter: Rashmi Dixit Assignee: Rashmi Dixit Fix For: 4.10.0.0 There are a couple of issues: 1. When looking for the possible hosts for migration, not all are displayed. 2. If there is a large number of hosts, then the drop down showing is not easy to use. To fix this, propose to change the view to a list view which will show the hosts in a list view with radio button. Additionally have a search option where the hostname can be searched in this list to make it more usable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9716) baremetal:rvr:vm deployment gets stuck in starting state (waiting for notification)
Rashmi Dixit created CLOUDSTACK-9716: Summary: baremetal:rvr:vm deployment gets stuck in starting state (waiting for notification) Key: CLOUDSTACK-9716 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9716 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Baremetal Affects Versions: 4.9.0, 4.8.0, 4.7.0, 4.6.0, 4.5.0 Reporter: Rashmi Dixit Assignee: Rashmi Dixit Priority: Critical Fix For: 4.9.1.0 In normal network, vm deployment is successful (got notification properly). When we change existing the network offering to rvr for the baremetal network then vm deployment gets stuck in starting state(it has created 2 router and oxe booted properly but still waiting for notification) 1.create baremetal network 2.deploy a vm with above network. 3.destroy the vm 4.create another network offering based on RVR+barmetal 5.change network offering from normal to rvr barmetal 6. deploy a vm actual results: vm deployement stuck in starting state(it has created 2 router both master and backup and vm got pxe booted properly but CS still waiting for notification due to that vm state still showing in starting state) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9699) Metrics: Add a global setting to enable/disable Metrics view
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9699: - Fix Version/s: (was: 4.9.1.0) 4.10.0.0 > Metrics: Add a global setting to enable/disable Metrics view > > > Key: CLOUDSTACK-9699 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9699 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.10.0.0 > > > The Metrics view for each type of entity basically fires APIs and calculates > required values on the client end. For e.g. to display memory usage etc at > the zone level, it will fetch all zones. For each zone it will fetch > pods->cluster->host->VMs > For a very large Cloudstack installation this will have a major impact on the > performance. > Ideally, there should be an API which calculates all this in the backend and > the UI should simply show the values. However, for the time, introduce a > global setting called enable.metrics which will be set to false. This will > cause the metrics button not to be shown on any of the pages. > If the Admin changes this to true, then the button will be visible and > Metrics functionality will work as usual. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9695) For VM in stopped state, disable "Snapshot Memory" option
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9695: - Fix Version/s: (was: 4.9.1.0) 4.10.0.0 > For VM in stopped state, disable "Snapshot Memory" option > - > > Key: CLOUDSTACK-9695 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9695 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit >Priority: Minor > Fix For: 4.10.0.0 > > > For a VM in stopped state, the UI for VM snapshot creation shows an option > for 'snapshot memory'. Since this is not a valid option at that point, it > should be disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9700) Allow user to Register/Copy templates to multiple zones at the same time
Rashmi Dixit created CLOUDSTACK-9700: Summary: Allow user to Register/Copy templates to multiple zones at the same time Key: CLOUDSTACK-9700 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9700 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Template, UI Affects Versions: 4.9.0, 4.8.0, 4.7.0 Reporter: Rashmi Dixit Assignee: Rashmi Dixit Fix For: 4.9.1.0 A user can currently copy or register a template with only one zone at a time. The idea of this feature is to allow the user to allow copying or registering of one template to multiple zones at the same time. Both the UI and API need changes in this case. The UI for the destination zone is currently a drop down. It can be a multi-select box. The APIs need to accept destination zone as an array instead of a single ID. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9699) Metrics: Add a global setting to enable/disable Metrics view
Rashmi Dixit created CLOUDSTACK-9699: Summary: Metrics: Add a global setting to enable/disable Metrics view Key: CLOUDSTACK-9699 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9699 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.9.0, 4.8.0, 4.7.0 Reporter: Rashmi Dixit Assignee: Rashmi Dixit Fix For: 4.9.1.0 The Metrics view for each type of entity basically fires APIs and calculates required values on the client end. For e.g. to display memory usage etc at the zone level, it will fetch all zones. For each zone it will fetch pods->cluster->host->VMs For a very large Cloudstack installation this will have a major impact on the performance. Ideally, there should be an API which calculates all this in the backend and the UI should simply show the values. However, for the time, introduce a global setting called enable.metrics which will be set to false. This will cause the metrics button not to be shown on any of the pages. If the Admin changes this to true, then the button will be visible and Metrics functionality will work as usual. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9675) Cloudstack Metrics: Miscellaneous bug fixes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9675: - Description: There are a number of issues in cloudstack metrics feature 1. Goto Zone metrics or Hosts metrics. NUmerical values are not listed under Mem Usage and Mem Allocation columns. Instead 'NaN' is displayed. 2. Create a Windows instance on a Xen cluster. No IOPS data is generated or shown in the Disk Usage Tab for that Instance. 3. Changing storage.overprovisioning factor should cause changed values in storage metrics. This doesnt happen currently. 4. Allocated memory is not correctly calculated on Hosts Metrics page for a xen server with multiple instances. 5. List of Virtual Machines will be incorrect if the number is greater than the default.page.size. was: There are a number of issues in cloudstack metrics feature 1. Goto Zone metrics or Hosts metrics. NUmerical values are not listed under Mem Usage and Mem Allocation columns. Instead 'NaN' is displayed. 2. Create a Windows instance on a Xen cluster. No IOPS data is generated or shown in the Disk Usage Tab for that Instance. 3. Changing storage.overprovisioning factor should cause changed values in storage metrics. This doesnt happen currently. 4. Allocated memory is not correctly calculated on Hosts Metrics page for a xen server with multiple instances. > Cloudstack Metrics: Miscellaneous bug fixes > --- > > Key: CLOUDSTACK-9675 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9675 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.7.1 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.9.0 > > > There are a number of issues in cloudstack metrics feature > 1. Goto Zone metrics or Hosts metrics. NUmerical values are not listed under > Mem Usage and Mem Allocation columns. Instead 'NaN' is displayed. > 2. Create a Windows instance on a Xen cluster. No IOPS data is generated or > shown in the Disk Usage Tab for that Instance. > 3. Changing storage.overprovisioning factor should cause changed values in > storage metrics. This doesnt happen currently. > 4. Allocated memory is not correctly calculated on Hosts Metrics page for a > xen server with multiple instances. > 5. List of Virtual Machines will be incorrect if the number is greater than > the default.page.size. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9697) Better error message user if tries to shrink the VM ROOT volume size
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9697: - Summary: Better error message user if tries to shrink the VM ROOT volume size (was: UI should show error message user tries to shrink the VM ROOT volume size) > Better error message user if tries to shrink the VM ROOT volume size > > > Key: CLOUDSTACK-9697 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9697 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.9.1.0 > > > If a user tries to shrink the size of the root volume of a VM, the operation > fails with an error > Going from existing size of 10737418240 to size of 8589934592 would shrink > the volume.Need to sign off by supplying the shrinkok parameter with value of > true. > Instead, the UI can simply not allow shrink operation on the ROOT volume. > Throw a more user friendly message > "Shrink operation on ROOT volume not supported" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9697) UI should show error message user tries to shrink the VM ROOT volume size
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9697: - Issue Type: Bug (was: Improvement) > UI should show error message user tries to shrink the VM ROOT volume size > - > > Key: CLOUDSTACK-9697 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9697 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.9.1.0 > > > If a user tries to shrink the size of the root volume of a VM, the operation > fails with an error > Going from existing size of 10737418240 to size of 8589934592 would shrink > the volume.Need to sign off by supplying the shrinkok parameter with value of > true. > Instead, the UI can simply not allow shrink operation on the ROOT volume. > Throw a more user friendly message > "Shrink operation on ROOT volume not supported" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9697) UI should show error message user tries to shrink the VM ROOT volume size
Rashmi Dixit created CLOUDSTACK-9697: Summary: UI should show error message user tries to shrink the VM ROOT volume size Key: CLOUDSTACK-9697 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9697 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.9.0, 4.8.0, 4.7.0 Reporter: Rashmi Dixit Assignee: Rashmi Dixit Fix For: 4.9.1.0 If a user tries to shrink the size of the root volume of a VM, the operation fails with an error Going from existing size of 10737418240 to size of 8589934592 would shrink the volume.Need to sign off by supplying the shrinkok parameter with value of true. Instead, the UI can simply not allow shrink operation on the ROOT volume. Throw a more user friendly message "Shrink operation on ROOT volume not supported" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9695) For VM in stopped state, disable "Snapshot Memory" option
Rashmi Dixit created CLOUDSTACK-9695: Summary: For VM in stopped state, disable "Snapshot Memory" option Key: CLOUDSTACK-9695 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9695 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.9.0, 4.8.0, 4.7.0, 4.6.0 Reporter: Rashmi Dixit Assignee: Rashmi Dixit Priority: Minor Fix For: 4.9.1.0 For a VM in stopped state, the UI for VM snapshot creation shows an option for 'snapshot memory'. Since this is not a valid option at that point, it should be disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9693) Cluster status of an unmanaged cluster still shows enabled
Rashmi Dixit created CLOUDSTACK-9693: Summary: Cluster status of an unmanaged cluster still shows enabled Key: CLOUDSTACK-9693 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9693 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.9.0, 4.8.0, 4.7.1 Reporter: Rashmi Dixit Assignee: Rashmi Dixit Fix For: 4.9.1.0 If you unmanage a cluster, Cluster view status remains Enabled. The status is successfully changed in cluster metrics page. It should show as red if the cluster is disabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9675) Cloudstack Metrics: Miscellaneous bug fixes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9675: - Description: There are a number of issues in cloudstack metrics feature 1. Goto Zone metrics or Hosts metrics. NUmerical values are not listed under Mem Usage and Mem Allocation columns. Instead 'NaN' is displayed. 2. Create a Windows instance on a Xen cluster. No IOPS data is generated or shown in the Disk Usage Tab for that Instance. 3. Changing storage.overprovisioning factor should cause changed values in storage metrics. This doesnt happen currently. 4. Allocated memory is not correctly calculated on Hosts Metrics page for a xen server with multiple instances. was: There are a number of issues in cloudstack metrics feature 1. Goto Zone metrics or Hosts metrics. NUmerical values are not listed under Mem Usage and Mem Allocation columns. Instead 'NaN' is displayed. 2. Create a Windows instance on a Xen cluster. No IOPS data is generated or shown in the Disk Usage Tab for that Instance. 3. Changing storage.overprovisioning factor should cause changed values in storage metrics. This doesnt happen currently. 4. If a cluster is disabled, then the icon should show similar change on the cluster metrics page. Currently it shows up as red. 5. Allocated memory is not correctly calculated on Hosts Metrics page for a xen server with multiple instances. > Cloudstack Metrics: Miscellaneous bug fixes > --- > > Key: CLOUDSTACK-9675 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9675 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.7.1 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.9.0 > > > There are a number of issues in cloudstack metrics feature > 1. Goto Zone metrics or Hosts metrics. NUmerical values are not listed under > Mem Usage and Mem Allocation columns. Instead 'NaN' is displayed. > 2. Create a Windows instance on a Xen cluster. No IOPS data is generated or > shown in the Disk Usage Tab for that Instance. > 3. Changing storage.overprovisioning factor should cause changed values in > storage metrics. This doesnt happen currently. > 4. Allocated memory is not correctly calculated on Hosts Metrics page for a > xen server with multiple instances. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9675) Cloudstack Metrics: Miscellaneous bug fixes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9675: - Description: There are a number of issues in cloudstack metrics feature 1. Goto Zone metrics or Hosts metrics. NUmerical values are not listed under Mem Usage and Mem Allocation columns. Instead 'NaN' is displayed. 2. Create a Windows instance on a Xen cluster. No IOPS data is generated or shown in the Disk Usage Tab for that Instance. 3. Changing storage.overprovisioning factor should cause changed values in storage metrics. This doesnt happen currently. 4. If a cluster is disabled, then the icon should show similar change on the cluster metrics page. Currently it shows up as red. 5. Allocated memory is not correctly calculated on Hosts Metrics page for a xen server with multiple instances. was: Goto Zone metrics or Hosts metrics. NUmerical values are not listed under Mem Usage and Mem Allocation columns. Instead 'NaN' is displayed. > Cloudstack Metrics: Miscellaneous bug fixes > --- > > Key: CLOUDSTACK-9675 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9675 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.7.1 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.9.0 > > > There are a number of issues in cloudstack metrics feature > 1. Goto Zone metrics or Hosts metrics. NUmerical values are not listed under > Mem Usage and Mem Allocation columns. Instead 'NaN' is displayed. > 2. Create a Windows instance on a Xen cluster. No IOPS data is generated or > shown in the Disk Usage Tab for that Instance. > 3. Changing storage.overprovisioning factor should cause changed values in > storage metrics. This doesnt happen currently. > 4. If a cluster is disabled, then the icon should show similar change on the > cluster metrics page. Currently it shows up as red. > 5. Allocated memory is not correctly calculated on Hosts Metrics page for a > xen server with multiple instances. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9675) Cloudstack Metrics: Miscellaneous bug fixes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit updated CLOUDSTACK-9675: - Summary: Cloudstack Metrics: Miscellaneous bug fixes (was: Cloudstack Metrics: Mem Usage and Mem Allocation for all views do not list values. 'NnN' is displayed instead) > Cloudstack Metrics: Miscellaneous bug fixes > --- > > Key: CLOUDSTACK-9675 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9675 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.7.1 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.9.0 > > > Goto Zone metrics or Hosts metrics. NUmerical values are not listed under Mem > Usage and Mem Allocation columns. Instead 'NaN' is displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9678) listNetworkOfferings API is listing all the offerings which has same prefix in their name
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rashmi Dixit updated CLOUDSTACK-9678:
-
Assignee: (was: Rashmi Dixit)
> listNetworkOfferings API is listing all the offerings which has same prefix
> in their name
> -
>
> Key: CLOUDSTACK-9678
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9678
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Reporter: pallavi Dumbre
>
> steps to reproduce
> ---
> 1-list network offering with name=DefaultIsolatedNetworkOfferingForVpcNetworks
> expected
> -
> result should have service offering with specified name
> actual
> -
> result is listing all service offering , which has prefix
> DefaultIsolatedNetworkOfferingForVpcNetworks* in their name
> http://10.147.38.204:8080/client/api?command=listNetworkOfferings=json=true=1=20&_=1462168939385=DefaultIsolatedNetworkOfferingForVpcNetworks
> result
> {"listnetworkofferingsresponse":{"count":3,"networkoffering":[{"id":"2a103f96-cd94-4194-8441-6fdf419e403c","name":"DefaultIsolatedNetworkOfferingForVpcNetworks","displaytext":"Offering
> for Isolated Vpc networks with Source Nat service
> enabled","traffictype":"Guest","isdefault":true,"specifyvlan":false,"conservemode":false,"specifyipranges":false,"availability":"Optional","networkrate":200,"state":"Enabled","guestiptype":"Isolated","serviceofferingid":"9d1e424e-d762-4ab5-b614-f1ae36347558","service":[{"name":"Dhcp","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"SourceNat","provider":[
> {"name":"VpcVirtualRouter"}
> ],"capability":[
> {"name":"SupportedSourceNatTypes","value":"peraccount","canchooseservicecapability":false}
> ,
> {"name":"RedundantRouter","value":"false","canchooseservicecapability":false}
> ]},{"name":"UserData","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"NetworkACL","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"Lb","provider":[
> {"name":"VpcVirtualRouter"}
> ],"capability":[
> {"name":"SupportedLBIsolation","value":"dedicated","canchooseservicecapability":false}
> ,
> {"name":"ElasticLb","value":"false","canchooseservicecapability":false}
> ,
> {"name":"InlineMode","value":"false","canchooseservicecapability":false}
> ]},{"name":"StaticNat","provider":[
> {"name":"VpcVirtualRouter"}
> ],"capability":[
> {"name":"ElasticIp","value":"false","canchooseservicecapability":false}
> ,
> {"name":"AssociatePublicIP","value":"true","canchooseservicecapability":false}
> ]},{"name":"Dns","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"Vpn","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"PortForwarding","provider":[
> {"name":"VpcVirtualRouter"}
> ]}],"forvpc":true,"ispersistent":false,"egressdefaultpolicy":false,"supportsstrechedl2subnet":false},{"id":"c698be56-5612-4a2d-99da-d958cdeb32bc","name":"DefaultIsolatedNetworkOfferingForVpcNetworksNoLB","displaytext":"Offering
> for Isolated Vpc networks with Source Nat service enabled and LB service
> Disabled","traffictype":"Guest","isdefault":true,"specifyvlan":false,"conservemode":false,"specifyipranges":false,"availability":"Optional","networkrate":200,"state":"Enabled","guestiptype":"Isolated","serviceofferingid":"9d1e424e-d762-4ab5-b614-f1ae36347558","service":[{"name":"Dhcp","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"SourceNat","provider":[
> {"name":"VpcVirtualRouter"}
> ],"capability":[
> {"name":"SupportedSourceNatTypes","value":"peraccount","canchooseservicecapability":false}
> ,
> {"name":"RedundantRouter","value":"false","canchooseservicecapability":false}
> ]},{"name":"UserData","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"NetworkACL","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"StaticNat","provider":[
> {"name":"VpcVirtualRouter"}
> ],"capability":[
> {"name":"ElasticIp","value":"false","canchooseservicecapability":false}
> ,
> {"name":"AssociatePublicIP","value":"true","canchooseservicecapability":false}
> ]},{"name":"Dns","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"Vpn","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"PortForwarding","provider":[
> {"name":"VpcVirtualRouter"}
> ]}],"forvpc":true,"ispersistent":false,"egressdefaultpolicy":false,"supportsstrechedl2subnet":false},{"id":"6f8dc0da-8970-4e0c-8d22-71e46562df18","name":"DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB","displaytext":"Offering
> for Isolated Vpc networks with Internal LB
>
[jira] [Assigned] (CLOUDSTACK-9678) listNetworkOfferings API is listing all the offerings which has same prefix in their name
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rashmi Dixit reassigned CLOUDSTACK-9678:
Assignee: Rashmi Dixit
> listNetworkOfferings API is listing all the offerings which has same prefix
> in their name
> -
>
> Key: CLOUDSTACK-9678
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9678
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Reporter: pallavi Dumbre
>Assignee: Rashmi Dixit
>
> steps to reproduce
> ---
> 1-list network offering with name=DefaultIsolatedNetworkOfferingForVpcNetworks
> expected
> -
> result should have service offering with specified name
> actual
> -
> result is listing all service offering , which has prefix
> DefaultIsolatedNetworkOfferingForVpcNetworks* in their name
> http://10.147.38.204:8080/client/api?command=listNetworkOfferings=json=true=1=20&_=1462168939385=DefaultIsolatedNetworkOfferingForVpcNetworks
> result
> {"listnetworkofferingsresponse":{"count":3,"networkoffering":[{"id":"2a103f96-cd94-4194-8441-6fdf419e403c","name":"DefaultIsolatedNetworkOfferingForVpcNetworks","displaytext":"Offering
> for Isolated Vpc networks with Source Nat service
> enabled","traffictype":"Guest","isdefault":true,"specifyvlan":false,"conservemode":false,"specifyipranges":false,"availability":"Optional","networkrate":200,"state":"Enabled","guestiptype":"Isolated","serviceofferingid":"9d1e424e-d762-4ab5-b614-f1ae36347558","service":[{"name":"Dhcp","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"SourceNat","provider":[
> {"name":"VpcVirtualRouter"}
> ],"capability":[
> {"name":"SupportedSourceNatTypes","value":"peraccount","canchooseservicecapability":false}
> ,
> {"name":"RedundantRouter","value":"false","canchooseservicecapability":false}
> ]},{"name":"UserData","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"NetworkACL","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"Lb","provider":[
> {"name":"VpcVirtualRouter"}
> ],"capability":[
> {"name":"SupportedLBIsolation","value":"dedicated","canchooseservicecapability":false}
> ,
> {"name":"ElasticLb","value":"false","canchooseservicecapability":false}
> ,
> {"name":"InlineMode","value":"false","canchooseservicecapability":false}
> ]},{"name":"StaticNat","provider":[
> {"name":"VpcVirtualRouter"}
> ],"capability":[
> {"name":"ElasticIp","value":"false","canchooseservicecapability":false}
> ,
> {"name":"AssociatePublicIP","value":"true","canchooseservicecapability":false}
> ]},{"name":"Dns","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"Vpn","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"PortForwarding","provider":[
> {"name":"VpcVirtualRouter"}
> ]}],"forvpc":true,"ispersistent":false,"egressdefaultpolicy":false,"supportsstrechedl2subnet":false},{"id":"c698be56-5612-4a2d-99da-d958cdeb32bc","name":"DefaultIsolatedNetworkOfferingForVpcNetworksNoLB","displaytext":"Offering
> for Isolated Vpc networks with Source Nat service enabled and LB service
> Disabled","traffictype":"Guest","isdefault":true,"specifyvlan":false,"conservemode":false,"specifyipranges":false,"availability":"Optional","networkrate":200,"state":"Enabled","guestiptype":"Isolated","serviceofferingid":"9d1e424e-d762-4ab5-b614-f1ae36347558","service":[{"name":"Dhcp","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"SourceNat","provider":[
> {"name":"VpcVirtualRouter"}
> ],"capability":[
> {"name":"SupportedSourceNatTypes","value":"peraccount","canchooseservicecapability":false}
> ,
> {"name":"RedundantRouter","value":"false","canchooseservicecapability":false}
> ]},{"name":"UserData","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"NetworkACL","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"StaticNat","provider":[
> {"name":"VpcVirtualRouter"}
> ],"capability":[
> {"name":"ElasticIp","value":"false","canchooseservicecapability":false}
> ,
> {"name":"AssociatePublicIP","value":"true","canchooseservicecapability":false}
> ]},{"name":"Dns","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"Vpn","provider":[
> {"name":"VpcVirtualRouter"}
> ]},{"name":"PortForwarding","provider":[
> {"name":"VpcVirtualRouter"}
> ]}],"forvpc":true,"ispersistent":false,"egressdefaultpolicy":false,"supportsstrechedl2subnet":false},{"id":"6f8dc0da-8970-4e0c-8d22-71e46562df18","name":"DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB","displaytext":"Offering
> for Isolated Vpc networks with Internal LB
>
[jira] [Created] (CLOUDSTACK-9675) Cloudstack Metrics: Mem Usage and Mem Allocation for all views do not list values. 'NnN' is displayed instead
Rashmi Dixit created CLOUDSTACK-9675: Summary: Cloudstack Metrics: Mem Usage and Mem Allocation for all views do not list values. 'NnN' is displayed instead Key: CLOUDSTACK-9675 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9675 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.7.1 Reporter: Rashmi Dixit Assignee: Rashmi Dixit Fix For: 4.9.0 Goto Zone metrics or Hosts metrics. NUmerical values are not listed under Mem Usage and Mem Allocation columns. Instead 'NaN' is displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashmi Dixit reassigned CLOUDSTACK-9653: Assignee: Rashmi Dixit > listCapacity API shows incorrect output when sortBy=usage option is added > - > > Key: CLOUDSTACK-9653 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0 >Reporter: Rashmi Dixit >Assignee: Rashmi Dixit > Fix For: 4.9.1.0 > > > listCapacity API does not sum up values correctly when used with sortBy=usage > option. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added
Rashmi Dixit created CLOUDSTACK-9653: Summary: listCapacity API shows incorrect output when sortBy=usage option is added Key: CLOUDSTACK-9653 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.9.0, 4.8.0, 4.7.0, 4.6.0 Reporter: Rashmi Dixit Fix For: 4.9.1.0 listCapacity API does not sum up values correctly when used with sortBy=usage option. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9377) Metrics data incorrectly calculated in zone/cluster metrics view
Rashmi Dixit created CLOUDSTACK-9377: Summary: Metrics data incorrectly calculated in zone/cluster metrics view Key: CLOUDSTACK-9377 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9377 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.7.0 Reporter: Rashmi Dixit In the zone metrics view, listClusters and listHosts APIs are being used to compute average used and allocated data for metrics calculations. Issue: 1. All APIs have a default pagesize. Count of results are always equal to the default pagesize if not explicitly passed. The UI is not passing anything related to pagesize to these APIs 2. Example to explain issue 600 hosts in a cluster. Default Page size = 500. There is only one call to fetch clusters. This will fetch a maximum of 500 records. If there are more, then these aren't fetched. For each cluster, listHosts is called to fetch hosts. Since page size is 500 only 500 results are returned. Computation for 500 hosts is done but for calculating average this value is divided by 600. This is incorrect. UI should fetch all hosts in one go and correctly calculate metrics. However, this will result in performance degradation as number of hosts/clusters increase. Ideally a new API needs to be introduced for this metrics calculation. Same issue is present in the cluster metrics view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
