Re: [one-users] econe server connection reset by peer
Hi Daniel, It doesn't seem to be DB limitation. The info gets stored in the field body of user_pool which is medium text. mysql desc user_pool; +-+--+--+-+-+---+ | Field | Type | Null | Key | Default | Extra | +-+--+--+-+-+---+ | oid | int(11) | NO | PRI | NULL| | | name| varchar(128) | YES | UNI | NULL| | | body| mediumtext | YES | | NULL| | | uid | int(11) | YES | | NULL| | | gid | int(11) | YES | | NULL| | | owner_u | int(11) | YES | | NULL| | | group_u | int(11) | YES | | NULL| | | other_u | int(11) | YES | | NULL| | +-+--+--+-+-+---+ 8 rows in set (0.00 sec) The actual content of the body with ~300 keys is ~240K bytes which is much less then the documented (http://dev.mysql.com/doc/refman/5.0/en/storage-requirements.html) limit of L + 3 bytes, where L 224 mysql select body from user_pool where name = nova into outfile '/tmp/parag.db1'; Query OK, 1 row affected (0.00 sec) [oneadmin@fermicloud198 ~]$ wc --bytes /tmp/parag.db1 240136 /tmp/parag.db1 Also, the contents of the field in DB are valid base64 encoded. So there is no chance of DB truncating the info. We suspect the limit is somehow artificially imposed in the server. However we were not able to figure out where and how it is configurable. Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== On Oct 15, 2014, at 10:56 AM, Daniel Molina wrote: Hi Steven, It looks like a DB limitation, this information is stored in the user template. So it should depend on the BODY column type and the DB backend used Cheers On 11 October 2014 03:58, Steven C Timm t...@fnal.gov wrote: We have been doing bulk tests of the OpenNebula 4.8 econe-server. With just a straight econe-run-instances we can get up to 1000 VM's (the limit of our current subnet) started fairly quickly (about 30 minutes) But in practice we are using a more complicated sequence of EC2 calls via HTCondor. In particular it is doing a CreateKeyPair call before it launches each VM and then calling the RunInstances method with the --keypair option, a unique keypair for each VM. After the VM exits, it called a DeleteKeyPair call. IT appears there is a hard limit of the number of key pairs that can be stored in any one user's template and that hard limit is 301. Any further CreateKeyPair calls return with connection reset by peer causing HTCondor to mark the VM as held. Fortunately it is possible to override this and tell HTCondor to continue, but it's a pain. We do have ways to log into the vm's without the ssh key pair so we wouldn't even really need to register them at all. Is my analysis correct? Is there a hard limit of the number of keys that can be stored in the user template? If so, how best to get around this limit? Steve Timm ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- -- Daniel Molina Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org smime.p7s Description: S/MIME cryptographic signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] econe-run-instances idempotent?
Hi Daniel, Let me rephrase what we meant. 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. 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. 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. 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. Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== On Oct 15, 2014, at 11:02 AM, Daniel Molina wrote: On 15 October 2014 17:57, Steven Timm t...@fnal.gov wrote: If you call the same CreateInstances command more than once is there any way that it will create the instance twice or not. 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. Steve Timm On Wed, 15 Oct 2014, Daniel Molina wrote: Hi, What do you mean with idempotent? As long as the client implements the ec2 API, it should work Cheers On 13 October 2014 20:33, Parag Mhashilkar pa...@fnal.gov wrote: Hi, We are using HTCondor to launch VMs in OpenNebula using ec2 interface and would like to know if the submit calls are idempotent. Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- -- Daniel Molina Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula -- Steven C. Timm, Ph.D (630) 840-8525 t...@fnal.gov http://home.fnal.gov/~timm/ Fermilab Scientific Computing Division, Scientific Computing Services Quad. Grid and Cloud Services Dept., Associate Dept. Head for Cloud Computing -- -- Daniel Molina Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula smime.p7s Description: S/MIME cryptographic signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] econe-run-instances idempotent?
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. AWS achieves idempotency with --client-token option, which to me seems like a tagging the request from the client side. http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-RunInstances.html Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== On Oct 15, 2014, at 11:27 AM, Daniel Molina wrote: On 15 October 2014 18:18, Parag Mhashilkar pa...@fnal.gov wrote: Hi Daniel, Let me rephrase what we meant. 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. 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. 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. 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. And what about including a tag in the UserData instead of using the unique keypar? Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== On Oct 15, 2014, at 11:02 AM, Daniel Molina wrote: On 15 October 2014 17:57, Steven Timm t...@fnal.gov wrote: If you call the same CreateInstances command more than once is there any way that it will create the instance twice or not. 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. Steve Timm On Wed, 15 Oct 2014, Daniel Molina wrote: Hi, What do you mean with idempotent? As long as the client implements the ec2 API, it should work Cheers On 13 October 2014 20:33, Parag Mhashilkar pa...@fnal.gov wrote: Hi, We are using HTCondor to launch VMs in OpenNebula using ec2 interface and would like to know if the submit calls are idempotent. Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- -- Daniel Molina Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | dmol
Re: [one-users] econe-run-instances idempotent?
Hi Daniel 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 http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-DescribeInstances.html 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. Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== On Oct 15, 2014, at 11:44 AM, Daniel Molina wrote: I think tthat could be implemented in the econe server. 1. Include an EC2_CLIENT_TOKEN in the vm.allocate method containing the ClientToken param provided in the CreateInstance command. 2. When a new CreateInstance is requested and contains a ClientToken, the vmpool is retrieved to check if any vm contains that token On 15 October 2014 18:34, Parag Mhashilkar pa...@fnal.gov wrote: 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. AWS achieves idempotency with --client-token option, which to me seems like a tagging the request from the client side. http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-RunInstances.html Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== On Oct 15, 2014, at 11:27 AM, Daniel Molina wrote: On 15 October 2014 18:18, Parag Mhashilkar pa...@fnal.gov wrote: Hi Daniel, Let me rephrase what we meant. 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. 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. 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. 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. And what about including a tag in the UserData instead of using the unique keypar? Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== On Oct 15, 2014, at 11:02 AM, Daniel Molina wrote: On 15 October 2014 17:57, Steven Timm t...@fnal.gov wrote: If you call the same CreateInstances command more than once is there any way that it will create the instance twice or not. If you call the command twice it will create 2
Re: [one-users] econe server connection reset by peer
Is this the default if not configured? If so this size should not be the limiting factor. MESSAGE_SIZE = 1073741824 Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== On Oct 15, 2014, at 11:23 AM, Daniel Molina wrote: Maybe a limitation in the XMLRPC server? You can tweak it in the oned.conf: https://github.com/OpenNebula/one/blob/master/share/etc/oned.conf#L112 Also, on top of what server are you running the econe service? You can deploy it on top of Passenger to get a better performance. The configuration should be similar to Sunstone ( you don't need the memcache configuration, since econe does not use sessions) http://docs.opennebula.org/4.8/advanced_administration/scalability/suns_advance.html#running-sunstone-with-passenger-in-apache On 15 October 2014 18:15, Steven Timm t...@fnal.gov wrote: Just the same error Fri Oct 10 00:03:51 2014 [E]: Connection reset by peer Fri Oct 10 00:03:51 2014 [I]: 131.225.155.244 - - [10/Oct/2014 00:03:51] GET /? Action=CreateKeyPairKeyName=SSH_fermicloud189%20fnal%20gov%209618_schedd_glidei ns2%20fermicloud189%20fnal%20gov%20420%200%201412917397SignatureMethod=HmacSHA2 56SignatureVersion=2Timestamp=2014-10-10T05%3A03%3A40ZVersion=2012-10-01Sign ature After a while it also starts throwing a 500 error for DescribeInstances Tue Oct 14 21:57:54 2014 [E]: HTTP-Error: 500 Internal Server Error Tue Oct 14 21:57:54 2014 [I]: 131.225.155.244 - - [14/Oct/2014 21:57:54] GET /? Action=DescribeInstancesSignatureMethod=HmacSHA256SignatureVersion=2Timestamp =2014-10-15T02%3A57%3A47ZVersion=2012-10-01Signature=RcT3TNg3F0Rb7F6Z5t4KVALlw o41INbdas9CVRDc0aw%3D HTTP/1.1 500 154 2.7504 That's all we get. Steve On Wed, 15 Oct 2014, Daniel Molina wrote: On 15 October 2014 18:06, Parag Mhashilkar pa...@fnal.gov wrote: We suspect the limit is somehow artificially imposed in the server. However we were not able to figure out where and how it is configurable. Any error in the econe.log|error oned.log? -- -- Daniel Molina Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula -- Steven C. Timm, Ph.D (630) 840-8525 t...@fnal.gov http://home.fnal.gov/~timm/ Fermilab Scientific Computing Division, Scientific Computing Services Quad. Grid and Cloud Services Dept., Associate Dept. Head for Cloud Computing -- -- Daniel Molina Project Engineer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula smime.p7s Description: S/MIME cryptographic signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] econe-run-instances idempotent?
Hi, We are using HTCondor to launch VMs in OpenNebula using ec2 interface and would like to know if the submit calls are idempotent. Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-3109 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== smime.p7s Description: S/MIME cryptographic signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Shutting down a VM from within the VM
Hi Sharuzzaman, Thanks for your response. I am aware of the fact that OpenNebula requires human intervention when shutdown is issued from inside the VM. We can write scripts to do lot of things, but when in the business of resource provisioning, the resource provider does not necessarily control what runs in the VM, application that launches them and for obvious reasons I am not giving any access to ONE's database to the users. So these alternatives seem merely hacks rather than a much cleaner solution from the service. Such a feature is useful from a infrastructure provider's point of view. If AWS has done it (and Openstack I think) then there be a way out. -Parag On Oct 3, 2013, at 9:27 PM, Sharuzzaman Ahmat Raslan wrote: Hi Parag, I believe OpenNebula need to have human intervention to really determine whether to remove or not the VM that it has deployed. I also think that you can write a script that signal or call OpenNebula command as soon as the task finish, to shutdown the VM. Or if direct calling command not possible, maybe your application can write some status in a database, and a script in OpenNebula read that status and make decision from it. Thanks. On Thu, Oct 3, 2013 at 11:38 PM, Parag Mhashilkar pa...@fnal.gov wrote: Hi, Does OpenNebula EC2 interface support shutting down a VM from with in the VM itself and have the scheduler recognize that VM has been stopped/shutdown? How do we enable this feature? At Fermi, we have OpenNebula v3.2 and when the VM is shutdown it stays in the UNKNOWN state. Can OpenNebula get this ACPI shutdown info from virsh and handle the situation more gracefully rather than putting the VM in UKNOWN state? Here is an example why I think something like this is useful: When VMs are launched to perform certain tasks (classical equivalent of batch nodes), only the processes running in the VM know when the task is done and can shutdown the VM freeing up the resources. Running VM past the task life is wasted resources and controlling the lifetime of VM from outside is not always possible. In case of AWS, it supports following which is very good feature to have when controlling the VMs in above scenario. ec2-run-instaces --instance-initiated-shutdown-behavior stop|terminate How do we achieve this with Opennebula? Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-2783 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Sharuzzaman Ahmat Raslan smime.p7s Description: S/MIME cryptographic signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Shutting down a VM from within the VM
Hi, Does OpenNebula EC2 interface support shutting down a VM from with in the VM itself and have the scheduler recognize that VM has been stopped/shutdown? How do we enable this feature? At Fermi, we have OpenNebula v3.2 and when the VM is shutdown it stays in the UNKNOWN state. Can OpenNebula get this ACPI shutdown info from virsh and handle the situation more gracefully rather than putting the VM in UKNOWN state? Here is an example why I think something like this is useful: When VMs are launched to perform certain tasks (classical equivalent of batch nodes), only the processes running in the VM know when the task is done and can shutdown the VM freeing up the resources. Running VM past the task life is wasted resources and controlling the lifetime of VM from outside is not always possible. In case of AWS, it supports following which is very good feature to have when controlling the VMs in above scenario. ec2-run-instaces --instance-initiated-shutdown-behavior stop|terminate How do we achieve this with Opennebula? Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-2783 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== smime.p7s Description: S/MIME cryptographic signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] EC2_USER_DATA Maximum size?
Hi Daniel Thanks for the pointers. I will look around httpd conf and see whats going on. Seems like when trying VM creation using condor, if ec2_user_data goes above ~2K someone somewhere in the chain is not too happy. Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-2783 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== On Jun 24, 2013, at 4:32 AM, Daniel Molina wrote: Hi Parag, On 22 June 2013 05:32, Parag Mhashilkar pa...@fnal.gov wrote: Hi, I been trying to find maximum allowed size for EC2_USER_DATA in open nebula v3.2 but could not find it from manuals. Any help is appreciated. In Amazon EC2 user data is limited to 16KB. In OpenNebula there is no such limit, but you can limit the size of the http request body in your server configuration (apache, ...). Note that in OpenNebula 3.2 there was a bug and the resource representation is limited to 64KB, this has been fixed in OpenNebula 3.8.4 and 4.0 Hope this helps. Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-2783 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013 -- Daniel Molina Project Engineer OpenNebula - The Open Source Solution for Data Center Virtualization www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula smime.p7s Description: S/MIME cryptographic signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] EC2_USER_DATA Maximum size?
Hi, I been trying to find maximum allowed size for EC2_USER_DATA in open nebula v3.2 but could not find it from manuals. Any help is appreciated. Thanks Regards +== | Parag Mhashilkar | Fermi National Accelerator Laboratory, MS 120 | Wilson Kirk Road, Batavia, IL - 60510 |-- | Phone: 1 (630) 840-6530 Fax: 1 (630) 840-2783 |-- | Wilson Hall, 806E (Nov 8, 2012 - To date) | Wilson Hall, 867E (Nov 17, 2010 - Nov 7, 2012) | Wilson Hall, 863E (Apr 24, 2007 - Nov 16, 2010) | Wilson Hall, 856E (Mar 21, 2005 - Apr 23, 2007) +== smime.p7s Description: S/MIME cryptographic signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
