[jira] [Updated] (CLOUDSTACK-9551) Pull KVM agent's tmp folder usage within its own folder structure

2016-10-19 Thread Abhinandan Prateek (JIRA) 

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

Abhinandan Prateek updated CLOUDSTACK-9551:
---
Summary: Pull KVM agent's tmp folder usage within its own folder structure  
(was: Pull KVM agent's tmp folder urage within its own folder structure)

> Pull KVM agent's tmp folder usage within its own folder structure
> -
>
> Key: CLOUDSTACK-9551
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9551
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.1, 4.7.1, 4.9.1.0
>Reporter: Abhinandan Prateek
>Assignee: Abhinandan Prateek
>
> We ran into an issue today where the sysadmins wanted to put /tmp on its own 
> mount and set the "noexec" mount flag as a security measure. This is 
> incompatible with the CloudStack KVM agent, because it stores JNA tmp files 
> here and Java is unable to map into these objects. To get around this we 
> moved the agent's temp dir to live with the agent files, which seems like a 
> reasonable thing to do regardless of whether you're trying to secure /tmp.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-9551) Pull KVM agent's tmp folder urage within its own folder structure

2016-10-19 Thread Abhinandan Prateek (JIRA) 

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

Abhinandan Prateek updated CLOUDSTACK-9551:
---
Affects Version/s: 4.9.1.0
   4.7.1

> Pull KVM agent's tmp folder urage within its own folder structure
> -
>
> Key: CLOUDSTACK-9551
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9551
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.1, 4.7.1, 4.9.1.0
>Reporter: Abhinandan Prateek
>Assignee: Abhinandan Prateek
>
> We ran into an issue today where the sysadmins wanted to put /tmp on its own 
> mount and set the "noexec" mount flag as a security measure. This is 
> incompatible with the CloudStack KVM agent, because it stores JNA tmp files 
> here and Java is unable to map into these objects. To get around this we 
> moved the agent's temp dir to live with the agent files, which seems like a 
> reasonable thing to do regardless of whether you're trying to secure /tmp.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CLOUDSTACK-9551) Pull KVM agent's tmp folder urage within its own folder structure

2016-10-19 Thread Abhinandan Prateek (JIRA) 
Abhinandan Prateek created CLOUDSTACK-9551:
--

 Summary: Pull KVM agent's tmp folder urage within its own folder 
structure
 Key: CLOUDSTACK-9551
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9551
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.1
Reporter: Abhinandan Prateek
Assignee: Abhinandan Prateek


We ran into an issue today where the sysadmins wanted to put /tmp on its own 
mount and set the "noexec" mount flag as a security measure. This is 
incompatible with the CloudStack KVM agent, because it stores JNA tmp files 
here and Java is unable to map into these objects. To get around this we moved 
the agent's temp dir to live with the agent files, which seems like a 
reasonable thing to do regardless of whether you're trying to secure /tmp.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (CLOUDSTACK-6664) support Docker as a new hypervisor

2016-10-19 Thread tuna (JIRA) 

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

tuna closed CLOUDSTACK-6664.

   Resolution: Won't Fix
Fix Version/s: (was: Future)

> support Docker as a new hypervisor
> --
>
> Key: CLOUDSTACK-6664
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6664
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Hypervisor Controller
>Affects Versions: Future
>Reporter: tuna
>Assignee: tuna
>
> Supporting Docker as a new hypervisor, which can spawn containers from 
> Dockerfile, Docker image or Docker tar file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-6664) support Docker as a new hypervisor

2016-10-19 Thread tuna (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589754#comment-15589754
 ] 

tuna commented on CLOUDSTACK-6664:
--

Hi, this issue was presented at CCCNA14 as a demo and hadn't follow-up 
development due to running a single container is meaningless. For running 
Docker cluster in CloudStack, please take a look at: 
http://www.shapeblue.com/cloudstack-container-service/

> support Docker as a new hypervisor
> --
>
> Key: CLOUDSTACK-6664
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6664
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Hypervisor Controller
>Affects Versions: Future
>Reporter: tuna
>Assignee: tuna
> Fix For: Future
>
>
> Supporting Docker as a new hypervisor, which can spawn containers from 
> Dockerfile, Docker image or Docker tar file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9395) Add VirtIO Random Number Geneator to KVM Instances

2016-10-19 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589647#comment-15589647
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9395:


Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1572
  
