Dear Riccardo, (Ana Jokanović, Sun, Jan 15, 2017 at 03:04:19PM -0800:) > > Still, I am getting the same problem. I attached the fronted log. It > seems > > there is a problem with cloud-init. > > [...] > > 2017-01-15 21:51:03,234 - url_helper.py[WARNING]: Calling ' > http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: > request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max > retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by > <class 'socket.error'>: [Errno 111] Connection refused)] > > 2017-01-15 21:53:03,982 - DataSourceEc2.py[CRITICAL]: Giving up on md > from ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after > 120 seconds > > 2017-01-15 21:53:04,020 - url_helper.py[WARNING]: Calling ' > http://172.16.100.3//latest/meta-data/instance-id' failed [0/120s]: > request error [HTTPConnectionPool(host='172.16.100.3', port=80): Max > retries exceeded with url: //latest/meta-data/instance-id (Caused by <class > 'socket.error'>: [Errno 111] Connection refused)] > > 2017-01-15 21:54:57,055 - url_helper.py[WARNING]: Calling ' > http://172.16.100.3//latest/meta-data/instance-id' failed [113/120s]: > request error [HTTPConnectionPool(host='172.16.100.3', port=80): Max > retries exceeded with url: //latest/meta-data/instance-id (Caused by <class > 'socket.error'>: [Errno 111] Connection refused)] > > 2017-01-15 21:55:04,070 - DataSourceCloudStack.py[CRITICAL]: Giving up > on waiting for the metadata from [' > http://172.16.100.3//latest/meta-data/instance-id'] after 120 seconds > > Cloud-init v. 0.7.5 finished at Sun, 15 Jan 2017 21:57:20 +0000. > Datasource DataSourceNone. Up 574.35 seconds > > 2017-01-15 21:57:20,910 - cc_final_message.py[WARNING]: Used fallback > datasource > > Indeed, it looks like the VM image you're using is not properly > configured to run in OpenStack: it's using `DataSourceEc2` and > `DataSourceCloudStack` and then fall back on `DataSourceNone`. > It should try `DataSourceOpenStack` at some point for the customization > to happen successfully. (Or your OpenStack installation should have the > EC2 compatibility layer installed; you should see the `ec2-api-metadata` > service running and listening to port 8788 or 8789 if it does.) > > Are you able to (1) start a VM with the same keypair and VM image used by > ElastiCluster and (2) ssh into it from the command-line? >
I have tried what you suggested and I do see the same problem. I will dig into it to try to found the cause. For the time being, the problem does not seem to be on the ElastiCluster side. BTW, I have some questions about interaction between ElastiCluster and SLURM. I understand that ElastiCluster installs SLURM on the newly created cluster. Is SLURM source code within ElastiCluster source code? Where can I find it? May I substitute it with another (modified) version of SLURM? Also, can I edit slurm.conf and where can I find it? Which part of the ElastiCluster is responsible for resizing of the cluster? In SLURM's documentation I have found out about the Elastic computing and possibility to resize the cluster through setting ResumeProgram an SuspendProgram in slum.conf (https://slurm.schedmd.com/elastic_computing.html). Is this how ElastiCluster interact with SLURM, as well? Thank you. Best regards, Ana > Ciao, > R > > -- > Riccardo Murri, Schwerzenbacherstrasse 2, CH-8606 Nänikon, Switzerland > -- You received this message because you are subscribed to the Google Groups "elasticluster" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
