Openstack 管理虚拟机的引导错误

我正在使用Cloudify 2.7和OpenStack Icehouse。特别是，我将云驱动程序配置为引导2个管理VM（numberOfManagementMachines 2）

有时，在引导虚拟机时，我会收到以下错误：

cloudify@default> bootstrap-cloud --verbose openstack-icehouse-<project_name>
...
Starting agent and management processes:
[VM_Floating_IP] nohup gs-agent.sh gsa.global.lus 0 gsa.lus 1 gsa.gsc 0 gsa.global.gsm 0 gsa.gsm 1 gsa.global.esm 1 >/dev/null 2>&1
[VM_Floating_IP] STARTING CLOUDIFY MANAGEMENT
[VM_Floating_IP] .
[VM_Floating_IP] Discovered agent nic-address=177.86.0.3 lookup-groups=gigaspaces-Cloudify-2.7.1-ga.
[VM_Floating_IP] Detected LUS management process started by agent null  expected agent a0eec4e5-7fb0-4428-80e1-ec13a8b1c744
[VM_Floating_IP] Detected LUS management process started by agent a0eec4e5-7fb0-4428-80e1-ec13a8b1c744
[VM_Floating_IP] Detected GSM management process started by agent a0eec4e5-7fb0-4428-80e1-ec13a8b1c744
[VM_Floating_IP] Waiting for Management processes to start.
[VM_Floating_IP] Waiting for Elastic Service Manager
[VM_Floating_IP] Waiting for Management processes to start.
[VM_Floating_IP] .
[VM_Floating_IP] Waiting for Elastic Service Manager
[VM_Floating_IP] Waiting for Management processes to start.
[VM_Floating_IP] .
[VM_Floating_IP] Waiting for Elastic Service Manager
[VM_Floating_IP] Waiting for Management processes to start.
[VM_Floating_IP] .
[VM_Floating_IP] Waiting for Elastic Service Manager
[VM_Floating_IP] Waiting for Management processes to start.
[VM_Floating_IP] .failure occurred while renewing an event lease: Operation failed. net.jini.core.lease.UnknownLeaseException: Unknown event id: 3
[VM_Floating_IP]        at com.sun.jini.reggie.GigaRegistrar.renewEventLeaseInt(GigaRegistrar.java:5494)
[VM_Floating_IP]        at com.sun.jini.reggie.GigaRegistrar.renewEventLeaseDo(GigaRegistrar.java:5475)
[VM_Floating_IP]        at com.sun.jini.reggie.GigaRegistrar.renewEventLease(GigaRegistrar.java:2836)
[VM_Floating_IP]        at com.sun.jini.reggie.RegistrarGigaspacesMethodinternalInvoke16.internalInvoke(Unknown Source)
[VM_Floating_IP]        at com.gigaspaces.internal.reflection.fast.AbstractMethod.invoke(AbstractMethod.java:41)
[VM_Floating_IP]        at com.gigaspaces.lrmi.LRMIRuntime.invoked(LRMIRuntime.java:464)
[VM_Floating_IP]        at com.gigaspaces.lrmi.nio.Pivot.consumeAndHandleRequest(Pivot.java:561)
[VM_Floating_IP]        at com.gigaspaces.lrmi.nio.Pivot.handleRequest(Pivot.java:662)
[VM_Floating_IP]        at com.gigaspaces.lrmi.nio.Pivot$ChannelEntryTask.run(Pivot.java:196)
[VM_Floating_IP]        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[VM_Floating_IP]        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[VM_Floating_IP]        at java.lang.Thread.run(Thread.java:662)
[VM_Floating_IP]
[VM_Floating_IP]
[VM_Floating_IP] Waiting for Elastic Service Manager
[VM_Floating_IP] Waiting for Management processes to start.
....
[VM_Floating_IP] ....Failed to add [Processing Unit Instance] with uid [8038e956-1ae2-4378-8bb1-e2055202c160]: Operation failed. java.rmi.ConnectException: Connect Failed to [NIO://177.86.0.3:7011/pid[4390]/164914896032_3_8060218823096628119_details[class org.openspaces.pu.container.servicegrid.PUServiceBeanImpl]]; nested exception is: 
[VM_Floating_IP]        java.net.SocketTimeoutException
...
[VM_Floating_IP] Failed to add [GSM] with uid [3c0e20e9-bf85-4d22-8ed6-3b387e690878]: Operation failed. java.rmi.ConnectException: Connect Failed to [NIO://177.86.0.3:7000/pid[4229]/154704895271_2_2245795805687723285_details[class com.gigaspaces.grid.gsm.GSMImpl]]; nested exception is:
[VM_Floating_IP]        java.net.SocketTimeoutException
...
[VM_Floating_IP] Failed to add GSC with uid [8070dabb-d80d-43c7-bd9c-1d2478f95710]: Operation failed. java.rmi.ConnectException: Connect Failed to [NIO://177.86.0.3:7011/pid[4390]/164914896020_2_8060218823096628119_details[class com.gigaspaces.grid.gsc.GSCImpl]]; nested exception is:
[VM_Floating_IP]        java.net.SocketTimeoutException
...
[VM_Floating_IP] Failed to add [GSA] with uid [a0eec4e5-7fb0-4428-80e1-ec13a8b1c744]: Operation failed. java.rmi.ConnectException: Connect Failed to [NIO://177.86.0.3:7002/pid[4086]/153569177936_2_8701370873164361474_details[class com.gigaspaces.grid.gsa.GSAImpl]]; nested exception is:
[VM_Floating_IP]        java.net.SocketTimeoutException
...
[VM_Floating_IP] Waiting for Management processes to start.
[VM_Floating_IP] Failed to connect to LUS on 177.86.0.3:4174, retry in 73096ms: Operation failed. java.net.ConnectException: Connection timed out
...
[VM_Floating_IP] .Failed to add [ESM] with uid [996c8898-897c-4416-a877-82efb22c7ea6]: Operation failed. java.rmi.ConnectException: Connect Failed to [NIO://177.86.0.3:7003/pid[4504]/172954418920_2_5475350805758957057_details[class org.openspaces.grid.esm.ESMImpl]]; nested exception is:
[VM_Floating_IP]        java.net.SocketTimeoutException

---

此外，Cloudify创建了一个专用网络“Cloudify manager Cloudify管理网络”，其子网为177.86.0.0/24，并为每个虚拟机请求一个浮动IP。

ESM是Cloudify的协调器。一次只能运行一个实例。错误表明boostrap进程希望找到一个正在运行的ESM，但没有找到。这似乎与管理器实例之间的通信错误有关-是否可能为管理器定义的安全组未打开管理器之间的所有端口

安全组/防火墙配置是常见问题。manager虚拟机也可能太小-它应该至少有4 GB Ram和2个VCPU

---

请记住，Cloudify 2.X已经到了生命的尽头，不再受支持。您可能想查看Cloudify 3。

我在上一个问题中添加了一些信息。我认为这不是安全组/风格问题。请尝试通过添加安全组规则来修改manager安全组，以打开manager安全组入口的所有端口。有没有可能在manager机器上有像iptables一样的防火墙？我使用的是Ubuntu服务器12.04和14.04映像，里面没有防火墙。如何修改Cloudify创建的安全组？我的意思是，安全组是由Cloudify创建的。因此，我想我应该编辑一个配置文件。您可以从云控制台（horizon）编辑安全组

cloudify-manager-cluster    

Egress  IPv4    Any -       0.0.0.0/0 (CIDR)    
Egress  IPv6    Any -       ::/0 (CIDR)

cloudify-manager-management

Egress  IPv4    Any -       0.0.0.0/0 (CIDR)    
Egress  IPv6    Any -       ::/0 (CIDR) 
Ingress IPv4    TCP 22      0.0.0.0/0 (CIDR)    
Ingress IPv4    TCP 4174    cfy-mngt-cluster    
Ingress IPv4    TCP 6666    cfy-mngt-cluster    
Ingress IPv4    TCP 7000    cfy-mngt-cluster    
Ingress IPv4    TCP 7001    cfy-mngt-cluster    
Ingress IPv4    TCP 7002    cfy-mngt-cluster    
Ingress IPv4    TCP 7003    cfy-mngt-cluster    
Ingress IPv4    TCP 7010 - 7110 cfy-mngt-cluster    
Ingress IPv4    TCP 8099    0.0.0.0/0 (CIDR)    
Ingress IPv4    TCP 8100    0.0.0.0/0 (CIDR)