cloudstack-users-cn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sunko2014 <sunko2...@gmail.com>
Subject help,高级部署,创建VM失败:Cleaning up because we're unable to implement the network Ntwk[207|Guest|8]
Date Thu, 01 Aug 2013 07:02:02 GMT
hello:
         了解CloudStack的网络方案后,尝试高级部署CloudStack,我的部署方案是:

 1、管理和存储走一个交换机网络(172.16.100.x),Public和Guest走一个交换机网络,Pulic是公司内网(192.168.45.x),guest是自定义网络(10.1.1.x)
           2、1台主机跑Manage
Server,网卡接管理存储网络,1台主机跑XENServer,2张网卡,1张接管理存储网络,1张接Public&Guest网络,1台主机跑NFS(提供Secondary
Storage),接网络存储网络
           添加zone后,host、主存储、辅存储,SSVM和CPVM都正常启动,但是router
vm没有启动。
           通过ISO创建VM时,提示创建失败,查了下log,应该是网络出了问题,log如下,请各位提供点意见,谢谢。
... ...
2013-08-01 14:29:59,780 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-2:job-36) VM is being created in podId: 1
2013-08-01 14:29:59,792 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) Lock is acquired for network id 207 as a part of
network implement
2013-08-01 14:29:59,792 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) Asking ExternalGuestNetworkGuru to implement
Ntwk[207|Guest|8]
2013-08-01 14:29:59,915 DEBUG [db.Transaction.Transaction]
(Job-Executor-2:job-36) Rolling back the transaction: Time = 3 Name =
 -AsyncJobManagerImpl$1.run:398-Exec
utors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679;
ca
lled by
-Transaction.rollback:887-Transaction.removeUpTo:830-Transaction.close:649-DatabaseCallback.interceptComplete:71-DatabaseCallback.intercept:36-DataCenterDaoI
mpl.allocateVnet:190-DatabaseCallback.intercept:34-GuestNetworkGuru.allocateVnet:310-GuestNetworkGuru.implement:337-ExternalGuestNetworkGuru.implement:126-NetworkMan
agerImpl.implementNetwork:1956-DatabaseCallback.intercept:34
2013-08-01 14:29:59,929 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) Cleaning up because we're unable to implement the
network Ntwk[207|Guest|8]
2013-08-01 14:30:00,055 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) Releasing 0 port forwarding rules for network
id=207 as a part of shutdownNe
tworkRules
2013-08-01 14:30:00,055 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) There are no rules to forward to the network
elements
2013-08-01 14:30:00,068 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) Releasing 0 static nat rules for network id=207 as
a part of shutdownNetwork
Rules
2013-08-01 14:30:00,068 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) There are no rules to forward to the network
elements
2013-08-01 14:30:00,093 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) There are no rules to forward to the network
elements
2013-08-01 14:30:00,096 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) Releasing 0 firewall rules for network id=207 as a
part of shutdownNetworkRu
les
2013-08-01 14:30:00,096 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) There are no rules to forward to the network
elements
2013-08-01 14:30:00,099 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) Releasing 0 Network ACLs for network id=207 as a
part of shutdownNetworkRule
s
2013-08-01 14:30:00,099 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) There are no rules to forward to the network
elements
2013-08-01 14:30:00,102 DEBUG [network.rules.RulesManagerImpl]
(Job-Executor-2:job-36) Found 0 static nat rules to apply for network id 207
2013-08-01 14:30:00,126 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) Sending network shutdown to VirtualRouter
2013-08-01 14:30:00,130 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) Network id=207 is shutdown successfully, cleaning
up corresponding resources
 now.
2013-08-01 14:30:00,135 DEBUG [network.guru.GuestNetworkGuru]
(Job-Executor-2:job-36) Releasing vnet for the network id=207
2013-08-01 14:30:00,218 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-2:job-36) Lock is released for network id 207 as a part of
network implement
2013-08-01 14:30:00,219 INFO  [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-2:job-36) Insufficient capacity
com.cloud.exception.InsufficientVirtualNetworkCapcityException: Unable to
allocate vnet as a part of network Ntwk[207|Guest|8] implement
Scope=interface com.cloud.dc
.DataCenter; id=1
        at
com.cloud.network.guru.GuestNetworkGuru.allocateVnet(GuestNetworkGuru.java:312)
        at
com.cloud.network.guru.GuestNetworkGuru.implement(GuestNetworkGuru.java:337)
        at
com.cloud.network.guru.ExternalGuestNetworkGuru.implement(ExternalGuestNetworkGuru.java:126)
        at
com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1956)
        at
com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
        at
com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2110)
        at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:752)
        at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:472)
        at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2929)
        at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2601)
        at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2589)

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message