[jira] [Created] (CLOUDSTACK-4231) make apache server listen on all the ipaliases to provide access to meta-data.

Bharat Kumar created CLOUDSTACK-4231: Summary: make apache server listen on all the ipaliases to provide access to meta-data. Key: CLOUDSTACK-4231 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4231

[jira] [Updated] (CLOUDSTACK-4231) make apache server listen on all the ipaliases to provide access to meta-data.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4231: - Issue Type: Bug (was: Improvement) > make apache server listen on all the ipali

[jira] [Commented] (CLOUDSTACK-4231) make apache server listen on all the ipaliases to provide access to meta-data.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736220#comment-13736220 ] Bharat Kumar commented on CLOUDSTACK-4231: -- Changed the issue type to bug to

[jira] [Updated] (CLOUDSTACK-4231) make apache server listen on all the ipaliases to provide access to meta-data.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4231: - Status: Ready To Review (was: In Progress) > make apache server listen on all t

[jira] [Created] (CLOUDSTACK-4236) update the docs as per the latest changes to multiple subnets feature.

Bharat Kumar created CLOUDSTACK-4236: Summary: update the docs as per the latest changes to multiple subnets feature. Key: CLOUDSTACK-4236 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4236

[jira] [Resolved] (CLOUDSTACK-4231) make apache server listen on all the ipaliases to provide access to meta-data.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-4231. -- Resolution: Fixed > make apache server listen on all the ipaliases to provide

[jira] [Commented] (CLOUDSTACK-4132) current dnsmasq config does not allow guest virtual machines(clients) to update its hostnames with a DNS server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738619#comment-13738619 ] Bharat Kumar commented on CLOUDSTACK-4132: -- I tried to do some sanity checks

[jira] [Commented] (CLOUDSTACK-4132) current dnsmasq config does not allow guest virtual machines(clients) to update its hostnames with a DNS server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738641#comment-13738641 ] Bharat Kumar commented on CLOUDSTACK-4132: -- i can see the option 81 in both

[jira] [Created] (CLOUDSTACK-4317) make the regular expressions in dnsmaq.sh tighter to avoid matching ip6dns in command line.

Bharat Kumar created CLOUDSTACK-4317: Summary: make the regular expressions in dnsmaq.sh tighter to avoid matching ip6dns in command line. Key: CLOUDSTACK-4317 URL: https://issues.apache.org/jira/browse/CLOUDS

[jira] [Updated] (CLOUDSTACK-4317) make the regular expressions in dnsmaq.sh tighter to avoid matching ip6dns in command line.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4317: - Status: Ready To Review (was: In Progress) > make the regular expressions in dn

[jira] [Updated] (CLOUDSTACK-4132) current dnsmasq config does not allow guest virtual machines(clients) to update its hostnames with a DNS server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4132: - Status: Ready To Review (was: In Progress) > current dnsmasq config does not al

[jira] [Resolved] (CLOUDSTACK-4068) scaling up user vm and system vm is failing with NPE if current service offering is deleted

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-4068. -- Resolution: Fixed > scaling up user vm and system vm is failing with NPE if

[jira] [Commented] (CLOUDSTACK-4132) current dnsmasq config does not allow guest virtual machines(clients) to update its hostnames with a DNS server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742827#comment-13742827 ] Bharat Kumar commented on CLOUDSTACK-4132: -- This was introduced in the versi

[jira] [Resolved] (CLOUDSTACK-4132) current dnsmasq config does not allow guest virtual machines(clients) to update its hostnames with a DNS server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-4132. -- Resolution: Fixed > current dnsmasq config does not allow guest virtual machin

[jira] [Created] (CLOUDSTACK-4498) we should not reserver memory and cpu for vmware VMs if the vmware.reserve.cpu and vmware.reserve.mem are set to false.

Bharat Kumar created CLOUDSTACK-4498: Summary: we should not reserver memory and cpu for vmware VMs if the vmware.reserve.cpu and vmware.reserve.mem are set to false. Key: CLOUDSTACK-4498 URL: https://issues.a

