<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 15 October 2014 18:57, Parag Mhashilkar <span dir="ltr"><<a href="mailto:parag@fnal.gov" target="_blank">parag@fnal.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Daniel<br>
<br>
Such a feature would be really useful when provisioning VMs and avoiding leaks. To be useful, this also requires support for client token in ec2-describe-instances equivalent in open nebula<br>
<a href="http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-DescribeInstances.html" target="_blank">http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-DescribeInstances.html</a><br>
<br></blockquote><div><br></div><div>I have opened a ticker in our dev portal, and we will try to implement it.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
AWS uses client token to achieve idempotency in few other calls too, but I will leave that upto you on if and where you want to support such a functionality.<br></blockquote><div><br></div><div>The easiest way to implement this is only for VMs as I explained before. If we want to support this for any call we would have to generate a client token pool and it will be trickier.</div><div><br></div><div>Cheers </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="im HOEnZb"><br>
Thanks & Regards<br>
+==========================================================<br>
| Parag Mhashilkar<br>
| Fermi National Accelerator Laboratory, MS 120<br>
| Wilson & Kirk Road, Batavia, IL - 60510<br>
|----------------------------------------------------------<br>
| Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109<br>
|----------------------------------------------------------<br>
| Wilson Hall, 806E (Nov 8, 2012 - To date)<br>
| Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012)<br>
| Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010)<br>
| Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007)<br>
+==========================================================<br>
<br>
</span><div class="HOEnZb"><div class="h5">On Oct 15, 2014, at 11:44 AM, Daniel Molina wrote:<br>
<br>
> I think tthat could be implemented in the econe server.<br>
> 1. Include an EC2_CLIENT_TOKEN in the vm.allocate method containing the ClientToken param provided in the CreateInstance command.<br>
> 2. When a new CreateInstance is requested and contains a ClientToken, the vmpool is retrieved to check if any vm contains that token<br>
><br>
> On 15 October 2014 18:34, Parag Mhashilkar <<a href="mailto:parag@fnal.gov">parag@fnal.gov</a>> wrote:<br>
> That won't help. If the middle ware like HTcondor or run-instance commands starts putting anything in the user data, users are deprived of the functionality of user data.<br>
><br>
> AWS achieves idempotency with --client-token option, which to me seems like a tagging the request from the client side.<br>
><br>
> <a href="http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-RunInstances.html" target="_blank">http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-RunInstances.html</a><br>
><br>
><br>
> Thanks & Regards<br>
> +==========================================================<br>
> | Parag Mhashilkar<br>
> | Fermi National Accelerator Laboratory, MS 120<br>
> | Wilson & Kirk Road, Batavia, IL - 60510<br>
> |----------------------------------------------------------<br>
> | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109<br>
> |----------------------------------------------------------<br>
> | Wilson Hall, 806E (Nov 8, 2012 - To date)<br>
> | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012)<br>
> | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010)<br>
> | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007)<br>
> +==========================================================<br>
><br>
> On Oct 15, 2014, at 11:27 AM, Daniel Molina wrote:<br>
><br>
> ><br>
> ><br>
> > On 15 October 2014 18:18, Parag Mhashilkar <<a href="mailto:parag@fnal.gov">parag@fnal.gov</a>> wrote:<br>
> > Hi Daniel,<br>
> ><br>
> > Let me rephrase what we meant.<br>
> ><br>
> > As Steve mentioned in one of his emails, we use HTCondor to launch VMs. There is always a possibility that something can go wrong after a run-instance command is issued and before the ec2 server gets back to you with a valid instance id or an error message. Note that in this case the server may serve the request, but there is no way for the client to know the exact instance name that resulted from the request. Life is much easier if the client crashes after it gets back the instance name.<br>
> ><br>
> > One way for the client to know the exact status of the request even after a crash (and before it gets the instance id) is to assign a unique identifier of its own like a tag name or something. This way client will never lose track of the request and result in the leaked VMs.<br>
> ><br>
> > The way HTCondor is implementing this is by creating a new key pair and giving it a unique name and tracking the requests based on the key pair. But then we are hit by other limit ~300 that we observed.<br>
> ><br>
> > Ideally, we would like to use the --keypair option and use the existing pre registered key. But than we cannot track the results of the create-instance in case something goes wrong before the instance id is issued.<br>
> ><br>
> > And what about including a tag in the UserData instead of using the unique keypar?<br>
> ><br>
> ><br>
> ><br>
> > Thanks & Regards<br>
> > +==========================================================<br>
> > | Parag Mhashilkar<br>
> > | Fermi National Accelerator Laboratory, MS 120<br>
> > | Wilson & Kirk Road, Batavia, IL - 60510<br>
> > |----------------------------------------------------------<br>
> > | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109<br>
> > |----------------------------------------------------------<br>
> > | Wilson Hall, 806E (Nov 8, 2012 - To date)<br>
> > | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012)<br>
> > | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010)<br>
> > | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007)<br>
> > +==========================================================<br>
> ><br>
> > On Oct 15, 2014, at 11:02 AM, Daniel Molina wrote:<br>
> ><br>
> > ><br>
> > ><br>
> > > On 15 October 2014 17:57, Steven Timm <<a href="mailto:timm@fnal.gov">timm@fnal.gov</a>> wrote:<br>
> > > If you call the same CreateInstances command more than once<br>
> > > is there any way that it will create the instance twice or not.<br>
> > ><br>
> > > If you call the command twice it will create 2 instances. You can also provide de MaxCount param in the CreateInstance command to create more than one instance at once.<br>
> > ><br>
> > ><br>
> > > Steve Timm<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > On Wed, 15 Oct 2014, Daniel Molina wrote:<br>
> > ><br>
> > > Hi,<br>
> > > What do you mean with "idempotent"? As long as the client implements the ec2 API, it should work<br>
> > > Cheers<br>
> > ><br>
> > > On 13 October 2014 20:33, Parag Mhashilkar <<a href="mailto:parag@fnal.gov">parag@fnal.gov</a>> wrote:<br>
> > > Hi,<br>
> > ><br>
> > > We are using HTCondor to launch VMs in OpenNebula using ec2 interface and would like to know if the<br>
> > > submit calls are idempotent.<br>
> > ><br>
> > > Thanks & Regards<br>
> > > +==========================================================<br>
> > > | Parag Mhashilkar<br>
> > > | Fermi National Accelerator Laboratory, MS 120<br>
> > > | Wilson & Kirk Road, Batavia, IL - 60510<br>
> > > |----------------------------------------------------------<br>
> > > | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109<br>
> > > |----------------------------------------------------------<br>
> > > | Wilson Hall, 806E (Nov 8, 2012 - To date)<br>
> > > | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012)<br>
> > > | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010)<br>
> > > | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007)<br>
> > > +==========================================================<br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > Users mailing list<br>
> > > <a href="mailto:Users@lists.opennebula.org">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>
> > ><br>
> > ><br>
> > ><br>
> > > --<br>
> > > --<br>
> > > Daniel Molina<br>
> > > Project Engineer<br>
> > > OpenNebula - Flexible Enterprise Cloud Made Simple<br>
> > > <a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:dmolina@opennebula.org">dmolina@opennebula.org</a> | @OpenNebula<br>
> > ><br>
> > ><br>
> > ><br>
> > > ------------------------------------------------------------------<br>
> > > Steven C. Timm, Ph.D (630) 840-8525<br>
> > > <a href="mailto:timm@fnal.gov">timm@fnal.gov</a> <a href="http://home.fnal.gov/~timm/" target="_blank">http://home.fnal.gov/~timm/</a><br>
> > > Fermilab Scientific Computing Division, Scientific Computing Services Quad.<br>
> > > Grid and Cloud Services Dept., Associate Dept. Head for Cloud Computing<br>
> > ><br>
> > ><br>
> > ><br>
> > > --<br>
> > > --<br>
> > > Daniel Molina<br>
> > > Project Engineer<br>
> > > OpenNebula - Flexible Enterprise Cloud Made Simple<br>
> > > <a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:dmolina@opennebula.org">dmolina@opennebula.org</a> | @OpenNebula<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > --<br>
> > Daniel Molina<br>
> > Project Engineer<br>
> > OpenNebula - Flexible Enterprise Cloud Made Simple<br>
> > <a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:dmolina@opennebula.org">dmolina@opennebula.org</a> | @OpenNebula<br>
><br>
><br>
><br>
><br>
> --<br>
> --<br>
> Daniel Molina<br>
> Project Engineer<br>
> OpenNebula - Flexible Enterprise Cloud Made Simple<br>
> <a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:dmolina@opennebula.org">dmolina@opennebula.org</a> | @OpenNebula<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>--<br></div>Daniel Molina<br>Project Engineer<br>OpenNebula - Flexible Enterprise Cloud Made Simple<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:dmolina@opennebula.org" target="_blank">dmolina@opennebula.org</a> | @OpenNebula</div>
</div></div>