[jira] [Updated] (CLOUDSTACK-10106) GPU/vGPU Support on VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10106: -- Description: VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on ESXi hosts to use the GPU cards connected to it. Currently, it supports only NVIDIA GRID K1 and K2 cards for CloudStack VMs. Feature Specification: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681765 was: VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on ESXi hosts to use the GPU cards connected to it. Currently, it supports only NVIDIA GRID K1 and K2 cards for CloudStack VMs. FS: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681765 > GPU/vGPU Support on VMWare > -- > > Key: CLOUDSTACK-10106 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10106 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI, VMware >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Labels: VMWARE > Fix For: 4.11.0.0 > > > VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well > as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on > ESXi hosts to use the GPU cards connected to it. Currently, it supports only > NVIDIA GRID K1 and K2 cards for CloudStack VMs. > Feature Specification: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681765 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CLOUDSTACK-10106) GPU/vGPU Support on VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266013#comment-16266013 ] Nitin Kumar Maharana commented on CLOUDSTACK-10106: --- Hi [~haijiao], I have created a PR with Tesla M60 card added in CloudStack. If you have NVIDIA Tesla M60 card available in the lab, please feel free to test the change and report the result. PR: https://github.com/apache/cloudstack/pull/2339 Thanks, Nitin > GPU/vGPU Support on VMWare > -- > > Key: CLOUDSTACK-10106 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10106 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI, VMware >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Labels: VMWARE > Fix For: 4.11.0.0 > > > VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well > as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on > ESXi hosts to use the GPU cards connected to it. Currently, it supports only > NVIDIA GRID K1 and K2 cards for CloudStack VMs. > FS: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681765 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CLOUDSTACK-10159) Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10159: -- Description: Introduction: == Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 6.5 SP1 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs.(Only on M60-8Q, M60-4Q, M60-2Q, M60-1Q, M60-0Q) 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). Tesla M60 Virtual GPU Types: === ||Physical GPUs||GRID Virtual GPU||Frame Buffer (MB)||Virtual Display Heads||Maximum Resolution per Display Head||Maximum vGPUs per GPU||Maximum vGPU per Board|| |2|M60-8Q|8192|4|4096×2160|1|2| |2|M60-4Q|4096|4|4096×2160|2|4| |2|M60-2Q|2048|4|4096×2160|4|8| |2|M60-1Q|1024|2|4096×2160|8|16| |2|M60-0Q|512|2|2560×1600|16|32| |2|M60-1B|1024|4|2560×1600|8|16| |2|M60-0B|512|2|2560×1600|16|32| |2|M60-8A|8192|1|1280×1024|1|2| |2|M60-4A|4096|1|1280×1024|2|4| |2|M60-2A|2048|1|1280×1024|4|8| |2|M60-1A|1024|1|1280×1024|8|16| Reference: [1] https://www.citrix.com/blogs/2015/11/06/nvidia-m60-support-on-xenserver/ [2] http://hcl.xenserver.org/gpus/28/Nvidia_Tesla_M60 [3] http://images.nvidia.com/content/grid/pdf/GRID-vGPU-User-Guide.pdf was: Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 6.5 SP1 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs.(Only on M60-8Q, M60-4Q, M60-2Q, M60-1Q, M60-0Q) 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). Tesla M60 Virtual GPU types: === ||Physical GPUs||GRID Virtual GPU||Frame Buffer (MB)||Virtual Display Heads||Maximum Resolution per Display Head||Maximum vGPUs per GPU||Maximum vGPU per Board|| |2|M60-8Q|8192|4|4096×2160|1|2| |2|M60-4Q|4096|4|4096×2160|2|4| |2|M60-2Q|2048|4|4096×2160|4|8| |2|M60-1Q|1024|2|4096×2160|8|16| |2|M60-0Q|512|2|2560×1600|16|32| |2|M60-1B|1024|4|2560×1600|8|16| |2|M60-0B|512|2|2560×1600|16|32| |2|M60-8A|8192|1|1280×1024|1|2| |2|M60-4A|4096|1|1280×1024|2|4| |2|M60-2A|2048|1|1280×1024|4|8| |2|M60-1A|1024|1|1280×1024|8|16| Reference: [1] https://www.citrix.com/blogs/2015/11/06/nvidia-m60-support-on-xenserver/ [2] http://hcl.xenserver.org/gpus/28/Nvidia_Tesla_M60 [3] http://images.nvidia.com/content/grid/pdf/GRID-vGPU-User-Guide.pdf > Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1) > --- > > Key: CLOUDSTACK-10159 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10159 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > > Introduction: > == > Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 > cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support > for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU > features. This improvement would allow the user to get benefits of Telsa GPU > cards while deploying a VM with GPU enabled. > Benefits of Tesla M60: > = > 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. > 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 > VMs on a XenServer 6.5 SP1 host. > 3. Now It can run on a blade server and supports vGPU on Linux VMs.(Only on > M60-8Q, M60-4Q, M60-2Q, M60-1Q, M60-0Q) > 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. > 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). > Tesla M60
[jira] [Updated] (CLOUDSTACK-10159) Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10159: -- Description: Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 6.5 SP1 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs.(Only on M60-8Q, M60-4Q, M60-2Q, M60-1Q, M60-0Q) 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). Tesla M60 Virtual GPU types: === ||Physical GPUs||GRID Virtual GPU||Frame Buffer (MB)||Virtual Display Heads||Maximum Resolution per Display Head||Maximum vGPUs per GPU||Maximum vGPU per Board|| |2|M60-8Q|8192|4|4096×2160|1|2| |2|M60-4Q|4096|4|4096×2160|2|4| |2|M60-2Q|2048|4|4096×2160|4|8| |2|M60-1Q|1024|2|4096×2160|8|16| |2|M60-0Q|512|2|2560×1600|16|32| |2|M60-1B|1024|4|2560×1600|8|16| |2|M60-0B|512|2|2560×1600|16|32| |2|M60-8A|8192|1|1280×1024|1|2| |2|M60-4A|4096|1|1280×1024|2|4| |2|M60-2A|2048|1|1280×1024|4|8| |2|M60-1A|1024|1|1280×1024|8|16| Reference: [1] https://www.citrix.com/blogs/2015/11/06/nvidia-m60-support-on-xenserver/ [2] http://hcl.xenserver.org/gpus/28/Nvidia_Tesla_M60 [3] http://images.nvidia.com/content/grid/pdf/GRID-vGPU-User-Guide.pdf was: Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 6.5 SP1 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs.(Only on M60-8Q, M60-4Q, M60-2Q, M60-1Q, M60-0Q) 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). Tesla M60 Virtual GPU types: === ||Heading 1||Heading 2|| |Col A1|Col A2| Reference: [1] https://www.citrix.com/blogs/2015/11/06/nvidia-m60-support-on-xenserver/ [2] http://hcl.xenserver.org/gpus/28/Nvidia_Tesla_M60 [3] http://images.nvidia.com/content/grid/pdf/GRID-vGPU-User-Guide.pdf > Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1) > --- > > Key: CLOUDSTACK-10159 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10159 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > > Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 > cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support > for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU > features. This improvement would allow the user to get benefits of Telsa GPU > cards while deploying a VM with GPU enabled. > Benefits of Tesla M60: > = > 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. > 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 > VMs on a XenServer 6.5 SP1 host. > 3. Now It can run on a blade server and supports vGPU on Linux VMs.(Only on > M60-8Q, M60-4Q, M60-2Q, M60-1Q, M60-0Q) > 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. > 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). > Tesla M60 Virtual GPU types: > === > ||Physical GPUs||GRID Virtual GPU||Frame Buffer (MB)||Virtual Display > Heads||Maximum Resolution per Display Head||Maximum vGPUs per GPU||Maximum > vGPU per Board|| > |2|M60-8Q|8192|4|4096×2160|1|2| > |2|M60-4Q|4096|4|4096×2160|2|4| > |2|M60-2Q|2048|4|4096×2160|4|8| > |2|M60-1Q|1024|2|4096×2160|8|16| > |2|M60-0Q|512|2|2560×1600|16|32| > |2|M60-1B|1024|4|2560×1600|8|16| > |2|M60-0B|512|2|2560×1600|16|32| > |2|M60-8A|8192|1|1280×1024|1|2| > |2|M60-4A|4096|1|1280×1024|2|4| >
[jira] [Updated] (CLOUDSTACK-10159) Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10159: -- Description: Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 6.5 SP1 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs.(Only on M60-8Q, M60-4Q, M60-2Q, M60-1Q, M60-0Q) 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). Tesla M60 Virtual GPU types: === ||Heading 1||Heading 2|| |Col A1|Col A2| Reference: [1] https://www.citrix.com/blogs/2015/11/06/nvidia-m60-support-on-xenserver/ [2] http://hcl.xenserver.org/gpus/28/Nvidia_Tesla_M60 [3] http://images.nvidia.com/content/grid/pdf/GRID-vGPU-User-Guide.pdf was: Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 6.5 SP1 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs. 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). Reference: [1] https://www.citrix.com/blogs/2015/11/06/nvidia-m60-support-on-xenserver/ [2] http://hcl.xenserver.org/gpus/28/Nvidia_Tesla_M60 > Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1) > --- > > Key: CLOUDSTACK-10159 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10159 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > > Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 > cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support > for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU > features. This improvement would allow the user to get benefits of Telsa GPU > cards while deploying a VM with GPU enabled. > Benefits of Tesla M60: > = > 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. > 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 > VMs on a XenServer 6.5 SP1 host. > 3. Now It can run on a blade server and supports vGPU on Linux VMs.(Only on > M60-8Q, M60-4Q, M60-2Q, M60-1Q, M60-0Q) > 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. > 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). > Tesla M60 Virtual GPU types: > === > ||Heading 1||Heading 2|| > |Col A1|Col A2| > Reference: > > [1] https://www.citrix.com/blogs/2015/11/06/nvidia-m60-support-on-xenserver/ > [2] http://hcl.xenserver.org/gpus/28/Nvidia_Tesla_M60 > [3] http://images.nvidia.com/content/grid/pdf/GRID-vGPU-User-Guide.pdf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CLOUDSTACK-10159) Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10159: -- Description: Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 6.5 SP1 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs. 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). Reference: [1] https://www.citrix.com/blogs/2015/11/06/nvidia-m60-support-on-xenserver/ [2] http://hcl.xenserver.org/gpus/28/Nvidia_Tesla_M60 was: Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 6.5 SP1 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs. 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). > Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1) > --- > > Key: CLOUDSTACK-10159 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10159 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > > Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 > cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support > for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU > features. This improvement would allow the user to get benefits of Telsa GPU > cards while deploying a VM with GPU enabled. > Benefits of Tesla M60: > = > 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. > 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 > VMs on a XenServer 6.5 SP1 host. > 3. Now It can run on a blade server and supports vGPU on Linux VMs. > 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. > 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). > Reference: > > [1] https://www.citrix.com/blogs/2015/11/06/nvidia-m60-support-on-xenserver/ > [2] http://hcl.xenserver.org/gpus/28/Nvidia_Tesla_M60 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CLOUDSTACK-10159) Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10159: -- Description: Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 6.5 SP1 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs. 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). was: Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 7.0 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs. 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). > Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1) > --- > > Key: CLOUDSTACK-10159 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10159 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > > Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 > cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support > for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU > features. This improvement would allow the user to get benefits of Telsa GPU > cards while deploying a VM with GPU enabled. > Benefits of Tesla M60: > = > 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. > 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 > VMs on a XenServer 6.5 SP1 host. > 3. Now It can run on a blade server and supports vGPU on Linux VMs. > 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. > 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CLOUDSTACK-10159) Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10159: -- Summary: Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1) (was: Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 7.0)) > Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1) > --- > > Key: CLOUDSTACK-10159 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10159 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > > Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 > cards only on the XenServer Host. Now, XenServer 7.0 has added support for > NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU > features. This improvement would allow the user to get benefits of Telsa GPU > cards while deploying a VM with GPU enabled. > Benefits of Tesla M60: > = > 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. > 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 > VMs on a XenServer 7.0 host. > 3. Now It can run on a blade server and supports vGPU on Linux VMs. > 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. > 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CLOUDSTACK-10159) Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10159: -- Description: Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 7.0 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs. 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). was: Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 7.0 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 7.0 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs. 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). > Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 6.5 SP1) > --- > > Key: CLOUDSTACK-10159 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10159 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > > Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 > cards only on the XenServer Host. Now, XenServer 6.5 SP1 has added support > for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU > features. This improvement would allow the user to get benefits of Telsa GPU > cards while deploying a VM with GPU enabled. > Benefits of Tesla M60: > = > 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. > 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 > VMs on a XenServer 7.0 host. > 3. Now It can run on a blade server and supports vGPU on Linux VMs. > 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. > 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CLOUDSTACK-10159) Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 7.0)
Nitin Kumar Maharana created CLOUDSTACK-10159: - Summary: Addition of NVIDIA Tesla M60 card in CloudStack (XenServer 7.0) Key: CLOUDSTACK-10159 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10159 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.11.0.0 Reporter: Nitin Kumar Maharana Fix For: 4.11.0.0 Currently, CloudStack gets GPU capability through NVIDIA GRID K1 and GRID K2 cards only on the XenServer Host. Now, XenServer 7.0 has added support for NVIDIA Maxwell card(Tesla M60), which supports both Passthrough and vGPU features. This improvement would allow the user to get benefits of Telsa GPU cards while deploying a VM with GPU enabled. Benefits of Tesla M60: = 1. The Tesla M60 card supports latest NVIDIA GRID 2.0 technology. 2. The Tesla M60 can run more VMs per server. It supports a maximum of 128 VMs on a XenServer 7.0 host. 3. Now It can run on a blade server and supports vGPU on Linux VMs. 4. The Tesla M60 card supports a maximum resolution of 2560 X 1600. 5. Tesla M60 has a maximum CUDA core of 4096 on both the GPUs (2048 each). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CLOUDSTACK-10158) Icon over deploy instance from vmsnapshot via Storage - VM Snapshots path is missing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265794#comment-16265794 ] Nitin Kumar Maharana commented on CLOUDSTACK-10158: --- This issue is handled in PR: https://github.com/apache/cloudstack/pull/2338 > Icon over deploy instance from vmsnapshot via Storage - VM Snapshots path is > missing > > > Key: CLOUDSTACK-10158 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10158 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.11.0.0 > Environment: VMware >Reporter: Nitin Kumar Maharana > Labels: instance, snapshot, vmware > Fix For: 4.11.0.0 > > > Deploy VM instance from VM snapshot via Storage - VM Snapshots path is > missing from the UI. > Steps to Reproduce: > > 1. Deploy a VM and create VM snapshot > 2. Navigate to VM snapshot via the following route. > 3. Select "Storage" Tab > 4. Select "VM snapshot" from drop down > 5. Click on created VM snapshot > Observation: > == > Icon for Deploy VM instance is not visible on UI > Expected: > > Icon for Deploy VM instance should be visible on UI > Note: > > But the icon for same option can be seen when VM snapshot is accessed via > Instance path > The issue is dependent on CLOUDSTACK-8676. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CLOUDSTACK-10158) Icon over deploy instance from vmsnapshot via Storage - VM Snapshots path is missing
Nitin Kumar Maharana created CLOUDSTACK-10158: - Summary: Icon over deploy instance from vmsnapshot via Storage - VM Snapshots path is missing Key: CLOUDSTACK-10158 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10158 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.11.0.0 Environment: VMware Reporter: Nitin Kumar Maharana Fix For: 4.11.0.0 Deploy VM instance from VM snapshot via Storage - VM Snapshots path is missing from the UI. Steps to Reproduce: 1. Deploy a VM and create VM snapshot 2. Navigate to VM snapshot via the following route. 3. Select "Storage" Tab 4. Select "VM snapshot" from drop down 5. Click on created VM snapshot Observation: == Icon for Deploy VM instance is not visible on UI Expected: Icon for Deploy VM instance should be visible on UI Note: But the icon for same option can be seen when VM snapshot is accessed via Instance path The issue is dependent on CLOUDSTACK-8676. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CLOUDSTACK-10157) Wrong notification while migration
Nitin Kumar Maharana created CLOUDSTACK-10157: - Summary: Wrong notification while migration Key: CLOUDSTACK-10157 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10157 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.11.0.0 Reporter: Nitin Kumar Maharana Fix For: 4.11.0.0 RETRO STEPS: 1. Had three hosts in one cluster, two of them with GPU cards NVIDIA GRID K1 and K2 and one normal host. 2. Deployed a VM with K2 vgpu. 3. Stopped the VM and tried starting it on a different host. (Expected it to fail as there is only one host supporting that particular vgpu type) 4. The log showed it as failed operation, VM remained in the stopped state, yet the notification showed "Start Instance" as successful and no error message was displayed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CLOUDSTACK-10106) GPU/vGPU Support on VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245874#comment-16245874 ] Nitin Kumar Maharana commented on CLOUDSTACK-10106: --- [~haijiao], Addition of new cards is under development. I will publish once it is finished. Thanks! > GPU/vGPU Support on VMWare > -- > > Key: CLOUDSTACK-10106 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10106 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI, VMware >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Labels: VMWARE > Fix For: 4.11.0.0 > > > VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well > as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on > ESXi hosts to use the GPU cards connected to it. Currently, it supports only > NVIDIA GRID K1 and K2 cards for CloudStack VMs. > FS: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681765 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CLOUDSTACK-10106) GPU/vGPU Support on VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10106: -- Labels: VMWARE (was: ) Description: VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on ESXi hosts to use the GPU cards connected to it. Currently, it supports only NVIDIA GRID K1 and K2 cards for CloudStack VMs. FS: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681765 was:VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on ESXi hosts to use the GPU cards connected to it. Currently, it supports only NVIDIA GRID K1 and K2 cards for CloudStack VMs. > GPU/vGPU Support on VMWare > -- > > Key: CLOUDSTACK-10106 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10106 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI, VMware >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Labels: VMWARE > Fix For: 4.11.0.0 > > > VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well > as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on > ESXi hosts to use the GPU cards connected to it. Currently, it supports only > NVIDIA GRID K1 and K2 cards for CloudStack VMs. > FS: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681765 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CLOUDSTACK-10106) GPU/vGPU Support on VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10106: -- Description: VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on ESXi hosts to use the GPU cards connected to it. Currently it supports only NVIDIA GRID K1 and K2 cards for CloudStack VMs. (was: VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards. This feature allows CloudStack VMs on ESXi hosts to use the GPU cards connected to it. Currently it supports only NVIDIA GRID K1 and K2 cards for CloudStack VMs.) > GPU/vGPU Support on VMWare > -- > > Key: CLOUDSTACK-10106 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10106 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI, VMware >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > > VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well > as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on > ESXi hosts to use the GPU cards connected to it. Currently it supports only > NVIDIA GRID K1 and K2 cards for CloudStack VMs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CLOUDSTACK-10106) GPU/vGPU Support on VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10106: -- Description: VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on ESXi hosts to use the GPU cards connected to it. Currently, it supports only NVIDIA GRID K1 and K2 cards for CloudStack VMs. (was: VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on ESXi hosts to use the GPU cards connected to it. Currently it supports only NVIDIA GRID K1 and K2 cards for CloudStack VMs.) > GPU/vGPU Support on VMWare > -- > > Key: CLOUDSTACK-10106 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10106 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI, VMware >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > > VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards as well > as NVIDIA Tesla M6 and Tesla M60 cards. This feature allows CloudStack VMs on > ESXi hosts to use the GPU cards connected to it. Currently, it supports only > NVIDIA GRID K1 and K2 cards for CloudStack VMs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CLOUDSTACK-10106) GPU/vGPU Support on VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10106: -- Description: VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards. This feature allows CloudStack VMs on ESXi hosts to use the GPU cards connected to it. Currently it supports only NVIDIA GRID K1 and K2 cards for CloudStack VMs. (was: VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards. This feature will enable CloudStack users to deploy VM with GPU capability in VMware host.) > GPU/vGPU Support on VMWare > -- > > Key: CLOUDSTACK-10106 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10106 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI, VMware >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > > VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards. This > feature allows CloudStack VMs on ESXi hosts to use the GPU cards connected to > it. Currently it supports only NVIDIA GRID K1 and K2 cards for CloudStack VMs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CLOUDSTACK-10106) GPU/vGPU Support on VMWare
Nitin Kumar Maharana created CLOUDSTACK-10106: - Summary: GPU/vGPU Support on VMWare Key: CLOUDSTACK-10106 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10106 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Components: API, UI, VMware Affects Versions: 4.11.0.0 Reporter: Nitin Kumar Maharana Fix For: 4.11.0.0 VMware has added support for NVIDIA GRID K1 and NVIDIA GRID K2 cards. This feature will enable CloudStack users to deploy VM with GPU capability in VMware host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CLOUDSTACK-10099) GUI invokes migrateVirtualMachine instead of migrateVirtualMachineWithVolume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185346#comment-16185346 ] Nitin Kumar Maharana commented on CLOUDSTACK-10099: --- Amazing. Thanks, Mike!! Can you please raise a PR if you have made the code changes. -- Nitin > GUI invokes migrateVirtualMachine instead of migrateVirtualMachineWithVolume > > > Key: CLOUDSTACK-10099 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10099 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.11.0.0 > Environment: All >Reporter: Mike Tutkowski > Fix For: 4.11.0.0 > > > I have a VM whose root disk in on zone-wide, managed storage. > When I go to migrate the VM to a host in another cluster, the GUI correctly > points out that to migrate the VM to the desired host that storage migration > will be required. > Since I am good with both the VM and its disk being migrated, I initiate the > action. > The GUI ends up invoking the migrateVirtualMachine API command instead of the > migrateVirtualMachineWithVolume API command, which causes the process to > fail. The process does fail gracefully (nothing seems to be left in a bad > state). > If I invoke the migrateVirtualMachineWithVolume API command from CloudMonkey > and pass in the necessary parameters, the migration is successful. > I know this used to work from the GUI at some point in 4.10 development > because I recorded a video demonstrating this feature as executed from the > GUI: > https://www.youtube.com/watch?v=_pbnvQxTAqw=1006s=PLqOXKM0Bt13DFnQnwUx8ZtJzoyDV0Uuye=17 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CLOUDSTACK-10066) VM Snapshots in Hyper-V
Nitin Kumar Maharana created CLOUDSTACK-10066: - Summary: VM Snapshots in Hyper-V Key: CLOUDSTACK-10066 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10066 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana FS: https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+Snapshots+in+Hyper-V -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CLOUDSTACK-10059) Dashboard ignores resource value that is less than 1%
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148699#comment-16148699 ] Nitin Kumar Maharana commented on CLOUDSTACK-10059: --- GitHub PR: https://github.com/apache/cloudstack/pull/2255 > Dashboard ignores resource value that is less than 1% > - > > Key: CLOUDSTACK-10059 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10059 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.10.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > > If the resources' percentage is less than 1, Dashboard just displays % symbol. > In the screenshot attached, the Primary storage is 21.19GB/10.74GB which is > 0.19%, but that percentage is not displayed. > Also, in the GPU tab, it has to display 0% instead of just % when none of the > GPUs are in use. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CLOUDSTACK-10059) Dashboard ignores resource value that is less than 1%
Nitin Kumar Maharana created CLOUDSTACK-10059: - Summary: Dashboard ignores resource value that is less than 1% Key: CLOUDSTACK-10059 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10059 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.10.0.0 Reporter: Nitin Kumar Maharana Fix For: 4.11.0.0 If the resources' percentage is less than 1, Dashboard just displays % symbol. In the screenshot attached, the Primary storage is 21.19GB/10.74GB which is 0.19%, but that percentage is not displayed. Also, in the GPU tab, it has to display 0% instead of just % when none of the GPUs are in use. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CLOUDSTACK-10058) Error while opening the Settings tab in Secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148676#comment-16148676 ] Nitin Kumar Maharana commented on CLOUDSTACK-10058: --- GitHub PR: https://github.com/apache/cloudstack/pull/2254 > Error while opening the Settings tab in Secondary storage > - > > Key: CLOUDSTACK-10058 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10058 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.10.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > Attachments: After.png, Before.png > > > Home –>Infrastructure --> Secondary Storage --> --> Settings > The settings tab is not getting displayed. Find the attached pic. The api > results in null. > http://10.147.38.180:8080/client/api?command=listConfigurations=7c66dfc2-6f86-44b9-a55e-9b9a332a7465==true=1=20&_=1503979900913 > : > > 431 > > null > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CLOUDSTACK-10058) Error while opening the Settings tab in Secondary storage
Nitin Kumar Maharana created CLOUDSTACK-10058: - Summary: Error while opening the Settings tab in Secondary storage Key: CLOUDSTACK-10058 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10058 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.10.0.0 Reporter: Nitin Kumar Maharana Fix For: 4.11.0.0 Attachments: After.png, Before.png Home –>Infrastructure --> Secondary Storage --> --> Settings The settings tab is not getting displayed. Find the attached pic. The api results in null. http://10.147.38.180:8080/client/api?command=listConfigurations=7c66dfc2-6f86-44b9-a55e-9b9a332a7465==true=1=20&_=1503979900913 : 431 null -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CLOUDSTACK-10050) Improvements to NCC integration with CloudStack Feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-10050: -- Issue Type: Improvement (was: Bug) > Improvements to NCC integration with CloudStack Feature > --- > > Key: CLOUDSTACK-10050 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10050 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, UI >Affects Versions: 4.11.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.11.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CLOUDSTACK-10050) Improvements to NCC integration with CloudStack Feature
Nitin Kumar Maharana created CLOUDSTACK-10050: - Summary: Improvements to NCC integration with CloudStack Feature Key: CLOUDSTACK-10050 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10050 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.11.0.0 Reporter: Nitin Kumar Maharana Fix For: 4.11.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CLOUDSTACK-9948) [UI] Network update to new offering ( with services removed ) pops up forced update confirmation with incorrect functionality
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091385#comment-16091385
]
Nitin Kumar Maharana commented on CLOUDSTACK-9948:
--
GitHub PR: https://github.com/apache/cloudstack/pull/2191
> [UI] Network update to new offering ( with services removed ) pops up forced
> update confirmation with incorrect functionality
> --
>
> Key: CLOUDSTACK-9948
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9948
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
>Affects Versions: 4.10.0.0
>Reporter: DeepthiMachiraju
> Labels: PVR
> Fix For: 4.10.1.0
>
> Attachments: management-server.log
>
>
> - In Ad zone , Create an Isolated Network N1 with offering (
> DefaultIsolatedNetworkOfferingWithSourceNatService).
> - configure PF , FW , LB rules.
> - Now create a new offering which doesnt have PF , FW , LB services enabled .
> - Update the Nw N1 with the new offering .
> Observations :
> - User is popped with the following confirmation " Do you want to make a
> force update?" . when clicked on "yes" no action is seen on the UI , but
> update is implemented with forced parameter set to "TRUE". New VR is
> recreated with the depleted Services.[ job id : 883 ]
> - When the user clicks on "NO" the window closes down but still the api sends
> forced parameter as "True" . [ job - 889]
> Following exception is observed post clicking Yes followed by No Option due
> to multiple requests sent :
> 2017-06-08 07:34:41,085 ERROR [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-65:ctx-3fa1135c job-889/job-890) (logid:ac0e4c63) Unable
> to complete AsyncJobVO {id:890, userId: 2, accountId: 2, instanceType: null,
> instanceId: null, cmd: com.cloud.vm.VmWorkStop, cmdInfo:
> rO0ABXNyABdjb20uY2xvdWQudm0uVm1Xb3JrU3RvcALQ4GymiWjjAgABWgAHY2xlYW51cHhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIAUXQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwA,
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6760647622781, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: Thu Jun 08 07:34:35 EDT 2017}, job origin:889
> java.lang.NullPointerException
> at
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStop(VirtualMachineManagerImpl.java:4689)
> at sun.reflect.GeneratedMethodAccessor431.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> at
> com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4833)
> at
> com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:554)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:502)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> 2017-06-08 07:34:41,086 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-65:ctx-3fa1135c job-889/job-890) (logid:ac0e4c63) Complete
> async job-890, jobStatus: FAILED, resultCode: 0, result:
>
[jira] [Commented] (CLOUDSTACK-9747) Network Update with new N/W offering retains rules on UI but cleans up on Router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088902#comment-16088902 ] Nitin Kumar Maharana commented on CLOUDSTACK-9747: -- GitHub PR: https://github.com/apache/cloudstack/pull/2187 > Network Update with new N/W offering retains rules on UI but cleans up on > Router > > > Key: CLOUDSTACK-9747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9747 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.9.0.1 >Reporter: DeepthiMachiraju > Labels: pvr > Fix For: 4.10.1.0 > > > - Create a Network with default N/w offering " Offering for Isolated networks > with Source Nat service enabled ". > - Create PF rules , Firewall Rules on the n/w. > - Deploy a VM with the above Network. > - Create a new standalone n/w offering and update the above network with the > new offering. > observations: > - Once the N/w update is completed , its observed that the rules created with > default offering still persist on UI but the iptables on VR is cleaned up. > Expected Result : > - If the new n/w offering supports the VR service as the old one , rules > should be retained on both UI and VR. > or > - Irrespective of new and old n/w offerings supporting or not supporting > the VR service , rules on VR and UI to be cleaned up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CLOUDSTACK-10002) Restart network with cleanup spawns Redundant Routers(In Default Network Offering)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088491#comment-16088491 ] Nitin Kumar Maharana commented on CLOUDSTACK-10002: --- GitHub PR: https://github.com/apache/cloudstack/pull/2186 > Restart network with cleanup spawns Redundant Routers(In Default Network > Offering) > -- > > Key: CLOUDSTACK-10002 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10002 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.10.0.0 > Environment: Persistent VR >Reporter: Nitin Kumar Maharana > Fix For: 4.10.1.0 > > > Reproduction Steps: > Create a network with redundant router capability. > Create instances with the above network. > Update the network to Default > Offering(DefaultIsolatedNetworkOfferingWithSourceNAT). > After successful update, one router is created which is as expected. > Try to restart the network with cleanup=true. > Observation: > Two routers are created with redundant state UNKNOWN. > Note: - The similar behavior is seen when we update RVR to default. > Expectation: > After successful restart, only one router should be created > FS: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Persistent+Configuration+for+Virtual+Routers -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CLOUDSTACK-10002) Restart network with cleanup spawns Redundant Routers(In Default Network Offering)
Nitin Kumar Maharana created CLOUDSTACK-10002: - Summary: Restart network with cleanup spawns Redundant Routers(In Default Network Offering) Key: CLOUDSTACK-10002 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10002 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.10.0.0 Environment: Persistent VR Reporter: Nitin Kumar Maharana Fix For: 4.10.1.0 Reproduction Steps: Create a network with redundant router capability. Create instances with the above network. Update the network to Default Offering(DefaultIsolatedNetworkOfferingWithSourceNAT). After successful update, one router is created which is as expected. Try to restart the network with cleanup=true. Observation: Two routers are created with redundant state UNKNOWN. Note: - The similar behavior is seen when we update RVR to default. Expectation: After successful restart, only one router should be created FS: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Persistent+Configuration+for+Virtual+Routers -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CLOUDSTACK-9880) Expansion of Management IP Range.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-9880: - Description: At present, The management IP range can only be expanded under the same subnet. According to existing range, either the last IP can be forward extended or the first IP can be backward extended. But we cannot add an entirely different range from the same subnet. So the expansion of range is subnet bound, which is fixed. But when the range gets exhausted and a user wants to deploy more system VMs, then the operation would fail. The purpose of this feature is to expand the range of management network IPs within the existing subnet. It can also delete and list the IP ranges. Please find the FS here : https://cwiki.apache.org/confluence/display/CLOUDSTACK/Expansion+of+Management+IP+Range was:At present, The management IP range can only be expanded under the same subnet. According to existing range, either the last IP can be forward extended or the first IP can be backward extended. But we cannot add an entirely different range from the same subnet. So the expansion of range is subnet bound, which is fixed. But when the range gets exhausted and a user wants to deploy more system VMs, then the operation would fail. The purpose of this feature is to expand the range of management network IPs within the existing subnet. It can also delete and list the IP ranges. > Expansion of Management IP Range. > - > > Key: CLOUDSTACK-9880 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9880 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.10.0.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.10.0.0 > > > At present, The management IP range can only be expanded under the same > subnet. According to existing range, either the last IP can be forward > extended or the first IP can be backward extended. But we cannot add an > entirely different range from the same subnet. So the expansion of range is > subnet bound, which is fixed. But when the range gets exhausted and a user > wants to deploy more system VMs, then the operation would fail. The purpose > of this feature is to expand the range of management network IPs within the > existing subnet. It can also delete and list the IP ranges. > Please find the FS here : > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Expansion+of+Management+IP+Range -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CLOUDSTACK-9880) Expansion of Management IP Range.
Nitin Kumar Maharana created CLOUDSTACK-9880: Summary: Expansion of Management IP Range. Key: CLOUDSTACK-9880 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9880 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.10.0.0 Reporter: Nitin Kumar Maharana Fix For: 4.10.0.0 At present, The management IP range can only be expanded under the same subnet. According to existing range, either the last IP can be forward extended or the first IP can be backward extended. But we cannot add an entirely different range from the same subnet. So the expansion of range is subnet bound, which is fixed. But when the range gets exhausted and a user wants to deploy more system VMs, then the operation would fail. The purpose of this feature is to expand the range of management network IPs within the existing subnet. It can also delete and list the IP ranges. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CLOUDSTACK-9708) Router deployment failed due to two threads start VR simultaneosuly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Kumar Maharana updated CLOUDSTACK-9708:
-
Summary: Router deployment failed due to two threads start VR
simultaneosuly (was: Router deployment filed due to two threads start VR
simultaneosuly)
> Router deployment failed due to two threads start VR simultaneosuly
> ---
>
> Key: CLOUDSTACK-9708
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9708
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Nitin Kumar Maharana
>
> This is some race condition observed with HyperV host.
> The issue is produced when two or more threads try to start Router VMs
> simultaneously.
> This is a race condition between two threads trying to start Router VMs
> simultaneosuly, see the two threads below:
> 2015-01-08 17:10:03,750 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-11:ctx-5eb09ffd) (logid:b22fde6c) Sending cmd to
> https://10.81.56.130:8250/api/HypervResource/com.cloud.agent.api.GetStorageStatsCommand
> cmd
> data:{"id":"6e95644b-967e-3b15-a9f5-029e814252b1","localPath":"/storage/primary","pooltype":"SMB","contextMap":{"logid":"b22fde6c"},"wait":0}
> 2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb)
> (logid:d5036c46) Found 0 static nat(s) to apply as a part of domR
> VM[DomainRouter|r-8-VM] start.
> 2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085)
> (logid:1d478d14) Found 0 static nat(s) to apply as a part of domR
> VM[DomainRouter|r-7-VM] start.
> 2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085)
> (logid:1d478d14) Found 0 firewall Ingress rule(s) to apply as a part of domR
> VM[DomainRouter|r-7-VM] start.
> 2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb)
> (logid:d5036c46) Found 0 firewall Ingress rule(s) to apply as a part of domR
> VM[DomainRouter|r-8-VM] start.
> 2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb)
> (logid:d5036c46) Found 0 port forwarding rule(s) to apply as a part of domR
> VM[DomainRouter|r-8-VM] start.
> 2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085)
> (logid:1d478d14) Found 0 port forwarding rule(s) to apply as a part of domR
> VM[DomainRouter|r-7-VM] start.
> 2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085)
> (logid:1d478d14) Found 0 static nat rule(s) to apply as a part of domR
> VM[DomainRouter|r-7-VM] start.
> 2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb)
> (logid:d5036c46) Found 0 static nat rule(s) to apply as a part of domR
> VM[DomainRouter|r-8-VM] start.
> 2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb)
> (logid:d5036c46) Found 0 vpn(s) to apply as a part of domR
> VM[DomainRouter|r-8-VM] start.
> 2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085)
> (logid:1d478d14) Found 0 vpn(s) to apply as a part of domR
> VM[DomainRouter|r-7-VM] start.
> 2015-01-08 17:10:03,784 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085)
> (logid:1d478d14) Found 0 load balancing rule(s) to apply as a part of domR
> VM[DomainRouter|r-7-VM] start.
> 2015-01-08 17:10:03,784 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb)
> (logid:d5036c46) Found 0 load balancing rule(s) to apply as a part of domR
> VM[DomainRouter|r-8-VM] start.
> 2015-01-08 17:10:03,787 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085)
> (logid:1d478d14) Creating monitoring services on VM[DomainRouter|r-7-VM]
> start...
> 2015-01-08 17:10:03,787 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb)
> (logid:d5036c46) Creating monitoring services on VM[DomainRouter|r-8-VM]
> start...
> Then VR failed with NPE
> 2015-01-08 17:10:03,787
[jira] [Created] (CLOUDSTACK-9708) Router deployment filed due to two threads start VR simultaneosuly
Nitin Kumar Maharana created CLOUDSTACK-9708:
Summary: Router deployment filed due to two threads start VR
simultaneosuly
Key: CLOUDSTACK-9708
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9708
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Nitin Kumar Maharana
This is some race condition observed with HyperV host.
The issue is produced when two or more threads try to start Router VMs
simultaneously.
This is a race condition between two threads trying to start Router VMs
simultaneosuly, see the two threads below:
2015-01-08 17:10:03,750 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-11:ctx-5eb09ffd) (logid:b22fde6c) Sending cmd to
https://10.81.56.130:8250/api/HypervResource/com.cloud.agent.api.GetStorageStatsCommand
cmd
data:{"id":"6e95644b-967e-3b15-a9f5-029e814252b1","localPath":"/storage/primary","pooltype":"SMB","contextMap":{"logid":"b22fde6c"},"wait":0}
2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb) (logid:d5036c46)
Found 0 static nat(s) to apply as a part of domR VM[DomainRouter|r-8-VM] start.
2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085) (logid:1d478d14)
Found 0 static nat(s) to apply as a part of domR VM[DomainRouter|r-7-VM] start.
2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085) (logid:1d478d14)
Found 0 firewall Ingress rule(s) to apply as a part of domR
VM[DomainRouter|r-7-VM] start.
2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb) (logid:d5036c46)
Found 0 firewall Ingress rule(s) to apply as a part of domR
VM[DomainRouter|r-8-VM] start.
2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb) (logid:d5036c46)
Found 0 port forwarding rule(s) to apply as a part of domR
VM[DomainRouter|r-8-VM] start.
2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085) (logid:1d478d14)
Found 0 port forwarding rule(s) to apply as a part of domR
VM[DomainRouter|r-7-VM] start.
2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085) (logid:1d478d14)
Found 0 static nat rule(s) to apply as a part of domR VM[DomainRouter|r-7-VM]
start.
2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb) (logid:d5036c46)
Found 0 static nat rule(s) to apply as a part of domR VM[DomainRouter|r-8-VM]
start.
2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb) (logid:d5036c46)
Found 0 vpn(s) to apply as a part of domR VM[DomainRouter|r-8-VM] start.
2015-01-08 17:10:03,782 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085) (logid:1d478d14)
Found 0 vpn(s) to apply as a part of domR VM[DomainRouter|r-7-VM] start.
2015-01-08 17:10:03,784 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085) (logid:1d478d14)
Found 0 load balancing rule(s) to apply as a part of domR
VM[DomainRouter|r-7-VM] start.
2015-01-08 17:10:03,784 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb) (logid:d5036c46)
Found 0 load balancing rule(s) to apply as a part of domR
VM[DomainRouter|r-8-VM] start.
2015-01-08 17:10:03,787 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-5:ctx-16557d57 job-22/job-26 ctx-f19c2085) (logid:1d478d14)
Creating monitoring services on VM[DomainRouter|r-7-VM] start...
2015-01-08 17:10:03,787 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb) (logid:d5036c46)
Creating monitoring services on VM[DomainRouter|r-8-VM] start...
Then VR failed with NPE
2015-01-08 17:10:03,787 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Work-Job-Executor-4:ctx-7d37a603 job-21/job-25 ctx-d4e904bb) (logid:d5036c46)
Creating monitoring services on VM[DomainRouter|r-8-VM] start...
2015-01-08 17:10:03,818 DEBUG [c.c.a.ApiServlet]
(catalina-exec-13:ctx-8415f9bc) (logid:5aed5be9) ===START=== 10.81.29.157 --
GET
[jira] [Created] (CLOUDSTACK-9639) Unable to create shared network with vLan isolation
Nitin Kumar Maharana created CLOUDSTACK-9639: Summary: Unable to create shared network with vLan isolation Key: CLOUDSTACK-9639 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9639 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Create shared network fails with error While creating a shared network it fails to create with Error "The new IP range you have specified has overlapped with the guest network in the zone: XYZ. Please specify a different gateway/netmask" Steps to Reproduce: === Create an isolated network with a subnet eg: 10.1.1.0.24 Create a shared network with the same subnet but different VLAN, we should observe this issue. EXPECTED BEHAVIOR === It shouldn't restrict the creation of guest network's with same subnet as long as they are segmented by VLAN. ACTUAL BEHAVIOR It doesn't allow the creation of shared guest networks if there is any isolated guest network using the same subnet although it allows using the same subnet in multiple shared networks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9636) The host alerts box should be named as hosts in Alerts.
Nitin Kumar Maharana created CLOUDSTACK-9636: Summary: The host alerts box should be named as hosts in Alerts. Key: CLOUDSTACK-9636 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9636 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Nitin Kumar Maharana The host Alerts box shows hosts in Alerts. The name host Alerts is misleading, it should be changed to hosts in alerts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9623) Deploying virtual machine fails due to "Couldn't find vlanId" in Basic Zone
Nitin Kumar Maharana created CLOUDSTACK-9623: Summary: Deploying virtual machine fails due to "Couldn't find vlanId" in Basic Zone Key: CLOUDSTACK-9623 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9623 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Reporter: Nitin Kumar Maharana In Basic zone, while deploying a VM it fails with an unexpected exception. This is reproducible only when java asserts are enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9618) Load Balancer configuration page does not have "Source" method in the drop down list
Nitin Kumar Maharana created CLOUDSTACK-9618: Summary: Load Balancer configuration page does not have "Source" method in the drop down list Key: CLOUDSTACK-9618 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9618 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana If we create an isolated network with NetScaler published service offering for Load balancing service, then the load balancing configuration UI does not show "Source" as one of the supported LB methods in the drop down list. It only shows "Round-Robin" and "LeastConnection" methods in the list. Howerver, It successfully creates LB rule with "Source" as the LB method using API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9613) Unable to set NAT rules on any interfaces except first interface of VM.
Nitin Kumar Maharana created CLOUDSTACK-9613: Summary: Unable to set NAT rules on any interfaces except first interface of VM. Key: CLOUDSTACK-9613 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9613 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana VMs have multiple network interfaces. It is not possible to set a NAT rule on any of the interfaces except the first interface of the VM from UI. Because the UI only lists the IPs of the first interface. The rules can only be set on the "default" interface but even after setting the secondary as the default interface the outcome is still the same. Only the first interface is listed in the UI as available for setting NAT rules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9611) Dedicating a Guest VLAN range to Project does not work
Nitin Kumar Maharana created CLOUDSTACK-9611: Summary: Dedicating a Guest VLAN range to Project does not work Key: CLOUDSTACK-9611 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9611 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Trying to dedicate a guest VLAN range to an account fails. If we pass both account and projectid parameters to the dedicateGuestVlanRange (which are not mentioned as mutually exclusive in API description) the API layer throws error saying both are mutually exclusive. Steps to Reproduce: Create an account. Create a project in that account. Go to admin account and change view to the above project. Navigate to Infrastructure -> Zone -> Physical Network -> Guest -> Dedicate Guest VLAN range. Try to dedicate the guest VLAN range from the project view for the account associated with the project. It fails with Error saying accountName and projectId are mutually exclusive. Expected: The VLAN range should get dedicated to the project account. Notes: = If we do the dedication from default view then it works fine as no projectid is associated over there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9588) Add Load Balancer functionality in Network page is redundant.
Nitin Kumar Maharana created CLOUDSTACK-9588: Summary: Add Load Balancer functionality in Network page is redundant. Key: CLOUDSTACK-9588 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9588 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Steps to Reproduce: Network -> Select any network -> Observer Add Load Balancer tab The "Add Load Balancer" functionality is redundant. The above is used to create LB rule without any public IP. Resolution: There exist similar functionality in Network -> Any Network -> Details Tab -> View IP Addresses -> Any public IP -> Configuration Tab -> Observe Load Balancing. The above is used to create LB rule with a public IP. This is a more convenient way of creating LB rule as the IP is involved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9587) Add Load Balancer functionality in Network page is redundant.
Nitin Kumar Maharana created CLOUDSTACK-9587: Summary: Add Load Balancer functionality in Network page is redundant. Key: CLOUDSTACK-9587 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9587 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Steps to Reproduce: Network -> Select any network -> Observer Add Load Balancer tab The "Add Load Balancer" functionality is redundant. The above is used to create LB rule without any public IP. Resolution: There exist similar functionality in Network -> Any Network -> Details Tab -> View IP Addresses -> Any public IP -> Configuration Tab -> Observe Load Balancing. The above is used to create LB rule with a public IP. This is a more convenient way of creating LB rule as the IP is involved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9271) Keyboard layout name mismatch on VM console and VM instance creation dropdown. 2 of 13
Nitin Kumar Maharana created CLOUDSTACK-9271: Summary: Keyboard layout name mismatch on VM console and VM instance creation dropdown. 2 of 13 Key: CLOUDSTACK-9271 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9271 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Repro Steps: === 1. Setup basic environments as normal. 2. Open a browser, go to Web Console. 3. Go on "Templates" on left panel, register a win7x64Sp1 ISO. 4. Go on "Instances" on left panel, add a new instance by ISO in step3, choose the type Keyboard language, the name is localized. 5. Tap on Quickview of the new instance, click on "View console". 6. Check the type keyboard language in instance console. Expected Result: == Keyboard layout name should match on VM console and VM instance creation dropdown Actual Result: === Keyboard layout name mismatch on VM console and VM instance creation dropdown Language Info: SC -> Fail JA -> Fail -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9270) UI alignment gone bad in multiple places - VM Instance, Network, Egress rules
Nitin Kumar Maharana created CLOUDSTACK-9270: Summary: UI alignment gone bad in multiple places - VM Instance, Network, Egress rules Key: CLOUDSTACK-9270 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9270 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana UI alignment gone bad in multiple places - VM Instance, Network, Egress rules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9267) String is not localized on create instance wizards.
Nitin Kumar Maharana created CLOUDSTACK-9267: Summary: String is not localized on create instance wizards. Key: CLOUDSTACK-9267 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9267 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Repro Steps: 1. Setup basic environments as normal. 2. Open a browser, go to Web Console. 3. Upload a iso template. 4. Go to "Instances" page and add new instance. 5. Check the strings on create instance wizards. Expected Result: All the strings should be localized on create instance wizards. Actual Result: Some strings are not localized on create instance wizards. Language Info JA -> Fail SC -> Fail -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9268) Display VM in Load balancing rule in UI
Nitin Kumar Maharana created CLOUDSTACK-9268: Summary: Display VM in Load balancing rule in UI Key: CLOUDSTACK-9268 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9268 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Steps of Reproducing: == 1:Create VMs 2:Make LoadBalancing rule in GUI Name:WWW PrivatePort:80 PublicPort:80 Add VMs:some VMs The VMs which has been already assigned is still being listed when you add the VM to an existing rule. In addition to this, when we remove a VM, and again try to add for that rule,it will not list that VM in the list. The issue doesn’t occur if you go back to the network tab and view the loadbalance rules again. A page refresh is solving the issue, but need to resolve this issue without a refresh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9269) Missing field for Switch type for Management and Storage traffic types
Nitin Kumar Maharana created CLOUDSTACK-9269: Summary: Missing field for Switch type for Management and Storage traffic types Key: CLOUDSTACK-9269 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9269 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana In New Zone addition wizard, when user tries to configure physical network details, he has the option to select the traffic labels, VLAN IDs and Switch type in case of VmWare. But it is observed that Switch type filed (a drop down list) is missing for traffic types Management and Storage. The same list is available for Guest, Public traffic types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9272) No option in UI to add GSLB with service type "HTTP"
Nitin Kumar Maharana created CLOUDSTACK-9272: Summary: No option in UI to add GSLB with service type "HTTP" Key: CLOUDSTACK-9272 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9272 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana There is no option to add a GSLB rule with service type is "HTTP" Only options present are "tcp" and "udp". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9237) Create LB Healthcheck issues - button alignment and error message goes outside the window
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-9237: - Description: Blocker - because it shows poor workmanship on the UI Browser - Chrome Version 47.0.2526.106 m Steps to Repro: Open up - Network-Guest Networks -> IP Addresses-> IP -> Load Balancing - click on the "Configure" button below the healthcheck, - opens a "label.heath.check.wizard" Issues: == (1) Please see the UI attached - leave the default values as is and click on the "Create" - opens a "Status" dialog with an error message (2) Message on the dialog goes outside the window Fix: === Increased the size of width of dialog box. Json response parsing was missing. Added it. was: Blocker - because it shows poor workmanship on the UI Browser - Chrome Version 47.0.2526.106 m Steps to Repro: Open up - Network-Guest Networks -> IP Addresses-> IP -> Load Balancing - click on the "Configure" button below the healthcheck, - opens a "label.heath.check.wizard" Issues: == (1) Please see the UI attached - leave the default values as is and click on the "Create" - opens a "Status" dialog with an error message (2) Message on the dialog goes outside the window > Create LB Healthcheck issues - button alignment and error message goes > outside the window > - > > Key: CLOUDSTACK-9237 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9237 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana >Priority: Blocker > > Blocker - because it shows poor workmanship on the UI > Browser - Chrome Version 47.0.2526.106 m > Steps to Repro: > > Open up - Network-Guest Networks -> IP Addresses-> IP -> Load > Balancing > - click on the "Configure" button below the healthcheck, > - opens a "label.heath.check.wizard" > Issues: > == > (1) Please see the UI attached > - leave the default values as is and click on the "Create" > - opens a "Status" dialog with an error message > (2) Message on the dialog goes outside the window > Fix: > === > Increased the size of width of dialog box. > Json response parsing was missing. Added it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9237) Create LB Healthcheck issues - button alignment and error message goes outside the window
Nitin Kumar Maharana created CLOUDSTACK-9237: Summary: Create LB Healthcheck issues - button alignment and error message goes outside the window Key: CLOUDSTACK-9237 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9237 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Priority: Blocker Blocker - because it shows poor workmanship on the UI Browser - Chrome Version 47.0.2526.106 m Steps to Repro: Open up - Network-Guest Networks -> IP Addresses-> IP -> Load Balancing - click on the "Configure" button below the healthcheck, - opens a "label.heath.check.wizard" Issues: == (1) Please see the UI attached - leave the default values as is and click on the "Create" - opens a "Status" dialog with an error message (2) Message on the dialog goes outside the window -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9237) Create LB Healthcheck issues - button alignment and error message goes outside the window
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-9237: - Description: Blocker - because it shows poor workmanship on the UI Browser - Chrome Version 47.0.2526.106 m Steps to Repro: Open up - Network-Guest Networks -> IP Addresses-> IP -> Load Balancing - click on the "Configure" button below the healthcheck, - opens a "label.heath.check.wizard" Issues: == (1) Please see the snapshot attached - leave the default values as is and click on the "Create" - opens a "Status" dialog with an error message (2) Message on the dialog goes outside the window Fix: === Increased the size of width of dialog box. Json response parsing was missing. Added it. was: Blocker - because it shows poor workmanship on the UI Browser - Chrome Version 47.0.2526.106 m Steps to Repro: Open up - Network-Guest Networks -> IP Addresses-> IP -> Load Balancing - click on the "Configure" button below the healthcheck, - opens a "label.heath.check.wizard" Issues: == (1) Please see the UI attached - leave the default values as is and click on the "Create" - opens a "Status" dialog with an error message (2) Message on the dialog goes outside the window Fix: === Increased the size of width of dialog box. Json response parsing was missing. Added it. > Create LB Healthcheck issues - button alignment and error message goes > outside the window > - > > Key: CLOUDSTACK-9237 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9237 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana >Priority: Blocker > Attachments: Error_Message_Details.png, Fixed_SS1_Nitin.png, > Fixed_SS2_Nitin.png, Label_Health_Check_Window.png > > > Blocker - because it shows poor workmanship on the UI > Browser - Chrome Version 47.0.2526.106 m > Steps to Repro: > > Open up - Network-Guest Networks -> IP Addresses-> IP -> Load > Balancing > - click on the "Configure" button below the healthcheck, > - opens a "label.heath.check.wizard" > Issues: > == > (1) Please see the snapshot attached > - leave the default values as is and click on the "Create" > - opens a "Status" dialog with an error message > (2) Message on the dialog goes outside the window > Fix: > === > Increased the size of width of dialog box. > Json response parsing was missing. Added it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9237) Create LB Healthcheck issues - button alignment and error message goes outside the window
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-9237: - Attachment: Label_Health_Check_Window.png Fixed_SS2_Nitin.png Fixed_SS1_Nitin.png Error_Message_Details.png > Create LB Healthcheck issues - button alignment and error message goes > outside the window > - > > Key: CLOUDSTACK-9237 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9237 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana >Priority: Blocker > Attachments: Error_Message_Details.png, Fixed_SS1_Nitin.png, > Fixed_SS2_Nitin.png, Label_Health_Check_Window.png > > > Blocker - because it shows poor workmanship on the UI > Browser - Chrome Version 47.0.2526.106 m > Steps to Repro: > > Open up - Network-Guest Networks -> IP Addresses-> IP -> Load > Balancing > - click on the "Configure" button below the healthcheck, > - opens a "label.heath.check.wizard" > Issues: > == > (1) Please see the UI attached > - leave the default values as is and click on the "Create" > - opens a "Status" dialog with an error message > (2) Message on the dialog goes outside the window > Fix: > === > Increased the size of width of dialog box. > Json response parsing was missing. Added it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9231) Root volume migration from one primary to another primary storage within the same cluster is failing
Nitin Kumar Maharana created CLOUDSTACK-9231: Summary: Root volume migration from one primary to another primary storage within the same cluster is failing Key: CLOUDSTACK-9231 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9231 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana EXPECTED BEHAVIOR === Root Volume migration within cluster should work. ACTUAL BEHAVIOR Root volume migration within cluster failed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9229) Autoscale policy creation failing in VPC due to zoneid missing in createAutoScaleVmProfile
Nitin Kumar Maharana created CLOUDSTACK-9229: Summary: Autoscale policy creation failing in VPC due to zoneid missing in createAutoScaleVmProfile Key: CLOUDSTACK-9229 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9229 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Autoscale policy creation is failing on VPC while creating autoscalevmprofile since zoneid parameter is missing. Steps to Reproduce: 1. Create VPC Network offering with NS as service provider for LB 2. Create VPC using offering which has NetScaler as LB provider 3. Add a tier using the network offering created in Step1 4. Launch a VM 5. Acquire a public IP 6. Create an auto scale policy with all required parameters on an LB rule Result = Fails during autoscalevmprofile creation with the following error: 2015-12-30 12:17:45,243 DEBUG [c.c.a.ApiServlet] (catalina-exec-10:ctx-58bcf6cf) (logid:ae6742c8) ===START=== 10.144.7.6 -- GET command=createAutoScaleVmProfile=json=05ac866f-604c-43e2-a48b-47e83ef7c4f1=3cdd83c4-ad27-11e5-9eaf-42407779c24b=30%5B0%5D.name=snmpcommunity%5B0%5D.value=public%5B1%5D.name=snmpport%5B1%5D.value=161&_=1451458073663 2015-12-30 12:17:45,248 DEBUG [o.a.c.a.BaseCmd] (catalina-exec-10:ctx-58bcf6cf ctx-f5123e30) (logid:ae6742c8) Ignoring paremeter fordisplay as the caller is not authorized to pass it in 2015-12-30 12:17:45,248 INFO [c.c.a.ApiServer] (catalina-exec-10:ctx-58bcf6cf ctx-f5123e30) (logid:ae6742c8) Unable to execute API command autoscalevmprofile due to missing parameter zoneid Expected Result = Autoscale policy creation should be successful and the "min" number of VMs specified in the policy should be deployed. Following should be the params for autoscalevmprofile creation: command=createAutoScaleVmProfile=json=0b43fff3-c069-417b-ac0c-e4dc46b407ea=0 5ac866f-604c-43e2-a48b-47e83ef7c4f1=3cdd83c4-ad27-11e5-9eaf-42407779c24b=30%5B0%5D .name=snmpcommunity%5B0%5D.value=public%5B1%5D.name=snmpport%5B1%5D.value=161 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9228) Network update with mistmatch in services require forced option
Nitin Kumar Maharana created CLOUDSTACK-9228: Summary: Network update with mistmatch in services require forced option Key: CLOUDSTACK-9228 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9228 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Steps to reproduce: 1.Bring up CloudStack in advanced zone 2.Create isolated network with sourcenat, pf, lb, firewall services 3.Deploy a VM in the above network 4.Create another network offering with sourcenat, pf, firewall services 5.Try to update the network with offering created in step4 Result: == The new offering:DefaultIsolatedNetworkOfferingForVpcNetworksNoLB will remove the following services [Lb]along with all the related configuration currently in use. will not proceed with the network update.set forced parameter to true for forcing an update." Workaround: === Use api with forced=true -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9230) Remove unnecessary return statement from cloudStack.js
Nitin Kumar Maharana created CLOUDSTACK-9230: Summary: Remove unnecessary return statement from cloudStack.js Key: CLOUDSTACK-9230 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9230 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana The return statement is never reached. So removed the statement. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9235) Autoscale button is missing in VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096580#comment-15096580 ] Nitin Kumar Maharana commented on CLOUDSTACK-9235: -- Ref: CLOUDSTACK-5048: UI shouldn't show AutoScale button when setting up LB using Virtual Router > Autoscale button is missing in VPC > -- > > Key: CLOUDSTACK-9235 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9235 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana > > Autoscale button is missing. This should not be the case since we are able to > add NS as the external LB provider in VPC. > Steps: > = > 1. Create a VPC offering with NS as the external LB provider > 2. Create a VPC and configure the public tier with the above offering > 3. Acquire an IP address and try to configure Load Balancing rule > Result: > == > Autoscale option is not visible at all for the LB. > Expected Result: > = > Autoscale option should be available and should work exactly like the way it > works for a normal isolated network with NS. If we choose NS as service > provider for LB, autoscale should also be visible. If VR is chosen, only then > we should not display autoscale. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9235) Autoscale button is missing in VPC
Nitin Kumar Maharana created CLOUDSTACK-9235: Summary: Autoscale button is missing in VPC Key: CLOUDSTACK-9235 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9235 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Autoscale button is missing. This should not be the case since we are able to add NS as the external LB provider in VPC. Steps: = 1. Create a VPC offering with NS as the external LB provider 2. Create a VPC and configure the public tier with the above offering 3. Acquire an IP address and try to configure Load Balancing rule Result: == Autoscale option is not visible at all for the LB. Expected Result: = Autoscale option should be available and should work exactly like the way it works for a normal isolated network with NS. If we choose NS as service provider for LB, autoscale should also be visible. If VR is chosen, only then we should not display autoscale. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9236) Load Balancing Health Check button displayed when non-NetScaler offering is used
Nitin Kumar Maharana created CLOUDSTACK-9236: Summary: Load Balancing Health Check button displayed when non-NetScaler offering is used Key: CLOUDSTACK-9236 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9236 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Load balancing health check option / button should only be displayed when a NetScaler based networking offering is being used. If you try to use the health check option when NetScaler is not being used as the load balancing technology the UI throws an error stating that the health check option is not supported. This button / option should be removed from the UI if NetScaler is not included in the network offering as customers will be confused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066289#comment-15066289 ] Nitin Kumar Maharana edited comment on CLOUDSTACK-9192 at 12/21/15 10:27 AM: - Hi [~weizhou], Sorry I saw your comment now. I have already created one. Thank you. was (Author: nitin.maharana): Hi [~ustcweiz...@gmail.com], Sorry I saw your comment now. I have already created one. Thank you. > UpdateVpnCustomerGateway is failing > --- > > Key: CLOUDSTACK-9192 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9192 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana > > Reproducible Steps: > > 1.Create a customer gateway for a VPC. > 2.Edit it using UI(API call is UpdateVpnCustomerGateway). > 3.When we try to update the customer vpn gateway with connection state is not > in "Error", we see the API error but that won't be reflected to the user in > UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066289#comment-15066289 ] Nitin Kumar Maharana commented on CLOUDSTACK-9192: -- Hi [~ustcweiz...@gmail.com], Sorry I saw your comment now. I have already created one. Thank you. > UpdateVpnCustomerGateway is failing > --- > > Key: CLOUDSTACK-9192 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9192 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana > > Reproducible Steps: > > 1.Create a customer gateway for a VPC. > 2.Edit it using UI(API call is UpdateVpnCustomerGateway). > 3.When we try to update the customer vpn gateway with connection state is not > in "Error", we see the API error but that won't be reflected to the user in > UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing
Nitin Kumar Maharana created CLOUDSTACK-9192: Summary: UpdateVpnCustomerGateway is failing Key: CLOUDSTACK-9192 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9192 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Reproducible Steps: 1.Create a customer gateway for a VPC. 2.Edit it using UI(API call is UpdateVpnCustomerGateway). 3.When we try to update the customer vpn gateway with connection state is not in "Error", we see the API error but that won't be reflected to the user in UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9186) Root admin cannot see VPC created by Domain admin user
Nitin Kumar Maharana created CLOUDSTACK-9186: Summary: Root admin cannot see VPC created by Domain admin user Key: CLOUDSTACK-9186 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9186 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Issue: = Root admin cannot see LB rules and Public LB IP addresses created by domain-admin in UI therefore root admin cannot manage those. Reproducible Steps: 1. Log in as a Domain-Admin account and create a VPC with vpc virtual router as public load balancer provider 2. click on the newly created VPC -> click on the VPC tier -> click internal LB 3. Add internal LB, 4. Logoff domain-admin and login as root admin 5. Navigate the VPC created previously and click internal LB, internal lb is not showing up. Same steps for Public LB IP addresses except select the correct Network offering while creating a tier. Expected Behaviour: = Root admin should be able to manage VPC created by Domain admin user . Actual Behaviour: == Root admin cannot see VPC created by Domain admin user and hence not able to manage it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9132) API createVolume takes empty string for name parameter
Nitin Kumar Maharana created CLOUDSTACK-9132: Summary: API createVolume takes empty string for name parameter Key: CLOUDSTACK-9132 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9132 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Reporter: Nitin Kumar Maharana Steps to Reproduce: Create a volume using createVolume API where parameter name is empty. It creates a volume with empty name. But the name parameter is mandatory.(Issue) Expected Behaviour: It shouldn't create a volume with an empty name. Error should be returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9093) Listing Networks under Project view is throwing error message due to accountid is included in API call
Nitin Kumar Maharana created CLOUDSTACK-9093: Summary: Listing Networks under Project view is throwing error message due to accountid is included in API call Key: CLOUDSTACK-9093 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9093 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Nitin Kumar Maharana Fix For: 4.6.0 Under Projects view when we click on Networks tab, it throws an error that says "“Account and projectId can't be specified together” This is because as part of listing Networks we are also firing listRemoteAccessVpns API for which we are supplying both accountId and projectId parameters. This is not correct since project resources are shared across all accounts. We can’t list individually for an account belonging to a project. Steps to Reproduce 1. Create a project and add an account 2. Go to Project View and choose the Project created 3. Click on Networks tab -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-9068) Listing Port Forwarding Rules take too much time to load
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana resolved CLOUDSTACK-9068. -- Resolution: Fixed > Listing Port Forwarding Rules take too much time to load > > > Key: CLOUDSTACK-9068 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9068 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana > > ISSUE > == > The performance of listPortForwardingRules slows down dramatically as the > number of rules for an IP increases. If there are 100 rules for an IP and it > takes over a minute to respond. > REPRODUCE STEPS > == > 1) Create many port forwarding rules (75-100) for a particular IP. > 2) View the port forwarding rules for the IP in the UI or directly with the > listPortForwardingRules API command. > 3) Notice the slowness. > EXPECTED BEHAVIOR > == > listPortForwardingRules should always respond in a reasonable time. > ACTUAL BEHAVIOR > == > listPortForwardingRules responds very slowly even with less than 100 rules > configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9069) Newly added project is not showing in the drop down until the browser is refreshed.
Nitin Kumar Maharana created CLOUDSTACK-9069: Summary: Newly added project is not showing in the drop down until the browser is refreshed. Key: CLOUDSTACK-9069 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9069 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Steps to reproduce: 1.Login as admin and navigate to Projects page. 2.Add one project and navigate to Dashboard. 3.Check for newly added project in Project drop down. Actual behaviour: New project is showing in drop down only after refreshing the browser. Expected behaviour: New project should be shown in drop down without refreshing the browser also. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9068) Listing Port Forwarding Rules take too much time to load
Nitin Kumar Maharana created CLOUDSTACK-9068: Summary: Listing Port Forwarding Rules take too much time to load Key: CLOUDSTACK-9068 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9068 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana ISSUE == The performance of listPortForwardingRules slows down dramatically as the number of rules for an IP increases. If there are 100 rules for an IP and it takes over a minute to respond. REPRODUCE STEPS == 1) Create many port forwarding rules (75-100) for a particular IP. 2) View the port forwarding rules for the IP in the UI or directly with the listPortForwardingRules API command. 3) Notice the slowness. EXPECTED BEHAVIOR == listPortForwardingRules should always respond in a reasonable time. ACTUAL BEHAVIOR == listPortForwardingRules responds very slowly even with less than 100 rules configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9072) Listing Networks under Project view is throwing error message due to accountid included in API
Nitin Kumar Maharana created CLOUDSTACK-9072: Summary: Listing Networks under Project view is throwing error message due to accountid included in API Key: CLOUDSTACK-9072 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9072 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Under Projects view when we click on Networks tab, it throws an error that says "“Account and projectId can't be specified together” Steps = 1. Create a project and add an account 2. Go to Project View and choose the Project created 3. Click on Networks tab -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8928) While adding VMs to LB rule, default NIC IP is always displayed rather than the IP corresponding to the NIC where LB is being created
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana resolved CLOUDSTACK-8928. -- Resolution: Fixed > While adding VMs to LB rule, default NIC IP is always displayed rather than > the IP corresponding to the NIC where LB is being created > - > > Key: CLOUDSTACK-8928 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8928 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana > > Issue : > - > While creating LB rule, if the VM belongs to multiple NICs, always the > default NIC IP is the only one displayed. This causes issues in cases where > we want to create an LB using the non-default NIC of the VM. It fails with an > error message. This IP is never displayed in UI and only way is use the API > directly to create such an LB rule. > Steps > = > 1. Create a VM with multiple NICs (VM belongs to multiple networks) > 2. Navigate to the non-default Network of the VM -> IP Address -> > Configuration -> Load Balancing -> Create an LB rule -> Add -> Choose the VM > created > Observe that the IP listed does not belong to that Network. It is always the > IP of the default NIC. By choosing this IP, the LB creation will fail since > the IP and network ids would not match. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8919) Slow UI response while loading the list of networks in network tab.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana resolved CLOUDSTACK-8919. -- Resolution: Fixed > Slow UI response while loading the list of networks in network tab. > --- > > Key: CLOUDSTACK-8919 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8919 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Nitin Kumar Maharana > > Root cause of this Issue: Invokes 3 APIs, the 2nd API to check whether any > network is having security group service, this consumes 90% of the time. API > fetches network list and for each network calls DB to get services associated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8913) Search box in Templates tab out of alignment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana resolved CLOUDSTACK-8913. -- Resolution: Fixed > Search box in Templates tab out of alignment > > > Key: CLOUDSTACK-8913 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8913 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.1 >Reporter: Nitin Kumar Maharana > > CURRENT BEHAVIOUR > > Search box in Templates tab is not aligned with other buttons in Firefox, > Chrome, and Safari. > EXPECTED BEHAVIOUR > > Search box in Templates tab should be aligned with other buttons in all > browser. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8962) Dedicated cluster is used for virtual routers that belong to non-dedicated account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana resolved CLOUDSTACK-8962. -- Resolution: Fixed > Dedicated cluster is used for virtual routers that belong to non-dedicated > account > -- > > Key: CLOUDSTACK-8962 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8962 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.2 >Reporter: Nitin Kumar Maharana >Priority: Blocker > > ISSUE > == > A dedicated cluster is being populated with Virtual Routers from > domains/accounts to which the cluster is not dedicated. > The VR belongs to a non-dedicated account should not go to a dedicated > cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8967) UI icon over VM snapshot to deploy user instance
Nitin Kumar Maharana created CLOUDSTACK-8967: Summary: UI icon over VM snapshot to deploy user instance Key: CLOUDSTACK-8967 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8967 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Aa new icon over VM snapshot object, which upon invoked will open a deploy user instance wizard, where there is no choice to choose zone and ISO or template to deploy the user instance from. 1) A new icon to indicate deploy user instance from VM snapshot 2) The new icon is placed as an operation over each VM snapshot object. 3) Clicking this icon will show the wizard to deploy user instance, which is same as wizard for normal user instance except that zone selection page and ISO/template selection page would not be present in this wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8967) UI icon over VM snapshot to deploy user instance
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana closed CLOUDSTACK-8967. Resolution: Duplicate > UI icon over VM snapshot to deploy user instance > > > Key: CLOUDSTACK-8967 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8967 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana > > Aa new icon over VM snapshot object, which upon invoked will open a deploy > user instance wizard, where there is no choice to choose zone and ISO or > template to deploy the user instance from. > 1) A new icon to indicate deploy user instance from VM snapshot > 2) The new icon is placed as an operation over each VM snapshot object. > 3) Clicking this icon will show the wizard to deploy user instance, which is > same as wizard for normal user instance except that zone selection page and > ISO/template selection page would not be present in this wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8968) UI icon over VM snapshot to deploy user instance
Nitin Kumar Maharana created CLOUDSTACK-8968: Summary: UI icon over VM snapshot to deploy user instance Key: CLOUDSTACK-8968 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8968 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana A new icon over VM snapshot object, which upon invoked will open a deploy user instance wizard, where there is no choice to choose zone and ISO or template to deploy the user instance from. 1) A new icon to indicate deploy user instance from VM snapshot 2) The new icon is placed as an operation over each VM snapshot object. 3) Clicking this icon will show the wizard to deploy user instance, which is same as wizard for normal user instance except that zone selection page and ISO/template selection page would not be present in this wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8962) Dedicated cluster is used for virtual routers that belong to non-dedicated account
Nitin Kumar Maharana created CLOUDSTACK-8962: Summary: Dedicated cluster is used for virtual routers that belong to non-dedicated account Key: CLOUDSTACK-8962 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8962 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.2 Reporter: Nitin Kumar Maharana Priority: Blocker ISSUE == A dedicated cluster has been populated with Virtual Routers from domains to which the cluster is not dedicated. The VR belongs to a non-dedicated account should not go to a dedicated cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8962) Dedicated cluster is used for virtual routers that belong to non-dedicated account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-8962: - Description: ISSUE == A dedicated cluster has been populated with Virtual Routers from domains to which the cluster is not dedicated. The VR belongs to a non-dedicated account should not go to a dedicated cluster. TROUBLESHOOTING == mysql> select * from dedicated_resources; - id uuiddata_center_id pod_id cluster_id host_id domain_id account_id affinity_group_id - 10 dccf2f43-b9b0-443b-a614-6170cc8c70dbNULLNULL19 NULL 40 NULL66 12 efdb169f-f74e-493e-b2be-28f6d44fd0b49 NULLNULLNULL 7 NULL144 13 1419d64c-a387-4c6f-8a84-b2f110e291ec10 NULLNULLNULL 7 NULL144 16 28d92221-1c8d-45db-8696-dff9795da06912 NULLNULLNULL 7 NULL144 - mysql> select id from host where cluster_id = 19; - id - 61 62 101 - mysql> select id,name,account_id from vm_instance where host_id in (61,62,101) and removed is null; id nameaccount_id 62308f307c0a-15f5-4262-ad24-54fb9e89970039 6252a6cd3afb-4219-45b9-82a9-28b027f3c23739 6994r-6994-VM 74 7115r-7115-VM 128 7119r-7119-VM 371 7120r-7120-VM 1 7254r-7254-VM 128 7257r-7257-VM 272 7262r-7262-VM 11 7292r-7292-VM 402 7304r-7304-VM 44 7365r-7365-VM 1 7389r-7389-VM 1 755971532dab-fddb-421a-9565-34e250a3dcdc39 6111r-6111-VM 292 6123r-6123-VM 292 6149r-6149-VM 301 6151r-6151-VM 303 6160r-6160-VM 280 6256e01fb237-3b18-4978-b91e-f74487187d6939 6293r-6293-VM 313 6415r-6415-VM 272 6529r-6529-VM 272 6539r-6539-VM 1 6567r-6567-VM 1 6600r-6600-VM 1 6627r-6627-VM 1 6661r-6661-VM 1 6670r-6670-VM 1 6701r-6701-VM 1 6704r-6704-VM 227 6746r-6746-VM 328 6828r-6828-VM 236 6886r-6886-VM 348 6895r-6895-VM 330 6921r-6921-VM 327 6949r-6949-VM 272 6989r-6989-VM 272 7005r-7005-VM 1 7061r-7061-VM 227 7077r-7077-VM 80 75570b2beeb1-ae4c-48e1-8299-a0e820a6a14639 7619r-7619-VM 359 7620r-7620-VM 1 62356f356186-d53f-4ebe-89e5-796b9d8bf8d739 75589fb9309c-0a1d-4354-81a1-0ea4abc554c439 7674r-7674-VM 436 7816r-7816-VM 441 mysql> select id as Account,domain_id from account where id in (select account_id from vm_instance where host_id in (61,62,101) and removed is null); --+ Account domain_id --+ 1 1 11 12 39 40 44 45 74 76 80 82 128 116 227 217 236 226 272 253 280 261 292 274 301 286 303 288 313 297 327 310 328 311 330 313 348 331 359 343 371 355 402 393 436 428 441 433 --+ REPRO STEPS == was: ISSUE == A dedicated cluster has been populated with Virtual Routers from domains to which the cluster is not dedicated. The VR belongs to a non-dedicated account should not go to a dedicated cluster. TROUBLESHOOTING == >From custoemr system: mysql> select * from dedicated_resources; - id uuiddata_center_id pod_id cluster_id host_id domain_id account_id affinity_group_id - 10 dccf2f43-b9b0-443b-a614-6170cc8c70dbNULLNULL19 NULL 40 NULL66 12 efdb169f-f74e-493e-b2be-28f6d44fd0b49 NULLNULLNULL 7 NULL144 13 1419d64c-a387-4c6f-8a84-b2f110e291ec10 NULLNULLNULL 7 NULL144 16 28d92221-1c8d-45db-8696-dff9795da06912 NULLNULLNULL 7 NULL144 - mysql> select id
[jira] [Updated] (CLOUDSTACK-8962) Dedicated cluster is used for virtual routers that belong to non-dedicated account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-8962: - Description: ISSUE == A dedicated cluster has been populated with Virtual Routers from domains to which the cluster is not dedicated. The VR belongs to a non-dedicated account should not go to a dedicated cluster. TROUBLESHOOTING == >From custoemr system: mysql> select * from dedicated_resources; - id uuiddata_center_id pod_id cluster_id host_id domain_id account_id affinity_group_id - 10 dccf2f43-b9b0-443b-a614-6170cc8c70dbNULLNULL19 NULL 40 NULL66 12 efdb169f-f74e-493e-b2be-28f6d44fd0b49 NULLNULLNULL 7 NULL144 13 1419d64c-a387-4c6f-8a84-b2f110e291ec10 NULLNULLNULL 7 NULL144 16 28d92221-1c8d-45db-8696-dff9795da06912 NULLNULLNULL 7 NULL144 - mysql> select id from host where cluster_id = 19; - id - 61 62 101 - mysql> select id,name,account_id from vm_instance where host_id in (61,62,101) and removed is null; id nameaccount_id 62308f307c0a-15f5-4262-ad24-54fb9e89970039 6252a6cd3afb-4219-45b9-82a9-28b027f3c23739 6994r-6994-VM 74 7115r-7115-VM 128 7119r-7119-VM 371 7120r-7120-VM 1 7254r-7254-VM 128 7257r-7257-VM 272 7262r-7262-VM 11 7292r-7292-VM 402 7304r-7304-VM 44 7365r-7365-VM 1 7389r-7389-VM 1 755971532dab-fddb-421a-9565-34e250a3dcdc39 6111r-6111-VM 292 6123r-6123-VM 292 6149r-6149-VM 301 6151r-6151-VM 303 6160r-6160-VM 280 6256e01fb237-3b18-4978-b91e-f74487187d6939 6293r-6293-VM 313 6415r-6415-VM 272 6529r-6529-VM 272 6539r-6539-VM 1 6567r-6567-VM 1 6600r-6600-VM 1 6627r-6627-VM 1 6661r-6661-VM 1 6670r-6670-VM 1 6701r-6701-VM 1 6704r-6704-VM 227 6746r-6746-VM 328 6828r-6828-VM 236 6886r-6886-VM 348 6895r-6895-VM 330 6921r-6921-VM 327 6949r-6949-VM 272 6989r-6989-VM 272 7005r-7005-VM 1 7061r-7061-VM 227 7077r-7077-VM 80 75570b2beeb1-ae4c-48e1-8299-a0e820a6a14639 7619r-7619-VM 359 7620r-7620-VM 1 62356f356186-d53f-4ebe-89e5-796b9d8bf8d739 75589fb9309c-0a1d-4354-81a1-0ea4abc554c439 7674r-7674-VM 436 7816r-7816-VM 441 mysql> select id as Account,domain_id from account where id in (select account_id from vm_instance where host_id in (61,62,101) and removed is null); --+ Account domain_id --+ 1 1 11 12 39 40 44 45 74 76 80 82 128 116 227 217 236 226 272 253 280 261 292 274 301 286 303 288 313 297 327 310 328 311 330 313 348 331 359 343 371 355 402 393 436 428 441 433 --+ REPRO STEPS == was: ISSUE == A dedicated cluster has been populated with Virtual Routers from domains to which the cluster is not dedicated. The VR belongs to a non-dedicated account should not go to a dedicated cluster. > Dedicated cluster is used for virtual routers that belong to non-dedicated > account > -- > > Key: CLOUDSTACK-8962 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8962 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.2 >Reporter: Nitin Kumar Maharana >Priority: Blocker > > ISSUE > == > A dedicated cluster has been populated with Virtual Routers from domains to > which the cluster is not dedicated. > The VR belongs to a non-dedicated account should not go to a dedicated > cluster. > TROUBLESHOOTING > == > From custoemr system: > mysql> select * from dedicated_resources; >
[jira] [Updated] (CLOUDSTACK-8962) Dedicated cluster is used for virtual routers that belong to non-dedicated account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-8962: - Description: ISSUE == A dedicated cluster is being populated with Virtual Routers from domains/accounts to which the cluster is not dedicated. The VR belongs to a non-dedicated account should not go to a dedicated cluster. was: ISSUE == A dedicated cluster has been populated with Virtual Routers from domains to which the cluster is not dedicated. The VR belongs to a non-dedicated account should not go to a dedicated cluster. TROUBLESHOOTING == mysql> select * from dedicated_resources; - id uuiddata_center_id pod_id cluster_id host_id domain_id account_id affinity_group_id - 10 dccf2f43-b9b0-443b-a614-6170cc8c70dbNULLNULL19 NULL 40 NULL66 12 efdb169f-f74e-493e-b2be-28f6d44fd0b49 NULLNULLNULL 7 NULL144 13 1419d64c-a387-4c6f-8a84-b2f110e291ec10 NULLNULLNULL 7 NULL144 16 28d92221-1c8d-45db-8696-dff9795da06912 NULLNULLNULL 7 NULL144 - mysql> select id from host where cluster_id = 19; - id - 61 62 101 - mysql> select id,name,account_id from vm_instance where host_id in (61,62,101) and removed is null; id nameaccount_id 62308f307c0a-15f5-4262-ad24-54fb9e89970039 6252a6cd3afb-4219-45b9-82a9-28b027f3c23739 6994r-6994-VM 74 7115r-7115-VM 128 7119r-7119-VM 371 7120r-7120-VM 1 7254r-7254-VM 128 7257r-7257-VM 272 7262r-7262-VM 11 7292r-7292-VM 402 7304r-7304-VM 44 7365r-7365-VM 1 7389r-7389-VM 1 755971532dab-fddb-421a-9565-34e250a3dcdc39 6111r-6111-VM 292 6123r-6123-VM 292 6149r-6149-VM 301 6151r-6151-VM 303 6160r-6160-VM 280 6256e01fb237-3b18-4978-b91e-f74487187d6939 6293r-6293-VM 313 6415r-6415-VM 272 6529r-6529-VM 272 6539r-6539-VM 1 6567r-6567-VM 1 6600r-6600-VM 1 6627r-6627-VM 1 6661r-6661-VM 1 6670r-6670-VM 1 6701r-6701-VM 1 6704r-6704-VM 227 6746r-6746-VM 328 6828r-6828-VM 236 6886r-6886-VM 348 6895r-6895-VM 330 6921r-6921-VM 327 6949r-6949-VM 272 6989r-6989-VM 272 7005r-7005-VM 1 7061r-7061-VM 227 7077r-7077-VM 80 75570b2beeb1-ae4c-48e1-8299-a0e820a6a14639 7619r-7619-VM 359 7620r-7620-VM 1 62356f356186-d53f-4ebe-89e5-796b9d8bf8d739 75589fb9309c-0a1d-4354-81a1-0ea4abc554c439 7674r-7674-VM 436 7816r-7816-VM 441 mysql> select id as Account,domain_id from account where id in (select account_id from vm_instance where host_id in (61,62,101) and removed is null); --+ Account domain_id --+ 1 1 11 12 39 40 44 45 74 76 80 82 128 116 227 217 236 226 272 253 280 261 292 274 301 286 303 288 313 297 327 310 328 311 330 313 348 331 359 343 371 355 402 393 436 428 441 433 > Dedicated cluster is used for virtual routers that belong to non-dedicated > account > -- > > Key: CLOUDSTACK-8962 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8962 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.2 >Reporter: Nitin Kumar Maharana >Priority: Blocker > > ISSUE > == > A dedicated cluster is being populated with Virtual Routers from > domains/accounts to which the cluster is not dedicated. > The VR belongs to a non-dedicated account should not go to a dedicated > cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8962) Dedicated cluster is used for virtual routers that belong to non-dedicated account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana updated CLOUDSTACK-8962: - Description: ISSUE == A dedicated cluster has been populated with Virtual Routers from domains to which the cluster is not dedicated. The VR belongs to a non-dedicated account should not go to a dedicated cluster. TROUBLESHOOTING == mysql> select * from dedicated_resources; - id uuiddata_center_id pod_id cluster_id host_id domain_id account_id affinity_group_id - 10 dccf2f43-b9b0-443b-a614-6170cc8c70dbNULLNULL19 NULL 40 NULL66 12 efdb169f-f74e-493e-b2be-28f6d44fd0b49 NULLNULLNULL 7 NULL144 13 1419d64c-a387-4c6f-8a84-b2f110e291ec10 NULLNULLNULL 7 NULL144 16 28d92221-1c8d-45db-8696-dff9795da06912 NULLNULLNULL 7 NULL144 - mysql> select id from host where cluster_id = 19; - id - 61 62 101 - mysql> select id,name,account_id from vm_instance where host_id in (61,62,101) and removed is null; id nameaccount_id 62308f307c0a-15f5-4262-ad24-54fb9e89970039 6252a6cd3afb-4219-45b9-82a9-28b027f3c23739 6994r-6994-VM 74 7115r-7115-VM 128 7119r-7119-VM 371 7120r-7120-VM 1 7254r-7254-VM 128 7257r-7257-VM 272 7262r-7262-VM 11 7292r-7292-VM 402 7304r-7304-VM 44 7365r-7365-VM 1 7389r-7389-VM 1 755971532dab-fddb-421a-9565-34e250a3dcdc39 6111r-6111-VM 292 6123r-6123-VM 292 6149r-6149-VM 301 6151r-6151-VM 303 6160r-6160-VM 280 6256e01fb237-3b18-4978-b91e-f74487187d6939 6293r-6293-VM 313 6415r-6415-VM 272 6529r-6529-VM 272 6539r-6539-VM 1 6567r-6567-VM 1 6600r-6600-VM 1 6627r-6627-VM 1 6661r-6661-VM 1 6670r-6670-VM 1 6701r-6701-VM 1 6704r-6704-VM 227 6746r-6746-VM 328 6828r-6828-VM 236 6886r-6886-VM 348 6895r-6895-VM 330 6921r-6921-VM 327 6949r-6949-VM 272 6989r-6989-VM 272 7005r-7005-VM 1 7061r-7061-VM 227 7077r-7077-VM 80 75570b2beeb1-ae4c-48e1-8299-a0e820a6a14639 7619r-7619-VM 359 7620r-7620-VM 1 62356f356186-d53f-4ebe-89e5-796b9d8bf8d739 75589fb9309c-0a1d-4354-81a1-0ea4abc554c439 7674r-7674-VM 436 7816r-7816-VM 441 mysql> select id as Account,domain_id from account where id in (select account_id from vm_instance where host_id in (61,62,101) and removed is null); --+ Account domain_id --+ 1 1 11 12 39 40 44 45 74 76 80 82 128 116 227 217 236 226 272 253 280 261 292 274 301 286 303 288 313 297 327 310 328 311 330 313 348 331 359 343 371 355 402 393 436 428 441 433 was: ISSUE == A dedicated cluster has been populated with Virtual Routers from domains to which the cluster is not dedicated. The VR belongs to a non-dedicated account should not go to a dedicated cluster. TROUBLESHOOTING == mysql> select * from dedicated_resources; - id uuiddata_center_id pod_id cluster_id host_id domain_id account_id affinity_group_id - 10 dccf2f43-b9b0-443b-a614-6170cc8c70dbNULLNULL19 NULL 40 NULL66 12 efdb169f-f74e-493e-b2be-28f6d44fd0b49 NULLNULLNULL 7 NULL144 13 1419d64c-a387-4c6f-8a84-b2f110e291ec10 NULLNULLNULL 7 NULL144 16 28d92221-1c8d-45db-8696-dff9795da06912 NULLNULLNULL 7 NULL144 - mysql> select id from host where cluster_id = 19; - id - 61 62 101 - mysql>
[jira] [Created] (CLOUDSTACK-8930) Showing blank screen when click 'Next' link in final step of Add Zone wizard.
Nitin Kumar Maharana created CLOUDSTACK-8930: Summary: Showing blank screen when click 'Next' link in final step of Add Zone wizard. Key: CLOUDSTACK-8930 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8930 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.6.0 Reporter: Nitin Kumar Maharana Fix For: 4.6.0 Issue: Showing blank screen with 'Next' and 'Cancel' are showing when click 'Next' link in final step of Add Zone wizard. Navigate to 1st step of Add Zone wizard when click 'Next' link in blank screen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8928) While adding VMs to LB rule, default NIC IP is always displayed rather than the IP corresponding to the NIC where LB is being created
Nitin Kumar Maharana created CLOUDSTACK-8928: Summary: While adding VMs to LB rule, default NIC IP is always displayed rather than the IP corresponding to the NIC where LB is being created Key: CLOUDSTACK-8928 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8928 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana Issue : - While creating LB rule, if the VM belongs to multiple NICs, always the default NIC IP is the only one displayed. This causes issues in cases where we want to create an LB using the non-default NIC of the VM. It fails with an error message. This IP is never displayed in UI and only way is use the API directly to create such an LB rule. Steps = 1. Create a VM with multiple NICs (VM belongs to multiple networks) 2. Navigate to the non-default Network of the VM -> IP Address -> Configuration -> Load Balancing -> Create an LB rule -> Add -> Choose the VM created Observe that the IP listed does not belong to that Network. It is always the IP of the default NIC. By choosing this IP, the LB creation will fail since the IP and network ids would not match. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8919) Slow UI response while loading the list of networks in network tab.
Nitin Kumar Maharana created CLOUDSTACK-8919: Summary: Slow UI response while loading the list of networks in network tab. Key: CLOUDSTACK-8919 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8919 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Nitin Kumar Maharana Root cause of this Issue: Invokes 3 APIs, the 2nd API to check whether any network is having security group service, this consumes 90% of the time. API fetches network list and for each network calls DB to get services associated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8913) Search box in Templates tab out of alignment
Nitin Kumar Maharana created CLOUDSTACK-8913: Summary: Search box in Templates tab out of alignment Key: CLOUDSTACK-8913 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8913 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.1 Reporter: Nitin Kumar Maharana CURRENT BEHAVIOUR Search box in Templates tab is not aligned with other buttons in Firefox, Chrome, and Safari. EXPECTED BEHAVIOUR Search box in Templates tab should be aligned with other buttons in all browser. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8847) ListServiceOfferings is returning incompatible tagged offerings when called with VM id
Nitin Kumar Maharana created CLOUDSTACK-8847: Summary: ListServiceOfferings is returning incompatible tagged offerings when called with VM id Key: CLOUDSTACK-8847 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8847 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Kumar Maharana When calling listServiceOfferings with VM id as parameter. It is returning incompatible tagged offerings. It should only list all compatible tagged offerings. The new service offering should contain all the tags of the existing service offering. If that is the case It should list in the result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8821) Provide appropriate message in the UI when configuring the Firewall rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Kumar Maharana resolved CLOUDSTACK-8821. -- Resolution: Fixed > Provide appropriate message in the UI when configuring the Firewall rules > - > > Key: CLOUDSTACK-8821 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8821 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Nitin Kumar Maharana > > While adding Firewall rules, the egress rules can be to configure Allow / > Deny rules based on the Default egress policy in the network offering. > It should provide a clear message in the UI: such as if Allow – “Configure > the rules below to Block Traffic” – If Deny – “Configure the rules below to > Allow Traffic” -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8821) Provide appropriate message in the UI when configuring the Firewall rules
Nitin Kumar Maharana created CLOUDSTACK-8821: Summary: Provide appropriate message in the UI when configuring the Firewall rules Key: CLOUDSTACK-8821 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8821 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Nitin Kumar Maharana While adding Firewall rules, the egress rules can be to configure Allow / Deny rules based on the Default egress policy in the network offering. It should provide a clear message in the UI: such as if Allow – “Configure the rules below to Block Traffic” – If Deny – “Configure the rules below to Allow Traffic” -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8821) Provide appropriate message in the UI when configuring the Firewall rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734589#comment-14734589 ] Nitin Kumar Maharana commented on CLOUDSTACK-8821: -- Sure. I will add that. Thanks. > Provide appropriate message in the UI when configuring the Firewall rules > - > > Key: CLOUDSTACK-8821 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8821 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Nitin Kumar Maharana > > While adding Firewall rules, the egress rules can be to configure Allow / > Deny rules based on the Default egress policy in the network offering. > It should provide a clear message in the UI: such as if Allow – “Configure > the rules below to Block Traffic” – If Deny – “Configure the rules below to > Allow Traffic” -- This message was sent by Atlassian JIRA (v6.3.4#6332)