@mlsorensen We can indeed do that, but the good thing for now is that the 
RNG is disabled by default.

You also need a very ancient libvirt for it not to support RNG and that 
will get less and less over time.


> Add VirtIO Random Number Geneator to KVM Instances
> --
>
> Key: CLOUDSTACK-9395
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9395
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: kvm, libvirt, virtio
> Fix For: Future
>
>
> Add a VirtIO Random Number Generator (RNG) to all Instances to prevent 
> entropy starvation in guests.
> More information:
> - https://libvirt.org/formatdomain.html
> - https://fedoraproject.org/wiki/Features/Virtio_RNG
> In the end this make sure the Entropy performance in Instances is better



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9395) Add VirtIO Random Number Geneator to KVM Instances

2016-10-19 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589200#comment-15589200
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9395:


Github user mlsorensen commented on the issue:

https://github.com/apache/cloudstack/pull/1572
  
I realize I'm late to the party on this, but I'd like to suggest that we 
change from the agent.properties "vm.rng.enable=true" to simply using the 
libvirt version detection like we do for other things, and perhaps allow a 
"vm.rng.disable". It really seems like this is a useful setting and should 
probably be default wherever possible.


> Add VirtIO Random Number Geneator to KVM Instances
> --
>
> Key: CLOUDSTACK-9395
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9395
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: kvm, libvirt, virtio
> Fix For: Future
>
>
> Add a VirtIO Random Number Generator (RNG) to all Instances to prevent 
> entropy starvation in guests.
> More information:
> - https://libvirt.org/formatdomain.html
> - https://fedoraproject.org/wiki/Features/Virtio_RNG
> In the end this make sure the Entropy performance in Instances is better



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9183) CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

2016-10-19 Thread Paul Angus (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589098#comment-15589098
 ] 

Paul Angus commented on CLOUDSTACK-9183:


Pull suggests that reviewers check code that files were no longer in use.
obviously they were wrong, 5 mins digging yields:

getRouterAlerts.sh referenced as ROUTER_ALERTS
https://github.com/apache/cloudstack/blob/87ef8137534fa798101f65c6691fcf71513ac978/core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java#L57

ROUTER_ALERTS used by GetRouterAlertsAnswer 
https://github.com/apache/cloudstack/blob/87ef8137534fa798101f65c6691fcf71513ac978/core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java#L225

then it gets confusing because there is another GetRouterAlertsAnswer

import com.cloud.agent.api.GetRouterAlertsAnswer;
https://github.com/apache/cloudstack/blob/87ef8137534fa798101f65c6691fcf71513ac978/core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java#L46



> CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory
> ---
>
> Key: CLOUDSTACK-9183
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9183
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM
>Affects Versions: 4.7.0
> Environment: CloudStack 4.7.0 RC1, Ubuntu 14.04.3, KVM, NFS
>Reporter: Milamber
>  Labels: kvm, systemvm
>
> On my 4.7.0 RC1 test environment, I've this warning message:
> 2015-12-15 23:57:35,165 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get alerts 
> from router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or 
> directory
> I don't find this bash script anywhere (on management node, host node and 
> inside the VR)
> I find theses references to this script inside:
> public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
> ./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java
> ExecutionResult result = _vrDeployer.executeInVR(routerIp, 
> VRScripts.ROUTER_ALERTS, args);
> ./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9183) CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

2016-10-19 Thread Paul Angus (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589064#comment-15589064
 ] 

Paul Angus commented on CLOUDSTACK-9183:


I've found where it was removed.

$ git log -1 -- systemvm/patches/debian/config/opt/cloud/bin/getRouterAlerts.sh
commit 6477bd8ff7f982e10d0d20a97857262897dc05ed
Author: Wilder Rodrigues 
Date:   Tue Nov 17 12:14:56 2015 +0100

CLOUDSTACK-9067 - Remove old script file from the project

   - Java constants also removed
   - Project still compiling and all unit tests passing.


> CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory
> ---
>
> Key: CLOUDSTACK-9183
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9183
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM
>Affects Versions: 4.7.0
> Environment: CloudStack 4.7.0 RC1, Ubuntu 14.04.3, KVM, NFS
>Reporter: Milamber
>  Labels: kvm, systemvm
>
> On my 4.7.0 RC1 test environment, I've this warning message:
> 2015-12-15 23:57:35,165 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get alerts 
> from router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or 
> directory
> I don't find this bash script anywhere (on management node, host node and 
> inside the VR)
> I find theses references to this script inside:
> public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
> ./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java
> ExecutionResult result = _vrDeployer.executeInVR(routerIp, 
> VRScripts.ROUTER_ALERTS, args);
> ./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9183) CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

