[jira] [Commented] (CLOUDSTACK-9710) Switch to JDK 1.8

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9710:
-

Github user syed commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
@rhtyd I tried building the latest master I have problems getting the SSVM 
and the console proxy up. I get the following error 

```
4 localgw=172.31.0.1 private.network.device=eth1 internaldns1=8.8.8.8 
dns1=8.8.8.8 nfsVersion=null
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
com/cloud/agent/AgentShell : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at 
sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
```

The management server is running Java 8 but it looks like the systemvms are 
still running java 7. How can I upgrade the java version there? 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> Switch to JDK 1.8
> -
>
> Key: CLOUDSTACK-9710
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9710
> 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: Future, 4.10.0.0
>
>
> Switch to using JDK1.8 by default for building and running CloudStack.



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

[jira] [Commented] (CLOUDSTACK-9405) listDomains API call takes an extremely long time to respond

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9405:
-

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1901
  
Thanks @ustcweizhou LGTM for code review


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> listDomains API call takes an extremely long time to respond
> 
>
> Key: CLOUDSTACK-9405
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9405
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.8.0
>Reporter: dsclose
>  Labels: performance
>
> We recently upgraded from Cloudstack 4.5.2 to Cloudstack 4.8.0. Since this 
> update, the listDomains API call has started taking an extremely long time to 
> respond. This has caused issues with our services that rely on this API call. 
> Initially they simply timed out until we increased the thresholds. Now we 
> have processes that used to take a few seconds taking many minutes.
> This is so problematic for us that our organisation has put a halt on further 
> updates of Cloudstack 4.5.2 installations. If reversing the update of zones 
> already on 4.8.0 was feasible, we would have reverted back to 4.5.2.
> Here is a table of the times we're seeing:
> ||CS Version||Domain Count||API Response Time||
> |4.5.2|251|~3s|
> |4.8.0|182|~26s|
> |4.8.0|<10|<1s|
> This small data sample indicates that the response time for zones with a 
> larger amount of domains is significantly worse after the update to 4.8.0. 
> Zones with few domains aren't able to reproduce this issue.
> I recall a bug being resolved recently that concerned reducing the response 
> time for list* API calls. I also recall [~remibergsma] resolving a bug 
> concerning the sorting of the listDomains response. Is it possible that these 
> issues are connected?



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

[jira] [Commented] (CLOUDSTACK-9738) Optimize vm expunge process for instances with vm snapshots

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9738:
-

GitHub user nvazquez opened a pull request:

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

CLOUDSTACK-9738: Optimize vm expunge process for instances with vm snapshots

## Description
It was noticed that expunging instances with many vm snapshots took a look 
of time, as hypervisor received as many tasks as vm snapshots instance had, 
apart from the delete vm task. We propose a way to optimize this process for 
instances with vm snapshots by sending only one delete task to hypervisor, 
which will delete vm and its snapshots

## Use cases

1. deleteVMsnapohsot-> no changes to current behavior
2. destroyVM with expunge=false ->  no actions to VMsnaphsot is performed 
at the moment. When VM cleanup thread is executed it will perform the same 
sequence as (3). If instance is recovered before expunged by the cleanup thread 
it will remain intact with VMSnapshot chain present
3. destroyVM with expunge=true:
   * Vmsnaphsot is marked with removed timestamp and state = Expunging in DB
   * VM is deleted in HW

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

$ git pull https://github.com/nvazquez/cloudstack expungeVmRefactor

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

https://github.com/apache/cloudstack/pull/1905.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 #1905


commit f5bebb172c36710a3c795a0df542fe443c71a2c9
Author: nvazquez 
Date:   2017-01-09T20:08:32Z

CLOUDSTACK-9738: Optimize vm expunge process for instances with vm snapshots




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> Optimize vm expunge process for instances with vm snapshots
> ---
>
> Key: CLOUDSTACK-9738
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9738
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Fix For: 4.10.0.0
>
>
> h2. Description
> It was noticed that expunging instances with many vm snapshots took a look of 
> time, as hypervisor received as many tasks as vm snapshots instance had, 
> apart from the delete vm task. We propose a way to optimize this process for 
> instances with vm snapshots by sending only one delete task to hypervisor, 
> which will delete vm and its snapshots
> h2. Use cases
> # deleteVMsnapohsot-> no changes to current behavior
> # destroyVM with expunge=false ->  no actions to VMsnaphsot is performed at 
> the moment. When VM cleanup thread is executed it will perform the same 
> sequence as #3. If instance is recovered before expunged by the cleanup 
> thread it will remain intact with VMSnapshot chain present
> # destroyVM with expunge=true:
> #*   Vmsnaphsot is  marked with removed timestamp and state = Expunging 
> in DB
> #*   VM is deleted in HW



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

