Forum Discussion
Openstack ltm integration
here is my configuration :
1 virtual controller running under vanilla kvm with management vlan trunked into bridge .
3 compute nodes
eth0 = management network
eth1 = vxlan endpoint network
2 controllers just for networking
eth0 = management network
eth1 = vxlan endpoint network
eth2 = 802.11 tagged for multiple vlans as external networks.
the problem with the vlan / tagged networks is that , the computes do not have access to talk to the tagged network, they only speak via vxlan tunnels to the network controllers via br-tun , so if I create a vxlan network I can use a vlan network as a floating ip , but I cannot use the floating ips on the guests directly, because compute does not have access to the tagged vlans.
currently , I have moved away from the original model and Openstack is able to talk to the ltm ve in line , but still having problems setting up the vxlan portion .
I have created a network and subnet for external and internal , still kind of vague on what networks I am supposed to use in openstack, I assumed external would be the vxlan subnet that my physical network servers use and internal would be the internal network i created .
I created router X with neutron , then created an external network / Public with the vxlan vtep subnet trunked down and attached it to router X as the gateway subnet then created a private network and attached that network to router X . when I built the big ip ltm ve , I used a separate management network and appended a separate floating ip , and this works .
3 interfaces attached to the bigip
management = internal ip with external ip as floating ip .
internal = private subnet with port attached to external subnet
external = public subnet of neutron vtep
I also created a separate virt with cirros and appended the internal subnet , and then used an ip from the public vxlan subnet I created as a floating ip and was able to hit the public floating ip remotely and hit external addresses from internally , basically verifying that the private and public ip pairs work properly form a neutron perspective .
once I got the internal and external networks setup on the big ip , I changed the f5-bigip-lbaas-agent.ini config file and added the following
f5_vtep_folder = 'Common'
f5_vtep_selfip_name = 'vtep'
advertised_tunnel_types = vxlan
then restarted f5 agent , then went onto the f5 ltm and added a tunnel called vtep and assigned an ip from the external network also the vtep l3 network for neutron , NOTE: the ip assigned to the tunnel is not the same ip as the external interface ip , but I did try adding the same ip as well, and still see the same error in neutron f5-bigip-lbaas-agent.log on the network servers .
MissingVTEPAddress: device foo.foo1.com missing vtep selfip /Common/vtep
This is where I am locked up now .
Configs:
neutron server:
[ml2]
type_drivers = vlan,vxlan
tenant_network_types = vxlan,vlan
mechanism_drivers =openvswitch
[ml2_type_flat]
flat_networks = physnet1
[ml2_type_vlan]
network_vlan_ranges = physnet1:672:677,physnet1:767:767,physnet1:703:703,physnet1:667:668
[ml2_type_gre]
[ml2_type_vxlan]
vni_ranges =1001:2000
vxlan_group =239.1.1.2
[securitygroup]
enable_security_group = True
compute:
tunnel_types =vxlan
bridge_mappings =physnet1:br-ex
Maybe this is not the right network model if there is a more formidable solution please do feel free to chime in .
also based off your response, would not having the sdn module cause this error ?
Also if I wanted to move the f5 ltm outside of neutron control , maybe onto the kvm controller that the openstack controller its self is hosted on , how could I get the private ips that are transferred over vxlan to work outside of Neutron ?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com