2016-10-19 Thread Paul Angus (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588830#comment-15588830
 ] 

Paul Angus commented on CLOUDSTACK-9183:


on VMware with 4.6 i am seeing
getRouterAlerts.sh permission denied in the logs.

> CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory
> ---
>
> Key: CLOUDSTACK-9183
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9183
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM
>Affects Versions: 4.7.0
> Environment: CloudStack 4.7.0 RC1, Ubuntu 14.04.3, KVM, NFS
>Reporter: Milamber
>  Labels: kvm, systemvm
>
> On my 4.7.0 RC1 test environment, I've this warning message:
> 2015-12-15 23:57:35,165 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get alerts 
> from router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or 
> directory
> I don't find this bash script anywhere (on management node, host node and 
> inside the VR)
> I find theses references to this script inside:
> public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
> ./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java
> ExecutionResult result = _vrDeployer.executeInVR(routerIp, 
> VRScripts.ROUTER_ALERTS, args);
> ./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9550) Metrics view does not filter items based on zone/cluster/host it is in

2016-10-19 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588138#comment-15588138
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9550:


Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1712
  
I've navigated through Zone -> Compute and Storage -> to clusters, hosts 
and pr storages -> Metrics View. All the resources are there and they seem to 
be showing the same as from infrastructure. LGTM  

![screen shot 2016-10-19 at 12 09 33 
pm](https://cloud.githubusercontent.com/assets/13551960/19512588/53bc16de-95f5-11e6-8c7b-2021df29b8f2.png)

![screen shot 2016-10-19 at 12 09 47 
pm](https://cloud.githubusercontent.com/assets/13551960/19512589/53bd57c4-95f5-11e6-8aaa-a356c040ff67.png)

![screen shot 2016-10-19 at 12 10 52 
pm](https://cloud.githubusercontent.com/assets/13551960/19512587/53bb1efa-95f5-11e6-9f48-456f711274df.png)

![screen shot 2016-10-19 at 12 11 56 
pm](https://cloud.githubusercontent.com/assets/13551960/19512590/53bf8666-95f5-11e6-9c83-528cd007a75b.png)



> Metrics view does not filter items based on zone/cluster/host it is in
> --
>
> Key: CLOUDSTACK-9550
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9550
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
> Fix For: 4.10.0.0, 4.9.2.0, 4.8.2.0
>
>
> Go to zone -> compute and storage tab -> browse any of the resources under it 
> which have metrics view such as clusters, hosts, storage pool etc. The 
> metrics view on those resources don't filter items based on the 
> zone/cluster/host it is in, and ends up showing all the 
> cluster/host/storage-pool items.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9550) Metrics view does not filter items based on zone/cluster/host it is in

2016-10-19 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587980#comment-15587980
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9550:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1712
  
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-64


> Metrics view does not filter items based on zone/cluster/host it is in
> --
>
> Key: CLOUDSTACK-9550
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9550
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
> Fix For: 4.10.0.0, 4.9.2.0, 4.8.2.0
>
>
> Go to zone -> compute and storage tab -> browse any of the resources under it 
> which have metrics view such as clusters, hosts, storage pool etc. The 
> metrics view on those resources don't filter items based on the 
> zone/cluster/host it is in, and ends up showing all the 
> cluster/host/storage-pool items.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9550) Metrics view does not filter items based on zone/cluster/host it is in

2016-10-19 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587920#comment-15587920
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9550:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1712
  
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


> Metrics view does not filter items based on zone/cluster/host it is in
> --
>
> Key: CLOUDSTACK-9550
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9550
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
> Fix For: 4.10.0.0, 4.9.2.0, 4.8.2.0
>
>
> Go to zone -> compute and storage tab -> browse any of the resources under it 
> which have metrics view such as clusters, hosts, storage pool etc. The 
> metrics view on those resources don't filter items based on the 
> zone/cluster/host it is in, and ends up showing all the 
> cluster/host/storage-pool items.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9550) Metrics view does not filter items based on zone/cluster/host it is in

2016-10-19 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587919#comment-15587919
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9550:


Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1712
  
@blueorangutan package


> Metrics view does not filter items based on zone/cluster/host it is in
> --
>
> Key: CLOUDSTACK-9550
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9550
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
> Fix For: 4.10.0.0, 4.9.2.0, 4.8.2.0
>
>
> Go to zone -> compute and storage tab -> browse any of the resources under it 
> which have metrics view such as clusters, hosts, storage pool etc. The 
> metrics view on those resources don't filter items based on the 
> zone/cluster/host it is in, and ends up showing all the 
> cluster/host/storage-pool items.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9550) Metrics view does not filter items based on zone/cluster/host it is in

