RE: [ANNOUNCE] New Committer: Vijay Bhamidipati

[Rajesh Battala]

Hearty Congratulations 

-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org] 
Sent: Saturday, August 10, 2013 10:31 AM
To: CloudStack Dev
Subject: [ANNOUNCE] New Committer: Vijay Bhamidipati

The Project Management Committee (PMC) for Apache CloudStack has asked Vijay 
Bhamidipati to become a committer and we are pleased to announce that they have 
accepted.

Being a committer allows many contributors to contribute more autonomously. For 
developers, it makes it easier to submit changes and eliminates the need to 
have contributions reviewed via the patch submission process. Whether 
contributions are development-related or otherwise, it is a recognition of a 
contributor's participation in the project and commitment to the project and 
the Apache Way.

Please join me in congratulating Vijay!

--
Prasanna.,
on behalf of the Apache CloudStack PMC


Powered by BigRock.com

Re: Review Request 13424: CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2

[Kishan Kavala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13424/#review24964
---


Changes look good to me. But the upgrade path has changed to accommodate 
upgrades from 4.1.1 and 4.1.2. Patch doesn't apply on the latest code due to 
this change. Please submit the patch again. 

- Kishan Kavala


On Aug. 9, 2013, 5:20 p.m., Harikrishna Patnala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13424/
> ---
> 
> (Updated Aug. 9, 2013, 5:20 p.m.)
> 
> 
> Review request for cloudstack and Kishan Kavala.
> 
> 
> Bugs: CLOUDSTACK-4123 and CLOUDSTACK-4205
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the 
> Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2
> 
> Updating the new system template URLs for the existing templates during 
> upgrade to 4.2.
> If new 4.2 system template is registered before upgrade then marking the 
> old templates as removed during upgrade.
> 
> CLOUDSTACK-4205: System VMs are not booting up with new templates after 
> Upgrade from 3.0.6 to 4.2. 
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/storage/dao/VMTemplateDaoImpl.java 9243225 
>   engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java 0941408 
>   server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java a583954 
>   server/src/com/cloud/resource/ResourceManagerImpl.java e5441af 
>   server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java 
> 17cbf5c 
> 
> Diff: https://reviews.apache.org/r/13424/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Harikrishna Patnala
> 
>

Re: [ANNOUNCE] New Committer: Vijay Bhamidipati

[Ahmad Emneina]

Way to go Vijay! Congrats.

Ahmad

On Aug 10, 2013, at 12:30 AM, Rajesh Battala  wrote:

> Hearty Congratulations 
> 
> -Original Message-
> From: Prasanna Santhanam [mailto:t...@apache.org] 
> Sent: Saturday, August 10, 2013 10:31 AM
> To: CloudStack Dev
> Subject: [ANNOUNCE] New Committer: Vijay Bhamidipati
> 
> The Project Management Committee (PMC) for Apache CloudStack has asked Vijay 
> Bhamidipati to become a committer and we are pleased to announce that they 
> have accepted.
> 
> Being a committer allows many contributors to contribute more autonomously. 
> For developers, it makes it easier to submit changes and eliminates the need 
> to have contributions reviewed via the patch submission process. Whether 
> contributions are development-related or otherwise, it is a recognition of a 
> contributor's participation in the project and commitment to the project and 
> the Apache Way.
> 
> Please join me in congratulating Vijay!
> 
> --
> Prasanna.,
> on behalf of the Apache CloudStack PMC
> 
> 
> Powered by BigRock.com
> 

Re: [DISCUSS] Binary diff and hot patch

[Daan Hoogland]

Another take is to have a big datastore with all jenkins results and
pick e build from it (containing the patch id in the name) to see if
it is the culprit.

It might be possible, what you are looking for.

On Fri, Aug 9, 2013 at 5:38 PM, Musayev, Ilya  wrote:
> I guess no way to do this :(
>
>> -Original Message-
>> From: Musayev, Ilya [mailto:imusa...@webmd.net]
>> Sent: Wednesday, August 07, 2013 5:51 PM
>> To: dev@cloudstack.apache.org
>> Subject: [DISCUSS] Binary diff and hot patch
>>
>> I was wondering if we can use binary diffs to hotpatch ACS.
>>
>> Currently, the way for me to identify what patch could have caused issue X,
>> would be  - try to find the suspects - it could be several. Revert 1 commit,
>> rebuild and retry, if failed, restore previously reverted commit, revert 2nd
>> commit, rebuild and retry - etc..
>>
>> As you can see, this is very time consuming and painful, I'm wondering if
>> there is a better way to do this. I came across a project called javaxdelta 
>> on
>> sourceforge - curious what your thought on this may be, and if there is a
>> better way to try out patches instead of what I'm doing now.
>>
>> Thanks
>> ilya
>

Re: Review Request 13424: CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2

[Harikrishna Patnala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13424/
---

(Updated Aug. 10, 2013, 10:16 a.m.)


Review request for cloudstack and Kishan Kavala.


Changes
---

Updated patch after rebasing


Bugs: CLOUDSTACK-4123 and CLOUDSTACK-4205


Repository: cloudstack-git


Description
---

CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the 
Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2

Updating the new system template URLs for the existing templates during 
upgrade to 4.2.
If new 4.2 system template is registered before upgrade then marking the 
old templates as removed during upgrade.

CLOUDSTACK-4205: System VMs are not booting up with new templates after Upgrade 
from 3.0.6 to 4.2. 


Diffs (updated)
-

  engine/schema/src/com/cloud/storage/dao/VMTemplateDaoImpl.java 9243225 
  engine/schema/src/com/cloud/upgrade/dao/Upgrade412to420.java d703cc3 
  server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java a583954 
  server/src/com/cloud/resource/ResourceManagerImpl.java e5441af 
  server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java 
17cbf5c 

Diff: https://reviews.apache.org/r/13424/diff/


Testing
---


Thanks,

Harikrishna Patnala

Re: [DISCUSS] KVM io throttling

[Wido den Hollander]

On 08/09/2013 08:32 PM, Edison Su wrote:

There is another issue, there is no way to change io speed from UI for system 
vm's guest network(nic2) in basic network model, which will impact all the 
template downloading in a negatively way.
We'd better don't throttle system vm's io speed by default, or at least give 
admin the way to change the io speed.



I'd say for now, do not throttle System VMs.

You mainly want to throttle user Instances to prevent them from clogging 
up the network.


Wido


-Original Message-
From: Edison Su [mailto:edison...@citrix.com]
Sent: Friday, August 09, 2013 11:27 AM
To: dev@cloudstack.apache.org
Subject: RE: [DISCUSS] KVM io throttling




-Original Message-
From: Wido den Hollander [mailto:w...@widodh.nl]
Sent: Friday, August 09, 2013 2:41 AM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] KVM io throttling



On 08/09/2013 02:05 AM, Edison Su wrote:

Hi All,
   For basic network, the io limit for guest network(nic 2) is
200MB/s, we

set the io limit on kvm host as:




I think you mean 200Mbit/s?

Oh, I see, it's 200Mb/s.









   


  From libvirt doc(http://libvirt.org/formatnetwork.html), it says
above unit

is KB/s, but per my testing, it sounds like it's Kb/s. Is there
anybody have the same issue?




No, my testing tells me it's is KB/sec (KiloByte).

On centos 6.3 + libvirt 0.9.10, the number doesn't match:
With the following simple test:

dd if=/dev/zero of=some-nfs-mount-point bs=1M count=10 I can get 104
MB/s if nic2 speed is unlimited, while only get 1MB/s, if nic2 is configured
with 
 
 
   

Maybe it's an issue on Centos 6.3?




My libvirt version is 0.9.10 on Centos 6.3.



My libvirt version is 1.0.6 under Ubuntu 12.04 using the Cloud Archive
for OpenStack Havana from Canonical:
https://wiki.ubuntu.com/ServerTeam/CloudArchive

Wido

Review Request 13468: CLOUDSTACK-3228: system vms are not comming up in zone with two cluster xen and kvm; Zone host is ready, but secondary storage vm template: 3 is not ready on secondary storage: 2

[Harikrishna Patnala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13468/
---

Review request for cloudstack and Nitin Mehta.


Bugs: CLOUDSTACK-3228


Repository: cloudstack-git


Description
---

CLOUDSTACK-3228:  system vms are not comming up in zone with two cluster xen 
and kvm;Zone host is ready, but secondary storage vm template: 3 is not ready 
on secondary storage: 2 


Diffs
-

  server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java c5faccb 
  server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java 
d1c148b 

Diff: https://reviews.apache.org/r/13468/diff/


Testing
---

Tested the scenario mentioned in the bug ticket


Thanks,

Harikrishna Patnala

Review Request 13469: CLOUDSTACK-3946 [KVM] [Zone Wide Primary Storages] migrateVolume is deleting the volume if the source and destination pool are same.

[Rajesh Battala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13469/
---

Review request for cloudstack, Devdeep Singh, edison su, and Ram Ganesh.


Bugs: CLOUDSTACK-3946


Repository: cloudstack-git


Description
---

while migrating volume, if the storage and destination pool are same, we are 
still do overhead of copying the volume to same pool and deleting the other src 
copy.

fixed the issue by restricting volumemigration if the source and destination 
pool are same.


Diffs
-

  server/src/com/cloud/storage/VolumeManagerImpl.java 100aad3 

Diff: https://reviews.apache.org/r/13469/diff/


Testing
---

1. Successfully migrated the volume from Storagepool A to pool B.
2. migration is not allowed if the source and destination are same.
3. tried the volume with storage pool scope (ZONE and Cluster)


Thanks,

Rajesh Battala

Review Request 13471: test_vm_passwd_enable.py is failing for basic zone

[SrikanteswaraRao Talluri]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13471/
---

Review request for cloudstack and Prasanna Santhanam.


Bugs: CLOUDSTACK-4230


Repository: cloudstack-git


Description
---

fix the script to not to add egress rule if the zone network type is not 
advanced


Diffs
-

  test/integration/component/test_vm_passwdenabled.py 586f311 

Diff: https://reviews.apache.org/r/13471/diff/


Testing
---

tested


Thanks,

SrikanteswaraRao Talluri

Re: Review Request 13424: CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13424/#review24965
---


Commit 48c8e64ae9c872d339b0fb8a2fc7fa453862fada in branch refs/heads/4.2 from 
Harikrishna Patnala
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=48c8e64 ]

CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the 
Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2

Updating the new system template URLs for the existing templates during upgrade 
to 4.2.
If new 4.2 system template is registered before upgrade then marking the old 
templates as removed during upgrade.


- ASF Subversion and Git Services


On Aug. 10, 2013, 10:16 a.m., Harikrishna Patnala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13424/
> ---
> 
> (Updated Aug. 10, 2013, 10:16 a.m.)
> 
> 
> Review request for cloudstack and Kishan Kavala.
> 
> 
> Bugs: CLOUDSTACK-4123 and CLOUDSTACK-4205
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the 
> Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2
> 
> Updating the new system template URLs for the existing templates during 
> upgrade to 4.2.
> If new 4.2 system template is registered before upgrade then marking the 
> old templates as removed during upgrade.
> 
> CLOUDSTACK-4205: System VMs are not booting up with new templates after 
> Upgrade from 3.0.6 to 4.2. 
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/storage/dao/VMTemplateDaoImpl.java 9243225 
>   engine/schema/src/com/cloud/upgrade/dao/Upgrade412to420.java d703cc3 
>   server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java a583954 
>   server/src/com/cloud/resource/ResourceManagerImpl.java e5441af 
>   server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java 
> 17cbf5c 
> 
> Diff: https://reviews.apache.org/r/13424/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Harikrishna Patnala
> 
>

Re: Review Request 13424: CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2

[Kishan Kavala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13424/#review24967
---

Ship it!


commit 48c8e64ae9c872d339b0fb8a2fc7fa453862fada

- Kishan Kavala


On Aug. 10, 2013, 3:46 p.m., Harikrishna Patnala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13424/
> ---
> 
> (Updated Aug. 10, 2013, 3:46 p.m.)
> 
> 
> Review request for cloudstack and Kishan Kavala.
> 
> 
> Bugs: CLOUDSTACK-4123 and CLOUDSTACK-4205
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the 
> Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2
> 
> Updating the new system template URLs for the existing templates during 
> upgrade to 4.2.
> If new 4.2 system template is registered before upgrade then marking the 
> old templates as removed during upgrade.
> 
> CLOUDSTACK-4205: System VMs are not booting up with new templates after 
> Upgrade from 3.0.6 to 4.2. 
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/storage/dao/VMTemplateDaoImpl.java 9243225 
>   engine/schema/src/com/cloud/upgrade/dao/Upgrade412to420.java d703cc3 
>   server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java a583954 
>   server/src/com/cloud/resource/ResourceManagerImpl.java e5441af 
>   server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java 
> 17cbf5c 
> 
> Diff: https://reviews.apache.org/r/13424/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Harikrishna Patnala
> 
>

Re: Review Request 13424: CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13424/#review24966
---


Commit 5404bf606395fb4ff58252df9511341416eb160a in branch refs/heads/master 
from Harikrishna Patnala
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5404bf6 ]

CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the 
Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2

Updating the new system template URLs for the existing templates during upgrade 
to 4.2.
If new 4.2 system template is registered before upgrade then marking the old 
templates as removed during upgrade.


- ASF Subversion and Git Services


On Aug. 10, 2013, 10:16 a.m., Harikrishna Patnala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13424/
> ---
> 
> (Updated Aug. 10, 2013, 10:16 a.m.)
> 
> 
> Review request for cloudstack and Kishan Kavala.
> 
> 
> Bugs: CLOUDSTACK-4123 and CLOUDSTACK-4205
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-4123: 3.0.6 to ASF 4.2 Upgrade: On Adding VMWare Cluster to the 
> Setup, 3.0.6 System VM Template for VMWare is downloaded instead of 4.2
> 
> Updating the new system template URLs for the existing templates during 
> upgrade to 4.2.
> If new 4.2 system template is registered before upgrade then marking the 
> old templates as removed during upgrade.
> 
> CLOUDSTACK-4205: System VMs are not booting up with new templates after 
> Upgrade from 3.0.6 to 4.2. 
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/storage/dao/VMTemplateDaoImpl.java 9243225 
>   engine/schema/src/com/cloud/upgrade/dao/Upgrade412to420.java d703cc3 
>   server/src/com/cloud/consoleproxy/ConsoleProxyManagerImpl.java a583954 
>   server/src/com/cloud/resource/ResourceManagerImpl.java e5441af 
>   server/src/com/cloud/storage/secondary/SecondaryStorageManagerImpl.java 
> 17cbf5c 
> 
> Diff: https://reviews.apache.org/r/13424/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Harikrishna Patnala
> 
>

Review Request 13472: make apache server listen on all the ipaliases to provide access to meta-data.

[bharat kumar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13472/
---

Review request for cloudstack, Chiradeep Vittal and Sheng Yang.


Bugs: Cloudstack-4231


Repository: cloudstack-git


Description
---

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

Earlier we were using the name data-server to access the meta-data in case of 
multiple subnets. 
This requires updating the guest templates. 

Now we make apache server listen on all the ipaliases. So no need to update the 
template.
we create separate file for each ipAlias 


Diffs
-

  patches/systemvm/debian/config/etc/init.d/cloud-early-config a552d44 
  patches/systemvm/debian/config/root/createIpAlias.sh 5498195 
  patches/systemvm/debian/config/root/deleteIpAlias.sh fa228fb 

Diff: https://reviews.apache.org/r/13472/diff/


Testing
---

Tested on 4.2


Thanks,

bharat kumar

Re: Review Request 13441: CLOUDSTACK-3850: CPU cap should be per VM not per VCPU

[Koushik Das]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13441/#review24968
---



plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java


CPU weight computation is not considering the number of CPUs in the VM but 
utilization is considering it. Shouldn't both follow the same logic? If not can 
you explain the logic and put a comment in the code for the same.
 
Also what is logic for multiplying the speed with 0.99?


- Koushik Das


On Aug. 9, 2013, 1 p.m., Harikrishna Patnala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13441/
> ---
> 
> (Updated Aug. 9, 2013, 1 p.m.)
> 
> 
> Review request for cloudstack and Koushik Das.
> 
> 
> Bugs: CLOUDSTACK-3850
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-3850:  CPU cap should be per VM not per VCPU 
> 
> 
> Diffs
> -
> 
>   
> plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
>  e100211 
>   
> plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/XenServer56FP1Resource.java
>  d230be1 
> 
> Diff: https://reviews.apache.org/r/13441/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Harikrishna Patnala
> 
>

RE: [ANNOUNCE] New Committer: Vijay Bhamidipati

[Koushik Das]

Congrats Vijay!

> -Original Message-
> From: Prasanna Santhanam [mailto:t...@apache.org]
> Sent: Saturday, August 10, 2013 10:31 AM
> To: CloudStack Dev
> Subject: [ANNOUNCE] New Committer: Vijay Bhamidipati
> 
> The Project Management Committee (PMC) for Apache CloudStack has
> asked Vijay Bhamidipati to become a committer and we are pleased to
> announce that they have accepted.
> 
> Being a committer allows many contributors to contribute more
> autonomously. For developers, it makes it easier to submit changes and
> eliminates the need to have contributions reviewed via the patch submission
> process. Whether contributions are development-related or otherwise, it is a
> recognition of a contributor's participation in the project and commitment to
> the project and the Apache Way.
> 
> Please join me in congratulating Vijay!
> 
> --
> Prasanna.,
> on behalf of the Apache CloudStack PMC
> 
> 
> Powered by BigRock.com

Upgrading form 4.1.0 to 4.1.1 success; some issues with console proxy

[France]

Hi,

i've upgraded XenServers 6.0.2 to latest hotfixes and upgraded CS form 
4.1.0 to 4.1.1 (also iscsi HA cluster, but that's not relevant for CS).


The only actual problem whas that console proxy didn't reboot 
successfully using cloudstack-sysvmadm script. It never came up as 
started, even thou i could see it's running using direct VNC (it seems 
as it run out of disk space?!?). After manually changing states in 
vm_instance a couple of times (to Running and finally Stopped), i was 
able to destroy VM (it didn't succeed using CS UI) and after restarting 
CS UI a couple of times it finally decided the old console proxy is no 
more and created new one. After that everything else went well.


I might have leftover volume on SR from that console proxy, but i will 
check it out after a couple of days, to see if it was expunged/deleted.
I have to check if there are any orphaned volumes on out HA iscsi disks 
anyway. Is there a script or a way to check actual lvm devices and 
compare it to the devices and states in CS db?


Regards,
F.

Re: Review Request 13472: make apache server listen on all the ipaliases to provide access to meta-data.

[bharat kumar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13472/
---

(Updated Aug. 10, 2013, 1:25 p.m.)


Review request for cloudstack, Chiradeep Vittal and Sheng Yang.


Changes
---

Fixed some typos.


Bugs: Cloudstack-4231


Repository: cloudstack-git


Description
---

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

Earlier we were using the name data-server to access the meta-data in case of 
multiple subnets. 
This requires updating the guest templates. 

Now we make apache server listen on all the ipaliases. So no need to update the 
template.
we create separate file for each ipAlias 


Diffs (updated)
-

  patches/systemvm/debian/config/etc/init.d/cloud-early-config a552d44 
  patches/systemvm/debian/config/root/createIpAlias.sh 5498195 
  patches/systemvm/debian/config/root/deleteIpAlias.sh fa228fb 

Diff: https://reviews.apache.org/r/13472/diff/


Testing
---

Tested on 4.2


Thanks,

bharat kumar

Re: Review Request 13472: make apache server listen on all the ipaliases to provide access to meta-data.

[bharat kumar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13472/
---

(Updated Aug. 10, 2013, 1:31 p.m.)


Review request for cloudstack, Chiradeep Vittal and Sheng Yang.


Changes
---

updating the tests conducted.


Bugs: Cloudstack-4231


Repository: cloudstack-git


Description
---

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

Earlier we were using the name data-server to access the meta-data in case of 
multiple subnets. 
This requires updating the guest templates. 

Now we make apache server listen on all the ipaliases. So no need to update the 
template.
we create separate file for each ipAlias 


Diffs
-

  patches/systemvm/debian/config/etc/init.d/cloud-early-config a552d44 
  patches/systemvm/debian/config/root/createIpAlias.sh 5498195 
  patches/systemvm/debian/config/root/deleteIpAlias.sh fa228fb 

Diff: https://reviews.apache.org/r/13472/diff/


Testing (updated)
---

Tested on 4.2
deployed vms in different subnets.
used the script cloud-set-guest-sshkey.in to fetch the public keys form the 
router.
was able to get the keys without using the name data-server.

deleted the subnet and checked if the apache config was removed.

ran a failure case, all the config files generated during this operation were 
moved to failure_directory.


Thanks,

bharat kumar

Re: Review Request 13471: test_vm_passwd_enable.py is failing for basic zone

[Prasanna Santhanam]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13471/#review24969
---

Ship it!


- Prasanna Santhanam


On Aug. 10, 2013, 12:07 p.m., SrikanteswaraRao Talluri wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13471/
> ---
> 
> (Updated Aug. 10, 2013, 12:07 p.m.)
> 
> 
> Review request for cloudstack and Prasanna Santhanam.
> 
> 
> Bugs: CLOUDSTACK-4230
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> fix the script to not to add egress rule if the zone network type is not 
> advanced
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_vm_passwdenabled.py 586f311 
> 
> Diff: https://reviews.apache.org/r/13471/diff/
> 
> 
> Testing
> ---
> 
> tested
> 
> 
> Thanks,
> 
> SrikanteswaraRao Talluri
> 
>

Re: CloudStack source which is on SourceForge but which should be with Apache?

[David Nalley]

Those are indeed problems, please file a bug for this.

--David

On Fri, Aug 9, 2013 at 6:16 PM, Demetrius Tsitrelis  wrote:
>
>
> The admin and install guides recommend pulling files from SourceForge.  
> Specifically:
>
> SSH Key Gen script:
>
> http://downloads.sourceforge.net/project/cloudstack/SSH%20Key%20Gen%20Script/cloud-set-guest-sshkey.in?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fcloudstack%2Ffiles%2FSSH%2520Key%2520Gen%2520Script%2F&ts=1331225219&use_mirror=iweb
>
>
>
> Password management scripts:
>
> Linux:  http://cloudstack.org/dl/cloud-set-guest-password
>
> Windows:  
> http://sourceforge.net/projects/cloudstack/files/Password%20Management%20Scripts
>  The CloudInstanceManage.msi in the last link is in binary form only; the C 
> sources should be donated to Apache.  Also, some certificate will be needed 
> when it is built so the build instructions should note that.
>
>

RE: [ANNOUNCE] New Committer: Vijay Bhamidipati

[Prachi Damle]

Congratulations Vijay! Well deserved!

-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org] 
Sent: Friday, August 09, 2013 10:01 PM
To: CloudStack Dev
Subject: [ANNOUNCE] New Committer: Vijay Bhamidipati

The Project Management Committee (PMC) for Apache CloudStack has asked Vijay 
Bhamidipati to become a committer and we are pleased to announce that they have 
accepted.

Being a committer allows many contributors to contribute more autonomously. For 
developers, it makes it easier to submit changes and eliminates the need to 
have contributions reviewed via the patch submission process. Whether 
contributions are development-related or otherwise, it is a recognition of a 
contributor's participation in the project and commitment to the project and 
the Apache Way.

Please join me in congratulating Vijay!

--
Prasanna.,
on behalf of the Apache CloudStack PMC


Powered by BigRock.com

Re: CloudMonkey 5.0 (was Re: CloudMonkey's new home)

[Daan Hoogland]

+1 +question

Is cloudmonkey 5 backwards compatible in the sense that it can talk to a 4.x ms?

On Sat, Aug 10, 2013 at 5:50 AM, David Nalley  wrote:
> +1 move forward.
>
> On Fri, Aug 9, 2013 at 5:02 PM, Rohit Yadav  wrote:
>> Hi folks,
>>
>> Looks like the previous thread failed to capture attention on the dev ML.
>> I'm going forward with some decisions so as to move fast and as per our
>> philosophy to ask for forgiveness later than just waste time on too much
>> process polling now.
>>
>> Here are some proposals;
>>
>> - The version model would be to move fast, break things, release early and
>> release often
>> - Start with 5.0 version: Since cloudmonkey 4.x is already out there, I'm
>> proposing we start new cloudmonkey releases from 5.0; This is just to make
>> sure we don't end up releasing a 1.0 when we already have a 4.x
>> - Using semver, we don't deviate from major version "5" until we have
>> backward incompatible changes of configuration, paths, DSL etc.
>> - We'll use git tags to track (unvoted) releasable or testable candidates.
>> This is so we can release fast, release often. We can append a -rc for such
>> releases on git and pypi.
>> - A tested and voted release could take time and some process; but pypi
>> channel may not be necessarily used for only official releases, but all and
>> every release, even the test ones.
>>
>> Suggestions, flames?
>>
>> Moving forward, as it seems already, I may not be able to contribute on
>> weekends.
>>
>> I may be only able to help with the first release, that too the non-process
>> oriented parts, perhaps people who already have some idea about the
>> internals of cloudmonkey like Prasanna or Sebastien can help lead the
>> component?
>>
>> Regards.
>>
>>
>> On Sun, Jul 28, 2013 at 11:04 PM, Rohit Yadav  wrote:
>>
>>> Based on our previous discussion thread[1], we've moved CloudMonkey out of
>>> ACS's repository to its new home [2]. Now,
>>> with 6f84e74a68d78705a06fe58f7927f42f61453a16 on master, we no longer have
>>> cloudmonkey in tools/cli. CloudMonkey will be within CloudStack project but
>>> now as an independent sub-project with its own repository and will have a
>>> faster need-basis release cycle.
>>>
>>> For doing that, please suggest on the release process or how it should
>>> work? If the present RM or someone wants to lead the release process?
>>> I just want to keep it simple with fast releases whenever we have a
>>> releasable candidate and semver[3] versioning. So, we ship things fast and
>>> don't worry if it breaks since we'll be shipping fast. We can after a fast
>>> lazy consensus/voting and publish via pypi and put the tarballs/zipballs
>>> under dists/ on ASF/CloudStack.
>>>
>>> Regards.
>>>
>>> [1] http://markmail.org/message/tjlr753xfhpw4uk4
>>> [2] https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git
>>> [3] http://semver.org/
>>>

Re: [ANNOUNCE] New Committer: Vijay Bhamidipati

[Vijayendra Bhamidipati]

Thanks for the wishes Prasanna, Min, Sateesh, Sailaja, Rajesh, Ahmad,
Koushik, Prachi! :)

Regards,
Vijay



On 8/10/13 9:54 AM, "Prachi Damle"  wrote:

>Congratulations Vijay! Well deserved!
>
>-Original Message-
>From: Prasanna Santhanam [mailto:t...@apache.org]
>Sent: Friday, August 09, 2013 10:01 PM
>To: CloudStack Dev
>Subject: [ANNOUNCE] New Committer: Vijay Bhamidipati
>
>The Project Management Committee (PMC) for Apache CloudStack has asked
>Vijay Bhamidipati to become a committer and we are pleased to announce
>that they have accepted.
>
>Being a committer allows many contributors to contribute more
>autonomously. For developers, it makes it easier to submit changes and
>eliminates the need to have contributions reviewed via the patch
>submission process. Whether contributions are development-related or
>otherwise, it is a recognition of a contributor's participation in the
>project and commitment to the project and the Apache Way.
>
>Please join me in congratulating Vijay!
>
>--
>Prasanna.,
>on behalf of the Apache CloudStack PMC
>
>
>Powered by BigRock.com
>

Re: [ANNOUNCE] New Committer: Vijay Bhamidipati

[Rohit Yadav]

Hey, congrats Vijay.

Cheers.

On Sat, Aug 10, 2013 at 11:40 PM, Vijayendra Bhamidipati <
vijayendra.bhamidip...@citrix.com> wrote:

> Thanks for the wishes Prasanna, Min, Sateesh, Sailaja, Rajesh, Ahmad,
> Koushik, Prachi! :)
>
> Regards,
> Vijay
>
>
>
> On 8/10/13 9:54 AM, "Prachi Damle"  wrote:
>
> >Congratulations Vijay! Well deserved!
> >
> >-Original Message-
> >From: Prasanna Santhanam [mailto:t...@apache.org]
> >Sent: Friday, August 09, 2013 10:01 PM
> >To: CloudStack Dev
> >Subject: [ANNOUNCE] New Committer: Vijay Bhamidipati
> >
> >The Project Management Committee (PMC) for Apache CloudStack has asked
> >Vijay Bhamidipati to become a committer and we are pleased to announce
> >that they have accepted.
> >
> >Being a committer allows many contributors to contribute more
> >autonomously. For developers, it makes it easier to submit changes and
> >eliminates the need to have contributions reviewed via the patch
> >submission process. Whether contributions are development-related or
> >otherwise, it is a recognition of a contributor's participation in the
> >project and commitment to the project and the Apache Way.
> >
> >Please join me in congratulating Vijay!
> >
> >--
> >Prasanna.,
> >on behalf of the Apache CloudStack PMC
> >
> >
> >Powered by BigRock.com
> >
>
>

Re: CloudMonkey 5.0 (was Re: CloudMonkey's new home)

[Rohit Yadav]

On Sat, Aug 10, 2013 at 10:32 PM, Daan Hoogland wrote:

> +1 +question
>
> Is cloudmonkey 5 backwards compatible in the sense that it can talk to a
> 4.x ms?
>

Sorry for the confusion. Yes, in fact it is. It's the same cloudmonkey and
is aimed to work with Apache CloudStack 4.0.0-incubating and its
derivatives. If it does not it's a bug.

We're gaming the version number, since cloudmonkey-4.x was already out
here, it would create confusion if we release cloudmonkey-1.x. Therefore,
it made sense to just start with 5.0.0 and use semver from this version.

Regards.


>
> On Sat, Aug 10, 2013 at 5:50 AM, David Nalley  wrote:
> > +1 move forward.
> >
> > On Fri, Aug 9, 2013 at 5:02 PM, Rohit Yadav 
> wrote:
> >> Hi folks,
> >>
> >> Looks like the previous thread failed to capture attention on the dev
> ML.
> >> I'm going forward with some decisions so as to move fast and as per our
> >> philosophy to ask for forgiveness later than just waste time on too much
> >> process polling now.
> >>
> >> Here are some proposals;
> >>
> >> - The version model would be to move fast, break things, release early
> and
> >> release often
> >> - Start with 5.0 version: Since cloudmonkey 4.x is already out there,
> I'm
> >> proposing we start new cloudmonkey releases from 5.0; This is just to
> make
> >> sure we don't end up releasing a 1.0 when we already have a 4.x
> >> - Using semver, we don't deviate from major version "5" until we have
> >> backward incompatible changes of configuration, paths, DSL etc.
> >> - We'll use git tags to track (unvoted) releasable or testable
> candidates.
> >> This is so we can release fast, release often. We can append a -rc for
> such
> >> releases on git and pypi.
> >> - A tested and voted release could take time and some process; but pypi
> >> channel may not be necessarily used for only official releases, but all
> and
> >> every release, even the test ones.
> >>
> >> Suggestions, flames?
> >>
> >> Moving forward, as it seems already, I may not be able to contribute on
> >> weekends.
> >>
> >> I may be only able to help with the first release, that too the
> non-process
> >> oriented parts, perhaps people who already have some idea about the
> >> internals of cloudmonkey like Prasanna or Sebastien can help lead the
> >> component?
> >>
> >> Regards.
> >>
> >>
> >> On Sun, Jul 28, 2013 at 11:04 PM, Rohit Yadav 
> wrote:
> >>
> >>> Based on our previous discussion thread[1], we've moved CloudMonkey
> out of
> >>> ACS's repository to its new home [2]. Now,
> >>> with 6f84e74a68d78705a06fe58f7927f42f61453a16 on master, we no longer
> have
> >>> cloudmonkey in tools/cli. CloudMonkey will be within CloudStack
> project but
> >>> now as an independent sub-project with its own repository and will
> have a
> >>> faster need-basis release cycle.
> >>>
> >>> For doing that, please suggest on the release process or how it should
> >>> work? If the present RM or someone wants to lead the release process?
> >>> I just want to keep it simple with fast releases whenever we have a
> >>> releasable candidate and semver[3] versioning. So, we ship things fast
> and
> >>> don't worry if it breaks since we'll be shipping fast. We can after a
> fast
> >>> lazy consensus/voting and publish via pypi and put the
> tarballs/zipballs
> >>> under dists/ on ASF/CloudStack.
> >>>
> >>> Regards.
> >>>
> >>> [1] http://markmail.org/message/tjlr753xfhpw4uk4
> >>> [2]
> https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git
> >>> [3] http://semver.org/
> >>>
>

Re: Review Request 13441: CLOUDSTACK-3850: CPU cap should be per VM not per VCPU

[Harikrishna Patnala]

> On Aug. 10, 2013, 1:11 p.m., Koushik Das wrote:
> > plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java,
> >  line 663
> > 
> >
> > CPU weight computation is not considering the number of CPUs in the VM 
> > but utilization is considering it. Shouldn't both follow the same logic? If 
> > not can you explain the logic and put a comment in the code for the same.
> >  
> > Also what is logic for multiplying the speed with 0.99?

This is as per the design of xenserver.
CPU weight is calculated per VCPU. So whatever the weight we assign Xenserver 
allocates to each VCPU and cpu cap is per VM.
Please refer 

For CPU Weight: 
http://blog.xen.org/index.php/2010/08/13/rfc-credit1-make-weight-per-vcpu/

For CPU cap: 
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201206.mbox/%3cb1df26ecc0458748ac97cece2da98d41012f9d61a...@sjcpmailbox01.citrite.net%3E

Multiplication with 0.99 is what we follow during vm deployment may be for some 
overhead calculations, So It should be the same during scale vm also.


- Harikrishna


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13441/#review24968
---


On Aug. 9, 2013, 1 p.m., Harikrishna Patnala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13441/
> ---
> 
> (Updated Aug. 9, 2013, 1 p.m.)
> 
> 
> Review request for cloudstack and Koushik Das.
> 
> 
> Bugs: CLOUDSTACK-3850
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-3850:  CPU cap should be per VM not per VCPU 
> 
> 
> Diffs
> -
> 
>   
> plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
>  e100211 
>   
> plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/XenServer56FP1Resource.java
>  d230be1 
> 
> Diff: https://reviews.apache.org/r/13441/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Harikrishna Patnala
> 
>

Re: Review Request 13441: CLOUDSTACK-3850: CPU cap should be per VM not per VCPU

[Harikrishna Patnala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13441/
---

(Updated Aug. 10, 2013, 7:08 p.m.)


Review request for cloudstack and Koushik Das.


Changes
---

updated patch.(added comments)


Bugs: CLOUDSTACK-3850


Repository: cloudstack-git


Description
---

CLOUDSTACK-3850:  CPU cap should be per VM not per VCPU 


Diffs (updated)
-

  
plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
 e100211 
  
plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/XenServer56FP1Resource.java
 d230be1 

Diff: https://reviews.apache.org/r/13441/diff/


Testing
---


Thanks,

Harikrishna Patnala

db exception?

[Vijayendra Bhamidipati]

On a fresh nonoss dev setup of the latest 4.2 branch, I'm running into this DB 
exception when the SSVM is being started upon enabling a zone:


INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-2:) No running 
ssvm is found, so command will be sent to LocalHostEndPoint
INFO  [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:) No 
running secondary storage vms found in datacenter id=1, starting one
INFO  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) No 
stopped secondary storage vm is available, need to allocate a new secondary 
storage vm
WARN  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) Exception 
while trying to start secondary storage vm
com.cloud.utils.exception.CloudRuntimeException: DB Exception on: SELECT 
clusterList.cluster_id FROM (  SELECT cluster.cluster_id cluster_id, ( 
(sum(cluster.used) + sum(cluster.reserved) + ?)/sum(cluster.total) ) ratio, 
cluster.configValue value FROM (SELECT capacity.cluster_id cluster_id, 
capacity.used_capacity used, capacity.reserved_capacity reserved, 
capacity.total_capacity * overcommit.value total, CASE (SELECT count(*) FROM 
`cloud`.`cluster_details` details WHERE details.cluster_id = 
capacity.cluster_id AND details.name = ? ) WHEN 1 THEN ( CASE WHEN (SELECT 
details.value FROM `cloud`.`cluster_details` details WHERE details.cluster_id = 
capacity.cluster_id AND details.name = ?) is NULL THEN (SELECT config.value 
FROM `cloud`.`configuration` config WHERE config.name = ?)ELSE (SELECT 
details.value FROM `cloud`.`cluster_details` details WHERE details.cluster_id = 
capacity.cluster_id AND details.name = ? ) END )ELSE ( SELECT config.value FROM 
`cloud`.`configuration` config WHERE config.name = ?) END configValue FROM 
`cloud`.`op_host_capacity` capacity INNER JOIN `cloud`.`cluster_details` 
overcommit ON overcommit.cluster_id = capacity.cluster_id WHERE 
capacity.data_center_id = ? AND capacity.capacity_type = ? AND 
capacity.total_capacity > 0 AND overcommit.name = ?) cluster GROUP BY 
cluster.cluster_id)  clusterList WHERE clusterList.ratio > clusterList.value;
at 
com.cloud.capacity.dao.CapacityDaoImpl.listClustersCrossingThreshold(CapacityDaoImpl.java:217)
at 
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at 
com.cloud.deploy.FirstFitPlanner.removeClustersCrossingThreshold(FirstFitPlanner.java:284)
at 
com.cloud.deploy.FirstFitPlanner.scanClustersForDestinationInZoneOrPod(FirstFitPlanner.java:339)
at 
com.cloud.deploy.FirstFitPlanner.orderClusters(FirstFitPlanner.java:175)
at 
com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:405)
at 
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:822)
at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:574)
at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:567)
at 
com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:268)
at 
com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:693)
at 
com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300)
at 
com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123)
at 
com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50)
at 
com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104)
at 
com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
at 
com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at 
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.sql.SQLException: Got error 28 from storage engine
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1074)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4074)
at com.mysql.jdbc.MysqlIO.checkEr