[jira] [Commented] (CLOUDSTACK-9695) For VM in stopped state, disable "Snapshot Memory" option

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9695:
-

Github user ustcweizhou commented on the issue:

https://github.com/apache/cloudstack/pull/1852
  
why not change vmActionfilter in ui/scripts/instances.js ?
it will be much simple.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> For VM in stopped state, disable "Snapshot Memory" option
> -
>
> Key: CLOUDSTACK-9695
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9695
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
>Priority: Minor
> Fix For: 4.10.0.0
>
>
> For a VM in stopped state, the UI for VM snapshot creation shows an option 
> for 'snapshot memory'. Since this is not a valid option at that point, it 
> should be disabled.



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

[jira] [Commented] (CLOUDSTACK-9136) SSH keypairs are left and cannot be removed after removing account

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9136:
-

Github user ustcweizhou closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> SSH keypairs are left and cannot be removed after removing account
> --
>
> Key: CLOUDSTACK-9136
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9136
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Wei Zhou
>Assignee: Wei Zhou
>
> When we remove an account who have some ssh keypairs created/registered, the 
> keypairs are left in cloudstack, we can still list it in Account->SSH Keypair 
> page, but cannot remove them.



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

[jira] [Commented] (CLOUDSTACK-9136) SSH keypairs are left and cannot be removed after removing account

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9136:
-

Github user ustcweizhou commented on the issue:

https://github.com/apache/cloudstack/pull/1212
  
rebased with apache/4.9, and added unit test


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> SSH keypairs are left and cannot be removed after removing account
> --
>
> Key: CLOUDSTACK-9136
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9136
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Wei Zhou
>Assignee: Wei Zhou
>
> When we remove an account who have some ssh keypairs created/registered, the 
> keypairs are left in cloudstack, we can still list it in Account->SSH Keypair 
> page, but cannot remove them.



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

[jira] [Commented] (CLOUDSTACK-9136) SSH keypairs are left and cannot be removed after removing account

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9136:
-

GitHub user ustcweizhou reopened a pull request:

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

CLOUDSTACK-9136: remove ssh keypairs along with removing account

We also allow ROOT Admin to remove remained ssh keypairs of removed account


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

$ git pull https://github.com/ustcweizhou/cloudstack remove-ssh-keypairs

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

https://github.com/apache/cloudstack/pull/1212.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 #1212


commit e57adc195cd12d9cffe1c55080e96bf07ef4473e
Author: Wei Zhou 
Date:   2015-12-10T13:25:22Z

CLOUDSTACK-9136: remove ssh keypairs along with removing account

We also allow ROOT Admin to remove remained ssh keypairs of removed account




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> SSH keypairs are left and cannot be removed after removing account
> --
>
> Key: CLOUDSTACK-9136
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9136
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Wei Zhou
>Assignee: Wei Zhou
>
> When we remove an account who have some ssh keypairs created/registered, the 
> keypairs are left in cloudstack, we can still list it in Account->SSH Keypair 
> page, but cannot remove them.



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

[jira] [Commented] (CLOUDSTACK-9165) unable to use reserved IP range in a network for external VMs

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9165:
-

Github user SudharmaJain commented on the issue:

https://github.com/apache/cloudstack/pull/1246
  
Moved the getValidNetworkCidr to common class NetworkModel and Rebased with 
master.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> unable to use reserved IP range in a network for external VMs
> -
>
> Key: CLOUDSTACK-9165
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9165
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: sudharma jain
>




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

[jira] [Commented] (CLOUDSTACK-9317) Disabling static NAT on many IPs can leave wrong IPs on the router

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9317:
-

Github user jayapalu commented on the issue:

https://github.com/apache/cloudstack/pull/1450
  
@ProjectMoon 
I am working on it. I will be updating the fix.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> Disabling static NAT on many IPs can leave wrong IPs on the router
> --
>
> Key: CLOUDSTACK-9317
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9317
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, Virtual Router
>Affects Versions: 4.7.0, 4.7.1, 4.7.2
>Reporter: Jeff Hair
>
> The current behavior of enabling or disabling static NAT will call the apply 
> IP associations method in the management server. The method is not 
> thread-safe. If it's called from multiple threads, each thread will load up 
> the list of public IPs in different states (add or revoke)--correct for the 
> thread, but not correct overall. Depending on execution order on the virtual 
> router, the router can end up with public IPs assigned to it that are not 
> supposed to be on it anymore. When another account acquires the same IP, this 
> of course leads to network problems.
> The problem has been in CS since at least 4.2, and likely affects all 
> recently released versions. Affected version is set to 4.7.x because that's 
> what we verified against.



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