2016-10-19 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587873#comment-15587873
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9550:


Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1712
  
@borisstoyanov can you help with manual testing of the fix with some 
screenshots, thanks.


> Metrics view does not filter items based on zone/cluster/host it is in
> --
>
> Key: CLOUDSTACK-9550
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9550
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
> Fix For: 4.10.0.0, 4.9.2.0, 4.8.2.0
>
>
> Go to zone -> compute and storage tab -> browse any of the resources under it 
> which have metrics view such as clusters, hosts, storage pool etc. The 
> metrics view on those resources don't filter items based on the 
> zone/cluster/host it is in, and ends up showing all the 
> cluster/host/storage-pool items.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-9550) Metrics view does not filter items based on zone/cluster/host it is in

2016-10-19 Thread Rohit Yadav (JIRA) 

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

Rohit Yadav updated CLOUDSTACK-9550:

Status: Reviewable  (was: In Progress)

> Metrics view does not filter items based on zone/cluster/host it is in
> --
>
> Key: CLOUDSTACK-9550
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9550
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
> Fix For: 4.10.0.0, 4.9.2.0, 4.8.2.0
>
>
> Go to zone -> compute and storage tab -> browse any of the resources under it 
> which have metrics view such as clusters, hosts, storage pool etc. The 
> metrics view on those resources don't filter items based on the 
> zone/cluster/host it is in, and ends up showing all the 
> cluster/host/storage-pool items.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9550) Metrics view does not filter items based on zone/cluster/host it is in

2016-10-19 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587867#comment-15587867
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9550:


GitHub user rhtyd opened a pull request:

https://github.com/apache/cloudstack/pull/1712

CLOUDSTACK-9550: Use context to filter items in a metrics view

Use available context to filter a metrics view based on zone, cluster, host
in the context object. This fixes metrics view filtering when metrics view 
is
viewed via Zone->Compute and Storage-> for a resource.

/cc @jburwell @karuturi -- this is a pure UI fix, one manual test LGTM 
would be required.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shapeblue/cloudstack 
metrics-view-context-filtering

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1712.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1712


commit 2767e1ade6cd9918ea952be4898d02ae30479feb
Author: Rohit Yadav 
Date:   2016-10-19T06:11:08Z

CLOUDSTACK-9550: Use context to filter items in a metrics view

Use available context to filter a metrics view based on zone, cluster, host
in the context object. This fixes metrics view filtering when metrics view 
is
viewed via Zone->Compute and Storage-> for a resource.

Signed-off-by: Rohit Yadav 




> Metrics view does not filter items based on zone/cluster/host it is in
> --
>
> Key: CLOUDSTACK-9550
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9550
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
> Fix For: 4.10.0.0, 4.9.2.0, 4.8.2.0
>
>
> Go to zone -> compute and storage tab -> browse any of the resources under it 
> which have metrics view such as clusters, hosts, storage pool etc. The 
> metrics view on those resources don't filter items based on the 
> zone/cluster/host it is in, and ends up showing all the 
> cluster/host/storage-pool items.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CLOUDSTACK-9550) Metrics view does not filter items based on zone/cluster/host it is in

2016-10-19 Thread Rohit Yadav (JIRA) 
Rohit Yadav created CLOUDSTACK-9550:
---

 Summary: Metrics view does not filter items based on 
zone/cluster/host it is in
 Key: CLOUDSTACK-9550
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9550
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Rohit Yadav
Assignee: Rohit Yadav
 Fix For: 4.10.0.0, 4.9.2.0, 4.8.2.0


Go to zone -> compute and storage tab -> browse any of the resources under it 
which have metrics view such as clusters, hosts, storage pool etc. The metrics 
view on those resources don't filter items based on the zone/cluster/host it is 
in, and ends up showing all the cluster/host/storage-pool items.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)