Hi All,
I have BIG-IP F5 VE (virtual edition), was able to added it to Cloudstack,
created network offering using F5 LB, after that i had bunch of problems, that
i can't resolve.
1) I created not dedicated LB, can't create instance, logs shows:
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] 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:135)
at
com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:1769)
at
com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1722)
at
com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:30)
at
com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:1842)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:741)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:461)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2580)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2517)
at
com.cloud.event.ActionEventCallback.intercept(ActionEventCallback.java:32)
at com.cloud.api.commands.DeployVMCmd.execute(DeployVMCmd.java:317)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:132)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:427)
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)
but i don't have any networks there yet, default capacity is 50. Why it
happened
2) I created dedicated LB, trying to create VM instance, failed, log shows the
following:
2012-05-25 12:43:01,530 ERROR [network.resource.F5BigIpResource]
(DirectAgent-39:null) Exception caught in Networking::urn:iCont
rol:Networking/VLAN::create()
Exception: Common::OperationFailed
primary_error_code : 16908390 (0x01020066)
secondary_error_code : 0
error_string : 01020066:3: The requested VLAN (/Common/vlan-608)
already exists in partition Common.
2012-05-25 12:43:01,530 ERROR [network.resource.F5BigIpResource]
(DirectAgent-39:null) Failed to execute IPAssocCommand due to c
om.cloud.utils.exception.ExecutionException: Exception caught in
Networking::urn:iControl:Networking/VLAN::create()
Exception: Common::OperationFailed
primary_error_code : 16908390 (0x01020066)
secondary_error_code : 0
error_string : 01020066:3: The requested VLAN (/Common/vlan-608)
already exists in partition Common.
2012-05-25 12:43:01,615 ERROR [network.resource.F5BigIpResource]
(DirectAgent-39:null) Retrying IpAssocCommand. Number of retrie
s remaining: 0
2012-05-25 12:43:01,819 DEBUG [network.resource.F5BigIpResource]
(DirectAgent-39:null) Creating a guest VLAN with tag 608
2012-05-25 12:43:01,847 ERROR [network.resource.F5BigIpResource]
(DirectAgent-39:null) Exception caught in Networking::urn:iCont
rol:Networking/VLAN::create()
Exception: Common::OperationFailed
primary_error_code : 16908390 (0x01020066)
secondary_error_code : 0
error_string : 01020066:3: The requested VLAN (/Common/vlan-608)
already exists in partition Common.
2012-05-25 12:43:01,847 ERROR [network.resource.F5BigIpResource]
(DirectAgent-39:null) Failed to execute IPAssocCommand due to c
om.cloud.utils.exception.ExecutionException: Exception caught in
Networking::urn:iControl:Networking/VLAN::create()
Exception: Common::OperationFailed
primary_error_code : 16908390 (0x01020066)
secondary_error_code : 0
error_string : 01020066:3: The requested VLAN (/Common/vlan-608)
already exists in partition Common.
seems like CS is trying to create it twice and failed. Actual vlan was created
on the LB, but no IP assigned.
3) Now i'm trying to clean-up CS, removing all F5 LBs, failed again, CS is
saying that there are network which still uses that loadbalancer.
Is F5 support phased out ? If not what is the support status for it ? Will you
continue to support it ? Built in loadbalancer (haproxy-based) is good but it's
acting as reverse-proxy, so it's well suitable for http/https traffic (not sure
if it's gonna work for https offload). Hacking CS internals (modifying system
VMs) - yes it's possible, but it's not good idea for product of such level
because side effects are not predictable. Please need your help.
Dan/borei.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
