You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@deltacloud.apache.org by mf...@apache.org on 2012/01/20 12:40:38 UTC
svn commit: r1233878 -
/deltacloud/trunk/server/lib/deltacloud/drivers/vsphere/vsphere_driver.rb
Author: mfojtik
Date: Fri Jan 20 11:40:38 2012
New Revision: 1233878
URL: http://svn.apache.org/viewvc?rev=1233878&view=rev
Log:
VSphere: Replaced the effectiveMemory in hardware profile with hardcoded value (DTACLOUD-123)
Modified:
deltacloud/trunk/server/lib/deltacloud/drivers/vsphere/vsphere_driver.rb
Modified: deltacloud/trunk/server/lib/deltacloud/drivers/vsphere/vsphere_driver.rb
URL: http://svn.apache.org/viewvc/deltacloud/trunk/server/lib/deltacloud/drivers/vsphere/vsphere_driver.rb?rev=1233878&r1=1233877&r2=1233878&view=diff
==============================================================================
--- deltacloud/trunk/server/lib/deltacloud/drivers/vsphere/vsphere_driver.rb (original)
+++ deltacloud/trunk/server/lib/deltacloud/drivers/vsphere/vsphere_driver.rb Fri Jan 20 11:40:38 2012
@@ -42,13 +42,17 @@ module Deltacloud::Drivers::VSphere
safely do
service = vsphere.serviceInstance.content
max_memory, max_cpu_cores = [], []
+ #
+ # Note: Memory is being hardcoded now to range 512MB to 2GB
+ # JIRA: DTACLOUD-123
+ #
service.rootFolder.childEntity.grep(RbVmomi::VIM::Datacenter).each do |dc|
- max_memory << dc.hostFolder.childEntity.first.summary.effectiveMemory
+ # max_memory << dc.hostFolder.childEntity.first.summary.effectiveMemory
max_cpu_cores << dc.hostFolder.childEntity.first.summary.numCpuCores
end
[Deltacloud::HardwareProfile::new('default') do
cpu (1..max_cpu_cores.min)
- memory (128..max_memory.min)
+ memory (512..2048)
architecture ['x86_64', 'i386']
end]
end