[jira] [Commented] (CLOUDSTACK-9317) Disabling static NAT on many IPs can leave wrong IPs on the router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820665#comment-15820665 ] ASF GitHub Bot commented on CLOUDSTACK-9317: Github user jayapalu commented on the issue: https://github.com/apache/cloudstack/pull/1450 I tested this patch with below steps. It is not removing the ip addresses on the VR interface. Some times observed that even there is one ip with static nat but the interface got removed. Steps to test this: 1. Configure additional public subnet and acquire 4 ip addresses 2. Enabled static nat on the 4 public ip addresses. 3. Go to VR console and see the new public interface created and ips are configured on the interface. 4. Disable static on all 4 public addresses (disable from UI one by one quickly) expected: inteface should get removed from the VR. But the interface is there in VR In another case in step4 disable static nat on only 3 public ip addresses. expected: interface with one ip supposed to be there. But the interface is deleted > 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-9317) Disabling static NAT on many IPs can leave wrong IPs on the router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820693#comment-15820693 ] ASF GitHub Bot commented on CLOUDSTACK-9317: Github user ProjectMoon commented on the issue: https://github.com/apache/cloudstack/pull/1450 @jayapalu Can you post this in the new version of the fix? (And possibly re-test, if you were using an older version) > 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-9729) Spring 4.x support PR-1638 broke Nuage VSP plugin as of dependency to com.amazonaws.util.json.JSONException
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821134#comment-15821134
]
ASF GitHub Bot commented on CLOUDSTACK-9729:
GitHub user fmaximus opened a pull request:
https://github.com/apache/cloudstack/pull/1904
Use latest Nuage client.
CloudStack root pom change to use Amazon WS 11.1.16
caused our client to fail, as it was depending on classes,
which are not not present anymore.
Latest client version uses Gson instead.
BUG-ID: CLOUDSTACK-9729
Bugfix-for: master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fmaximus/cloudstack bugfix/CLOUDSTACK-9729
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1904.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 #1904
commit ec4216476eb274b970c5e319cae57887f68a45f8
Author: Frank Maximus
Date: 2017-01-12T13:15:22Z
Use latest Nuage client.
CloudStack root pom change to use Amazon WS 11.1.16
caused our client to fail, as it was depending on classes,
which are not not present anymore.
Latest client version uses Gson instead.
BUG-ID: CLOUDSTACK-9729
Bugfix-for: master
> Spring 4.x support PR-1638 broke Nuage VSP plugin as of dependency to
> com.amazonaws.util.json.JSONException
> ---
>
> Key: CLOUDSTACK-9729
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9729
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.10.0.0
>Reporter: Kris Sterckx
>Assignee: Frank Maximus
>Priority: Blocker
> Fix For: 4.10.0.0
>
>
> https://github.com/apache/cloudstack/pull/1638 has moved from
> {noformat}
> 1.10.64
> {noformat}
> to
> {noformat}
> 1.11.61
> {noformat}
> which breaks the use of com.amazonaws.util.json.JSONException
> This breaks Nuage VSP network plugin as of its dependency to
> {noformat}
> net.nuagenetworks.vsp
> nuage-vsp-acs-client
> 1.0.0
> {noformat}
>
> We need to fix that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9695) For VM in stopped state, disable "Snapshot Memory" option
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
[jira] [Commented] (CLOUDSTACK-9695) For VM in stopped state, disable "Snapshot Memory" option
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-9405) listDomains API call takes an extremely long time to respond
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
