Hi Tino,
thanks for prompt reply! Comments inline.
Tino Vazquez wrote on 30/03/11 20:29:
Hi,
I think the problem comes with this
DISK=[
DISKINODES=200000:220000,
DISKSPACE=1048576:1153024,
DISK_ID=1,
QUOTATIME=0,
TYPE=os ]
It doesn't have source path
you are right. The mentioned error disappeared when I specified as below:
DISK = [ IMAGE = "centos-5-x86",
DISKSPACE="1048576:1153024",
DISKINODES="200000:220000",
QUOTATIME="0" ]
But then DISKSPACE, DISKINODES and QUOTATIME are not passed to remote
node in deployment.0 file :
<TEMPLATE>
<CPU>
<CPUS><![CDATA[1]]></CPUS>
<CPUUNITS><![CDATA[1000]]></CPUUNITS>
</CPU>
<DISK>
<CLONE><![CDATA[YES]]></CLONE>
<DISK_ID><![CDATA[0]]></DISK_ID>
<IMAGE><![CDATA[centos-5-x86]]></IMAGE>
<IMAGE_ID><![CDATA[1]]></IMAGE_ID>
<READONLY><![CDATA[NO]]></READONLY>
<SAVE><![CDATA[NO]]></SAVE>
<SOURCE><![CDATA[/srv/cloud/one/one-2.2.0/var//images/70f38bbaf574eef06b8e3ca4e8ebee3eb1f1786d]]></SOURCE>
<TARGET><![CDATA[sda]]></TARGET>
<TYPE><![CDATA[DISK]]></TYPE>
</DISK>
<DISK>
<DISK_ID><![CDATA[1]]></DISK_ID>
<READONLY><![CDATA[no]]></READONLY>
<SIZE><![CDATA[1024]]></SIZE>
<TARGET><![CDATA[sdd]]></TARGET>
<TYPE><![CDATA[swap]]></TYPE>
</DISK>
<MEMORY>
<KMEMSIZE><![CDATA[14372700:14790164]]></KMEMSIZE>
<LOCKEDPAGES><![CDATA[2048:2048]]></LOCKEDPAGES
<OOMGUARPAGES><![CDATA[26112:unlimited]]></OOMGUARPAGES
<PHYSPAGES><![CDATA[0:unlimited]]></PHYSPAGES>
<PRIVVMPAGES><![CDATA[65536:69632]]></PRIVVMPAGES>
<SHMPAGES><![CDATA[21504:21504]]></SHMPAGES>
<VMGUARPAGES><![CDATA[33792:unlimited]]></VMGUARPAGES>
</MEMORY>
<NAME><![CDATA[one-6]]></NAME>
<ONBOOT><![CDATA[yes]]></ONBOOT>
<VMID><![CDATA[6]]></VMID>
</TEMPLATE
What way would you recommend to pass disk-related parameters such as
DISKSPACE, DISKINODES and QUOTATIME (and could be more) to deployment.0
file?
, are you using the Image Catalog or
writing the disk entries by hand?
I am trying to use the OS image from ONE Image Catalog (I guess that is
preferred method in ONE).
About the other concern, I believe ruben is talking about the actual
external, another process driver, the one that invokes the "deploy"
script.
as far as I understand the deployment and basic domain (VM) operations
have already implemented in the file
$ONE_LOCATION/lib/mads/one_vmm_ssh.rb. So I guess the operations
themselves executing on remote host are needed to be properly
implemented (apart from passing properly VM options from ONE format
template into XML one).
Thanks for your help!
Nikolay.
_______________________________________________
Users mailing list
[email protected]
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
