Neutron networking question with openstack-base
Liam Young
liam.young at canonical.com
Mon Oct 19 10:10:39 UTC 2015
Hi Daniel,
Have you set 'ext-port' in the neutron-gateway charm? ext-port
specifies the external port the neutron-gateway charm should use for
routing of instance traffic to the external public network. If eth1 on
the neutron-gateway is plumbed into 143.207.94.0/24 network then you
would set it with:
juju set neutron-gateway ext-port=eth1
I'd also take a look at the Network Topology page in the horizon
dashboard and check that ext_net and your private net are both plumbed
into your router and that your instances are plumbed into your private
network. I'm not sure which version of Openstack you are deploying but
certainly in Icehouse I have seen horizon claim the state of
network:router_gateway to be 'down' when it is actually working.
Do you see the floating IPs that you have assigned your instance(s)
listed when you look at the 'Attached Devices' in the detail tab of
ext_net ?
Also check that when the instance booted DHCP succeeded. You can do this
through horizon by going to Compute -> Instances -> Click on Instance
Name -> Log tab. The message you are looking for will differ depending
on the image you booted the instance from but something like:
ci-info: eth0 : 1 192.168.0.4 255.255.255.0 fa:16:3e:ef:d8:53
or
Lease of 192.168.0.2 obtained, lease time 86400
Thanks,
Liam Young
On 15/10/15 20:49, Daniel Bidwell wrote:
> I have installed a small openstack cloud with the openstack-base charm.
>
> After everything came up I ran the neutron-ext-net and
> neutron-tenant-net. I ran neutron-ext-net with -g 143.207.94.1 -c
> 143.207.94.0/24 -f 143.207.94.10:143.207.94.254 ext_net
>
> Each machine in my cloud has an interface on the 143.207.94.0/24
> network. When I look at the horizon dashboard, under
> admin->networks->ext_net it says that the port on 143.207.94.x as
> network:router_gateway has an admin state of UP, but a Status of Down
> and I have now access from the external addresses on 143.207.94.0 to the
> internal addresses on the 143.207.94.0 network. I have tried to set the
> access rules for ping and ssh, but nothing goes through.
>
> How do I find out why the two different networks don't connect? How do
> I make them connect?
More information about the Juju
mailing list