Re: db exception?

[Pedro Roque Marques]

I've bumped into exceptions with similar signature in the past when the 
database schema has not been updated to match the Dao objects.

Check whether the cloud.cluster database has all the fields listed in the 
select statement displayed in the exception.

  Pedro.

On Aug 10, 2013, at 3:03 PM, Vijayendra Bhamidipati wrote:

> On a fresh nonoss dev setup of the latest 4.2 branch, I'm running into this 
> DB exception when the SSVM is being started upon enabling a zone:
> 
> 
> INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-2:) No 
> running ssvm is found, so command will be sent to LocalHostEndPoint
> INFO  [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:) 
> No running secondary storage vms found in datacenter id=1, starting one
> INFO  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) No 
> stopped secondary storage vm is available, need to allocate a new secondary 
> storage vm
> WARN  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) 
> Exception while trying to start secondary storage vm
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on: SELECT 
> clusterList.cluster_id FROM (  SELECT cluster.cluster_id cluster_id, ( 
> (sum(cluster.used) + sum(cluster.reserved) + ?)/sum(cluster.total) ) ratio, 
> cluster.configValue value FROM (SELECT capacity.cluster_id cluster_id, 
> capacity.used_capacity used, capacity.reserved_capacity reserved, 
> capacity.total_capacity * overcommit.value total, CASE (SELECT count(*) FROM 
> `cloud`.`cluster_details` details WHERE details.cluster_id = 
> capacity.cluster_id AND details.name = ? ) WHEN 1 THEN ( CASE WHEN (SELECT 
> details.value FROM `cloud`.`cluster_details` details WHERE details.cluster_id 
> = capacity.cluster_id AND details.name = ?) is NULL THEN (SELECT config.value 
> FROM `cloud`.`configuration` config WHERE config.name = ?)ELSE (SELECT 
> details.value FROM `cloud`.`cluster_details` details WHERE details.cluster_id 
> = capacity.cluster_id AND details.name = ? ) END )ELSE ( SELECT config.value 
> FROM `cloud`.`configuration` config WHERE config.name = ?) END configValue 
> FROM `cloud`.`op_host_capacity` capacity INNER JOIN `cloud`.`cluster_details` 
> overcommit ON overcommit.cluster_id = capacity.cluster_id WHERE 
> capacity.data_center_id = ? AND capacity.capacity_type = ? AND 
> capacity.total_capacity > 0 AND overcommit.name = ?) cluster GROUP BY 
> cluster.cluster_id)  clusterList WHERE clusterList.ratio > clusterList.value;
>at 
> com.cloud.capacity.dao.CapacityDaoImpl.listClustersCrossingThreshold(CapacityDaoImpl.java:217)
>at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>at 
> com.cloud.deploy.FirstFitPlanner.removeClustersCrossingThreshold(FirstFitPlanner.java:284)
>at 
> com.cloud.deploy.FirstFitPlanner.scanClustersForDestinationInZoneOrPod(FirstFitPlanner.java:339)
>at 
> com.cloud.deploy.FirstFitPlanner.orderClusters(FirstFitPlanner.java:175)
>at 
> com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:405)
>at 
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:822)
>at 
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:574)
>at 
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:567)
>at 
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:268)
>at 
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:693)
>at 
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300)
>at 
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123)
>at 
> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50)
>at 
> com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104)
>at 
> com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
>at 
> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
>at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
>at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>at 
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
>at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
>at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
>at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
>at 
> java.util.con

