You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users-cn@cloudstack.apache.org by 李红岩 <ho...@neusoft.com> on 2014/07/18 02:59:15 UTC
求助：cloudstack与外部设备集成
各位好，
哪位大神有cloudstack与外部设备（F5、juniper等）集成的经验，请帮助我一下，十分感谢。
李红岩
网络安全事业部
东软集团股份有限公司
沈阳市浑南新区新秀街2号 东软软件园 A2楼 417室
Postcode: 110179
Tel: 024-836 60118
E-mail: hongyan-li@neusoft.com
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)
is intended only for the use of the intended recipient and may be confidential and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is
not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this communication in error,please
immediately notify the sender by return e-mail, and delete the original message and all copies from
your system. Thank you.
---------------------------------------------------------------------------------------------------
Re: Re:求助：cloudstack与外部设备集成
Posted by 李红岩 <ho...@neusoft.com>.
我现在就打算研究一下cloudstack与外部设备的集成，但是没有经验，环境还没搭建起来，遇到了一下问题，能帮忙解决一下吗？
hongyan-li
发件人： HellCat
发送时间： 2014-07-18 09:14
收件人： users-cn
主题： Re:求助：cloudstack与外部设备集成
目前的VR估计扛不住业务的流量，也考虑搞台SRX。目前打算向供应商咨询下，你也可以试试
------------------ Original ------------------
From: "李红岩";<ho...@neusoft.com>;
Date: Fri, Jul 18, 2014 08:59 AM
To: "cloudstack"<us...@cloudstack.apache.org>;
Subject: 求助：cloudstack与外部设备集成
各位好，
哪位大神有cloudstack与外部设备（F5、juniper等）集成的经验，请帮助我一下，十分感谢。
李红岩
网络安全事业部
东软集团股份有限公司
沈阳市浑南新区新秀街2号 东软软件园 A2楼 417室
Postcode: 110179
Tel: 024-836 60118
E-mail: hongyan-li@neusoft.com
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)
is intended only for the use of the intended recipient and may be confidential and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is
not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this communication in error,please
immediately notify the sender by return e-mail, and delete the original message and all copies from
your system. Thank you.
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)
is intended only for the use of the intended recipient and may be confidential and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is
not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this communication in error,please
immediately notify the sender by return e-mail, and delete the original message and all copies from
your system. Thank you.
---------------------------------------------------------------------------------------------------
Re: Re:求助：cloudstack与外部设备集成
Posted by 李红岩 <ho...@neusoft.com>.
谢谢。
由于没有物理设备，是采用F5的试用版在虚拟机安装代替的，你们Juniper的设备是物理的还是虚拟的？
以下是与F5集成的步骤，请帮忙看看哪里有问题，具体如下：
1.在服务方案中新建一个名称为“f5”的网络方案，提供的服务功能只有f5bigip。
2.添加设备，这步中对公用接口与专用接口不是很理解。
3.在网络中添加网络。
a.添加来宾网络，添加ip地址一直有问题，不知道如何填写。
b.添加隔离网络的时没有f5的网络方案可以选择。
这个方案添加成功后，修改这种方案，可以把网络方案修改为f5，但是新建实例提示错误。
2014-07-17 13:48:32,801 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Asking F5BigIP to implemenet Ntwk[233|Guest|18]
2014-07-17 13:48:32,817 DEBUG [c.c.u.d.T.Transaction] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Rolling back the transaction: Time = 3 Name = Job-Executor-3; called by -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-ExternalLoadBalancerDeviceManagerImpl.allocateLoadBalancerForNetwork:426-ExternalLoadBalancerDeviceManagerImpl.manageGuestNetworkWithExternalLoadBalancer:969-F5ExternalLoadBalancerElement.implement:157-NetworkOrchestrator.implementNetworkElementsAndResources:1070-NetworkOrchestrator.implementNetwork:977-NetworkOrchestrator.prepare:1238-VirtualMachineManagerImpl.orchestrateStart:960-VirtualMachineManagerImpl.advanceStart:761
2014-07-17 13:48:32,824 DEBUG [c.c.u.d.T.Transaction] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Rolling back the transaction: Time = 3 Name = Job-Executor-3; called by -TransactionLegacy.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-ExternalLoadBalancerDeviceManagerImpl.allocateLoadBalancerForNetwork:426-ExternalLoadBalancerDeviceManagerImpl.manageGuestNetworkWithExternalLoadBalancer:969-F5ExternalLoadBalancerElement.implement:157-NetworkOrchestrator.implementNetworkElementsAndResources:1070-NetworkOrchestrator.implementNetwork:977-NetworkOrchestrator.prepare:1238-VirtualMachineManagerImpl.orchestrateStart:960-VirtualMachineManagerImpl.advanceStart:761
2014-07-17 13:48:32,825 WARN [c.c.n.ExternalLoadBalancerDeviceManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) There are no load balancer device with the capacity for implementing this network
2014-07-17 13:48:32,826 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Cleaning up because we're unable to implement the network Ntwk[233|Guest|18]
2014-07-17 13:48:32,845 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Lock is acquired for network Ntwk[233|Guest|18] as a part of network shutdown
2014-07-17 13:48:32,853 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Releasing 0 port forwarding rules for network id=233 as a part of shutdownNetworkRules
2014-07-17 13:48:32,853 DEBUG [c.c.n.f.FirewallManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) There are no rules to forward to the network elements
2014-07-17 13:48:32,855 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Releasing 0 static nat rules for network id=233 as a part of shutdownNetworkRules
2014-07-17 13:48:32,855 DEBUG [c.c.n.f.FirewallManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) There are no rules to forward to the network elements
2014-07-17 13:48:32,858 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Revoking 0 Public load balancing rules for network id=233
2014-07-17 13:48:32,858 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) There are no Load Balancing Rules to forward to the network elements
2014-07-17 13:48:32,860 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Revoking 0 Internal load balancing rules for network id=233
2014-07-17 13:48:32,860 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) There are no Load Balancing Rules to forward to the network elements
2014-07-17 13:48:32,862 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Releasing 0 firewall ingress rules for network id=233 as a part of shutdownNetworkRules
2014-07-17 13:48:32,862 DEBUG [c.c.n.f.FirewallManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) There are no rules to forward to the network elements
2014-07-17 13:48:32,864 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Releasing 0 firewall egress rules for network id=233 as a part of shutdownNetworkRules
2014-07-17 13:48:32,866 DEBUG [c.c.n.f.FirewallManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) There are no rules to forward to the network elements
2014-07-17 13:48:32,868 DEBUG [c.c.n.r.RulesManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Found 0 static nat rules to apply for network id 233
2014-07-17 13:48:32,881 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Sending network shutdown to F5BigIP
2014-07-17 13:48:32,887 WARN [c.c.n.ExternalLoadBalancerDeviceManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Network shutdwon requested on external load balancer element, which did not implement the network. Either network implement failed half way through or already network shutdown is completed. So just returning.
2014-07-17 13:48:32,888 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Network id=233 is shutdown successfully, cleaning up corresponding resources now.
2014-07-17 13:48:32,892 DEBUG [c.c.n.g.GuestNetworkGuru] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Releasing vnet for the network id=233
2014-07-17 13:48:32,903 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Lock is released for network Ntwk[233|Guest|18] as a part of network shutdown
2014-07-17 13:48:32,904 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Lock is released for network id 233 as a part of network implement
2014-07-17 13:48:32,904 INFO [c.c.v.VirtualMachineManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Unable to contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:2] is unreachable: There are no F5 load balancer devices with the free capacity for implementing this network
at com.cloud.network.element.F5ExternalLoadBalancerElement.implement(F5ExternalLoadBalancerElement.java:159)
at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetworkElementsAndResources(NetworkOrchestrator.java:1070)
at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:977)
at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1238)
at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:960)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:601)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:228)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3161)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3147)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy169.startVirtualMachine(Unknown Source)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:509)
at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-07-17 13:48:32,909 DEBUG [c.c.v.VirtualMachineManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Cleaning up resources for the vm VM[User|VM-dea831d5-8900-4fa6-9d5d-76c34200e419] in Starting state
2014-07-17 13:48:32,913 DEBUG [c.c.a.t.Request] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Seq 18-1673658389: Sending { Cmd , MgmtId: 52242177443, via: 18(xenserver2.cloud.pri), Ver: v1, Flags: 100011, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-2-218-VM","wait":0}}] }
2014-07-17 13:48:32,914 DEBUG [c.c.a.t.Request] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Seq 18-1673658389: Executing: { Cmd , MgmtId: 52242177443, via: 18(xenserver2.cloud.pri), Ver: v1, Flags: 100011, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-2-218-VM","wait":0}}] }
2014-07-17 13:48:32,915 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-34:ctx-ae7f3a01) Seq 18-1673658389: Executing request
2014-07-17 13:48:33,013 INFO [c.c.h.x.r.CitrixResourceBase] (DirectAgent-34:ctx-ae7f3a01) VM does not exist on XenServer9259e211-5010-41b0-b8c9-d4c7467eb655
2014-07-17 13:48:33,014 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-34:ctx-ae7f3a01) Seq 18-1673658389: Response Received:
2014-07-17 13:48:33,014 DEBUG [c.c.a.t.Request] (DirectAgent-34:ctx-ae7f3a01) Seq 18-1673658389: Processing: { Ans: , MgmtId: 52242177443, via: 18, Ver: v1, Flags: 10, [{"com.cloud.agent.api.StopAnswer":{"result":true,"details":"VM does not exist","wait":0}}] }
2014-07-17 13:48:33,015 DEBUG [c.c.a.t.Request] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Seq 18-1673658389: Received: { Ans: , MgmtId: 52242177443, via: 18, Ver: v1, Flags: 10, { StopAnswer } }
2014-07-17 13:48:33,027 DEBUG [c.c.v.VirtualMachineManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Successfully released network resources for the vm VM[User|VM-dea831d5-8900-4fa6-9d5d-76c34200e419]
2014-07-17 13:48:33,027 DEBUG [c.c.v.VirtualMachineManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Successfully cleanued up resources for the vm VM[User|VM-dea831d5-8900-4fa6-9d5d-76c34200e419] in Starting state
2014-07-17 13:48:33,045 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Deploy avoids pods: [], clusters: [], hosts: [18]
2014-07-17 13:48:33,045 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) DataCenter id = '2' provided is in avoid set, DeploymentPlanner cannot allocate the VM, returning.
2014-07-17 13:48:33,061 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: null new host id: null host id before state transition: 18
2014-07-17 13:48:33,073 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Hosts's actual total CPU: 19144 and CPU after applying overprovisioning: 19144
2014-07-17 13:48:33,073 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Hosts's actual total RAM: 7216566336 and RAM after applying overprovisioning: 7216566272
2014-07-17 13:48:33,074 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) release cpu from host: 18, old used: 2500,reserved: 0, actual total: 19144, total with overprovisioning: 19144; new used: 1500,reserved:0; movedfromreserved: false,moveToReserveredfalse
2014-07-17 13:48:33,074 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) release mem from host: 18, old used: 2818572288,reserved: 0, total: 7216566272; new used: 1744830464,reserved:0; movedfromreserved: false,moveToReserveredfalse
2014-07-17 13:48:33,096 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) VM state transitted from :Stopped to Starting with event: StartRequestedvm's original host id: null new host id: null host id before state transition: null
2014-07-17 13:48:33,096 DEBUG [c.c.v.VirtualMachineManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Successfully transitioned to start state for VM[User|VM-dea831d5-8900-4fa6-9d5d-76c34200e419] reservation id = 07c4c4fc-3946-44c7-8f1a-4e76e1bfc41b
2014-07-17 13:48:33,099 DEBUG [c.c.v.VirtualMachineManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Trying to deploy VM, vm has dcId: 2 and podId: 2
2014-07-17 13:48:33,099 DEBUG [c.c.v.VirtualMachineManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Deploy avoids pods: [], clusters: [], hosts: [18]
2014-07-17 13:48:33,119 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Deploy avoids pods: [], clusters: [], hosts: [18]
2014-07-17 13:48:33,119 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) DataCenter id = '2' provided is in avoid set, DeploymentPlanner cannot allocate the VM, returning.
2014-07-17 13:48:33,134 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: null new host id: null host id before state transition: null
2014-07-17 13:48:33,148 DEBUG [c.c.v.UserVmManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) Destroying vm VM[User|VM-dea831d5-8900-4fa6-9d5d-76c34200e419] as it failed to create on Host with Id:null
2014-07-17 13:48:33,164 DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) VM state transitted from :Stopped to Error with event: OperationFailedToErrorvm's original host id: null new host id: null host id before state transition: null
2014-07-17 13:48:33,178 WARN [o.a.c.alerts] (Job-Executor-3:ctx-2bb706f5 ctx-d30ad2e8) alertType:: 8 // dataCenterId:: 2 // podId:: 2 // clusterId:: null // message:: Failed to deploy Vm with Id: 218, on Host with Id: null
2014-07-17 13:48:33,220 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-3:ctx-2bb706f5) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to insufficient capacity
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:605)
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3161)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3147)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy169.startVirtualMachine(Unknown Source)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:509)
at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|VM-dea831d5-8900-4fa6-9d5d-76c34200e419]Scope=interface com.cloud.dc.DataCenter; id=2
at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:921)
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:601)
... 38 more
2014-07-17 13:48:33,224 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-3:ctx-2bb706f5) Complete async job-521, jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Unable to start a VM due to insufficient capacity"}
2014-07-17 13:48:33,233 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-3:ctx-2bb706f5) Done executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd for job-521
2014-07-17 13:48:33,240 INFO [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-3:ctx-2bb706f5) Remove job-521 from job monitoring
2014-07-17 13:48:35,395 DEBUG [c.c.a.ApiServlet] (catalina-exec-16:ctx-da2a98b4) ===START=== 10.3.5.100 -- GET command=queryAsyncJobResult&jobId=1fdac045-9a97-4ddb-b0fa-f35856e4de45&response=json&sessionkey=kkrpuv17dJaSZoi86D1Ygsat17g%3D&_=1405580438994
2014-07-17 13:48:35,424 DEBUG [c.c.a.ApiServlet] (catalina-exec-16:ctx-da2a98b4 ctx-1481a230) ===END=== 10.3.5.100 -- GET command=queryAsyncJobResult&jobId=1fdac045-9a97-4ddb-b0fa-f35856e4de45&response=json&sessionkey=kkrpuv17dJaSZoi86D1Ygsat17g%3D&_=1405580438994
2014-07-17 13:48:35,441 DEBUG [c.c.a.ApiServlet] (catalina-exec-13:ctx-54f77668) ===START=== 10.3.5.100 -- GET command=listVirtualMachines&id=dea831d5-8900-4fa6-9d5d-76c34200e419&response=json&sessionkey=kkrpuv17dJaSZoi86D1Ygsat17g%3D&_=1405580439035
2014-07-17 13:48:35,477 DEBUG [c.c.a.ApiServlet] (catalina-exec-13:ctx-54f77668 ctx-581ba127) ===END=== 10.3.5.100 -- GET command=listVirtualMachines&id=dea831d5-8900-4fa6-9d5d-76c34200e419&response=json&sessionkey=kkrpuv17dJaSZoi86D1Ygsat17g%3D&_=1405580439035
发件人： Liu Fred
发送时间： 2014-07-18 09:20
收件人： hongyan-li@neusoft.com
抄送： users-cn@cloudstack.apache.org
主题： Re:求助：cloudstack与外部设备集成
Neusoft看着好亲切，呵呵
我们做过和Juniper的集成， 有什么问题可以联系。 下次说不定我们可以再请Juniper
和F5的人进社区分享一下
在 14-7-18 上午9:14， "HellCat" <qs...@qq.com> 写入:
>目前的VR估计扛不住业务的流量，也考虑搞台SRX。目前打算向供应商咨询下，你也可以试试
>
>
>
>
>------------------ Original ------------------
>From: "李红岩";<ho...@neusoft.com>;
>Date: Fri, Jul 18, 2014 08:59 AM
>To: "cloudstack"<us...@cloudstack.apache.org>;
>
>Subject: 求助：cloudstack与外部设备集成
>
>
>
>各位好，
>哪位大神有cloudstack与外部设备（F5、juniper等）集成的经验，请帮助我一下，十分感谢。
>
>
>
>
>
>李红岩
>网络安全事业部
>东软集团股份有限公司
>沈阳市浑南新区新秀街2号 东软软件园 A2楼 417室
>Postcode: 110179
>Tel: 024-836 60118
>E-mail: hongyan-li@neusoft.com
>--------------------------------------------------------------------------
>-------------------------
>Confidentiality Notice: The information contained in this e-mail and any
>accompanying attachment(s)
>is intended only for the use of the intended recipient and may be
>confidential and/or privileged of
>Neusoft Corporation, its subsidiaries and/or its affiliates. If any
>reader of this communication is
>not the intended recipient, unauthorized use, forwarding, printing,
>storing, disclosure or copying
>is strictly prohibited, and may be unlawful.If you have received this
>communication in error,please
>immediately notify the sender by return e-mail, and delete the original
>message and all copies from
>your system. Thank you.
>--------------------------------------------------------------------------
>-------------------------
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)
is intended only for the use of the intended recipient and may be confidential and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is
not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this communication in error,please
immediately notify the sender by return e-mail, and delete the original message and all copies from
your system. Thank you.
---------------------------------------------------------------------------------------------------
Re: 求助：cloudstack与外部设备集成
Posted by Liu Fred <fr...@tcloudcomputing.com>.
Neusoft看着好亲切，呵呵
我们做过和Juniper的集成， 有什么问题可以联系。 下次说不定我们可以再请Juniper
和F5的人进社区分享一下
在 14-7-18 上午9:14， "HellCat" <qs...@qq.com> 写入:
>目前的VR估计扛不住业务的流量，也考虑搞台SRX。目前打算向供应商咨询下，你也可以试试
>
>
>
>
>------------------ Original ------------------
>From: "李红岩";<ho...@neusoft.com>;
>Date: Fri, Jul 18, 2014 08:59 AM
>To: "cloudstack"<us...@cloudstack.apache.org>;
>
>Subject: 求助：cloudstack与外部设备集成
>
>
>
>各位好，
>哪位大神有cloudstack与外部设备（F5、juniper等）集成的经验，请帮助我一下，十分感谢。
>
>
>
>
>
>李红岩
>网络安全事业部
>东软集团股份有限公司
>沈阳市浑南新区新秀街2号 东软软件园 A2楼 417室
>Postcode: 110179
>Tel: 024-836 60118
>E-mail: hongyan-li@neusoft.com
>--------------------------------------------------------------------------
>-------------------------
>Confidentiality Notice: The information contained in this e-mail and any
>accompanying attachment(s)
>is intended only for the use of the intended recipient and may be
>confidential and/or privileged of
>Neusoft Corporation, its subsidiaries and/or its affiliates. If any
>reader of this communication is
>not the intended recipient, unauthorized use, forwarding, printing,
>storing, disclosure or copying
>is strictly prohibited, and may be unlawful.If you have received this
>communication in error,please
>immediately notify the sender by return e-mail, and delete the original
>message and all copies from
>your system. Thank you.
>--------------------------------------------------------------------------
>-------------------------
Re:求助：cloudstack与外部设备集成
Posted by HellCat <qs...@qq.com>.
目前的VR估计扛不住业务的流量，也考虑搞台SRX。目前打算向供应商咨询下，你也可以试试
------------------ Original ------------------
From: "李红岩";<ho...@neusoft.com>;
Date: Fri, Jul 18, 2014 08:59 AM
To: "cloudstack"<us...@cloudstack.apache.org>;
Subject: 求助：cloudstack与外部设备集成
各位好，
哪位大神有cloudstack与外部设备（F5、juniper等）集成的经验，请帮助我一下，十分感谢。
李红岩
网络安全事业部
东软集团股份有限公司
沈阳市浑南新区新秀街2号 东软软件园 A2楼 417室
Postcode: 110179
Tel: 024-836 60118
E-mail: hongyan-li@neusoft.com
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)
is intended only for the use of the intended recipient and may be confidential and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is
not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this communication in error,please
immediately notify the sender by return e-mail, and delete the original message and all copies from
your system. Thank you.
---------------------------------------------------------------------------------------------------