[jira] [Updated] (CLOUDSTACK-2997) HAProxy maxconn is not configurable

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-2997: - Status: Ready To Review (was: In Progress) > HAProxy maxconn is not configurabl

[jira] [Resolved] (CLOUDSTACK-3910) Upgrade from 3.0.6 to 4.2 is failing with DB exceptions.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3910. -- Resolution: Fixed commit hash in 4.2 03cbf51e159a452f18f560ac64c6ae64e34df12c

[jira] [Resolved] (CLOUDSTACK-2622) createipAlias.sh/deleteipAliash.sh should not be allowed with Isolated Guest Networks

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-2622. -- Resolution: Fixed > createipAlias.sh/deleteipAliash.sh should not be allowed w

[jira] [Resolved] (CLOUDSTACK-1640) overcommited memory is not getting displayed at zone level and used % is based on actual memory

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-1640. -- Resolution: Fixed 6e9bf56cf195f990cf4b37556d0f5e796de2238a > ove

[jira] [Updated] (CLOUDSTACK-2742) Xen Plugin failure for deleteIpAlias on XCP resource

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-2742: - Assignee: (was: Bharat Kumar) > Xen Plugin failure for deleteIpAlias on XCP

[jira] [Resolved] (CLOUDSTACK-2997) HAProxy maxconn is not configurable

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-2997. -- Resolution: Fixed commit id in 4.2 5c18483d8182ea3da9d8a34778b7f98f72bcd29c

