Hi Pablo, > I have tested elasticluster with SWITCHengines (openstack) and I hit a > problem when booting my first test cluster. The nodes are started but I get > this error when elasticluster checks the ssh connection to nodes: > https://gist.github.com/pescobar/f75b561f5775f20d60139bca9cbc4a47 > [...] > My guess is that elasticluster is not parsing correctly the public ip. is > it possible? Did anyone hit this issue?
I think that your guess is right - This looks certainly a bug in ElastiCluster, in that it mistakes an IPv6 address for IPv4+port ... can you please open an issue on the GitHub repo? That said, I have never tested ElastiCluster with IPv6 (no IPv6 here, alas) so other problems might pop up later on, e.g. in playbooks. > I have another doubt somehow related to this. I have seen that the default > option in the cloud section is "request_floating_ip=False" but using the > defaults I would not be able to connect to the booted machines. Is this > done on purpose so it's mandatory to change this config? No, it's just that it's the "right" setting to use here at UZH :-) so I keep it in order to minimize the local support requests. (I'm assumning we are still the largest users of ElastiCluster.) Maybe you should turn it on for SWITCHengines, if that means you get a public IPv4 address. > Is it possible to configure elasticluster so only the login node > has a floating ip and the compute nodes only private ips? This is not supported at the moment. I would like to support it eventually, but I have not given any real thought to this, and it may require extensive changes to the configuration file format and to the cloud providers. Any suggestion is very welcome, anyway! 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.
