Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Murali.Reddy@citrix.com
 designates 203.166.19.134 as permitted sender)
From: Murali Reddy <Murali.Reddy@citrix.com>
To: "cloudstack-users@incubator.apache.org"
	<cloudstack-users@incubator.apache.org>
Date: Mon, 28 May 2012 17:12:57 +0530
Subject: Re: CloudStack and F5 loadbalancer
Thread-Topic: CloudStack and F5 loadbalancer
Thread-Index: Ac08xrSNFL2wXhkcS5ijG7LAU0JzuQ==
Message-ID: <CBE94908.11A07%murali.reddy@citrix.com>
In-Reply-To: <20120525222535.1101184smyhcikpw@webmail.soleks.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.2.120421
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On 26/05/12 10:55 AM, "dan@soleks.com" <dan@soleks.com> wrote:

>
>
>Hi All,=20
>
>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=20
>com.cloud.network.element.F5ExternalLoadBalancerElement.implement(F5Extern
>alLoadBalancerElement.java:135)
>       at=20
>com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(
>NetworkManagerImpl.java:1769)
>       at=20
>com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.j
>ava:1722)
>       at=20
>com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:30)
>       at=20
>com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:1842)
>       at=20
>com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerI
>mpl.java:741)
>       at=20
>com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.jav
>a:461)
>       at=20
>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:
>2580)
>       at=20
>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:
>2517)
>       at=20
>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=20
>com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:427)
>       at=20
>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>       at=20
>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>       at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>       at=20
>java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
>1110)
>       at=20
>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=20

There might be a mismatch between resource guaranteed (to provide a
dedicated or shared load balancer) by a network offering and what load
balancer resources are provisioned in to the deployment. Please refer to
[1], section titled 'device allocation logic' might help to understand
whats going wrong.

>
>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.

Looks like F5 is not programmed completeley with guest vlan and guest
networks subnet IP. After Vlan is configured was there any error while
assigning subnet IP on to F5?

>
>Is F5 support phased out ? If not what is the support status for it ?
>Will you continue to support it ?

No, F5 support is not phased out. In fact CloudStack 3.0 network offering
feature is enhanced to support F5 as well, so that brings in addition use
cases (multiple F5 load balancers per zone, ability to assign a dedicated
F5 device to a tenant etc) with F5.

[1]. http://wiki.cloudstack.org/pages/viewpage.action?pageId=3D1344581