Direct Attach of Floating IPs [closed]

asked 2013-11-19 11:34:55 -0500

pjimenez gravatar image

Hi,

I have a full Havana environment with 3 nodes (Compute, Controller and Network), configured it with Neutron/vlan I have created multiple tenants with a router on each, all is working like a charm.

But I am trying to launch an instance attaching directy to external network on Admin Tenant with no success. The external network have been changed to allow DHCP on ext_net_subnet

neutron net-create ext-net -- --router:external=True --provider:network_type vlan --provider:physical_network physnet1 --provider:segmentation_id 2

neutron subnet-create ext-net --allocation-pool start=10.0.96.224,end=10.0.96.239 --dns-nameserver 8.8.8.8 --gateway=10.0.97.254 --enable_dhcp=True

The instance is created normally, spawned at compute node but when it tries to get the DHCP request ... only shows timeouts from inside.

Starting network...
udhcpc (v1.20.1) started
Sending discover...
Sending discover...
Sending discover...
  • I can see the DHCP request from the compute (eth1 is the data network interface) but no reply from the Network Node
18:26:55.604739 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:11:72:2f, length 280
18:27:55.665401 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:11:72:2f, length 280
18:28:55.726067 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:11:72:2f, length 280
  • If we compare the same instance booting from inside a tenant with a Router (typical Demo Tenant), it is posible to see the Request and the reply
[root@compute01 ~]# tcpdump -n -i eth1 port 67 or port 68
18:34:47.866695 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:ce:3c:42, length 280
18:34:47.871062 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:ce:3c:42, length 292

[root@network ~]# tcpdump -n -i eth1 port 67 or port 68
18:34:34.643372 IP 10.5.5.3.bootps > 10.5.5.4.bootpc: BOOTP/DHCP, Reply, length 327
18:34:34.644917 IP 10.5.5.3.bootps > 10.5.5.4.bootpc: BOOTP/DHCP, Reply, length 327

[root@network ~]# tcpdump -i br-int  port 67 or port 68
18:34:34.640439 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:ce:3c:42 (oui Unknown), length 280
18:34:34.644735 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:ce:3c:42 (oui Unknown), length 292
  • ┬┐Does anyone have a similar conf? I think it must be possible to set only a public range (floating IPs) to the instances connected to the external network.
edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by rbowen
close date 2017-05-24 13:42:12.604510

Comments

Closing: Your question refers to a version of OpenStack which has been designated End Of Life. (See http://releases.openstack.org for details).

rbowen gravatar imagerbowen ( 2017-05-24 13:42:07 -0500 )edit