Maybe one thing I to add, This is a devstack post-config. So what was
taken in addition from the default config is:
[ml2]
type_drivers = flat,gre
[securitygroup]
firewall_driver =
neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
And I predefined the bridge br-ext.
Goo
Hi Andreas,
it seems I screwed up my installation (not only Neutron). I'm in the
progress of resetting everything to the not-yet-configured state.
I'll try to adapt your config example and will report back once I come
to that point again.
Thanks again and have a nice weekend,
Uwe
Am 2
Hi Uwe, me again.
I just applied the gre on my new stable/juno system. This is the minimal
set of parameters that was required (also using ml2pop).
controller:
[[post-config|/$Q_PLUGIN_CONF_FILE]]
[ml2]
tenant_network_types = gre
mechanism_drivers = openvswitch,l2population
[ml2_type_gre]
tunnel
Hi Uwe,
this config is from a icehouse system. Maybe things have changed since
then. And as mentioned before, I'm not even sure if all parameters are
required... still have to figure this out. This is just how I got it
running. So I cannot give you a certain reason ;)
Thanks
--
Andreas
(irc:
Hi Uwe,
Enable debug, restart the service and you should get more info.
George
On Wed, Nov 26, 2014 at 11:28 AM, Uwe Sauter
wrote:
> Hi all,
>
> does anyone know why neutron-openvswitch-agent.service keeps crashing?
>
> Nov 26 17:25:40 os483601.localnet systemd[1]: Starting OpenStack Neutron
>
Hi all,
does anyone know why neutron-openvswitch-agent.service keeps crashing?
Nov 26 17:25:40 os483601.localnet systemd[1]: Starting OpenStack Neutron
Open vSwitch Agent...
Nov 26 17:25:40 os483601.localnet systemd[1]: Started OpenStack Neutron
Open vSwitch Agent.
Nov 26 17:25:41 os483601.localn
Hi Andreas,
can you elaborate why you have [agent] sections in your config. I read
somewhere a few days ago, that these aren't necessary with Juno and they
are not mentioned in the Juno docs.
Meanwhile I found out that neutron-openvswitch-agent.service crashed on
the network node (see my mail fro
Hi Uwe,
this is how my config for the ovs agent looks like. This one is working
but some of the parameters might be duplicates to the default or not
even required. I still have to figure this out.
But at least it is working ;)
Compute Node:
[ovs]
enable_tunneling = True
tenant_network_type =
Hi Andreas,
on each host /etc/neutron/plugin.ini is a symlink to
/etc/neutron/plugins/ml2/ml2_conf.ini.
Content on the controller node:
[ml2]
mechanism_drivers = openvswitch
tenant_network_types = gre
type_drivers = gre,vlan
[ml2_type_flat]
[ml2_type_vlan]
network_vlan_ranges = external:202:20
Hi Uwe,
could you please provide the content of your /etc/neutron/plugin.ini of
the compute and the network node?
--
Andreas
(irc: scheuran)
On Wed, 2014-11-26 at 14:14 +0100, Uwe Sauter wrote:
> Hi George,
>
> it seems I missed to list that service for the compute hosts.
> These are the s
Hi George,
it seems I missed to list that service for the compute hosts.
These are the services running on those hosts:
[root@os483401 ~]# systemctl list-units | grep -i open
neutron-openvswitch-agent.service
loaded active running OpenStack Neutron Open
vSwitch Agent
op
You have to install the neutron-openvswitch-agent on the compute nodes as
well.
On 26 Nov 2014 06:57, "Uwe Sauter" wrote:
> Hi all,
>
> I'm trying to setup Juno on five hosts (CentOS 7), following along the
> three-node setup guide as close as possible. My setup differs in that I
> have separate
Hi all,
I'm trying to setup Juno on five hosts (CentOS 7), following along the
three-node setup guide as close as possible. My setup differs in that I
have separate nodes for storage (cinder, glance) and network (neutron)
and two compute hosts:
Here's a list of the services that run on each host,
13 matches
Mail list logo
