Hi, > Why the $VMID can't be passed to fail.sh when it is activated?
Where did you get that? The docs say $ID, not $VMID. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula<http://twitter.com/opennebula><cmar...@opennebula.org> On Mon, Feb 3, 2014 at 10:58 AM, Qiubo Su (David Su) <qiub...@gmail.com>wrote: > Dear OpenNebula Community, > > I'm using the OpenNebula 3.8.1 at the moment, however both of the VM_HOOK > and HOST_HOOK features don't look working well. Does anyone have similar > problem with OpenNebula 3.8.1? How about the later version, e.g. 3.8.3 or > 3.8.5? > > Thank you very much. > > Best regards, > Q.D.S. > > > On Sun, Feb 2, 2014 at 9:17 PM, Qiubo Su (David Su) <qiub...@gmail.com>wrote: > >> Dear OpenNebula Community, >> >> Sent you below email yesterday about not able to generate the desired >> FAILED state event (i.e. "read permission denied" when chmod -r >> /var/lib/image/win-xp-2.qcow2) to activate the action defined in the >> VM_HOOK section in ~/etc/oned.conf. >> >> Moreover, the $VMID (2nd argument defined in the VM_HOOK) can't be passed >> to the /var/lib/one/var/remotes/hooks/fail.sh file. >> >> For example, simply defined the fail.sh as: >> >> #!/bin/bash >> echo "$1" " $2" >> >> When "onevm resubmit 2014", the fail.sh is activated by other FAILED >> state event (not the one specified in below email), the output by echo "$1" >> "$2" is "VM" only, while it should be "VM 2014". >> >> Why the $VMID can't be passed to fail.sh when it is activated? >> >> Thank you very much for your help and have a great weekend ! >> >> Best regards, >> Q.D.S. >> >> On Sat, Feb 1, 2014 at 9:26 PM, Qiubo Su (David Su) <qiub...@gmail.com>wrote: >> >>> Dear OpenNebula Community, >>> >>> The environment: a VT enabled physical machine with ubuntu 12.04 server >>> OS and opennebula 3.8.1 front end (KVM, QEMU and libvirtd installed for >>> hypervisor). >>> >>> Configure the ~/etc/oned.conf to support HOOKS as below: >>> >>> VM_HOOK = [ >>> name = "on_failure", >>> on = "FAILED", >>> command = "/var/lib/one/var/remotes/hooks/fail.sh", >>> arguments = "VM $VMID" ] >>> >>> Create a script /var/lib/one/var/remotes/hooks/fail.sh to capture the >>> FAILED state event and do desired action. >>> >>> To create a FAILED state event, after creating a VM image (below 1) is >>> the VM image creation template) and before creating a VM (below 2) is the >>> VM creation template), chmod -r /var/lib/image/win-xp-2.qcow2 to remove the >>> read permission from the VM image file which is referred in the VM image >>> creation template, but the VM can still be created successfully, while the >>> VM creation should be failed and there should be error message like "read >>> permission denied" in the ~/var/oned.log file. >>> >>> It is much appreciated if anyone can help with this, to explain why the >>> VM image creation and VM creation process don't work as it should be? Thank >>> very much ! >>> >>> 1) VM image creation template: >>> >>> NAME = "win-xp-1" >>> PATH = /var/lib/image/win-xp-2.qcow2 >>> TYPE = OS >>> >>> 2) VM creation template: >>> >>> HOSTNAME = OneHost >>> #CONTEXT definition section >>> CONTEXT=[FILES="/var/lib/one/.ssh/id_rsa.pub >>> /var/lib/one/image/setcontextvals.bat /var/lib/one/image/sethostname.vbs", >>> HOSTNAME=WinXP-$VMID, >>> IP_PUBLIC="$NIC[IP, NETWORK=\"Small network\"]", >>> PASSWORD=password, >>> ROOT_PUBKEY=id_rsa.pub, >>> USERNAME=user] >>> #CAPACITY Definition >>> NAME=WindowsXP-NoPers >>> CPU=1 >>> MEMORY=1024 >>> # OS image, mapped to hda. >>> DISK=[ DRIVER=qcow2, READONLY=no, IMAGE_ID = 1, TARGET=hda, TYPE=disk ] >>> FEATURES=[ ACPI=yes ] >>> # I/O Devices Section >>> GRAPHICS=[ TYPE=vnc ] >>> #NETWORK Section: >>> NIC=[ model=e1000, network = "Small network" ] >>> #OS and BOOT Options Section >>> OS=[ ARCH=i686, BOOT=hd ] >>> #RAW Section >>> RAW=[ TYPE=kvm ] >>> >>> Best regards, >>> Q.D.S. >>> >>> >>> On Fri, Jan 24, 2014 at 11:50 PM, Qiubo Su (David Su) <qiub...@gmail.com >>> > wrote: >>> >>>> Dear OpenNebula Community, I use OpenNebula 3.8.1, can't update it to >>>> 4.4, so what ds.conf should look like to achieve the purpose? Thanks. >>>> >>>> >>>> >>>> On Fri, Jan 24, 2014 at 11:30 PM, Tino Vazquez <cvazq...@c12g.com>wrote: >>>> >>>>> Hi, >>>>> >>>>> If you want to use the ssh drivers, you need to configure the DS as >>>>> follows: >>>>> >>>>> NAME = production >>>>> DS_MAD = ssh >>>>> TM_MAD = ssh >>>>> >>>>> Support for ssh drivers for VMware were dropped in more recent >>>>> releases, so its use is discouraged. Please update to 4.4 and use >>>>> 'vmfs' DS and TM drivers >>>>> >>>>> Regards, >>>>> >>>>> -Tino >>>>> >>>>> -- >>>>> OpenNebula - Flexible Enterprise Cloud Made Simple >>>>> >>>>> -- >>>>> Constantino Vázquez Blanco, PhD, MSc >>>>> Senior Infrastructure Architect at C12G Labs >>>>> www.c12g.com | @C12G | es.linkedin.com/in/tinova >>>>> >>>>> -- >>>>> Confidentiality Warning: The information contained in this e-mail and >>>>> any accompanying documents, unless otherwise expressly indicated, is >>>>> confidential and privileged, and is intended solely for the person >>>>> and/or entity to whom it is addressed (i.e. those identified in the >>>>> "To" and "cc" box). They are the property of C12G Labs S.L.. >>>>> Unauthorized distribution, review, use, disclosure, or copying of this >>>>> communication, or any part thereof, is strictly prohibited and may be >>>>> unlawful. If you have received this e-mail in error, please notify us >>>>> immediately by e-mail at ab...@c12g.com and delete the e-mail and >>>>> attachments and any copy from your system. C12G thanks you for your >>>>> cooperation. >>>>> >>>>> >>>>> On Thu, Jan 23, 2014 at 10:55 PM, Qiubo Su (David Su) < >>>>> qiub...@gmail.com> wrote: >>>>> > Dear Tino and OpenNebula Community, >>>>> > >>>>> > 1) can update the TM_MAD for datastore in Sunstone. >>>>> > >>>>> > 2) the content of ds.conf is as below. >>>>> > >>>>> > NAME = production >>>>> > DS_MAD = vmware >>>>> > TM_MAD = shared >>>>> > >>>>> > do you mean need to update it as below? >>>>> > >>>>> > NAME = production >>>>> > DS_MAD = vmfs >>>>> > TM_MAD = vmfs >>>>> > >>>>> > if using the 1st ds.conf, it has to manually create the >>>>> > /var/lib/one/var/datastores/100, so to be able to thin provisioned >>>>> the >>>>> > disk.vmdk (actually the Ubuntu.vmdk file in the package download from >>>>> > http://www.trendsigma.net/vmware/ubuntu1110t.html) by running >>>>> "vmkfstools >>>>> > -username root -password redhat123 -server esxi01 -i '[100] >>>>> > /images/disk.vmdk' -d thin '[100] /images/disk1.vmdk'" in the front >>>>> end >>>>> > server? (the name of this experiment is called "OpenNebula 3.8.1 and >>>>> VMware >>>>> > ESXI 5.0.0 Using shared VMware and ssh transfer drivers"). >>>>> > >>>>> > if using the 2nd ds.conf, can & how can the purpose of the >>>>> experiment be >>>>> > achieved? >>>>> > >>>>> > kind regards, >>>>> > q.s. >>>>> > >>>>> > >>>>> > On Wed, Jan 22, 2014 at 11:04 PM, Tino Vazquez <cvazq...@c12g.com> >>>>> wrote: >>>>> >> >>>>> >> Hi, >>>>> >> >>>>> >> About 1), do you get the same behaviour if you try and change it >>>>> >> through Sunstone? >>>>> >> >>>>> >> Regarding 2), can you share the contents of the datastore template >>>>> >> (ds.conf)? If you want to use VMware datastores, please note that >>>>> the >>>>> >> correct name for the TM and DS drivers are 'vmfs'. These drivers >>>>> >> *won't* create a directory in the front-end since the datastores are >>>>> >> only present in the ESX hosts. >>>>> >> >>>>> >> Moreover, BASE_PATH in VMware datastores need to be set to >>>>> /vmfs/volumes. >>>>> >> >>>>> >> Best, >>>>> >> >>>>> >> -Tino >>>>> >> >>>>> >> -- >>>>> >> OpenNebula - Flexible Enterprise Cloud Made Simple >>>>> >> >>>>> >> -- >>>>> >> Constantino Vázquez Blanco, PhD, MSc >>>>> >> Senior Infrastructure Architect at C12G Labs >>>>> >> www.c12g.com | @C12G | es.linkedin.com/in/tinova >>>>> >> >>>>> >> -- >>>>> >> Confidentiality Warning: The information contained in this e-mail >>>>> and >>>>> >> any accompanying documents, unless otherwise expressly indicated, is >>>>> >> confidential and privileged, and is intended solely for the person >>>>> >> and/or entity to whom it is addressed (i.e. those identified in the >>>>> >> "To" and "cc" box). They are the property of C12G Labs S.L.. >>>>> >> Unauthorized distribution, review, use, disclosure, or copying of >>>>> this >>>>> >> communication, or any part thereof, is strictly prohibited and may >>>>> be >>>>> >> unlawful. If you have received this e-mail in error, please notify >>>>> us >>>>> >> immediately by e-mail at ab...@c12g.com and delete the e-mail and >>>>> >> attachments and any copy from your system. C12G thanks you for your >>>>> >> cooperation. >>>>> >> >>>>> >> >>>>> >> On Sat, Jan 18, 2014 at 6:10 AM, Qiubo Su (David Su) < >>>>> qiub...@gmail.com> >>>>> >> wrote: >>>>> >> > Dear OpenNebula Community, >>>>> >> > >>>>> >> > For 2) problem listed in the below previous email, I created the >>>>> >> > datastore >>>>> >> > manually by running "onedatastore create ds.conf" and created >>>>> another >>>>> >> > one >>>>> >> > from Sunstone, but in both cases, can't see the >>>>> >> > /var/lib/one/var/datastores/101 directory in the file system >>>>> (../102 >>>>> >> > directory in the Sunstone case), even though can see the "BASE >>>>> PATH : >>>>> >> > /var/lib/one/var/datastores/101" when run "onedatastore show 101". >>>>> >> > >>>>> >> > It is much appreciated if anyone can help with this, tell me why >>>>> there >>>>> >> > is >>>>> >> > this problem and how to fix it? Thank you very much and Have a >>>>> Great >>>>> >> > Weekend >>>>> >> > ! >>>>> >> > >>>>> >> > >>>>> >> > >>>>> ****************************************************************************************** >>>>> >> > >>>>> >> > Sat Jan 18 17:48:40 2014 [ReM][D]: Req:5712 UID:0 HostPoolInfo >>>>> invoked >>>>> >> > Sat Jan 18 17:48:40 2014 [ReM][D]: Req:5712 UID:0 HostPoolInfo >>>>> result >>>>> >> > SUCCESS, "<HOST_POOL><HOST><ID..." >>>>> >> > Sat Jan 18 17:48:40 2014 [ReM][D]: Req:3376 UID:0 >>>>> VirtualMachinePoolInfo >>>>> >> > invoked, -2, -1, -1, -1 >>>>> >> > Sat Jan 18 17:48:40 2014 [ReM][D]: Req:3376 UID:0 >>>>> VirtualMachinePoolInfo >>>>> >> > result SUCCESS, "<VM_POOL></VM_POOL>" >>>>> >> > Sat Jan 18 17:48:40 2014 [ReM][D]: Req:4704 UID:0 AclInfo invoked >>>>> >> > Sat Jan 18 17:48:40 2014 [ReM][D]: Req:4704 UID:0 AclInfo result >>>>> >> > SUCCESS, >>>>> >> > "<ACL_POOL><ACL><ID>0..." >>>>> >> > Sat Jan 18 17:48:43 2014 [AuM][D]: Message received: LOG I 79 >>>>> ExitCode: >>>>> >> > 0 >>>>> >> > >>>>> >> > Sat Jan 18 17:48:43 2014 [AuM][I]: ExitCode: 0 >>>>> >> > Sat Jan 18 17:48:43 2014 [AuM][D]: Message received: AUTHENTICATE >>>>> >> > SUCCESS 79 >>>>> >> > - >>>>> >> > >>>>> >> > Sat Jan 18 17:48:43 2014 [ReM][D]: Req:32 UID:0 DatastoreAllocate >>>>> >> > invoked, >>>>> >> > "DISK_TYPE="block"...", -1 >>>>> >> > Sat Jan 18 17:48:43 2014 [ReM][D]: Req:32 UID:0 DatastoreAllocate >>>>> result >>>>> >> > SUCCESS, 102 >>>>> >> > Sat Jan 18 17:48:43 2014 [ReM][D]: Req:6800 UID:0 DatastoreInfo >>>>> invoked, >>>>> >> > 102 >>>>> >> > Sat Jan 18 17:48:43 2014 [ReM][D]: Req:6800 UID:0 DatastoreInfo >>>>> result >>>>> >> > SUCCESS, "<DATASTORE><ID>102</..." >>>>> >> > Sat Jan 18 17:48:45 2014 [ReM][D]: Req:1200 UID:0 >>>>> DatastorePoolInfo >>>>> >> > invoked >>>>> >> > Sat Jan 18 17:48:45 2014 [ReM][D]: Req:1200 UID:0 >>>>> DatastorePoolInfo >>>>> >> > result >>>>> >> > SUCCESS, "<DATASTORE_POOL><DAT..." >>>>> >> > Sat Jan 18 17:48:51 2014 [ReM][D]: Req:6880 UID:0 TemplatePoolInfo >>>>> >> > invoked, >>>>> >> > -2, -1, -1 >>>>> >> > Sat Jan 18 17:48:51 2014 [ReM][D]: Req:6880 UID:0 TemplatePoolInfo >>>>> >> > result >>>>> >> > SUCCESS, "<VMTEMPLATE_POOL></V..." >>>>> >> > Sat Jan 18 17:49:05 2014 [ReM][D]: Req:5360 UID:0 HostPoolInfo >>>>> invoked >>>>> >> > Sat Jan 18 17:49:05 2014 [ReM][D]: Req:5360 UID:0 HostPoolInfo >>>>> result >>>>> >> > SUCCESS, "<HOST_POOL><HOST><ID..." >>>>> >> > Sat Jan 18 17:49:06 2014 [ReM][D]: Req:3328 UID:0 AclInfo invoked >>>>> >> > Sat Jan 18 17:49:06 2014 [ReM][D]: Req:3328 UID:0 AclInfo result >>>>> >> > SUCCESS, >>>>> >> > "<ACL_POOL><ACL><ID>0..." >>>>> >> > >>>>> >> > >>>>> >> > On Fri, Jan 17, 2014 at 9:49 PM, Qiubo Su (David Su) < >>>>> qiub...@gmail.com> >>>>> >> > wrote: >>>>> >> >> >>>>> >> >> Dear OpenNebula Community, >>>>> >> >> >>>>> >> >> 1) run "onedatastore list", get below return: >>>>> >> >> >>>>> >> >> ID NAME CLUSTER IMAGES TYPE TM >>>>> >> >> 0 system - 0 - >>>>> >> >> shared >>>>> >> >> 1 default - 2 fs >>>>> >> >> shared >>>>> >> >> >>>>> >> >> run "onedatastore update 0" and change the TM_MAD from "shared" >>>>> to >>>>> >> >> "ssh" >>>>> >> >> and save it, but the TM of datastore 0 is still "shared", doesn't >>>>> >> >> change to >>>>> >> >> "ssh". why? >>>>> >> >> >>>>> >> >> 2) manually create a datastore production, and "onedatastore >>>>> list" >>>>> >> >> return >>>>> >> >> as below: >>>>> >> >> >>>>> >> >> ID NAME CLUSTER IMAGES TYPE TM >>>>> >> >> 0 system - 0 - >>>>> >> >> shared >>>>> >> >> 1 default - 2 fs >>>>> >> >> shared >>>>> >> >> 100 production - vmware >>>>> >> >> shared >>>>> >> >> >>>>> >> >> but there is /var/lib/one/var/datastores/100 directory, only >>>>> >> >> /var/lib/one/var/datastores/0 and /var/lib/one/var/datastores/1 >>>>> >> >> directories. >>>>> >> >> why? >>>>> >> >> >>>>> >> >> thanks for your help for these. >>>>> >> >> >>>>> >> >> best regards, >>>>> >> >> q.s. >>>>> >> > >>>>> >> > >>>>> >> > >>>>> >> > _______________________________________________ >>>>> >> > Users mailing list >>>>> >> > Users@lists.opennebula.org >>>>> >> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >>>>> >> > >>>>> > >>>>> > >>>>> >>>> >>>> >>> >> > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org