<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'>Ruben,<br>Thank you for the info. I was able to make some slight modifications to my TM driver. I tested my failover process and it works great. Simply change a few parameters in my DS template & redeploy the VM's on a different storage server.<br><br>Looking again at the docs for storage subsystem integration, unless I am misinterpreting them it does not appear that the parameters are described correctly. For example, what I am seeing when I log arguments to the ln script is that arg3 is the VMID and arg4 is the DSID for the image. It appears the docs may need some updating.<br><br>Thanks again,<br>gary<br><br><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Gary S. Cuozzo" <gary@isgsoftware.net><br><b>To: </b>"Users OpenNebula" <users@lists.opennebula.org><br><b>Sent: </b>Thursday, December 27, 2012 9:13:39 AM<br><b>Subject: </b>Re: [one-users] Access to DS for image in TM<br><br><style>p { margin: 0; }</style><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000">Hello Ruben,<br>I'm glad I asked. I must have missed something in the docs. I thought it was the system datastore of the remote host that was sent in. If it is the ID of the image DS, then I will be all set.<br><br>Thanks!<br>gary<br><br><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Ruben S. Montero" <rsmontero@opennebula.org><br><b>To: </b>"Gary S. Cuozzo" <gary@isgsoftware.net><br><b>Cc: </b>"Users OpenNebula" <users@lists.opennebula.org><br><b>Sent: </b>Thursday, December 27, 2012 4:01:40 AM<br><b>Subject: </b>Re: [one-users] Access to DS for image in TM<br><br><div dir="ltr">Hi Gary,<div><br></div><div style="">The last parameter of the TM scripts is the DS_ID of the image, you could get the information by simply onedatastore show $DS_ID, and probably xpath.rb to get the SAN_HOST if you are working in a shell script. </div>
<div style=""><br></div><div style="">Note that DS_ID refers to the Datastore of the image, so for CLONE, LN ... would make sense, other operations may use the System DS as the DS_ID (e.g. DELETE).</div><div style=""><br></div><div style="">
Is this good enough?</div><div style=""><br></div><div style="">Cheers</div><div style=""><br></div><div style="">Ruben</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 26, 2012 at 2:59 PM, Gary S. Cuozzo <span dir="ltr"><<a href="mailto:gary@isgsoftware.net" target="_blank">gary@isgsoftware.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-size:12pt;font-family:arial,helvetica,sans-serif">Hello,<br>Sorry this is sort of long, hope it makes sense...<br>
<br>I have created customized DS & TM drivers for our NFS based storage servers. Each storage server is snap-shotted and replicated at least every hour to another server. I have a use case that I would like to be able to remap all images for a particular server quickly in the event of a failure, such as a hardware issue.<br>
<br>In my DS driver, I have a parameter for SAN_HOST which is used to determine which storage server will be used to deploy the image. For my failure case, I would like to simply be able to edit the SAN_HOST parameter for the particular DS which failed and redeploy the vm's, having the images automatically go to the backup server and not have to remap them all. This would take the recovery process from several hours of manually remapping things to probably < 1 hour.<br>
<br>The TM drivers don't get any information passed to them about the DS of the particular image they are working with. What I would like to do is be able to access the DS parameters for an image and use them to remap certain aspects of the image so the remapping will work.<br>
<br>The obvious way I've thought of is to just use the image SOURCE and iterate through the image list in order to get a match, then go look up the associated DS.<br><br>Is there any better way that I may be missing? My way seems a bit kludgy but I didn't think of any other way.<br>
<br>Thanks in advance,<br>gary<br><br></div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Ruben S. Montero, PhD<br>Project co-Lead and Chief Architect<br>OpenNebula - The Open Source Solution for Data Center Virtualization<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.org</a> | @OpenNebula
</div>
</div><br></div><br>_______________________________________________<br>Users mailing list<br>Users@lists.opennebula.org<br>http://lists.opennebula.org/listinfo.cgi/users-opennebula.org<br></div><br></div></body></html>