[jira] [Commented] (CLOUDSTACK-9653) listCapacity API shows incorrect output when sortBy=usage option is added

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9653:
-

Github user koushik-das commented on the issue:

https://github.com/apache/cloudstack/pull/1819
  
Code changes LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> listCapacity API shows incorrect output when sortBy=usage option is added
> -
>
> Key: CLOUDSTACK-9653
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9653
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> listCapacity API does not sum up values correctly when used with sortBy=usage 
> option.



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

[jira] [Commented] (CLOUDSTACK-9718) Revamp the dropdown showing lists of hosts available for migration in a Zone

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9718:
-

Github user koushik-das commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1889#discussion_r95973044
  
--- Diff: 
api/src/org/apache/cloudstack/api/command/admin/host/ListHostsCmd.java ---
@@ -206,7 +206,7 @@ public void execute() {
 } else {
 Pair result;
 Ternary, List, Map> hostsForMigration =
-_mgr.listHostsForMigrationOfVM(getVirtualMachineId(), 
this.getStartIndex(), this.getPageSizeVal());
+_mgr.listHostsForMigrationOfVM(getVirtualMachineId(), 
this.getStartIndex(), this.getPageSizeVal(), null);
--- End diff --

Why keyword is not used here? All API commands derived from BaseListCmd 
should have keyword.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> Revamp the dropdown showing lists of hosts available for migration in a Zone
> 
>
> Key: CLOUDSTACK-9718
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9718
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.10.0.0
>
> Attachments: MigrateInstance-SeeHosts.PNG, 
> MigrateInstance-SeeHosts-Search.PNG
>
>
> There are a couple of issues:
> 1. When looking for the possible hosts for migration, not all are displayed.
> 2. If there is a large number of hosts, then the drop down showing is not 
> easy to use.
> To fix this, propose to change the view to a list view which will show the 
> hosts in a list view with radio button. Additionally have a search option 
> where the hostname can be searched in this list to make it more usable.



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

[jira] [Commented] (CLOUDSTACK-9718) Revamp the dropdown showing lists of hosts available for migration in a Zone

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9718:
-

Github user koushik-das commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1889#discussion_r95973392
  
--- Diff: ui/scripts/ui-custom/migrate.js ---
@@ -0,0 +1,127 @@
+// Licensed to the Apache Software Foundation (ASF) under one
--- End diff --

For UI changes please provide UI screenshots


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> Revamp the dropdown showing lists of hosts available for migration in a Zone
> 
>
> Key: CLOUDSTACK-9718
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9718
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.10.0.0
>
> Attachments: MigrateInstance-SeeHosts.PNG, 
> MigrateInstance-SeeHosts-Search.PNG
>
>
> There are a couple of issues:
> 1. When looking for the possible hosts for migration, not all are displayed.
> 2. If there is a large number of hosts, then the drop down showing is not 
> easy to use.
> To fix this, propose to change the view to a list view which will show the 
> hosts in a list view with radio button. Additionally have a search option 
> where the hostname can be searched in this list to make it more usable.



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

[jira] [Commented] (CLOUDSTACK-9693) Cluster status of an unmanaged cluster still shows enabled

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9693:
-

Github user koushik-das commented on the issue:

https://github.com/apache/cloudstack/pull/1848
  
@rashmidixit Please provide screenshots for UI changes (better if you also 
provide screenshot prior to the fix). Also for a cluster enabled/disabled and 
managed/unmanaged are different properties.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> Cluster status of an unmanaged cluster still shows enabled
> --
>
> Key: CLOUDSTACK-9693
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9693
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.7.1, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
> Fix For: 4.9.1.0
>
>
> If you unmanage a cluster, Cluster view status remains Enabled.
> The status is successfully changed in cluster metrics page.
> It should show as red if the cluster is disabled.



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

[jira] [Commented] (CLOUDSTACK-9695) For VM in stopped state, disable "Snapshot Memory" option

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9695:
-

Github user koushik-das commented on the issue:

https://github.com/apache/cloudstack/pull/1852
  
@rashmidixit Code LGTM. Please provide screenshots of the changes.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> For VM in stopped state, disable "Snapshot Memory" option
> -
>
> Key: CLOUDSTACK-9695
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9695
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
>Priority: Minor
> Fix For: 4.10.0.0
>
>
> For a VM in stopped state, the UI for VM snapshot creation shows an option 
> for 'snapshot memory'. Since this is not a valid option at that point, it 
> should be disabled.



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

[jira] [Commented] (CLOUDSTACK-8958) add dedicated ips to domain

2017-01-13 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-8958:
-

Github user ustcweizhou commented on the issue:

https://github.com/apache/cloudstack/pull/1357
  
rebased with 4.9.3,  and added unit tests (deleteDomain with/without 
cleanup).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> add dedicated ips to domain
> ---
>
> Key: CLOUDSTACK-8958
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8958
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Wei Zhou
>Assignee: Wei Zhou
>
> add dedicated ips to domain 
> ips are dedicated to Account for now, so other customers and projects in the 
> same domain will use the system ip. this is not what we need.



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

[jira] [Commented] (CLOUDSTACK-9405) listDomains API call takes an extremely long time to respond

2017-01-12 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9405:
-

Github user ustcweizhou commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1901#discussion_r95948158
  
--- Diff: 
api/src/org/apache/cloudstack/api/command/admin/domain/ListDomainsCmd.java ---
@@ -53,6 +59,12 @@
description = "If set to false, list only resources 
belonging to the command's caller; if set to true - list resources that the 
caller is authorized to see. Default value is false")
 private Boolean listAll;
 
+@Parameter(name = ApiConstants.DETAILS,
+   type = CommandType.LIST,
+   collectionType = CommandType.STRING,
+   description = "comma separated list of host details 
requested, value can be a list of [ all, resource, min]")
--- End diff --

@serg38 currently no difference. However if we want to add more type of 
details, then it will be useful. for example, we add a new detail type: stats 
in our branch.

the defition is copied from listhosts API (you can see host details in the 
decription, I will change it).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> listDomains API call takes an extremely long time to respond
> 
>
> Key: CLOUDSTACK-9405
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9405
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.8.0
>Reporter: dsclose
>  Labels: performance
>
> We recently upgraded from Cloudstack 4.5.2 to Cloudstack 4.8.0. Since this 
> update, the listDomains API call has started taking an extremely long time to 
> respond. This has caused issues with our services that rely on this API call. 
> Initially they simply timed out until we increased the thresholds. Now we 
> have processes that used to take a few seconds taking many minutes.
> This is so problematic for us that our organisation has put a halt on further 
> updates of Cloudstack 4.5.2 installations. If reversing the update of zones 
> already on 4.8.0 was feasible, we would have reverted back to 4.5.2.
> Here is a table of the times we're seeing:
> ||CS Version||Domain Count||API Response Time||
> |4.5.2|251|~3s|
> |4.8.0|182|~26s|
> |4.8.0|<10|<1s|
> This small data sample indicates that the response time for zones with a 
> larger amount of domains is significantly worse after the update to 4.8.0. 
> Zones with few domains aren't able to reproduce this issue.
> I recall a bug being resolved recently that concerned reducing the response 
> time for list* API calls. I also recall [~remibergsma] resolving a bug 
> concerning the sorting of the listDomains response. Is it possible that these 
> issues are connected?



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

[jira] [Commented] (CLOUDSTACK-9695) For VM in stopped state, disable "Snapshot Memory" option

2017-01-12 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9695:
-

GitHub user rashmidixit reopened a pull request:

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

CLOUDSTACK-9695: VM snapshot is disabled if the VM Instance is off

Refer to 
[CLOUDSTACK-9695](https://issues.apache.org/jira/browse/CLOUDSTACK-9695) for 
more details.

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

$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9695

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

https://github.com/apache/cloudstack/pull/1852.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 #1852


commit 00a47802ce279900fef444ec7069b57418dda204
Author: Sanket Thite 
Date:   2016-07-12T09:50:47Z

VM snapshot is disabled if the VM Instance is off




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> For VM in stopped state, disable "Snapshot Memory" option
> -
>
> Key: CLOUDSTACK-9695
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9695
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
>Priority: Minor
> Fix For: 4.10.0.0
>
>
> For a VM in stopped state, the UI for VM snapshot creation shows an option 
> for 'snapshot memory'. Since this is not a valid option at that point, it 
> should be disabled.



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

[jira] [Commented] (CLOUDSTACK-9695) For VM in stopped state, disable "Snapshot Memory" option

2017-01-12 Thread rashmidixit (JIRA) 

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

rashmidixit commented on CLOUDSTACK-9695:
-

Github user rashmidixit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


> For VM in stopped state, disable "Snapshot Memory" option
> -
>
> Key: CLOUDSTACK-9695
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9695
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
>Priority: Minor
> Fix For: 4.10.0.0
>
>
> For a VM in stopped state, the UI for VM snapshot creation shows an option 
> for 'snapshot memory'. Since this is not a valid option at that point, it 
> should be disabled.



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

<    1   2