Re: [ANNOUNCE] New Committer: Vijay Bhamidipati

[Bharat Kumar]

Congrats Vijay!

Re: db exception?

[Harikrishna Patnala]

Please check you cluster_details table for memory and cpu overcommit values. 
This statement expects to have these details in cluster_details table.

-Harikrishna
On 11-Aug-2013, at 4:45 AM, Pedro Roque Marques  
wrote:

> I've bumped into exceptions with similar signature in the past when the 
> database schema has not been updated to match the Dao objects.
> 
> Check whether the cloud.cluster database has all the fields listed in the 
> select statement displayed in the exception.
> 
>  Pedro.
> 
> On Aug 10, 2013, at 3:03 PM, Vijayendra Bhamidipati wrote:
> 
>> On a fresh nonoss dev setup of the latest 4.2 branch, I'm running into this 
>> DB exception when the SSVM is being started upon enabling a zone:
>> 
>> 
>> INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-2:) No 
>> running ssvm is found, so command will be sent to LocalHostEndPoint
>> INFO  [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:) 
>> No running secondary storage vms found in datacenter id=1, starting one
>> INFO  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) No 
>> stopped secondary storage vm is available, need to allocate a new secondary 
>> storage vm
>> WARN  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) 
>> Exception while trying to start secondary storage vm
>> com.cloud.utils.exception.CloudRuntimeException: DB Exception on: SELECT 
>> clusterList.cluster_id FROM (  SELECT cluster.cluster_id cluster_id, ( 
>> (sum(cluster.used) + sum(cluster.reserved) + ?)/sum(cluster.total) ) ratio, 
>> cluster.configValue value FROM (SELECT capacity.cluster_id cluster_id, 
>> capacity.used_capacity used, capacity.reserved_capacity reserved, 
>> capacity.total_capacity * overcommit.value total, CASE (SELECT count(*) FROM 
>> `cloud`.`cluster_details` details WHERE details.cluster_id = 
>> capacity.cluster_id AND details.name = ? ) WHEN 1 THEN ( CASE WHEN (SELECT 
>> details.value FROM `cloud`.`cluster_details` details WHERE 
>> details.cluster_id = capacity.cluster_id AND details.name = ?) is NULL THEN 
>> (SELECT config.value FROM `cloud`.`configuration` config WHERE config.name = 
>> ?)ELSE (SELECT details.value FROM `cloud`.`cluster_details` details WHERE 
>> details.cluster_id = capacity.cluster_id AND details.name = ? ) END )ELSE ( 
>> SELECT config.value FROM `cloud`.`configuration` config WHERE config.name = 
>> ?) END configValue FROM `cloud`.`op_host_capacity` capacity INNER JOIN 
>> `cloud`.`cluster_details` overcommit ON overcommit.cluster_id = 
>> capacity.cluster_id WHERE capacity.data_center_id = ? AND 
>> capacity.capacity_type = ? AND capacity.total_capacity > 0 AND 
>> overcommit.name = ?) cluster GROUP BY cluster.cluster_id)  clusterList WHERE 
>> clusterList.ratio > clusterList.value;
>>   at 
>> com.cloud.capacity.dao.CapacityDaoImpl.listClustersCrossingThreshold(CapacityDaoImpl.java:217)
>>   at 
>> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>>   at 
>> com.cloud.deploy.FirstFitPlanner.removeClustersCrossingThreshold(FirstFitPlanner.java:284)
>>   at 
>> com.cloud.deploy.FirstFitPlanner.scanClustersForDestinationInZoneOrPod(FirstFitPlanner.java:339)
>>   at 
>> com.cloud.deploy.FirstFitPlanner.orderClusters(FirstFitPlanner.java:175)
>>   at 
>> com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:405)
>>   at 
>> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:822)
>>   at 
>> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:574)
>>   at 
>> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:567)
>>   at 
>> com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:268)
>>   at 
>> com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:693)
>>   at 
>> com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300)
>>   at 
>> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123)
>>   at 
>> com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50)
>>   at 
>> com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104)
>>   at 
>> com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
>>   at 
>> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
>>   at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
>>   at 
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>>   at 
>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
>>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.ja