[jira] [Resolved] (CLOUDSTACK-1695) Not enough cpu avialable in cluster according to new overcommit ratio but all stopped Vms can be started without any failure(required cpu for stopped vm is > > avai

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-1695. -- Resolution: Fixed commit in 4.2 ba619ec112170b916f69a7466a779196f74bef7c

[jira] [Updated] (CLOUDSTACK-3836) 3.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on the Upgraded Setup - Table "volumes"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3836: - Status: Ready To Review (was: In Progress) > 3.0.6 to ASF 4.2 Upgrade: "cloud"

[jira] [Assigned] (CLOUDSTACK-3446) Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar reassigned CLOUDSTACK-3446: Assignee: Bharat Kumar > Guest OS is getting memory=memory in SO / memory.

[jira] [Commented] (CLOUDSTACK-3446) Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726223#comment-13726223 ] Bharat Kumar commented on CLOUDSTACK-3446: -- This is not a bug. once the ball

[jira] [Resolved] (CLOUDSTACK-3446) Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3446. -- Resolution: Fixed > Guest OS is getting memory=memory in SO / memory.overcommi

[jira] [Updated] (CLOUDSTACK-568) Source template id is recorded incorrectly.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-568: Assignee: Bharat Kumar > Source template id is recorded incorrectly. >

[jira] [Commented] (CLOUDSTACK-856) [DOC] Document CPU and memory overcommit functionality.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726296#comment-13726296 ] Bharat Kumar commented on CLOUDSTACK-856: - please add the following to the do

[jira] [Commented] (CLOUDSTACK-1695) Not enough cpu avialable in cluster according to new overcommit ratio but all stopped Vms can be started without any failure(required cpu for stopped vm is > > ava

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727371#comment-13727371 ] Bharat Kumar commented on CLOUDSTACK-1695: -- The vms should be deployed only

[jira] [Assigned] (CLOUDSTACK-3753) Multiple VLAN range API need to accept a list rather than "add" or "remove" per command

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar reassigned CLOUDSTACK-3753: Assignee: Bharat Kumar > Multiple VLAN range API need to accept a list rat

[jira] [Resolved] (CLOUDSTACK-3753) Multiple VLAN range API need to accept a list rather than "add" or "remove" per command

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3753. -- Resolution: Fixed > Multiple VLAN range API need to accept a list rather than

[jira] [Commented] (CLOUDSTACK-3836) 3.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on the Upgraded Setup - Table "volumes"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727609#comment-13727609 ] Bharat Kumar commented on CLOUDSTACK-3836: -- commit 60585b51819e4391373d71c63

[jira] [Resolved] (CLOUDSTACK-3836) 3.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on the Upgraded Setup - Table "volumes"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3836. -- Resolution: Fixed commit 65370f31bcb1ae5238be5e68462ea0d79df3296f in master.

[jira] [Comment Edited] (CLOUDSTACK-3836) 3.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on the Upgraded Setup - Table "volumes"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727609#comment-13727609 ] Bharat Kumar edited comment on CLOUDSTACK-3836 at 8/2/13 11:58 AM:

[jira] [Commented] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727610#comment-13727610 ] Bharat Kumar commented on CLOUDSTACK-3612: -- fixed the iso_id inconsistency.

[jira] [Resolved] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3612. -- Resolution: Fixed > 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies

[jira] [Closed] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar closed CLOUDSTACK-3612. Resolution: Fixed 60585b51819e4391373d71c63138e36f0a3c5898 in 4.2 > 3

[jira] [Reopened] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar reopened CLOUDSTACK-3612: -- > 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded > Set

[jira] [Resolved] (CLOUDSTACK-1695) Not enough cpu avialable in cluster according to new overcommit ratio but all stopped Vms can be started without any failure(required cpu for stopped vm is > > avai

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-1695. -- Resolution: Fixed 0951739e32fa6e2c9cee1bd1bca2817c2536ef50 hash in 4.2 80e2934bb7

[jira] [Resolved] (CLOUDSTACK-3763) [Automation] Fix the test_non_contiguous.py test case that tests addition/removal of non-contiguous VLANs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3763. -- Resolution: Fixed 6e83a54ffbf69e46a79fbaf0be63e63092385b65 commit in 4.2

[jira] [Commented] (CLOUDSTACK-3763) [Automation] Fix the test_non_contiguous.py test case that tests addition/removal of non-contiguous VLANs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729114#comment-13729114 ] Bharat Kumar commented on CLOUDSTACK-3763: -- 6e83a54ffbf69e46a79fbaf0be63e63

[jira] [Updated] (CLOUDSTACK-3763) [Automation] Fix the test_non_contiguous.py test case that tests addition/removal of non-contiguous VLANs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3763: - Assignee: Bharat Kumar > [Automation] Fix the test_non_contiguous.py test case t

[jira] [Closed] (CLOUDSTACK-3370) Add ipalias deletion to the network gc

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar closed CLOUDSTACK-3370. changed the desig not valid anymore. > Add ipalias deletion to the networ

[jira] [Created] (CLOUDSTACK-4100) Do not drop iso_id column while upgrading form 3.0.7 to 4.1

Bharat Kumar created CLOUDSTACK-4100: Summary: Do not drop iso_id column while upgrading form 3.0.7 to 4.1 Key: CLOUDSTACK-4100 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4100 Project:

[jira] [Updated] (CLOUDSTACK-4100) Do not drop iso_id column while upgrading form 3.0.7 to 4.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4100: - Summary: Do not drop iso_id column while upgrading form 3.0.7 to 4.2 (was: Do not d

[jira] [Updated] (CLOUDSTACK-4100) Do not drop iso_id column while upgrading form 3.0.7 to 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4100: - Description: we need to preserve the data in iso_id cloumn while upgraign from 3.0.7

[jira] [Updated] (CLOUDSTACK-4100) Do not drop iso_id column while upgrading form 3.0.7 to 4.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4100: - Description: we need to preserve the data in iso_id cloumn while upgrading from 3.0.

[jira] [Updated] (CLOUDSTACK-4105) Vnet's from Phisical network's table are getting deleted even the Vnet is used by Phisical network.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4105: - Assignee: Bharat Kumar > Vnet's from Phisical network's table are getting delete

[jira] [Updated] (CLOUDSTACK-3782) Data disk size is modified to KB from GB after it is attached to the instance

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3782: - Assignee: (was: Bharat Kumar) > Data disk size is modified to KB from GB aft

[jira] [Updated] (CLOUDSTACK-4105) Vnet's from Phisical network's table are getting deleted even the Vnet is used by Phisical network.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4105: - Status: Ready To Review (was: In Progress) > Vnet's from Phisical network's tab

[jira] [Commented] (CLOUDSTACK-4105) Vnet's from Phisical network's table are getting deleted even the Vnet is used by Phisical network.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730660#comment-13730660 ] Bharat Kumar commented on CLOUDSTACK-4105: -- in case when we are trying to re

[jira] [Updated] (CLOUDSTACK-4100) preserve data in iso_id column while upgrading form 3.0.7 to 4.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4100: - Summary: preserve data in iso_id column while upgrading form 3.0.7 to 4.2 (was: Do

[jira] [Resolved] (CLOUDSTACK-4105) Vnet's from Phisical network's table are getting deleted even the Vnet is used by Phisical network.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-4105. -- Resolution: Fixed 5dcded229f6508767c78804e7874d2fd2e320f6c commit in 4.2

[jira] [Created] (CLOUDSTACK-4138) keep the existing changes in cloud-set-guest-sshkey.in to make sure we do not break the backward compatibility.

Bharat Kumar created CLOUDSTACK-4138: Summary: keep the existing changes in cloud-set-guest-sshkey.in to make sure we do not break the backward compatibility. Key: CLOUDSTACK-4138 URL: https://issues.apache.o

[jira] [Updated] (CLOUDSTACK-4138) keep the existing changes in cloud-set-guest-sshkey.in to make sure we do not break the backward compatibility.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4138: - Status: Ready To Review (was: In Progress) > keep the existing changes in cloud

[jira] [Updated] (CLOUDSTACK-4083) [Multiple_IP_Ranges] Failure in adding additional network to a vm should delete the IP alias created

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4083: - Status: Ready To Review (was: In Progress) > [Multiple_IP_Ranges] Failure in ad

[jira] [Resolved] (CLOUDSTACK-4100) preserve data in iso_id column while upgrading form 3.0.7 to 4.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-4100. -- Resolution: Fixed Fix Version/s: 4.2.0 commit 95f36798559c71d1de9f34fedad59

[jira] [Commented] (CLOUDSTACK-4100) preserve data in iso_id column while upgrading form 3.0.7 to 4.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731976#comment-13731976 ] Bharat Kumar commented on CLOUDSTACK-4100: -- commit e55844c364818d4b9c103a9be

[jira] [Updated] (CLOUDSTACK-4134) UI dosent fire the API with the Vlan values if the Vlan range is blank.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-4134: - Assignee: Jessica Wang (was: Bharat Kumar) > UI dosent fire the API with the Vl

[jira] [Commented] (CLOUDSTACK-4134) UI dosent fire the API with the Vlan values if the Vlan range is blank.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733169#comment-13733169 ] Bharat Kumar commented on CLOUDSTACK-4134: -- The UI should pass vlan= when t

[jira] [Commented] (CLOUDSTACK-4083) [Multiple_IP_Ranges] Failure in adding additional network to a vm should delete the IP alias created

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733274#comment-13733274 ] Bharat Kumar commented on CLOUDSTACK-4083: -- Need to add this fix to master.

[jira] [Resolved] (CLOUDSTACK-4083) [Multiple_IP_Ranges] Failure in adding additional network to a vm should delete the IP alias created

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-4083. -- Resolution: Fixed > [Multiple_IP_Ranges] Failure in adding additional network

[jira] [Resolved] (CLOUDSTACK-568) Source template id is recorded incorrectly.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-568. - Resolution: Fixed > Source template id is recorded incorrectly. > ---

[jira] [Closed] (CLOUDSTACK-568) Source template id is recorded incorrectly.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar closed CLOUDSTACK-568. --- > Source template id is recorded incorrectly. > -

[jira] [Closed] (CLOUDSTACK-3882) remove the duplicate entries of the data-server from the /etc/hosts

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar closed CLOUDSTACK-3882. > remove the duplicate entries of the data-server from the /etc/hosts > --

[jira] [Updated] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3612: - Assignee: frank zhang (was: Bharat Kumar) > 3.0.6 to ASF 4.2 Upgrade: Database

[jira] [Commented] (CLOUDSTACK-856) [DOC] Document CPU and memory overcommit functionality.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734467#comment-13734467 ] Bharat Kumar commented on CLOUDSTACK-856: - Hi Jessica, I have gone through t

[jira] [Resolved] (CLOUDSTACK-4138) keep the existing changes in cloud-set-guest-sshkey.in to make sure we do not break the backward compatibility.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-4138. -- Resolution: Fixed > keep the existing changes in cloud-set-guest-sshkey.in to

[jira] [Resolved] (CLOUDSTACK-3313) Ipv6 - Not able to deploy VM in IPV6 network.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3313. -- Resolution: Fixed 6b549074fa239af31920b5a8e7112c8f5aa0b782 > Ipv6

[jira] [Resolved] (CLOUDSTACK-2997) HAProxy maxconn is not configurable

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-2997. -- Resolution: Fixed dd33abffbe3b7c5b615e8f64b1824a720329dd0d 954e1978130b3cfb0c73f2f

[jira] [Resolved] (CLOUDSTACK-3241) [Multiple_IP_Ranges] Adding ip range fails if there are two IP ranges existing in two different CIDRs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3241. -- Resolution: Fixed d73bb22802cba9116f27fada6780c966b0060b30 > [Mul

[jira] [Resolved] (CLOUDSTACK-2980) Adding a VLAN range that overlaps with two existing ranges results in inconsistent DB entries

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-2980. -- Resolution: Fixed f76bf5b053894b400f8c196923fe0e8804b64aec > Addi

[jira] [Resolved] (CLOUDSTACK-2150) DB table entries of phisical network is not proper.Shows Duplicate entries.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-2150. -- Resolution: Fixed f76bf5b053894b400f8c196923fe0e8804b64aec > DB t

[jira] [Commented] (CLOUDSTACK-3370) Add ipalias deletion to the network gc

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710936#comment-13710936 ] Bharat Kumar commented on CLOUDSTACK-3370: -- we are now deleting the ipalias

[jira] [Resolved] (CLOUDSTACK-3370) Add ipalias deletion to the network gc

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3370. -- Resolution: Invalid > Add ipalias deletion to the network gc > ---

[jira] [Resolved] (CLOUDSTACK-3263) [Multiple_IP_Ranges] IP in revoked state should be freed up after VR restart

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3263. -- Resolution: Fixed d73bb22802cba9116f27fada6780c966b0060b30 > [Mul

[jira] [Closed] (CLOUDSTACK-1823) Cpu and ram are incorrectly set in the hypervisor guru base

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar closed CLOUDSTACK-1823. > Cpu and ram are incorrectly set in the hypervisor guru base > --

[jira] [Commented] (CLOUDSTACK-3106) Delete all the ips except for the ip alias.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13711023#comment-13711023 ] Bharat Kumar commented on CLOUDSTACK-3106: -- Not valid any more changed the i

[jira] [Closed] (CLOUDSTACK-1613) NPE thrown from listClusters in upgraded case due to Cpu/Memory overcommit feature

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar closed CLOUDSTACK-1613. > NPE thrown from listClusters in upgraded case due to Cpu/Memory overcommit > featur

[jira] [Closed] (CLOUDSTACK-3106) Delete all the ips except for the ip alias.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar closed CLOUDSTACK-3106. > Delete all the ips except for the ip alias. > --

[jira] [Commented] (CLOUDSTACK-3589) VM created from VPC network is not getting IP

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712156#comment-13712156 ] Bharat Kumar commented on CLOUDSTACK-3589: -- it is not because of DnsMasqConf

[jira] [Updated] (CLOUDSTACK-3589) VM created from VPC network is not getting IP

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3589: - Assignee: (was: Bharat Kumar) > VM created from VPC network is not getting I

[jira] [Issue Comment Deleted] (CLOUDSTACK-3119) Shared network removal doesn't cleanup corresponding IP ranges

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3119: - Comment: was deleted (was: 974245991c4c3fe51e63fe18b19853f5f8a0c6fa) > Shared n

[jira] [Commented] (CLOUDSTACK-3119) Shared network removal doesn't cleanup corresponding IP ranges

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713585#comment-13713585 ] Bharat Kumar commented on CLOUDSTACK-3119: -- commit 6b0df2566db34eb87c9603e6e

[jira] [Commented] (CLOUDSTACK-3753) Multiple VLAN range API need to accept a list rather than "add" or "remove" per command

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718119#comment-13718119 ] Bharat Kumar commented on CLOUDSTACK-3753: -- Hi, previous API did not deal w

[jira] [Updated] (CLOUDSTACK-1646) user VMs with equal cpu speed and different number of vcpus getting same weight on xenserver

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-1646: - Assignee: Harikrishna Patnala (was: Bharat Kumar) > user VMs with equal cpu spe

[jira] [Commented] (CLOUDSTACK-3415) Guest os memory is not getting dynamically adjusted incase of overcommit

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721668#comment-13721668 ] Bharat Kumar commented on CLOUDSTACK-3415: -- The memory shown at the guest os

[jira] [Resolved] (CLOUDSTACK-3415) Guest os memory is not getting dynamically adjusted incase of overcommit

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-3415. -- Resolution: Fixed > Guest os memory is not getting dynamically adjusted incase

[jira] [Resolved] (CLOUDSTACK-970) when a template is deleted and then copied over again , it is still marked as "Removed" in template_zone_ref table.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-970. - Resolution: Fixed Not applicable anymore to changes in storage subsystem

[jira] [Comment Edited] (CLOUDSTACK-970) when a template is deleted and then copied over again , it is still marked as "Removed" in template_zone_ref table.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721836#comment-13721836 ] Bharat Kumar edited comment on CLOUDSTACK-970 at 7/28/13 3:51 AM: --

[jira] [Issue Comment Deleted] (CLOUDSTACK-1384) Cloudstack might show usage > 100% when overcommit ratio is decreased.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-1384: - Comment: was deleted (was: Not a valid bug based on the current design.) > Clou

[jira] [Commented] (CLOUDSTACK-1384) Cloudstack might show usage > 100% when overcommit ratio is decreased.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721913#comment-13721913 ] Bharat Kumar commented on CLOUDSTACK-1384: -- Not a valid bug based on the cur

[jira] [Commented] (CLOUDSTACK-1384) Cloudstack might show usage > 100% when overcommit ratio is decreased.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721915#comment-13721915 ] Bharat Kumar commented on CLOUDSTACK-1384: -- This is by design. I logged this

[jira] [Closed] (CLOUDSTACK-1384) Cloudstack might show usage > 100% when overcommit ratio is decreased.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar closed CLOUDSTACK-1384. Closing the issue as it dose not requite any testing > Cloudstack might s

[jira] [Resolved] (CLOUDSTACK-1384) Cloudstack might show usage > 100% when overcommit ratio is decreased.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-1384. -- Resolution: Fixed > Cloudstack might show usage > 100% when overcommit ratio i

[jira] [Updated] (CLOUDSTACK-2742) Xen Plugin failure for deleteIpAlias on XCP resource

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-2742: - Assignee: Bharat Kumar > Xen Plugin failure for deleteIpAlias on XCP resource >

[jira] [Assigned] (CLOUDSTACK-2622) createipAlias.sh/deleteipAliash.sh should not be allowed with Isolated Guest Networks

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar reassigned CLOUDSTACK-2622: Assignee: Bharat Kumar > createipAlias.sh/deleteipAliash.sh should not be

[jira] [Created] (CLOUDSTACK-3882) remove the duplicate entries of the vm name from the /etc/hosts

Bharat Kumar created CLOUDSTACK-3882: Summary: remove the duplicate entries of the vm name from the /etc/hosts Key: CLOUDSTACK-3882 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3882 Proje

[jira] [Updated] (CLOUDSTACK-3882) remove the duplicate entries of the data server from the /etc/hosts

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3882: - Summary: remove the duplicate entries of the data server from the /etc/hosts (was:

[jira] [Updated] (CLOUDSTACK-3882) remove the duplicate entries of the dataserver from the /etc/hosts

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-3882: - Summary: remove the duplicate entries of the dataserver from the /etc/hosts (was: r

  1   2   3   4   5   >