See inline please. On 10/29/2014 05:24 PM, Jeroen Groenewegen van der Weyden wrote:

1) the _core plugin have to be set otherwise no networks are created, checking with ip a and ip netns

Did you install neutron on a clean machine? Was an older version of Neutron running there before? It would be useful if you could paste some part of the neutron server log. For example the network creation that you say it's failing.

2) the sym link I have to set otherwise the gre tunnels are not created, checking with ovs-vsctl the ml2_conf.ini is present I set a symlink from the ovs_neutron_plugin.ini config file to point to the ml2 config file.

error messages I had many, I am not sure which on belongs to what error. If you can spare the time I can go through it with you one by one.

Rossella Sblendido schreef op 29-10-2014 om 16:48:

...

Hello Jeroen,

...

...

I setup neutron according to [documentation](http://docs.openstack.org/juno/install-guide/install/zypper/content/ch_netwo...)

However it does not work for me this way. Can you give me more details? What's not working exactly? Do you see any error in the log? The config values in the documentation seems OK.

...

...

2) and I set a symlink from

ovs_neutron_plugin.ini -> ../ml2/ml2_conf.ini Why do you have to set a symlink? Is ml2_conf.ini not present?

cheers,

Rossella

...

-------- Forwarded Message -------- Subject: [opensuse-cloud] Juno neutron configuration from docs.openstack.org Date: Tue, 28 Oct 2014 16:15:02 +0100 From: Jeroen Groenewegen van der Weyden To: opensuse-cloud@opensuse.org

Hi,

I'm trying to set up a openstack installation with juno from the repository http://download.opensuse.org/repositories/Cloud:/OpenStack:/Juno/openSUSE_13....

I setup neutron according to [documentation](http://docs.openstack.org/juno/install-guide/install/zypper/content/ch_netwo...)

However it does not work for me this way. I have to change the following to get thing done:

1) In neutron.conf I have to use

core_plugin = neutron.plugins.ml2.plugin.Ml2Plugin

instead of `core_plugin = ml2`

service_plugins = neutron.services.l3_router.l3_router_plugin.L3RouterPlugin

instead of `service_plugins = router`

2) and I set a symlink from

ovs_neutron_plugin.ini -> ../ml2/ml2_conf.ini

otherwise no network or gre tunnels come up.

I am curious why my setup is not working configured using the installation guide mentioned before, any body any idea? I am afraid not to run in to other issues later on not going with the guidelines.

BR, jeroen

-- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org

Hi, Concerning the symlink, at first there is only the br-int no gre tunnels come up. Then I set the symlink of ovs_neutron_plugin.ini to ml2_ini.conf and restart the neutron service. Afterwards the tunnels come up. this is the compute node Also note the service itself start with -config-file=/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini. Mocha:~ # ovs-vsctl show 86d8448a-6eaa-4cf0-9557-3e67c0cb494e Bridge br-int fail_mode: secure Port br-int Interface br-int type: internal ovs_version: "2.1.3" Mocha:~ # systemctl status openstack-neutron-openvswitch-agent.service > q Mocha:~ # cat q openstack-neutron-openvswitch-agent.service - LSB: OpenStack Networking (Neutron) - openvswitch-agent Loaded: loaded (/etc/init.d/openstack-neutron-openvswitch-agent) Active: active (running) since Thu 2014-10-30 12:50:50 CET; 4min 34s ago Process: 9613 ExecStop=/etc/init.d/openstack-neutron-openvswitch-agent stop (code=exited, status=0/SUCCESS) Process: 9690 ExecStart=/etc/init.d/openstack-neutron-openvswitch-agent start (code=exited, status=0/SUCCESS) CGroup: /system.slice/openstack-neutron-openvswitch-agent.service ââ9699 /usr/bin/python /usr/bin/neutron-openvswitch-agent --config-file=/etc/neutron/neutron.conf --config-file=/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini Oct 30 12:55:05 Mocha sudo[10306]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 30 12:55:07 Mocha sudo[10312]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 30 12:55:09 Mocha sudo[10318]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 30 12:55:11 Mocha sudo[10323]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 30 12:55:13 Mocha sudo[10327]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 30 12:55:15 Mocha sudo[10331]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 30 12:55:17 Mocha sudo[10335]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 30 12:55:19 Mocha sudo[10339]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 30 12:55:21 Mocha sudo[10343]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 30 12:55:23 Mocha sudo[10347]: pam_unix(sudo:session): session opened for user root by (uid=0) Mocha:~ # cd /etc/neutron/ Mocha:/etc/neutron # cd plugins/ Mocha:/etc/neutron/plugins # cd openvswitch/ Mocha:/etc/neutron/plugins/openvswitch # l total 36 drwxr-xr-x 2 root root 4096 Oct 30 12:15 ./ drwxr-xr-x 17 root root 4096 Oct 22 13:59 ../ -rw-r--r-- 1 root root 6292 Oct 30 12:15 ovs_neutron_plugin.ini -rw-r--r-- 1 root root 2826 Oct 22 17:23 ovs_neutron_plugin.ini.icehouse -rw-r--r-- 1 root root 6292 Oct 19 22:01 ovs_neutron_plugin.ini.orig -rw-r--r-- 1 root root 7004 Oct 17 12:58 ovs_neutron_plugin.ini.rpmnew Mocha:/etc/neutron/plugins/openvswitch # rm ovs_neutron_plugin.ini Mocha:/etc/neutron/plugins/openvswitch # ln -s ../ml2/ml2_conf.ini ovs_neutron_plugin.ini Mocha:/etc/neutron/plugins/openvswitch # l total 28 drwxr-xr-x 2 root root 4096 Oct 30 12:57 ./ drwxr-xr-x 17 root root 4096 Oct 22 13:59 ../ lrwxrwxrwx 1 root root 19 Oct 30 12:57 ovs_neutron_plugin.ini -> ../ml2/ml2_conf.ini -rw-r--r-- 1 root root 2826 Oct 22 17:23 ovs_neutron_plugin.ini.icehouse -rw-r--r-- 1 root root 6292 Oct 19 22:01 ovs_neutron_plugin.ini.orig -rw-r--r-- 1 root root 7004 Oct 17 12:58 ovs_neutron_plugin.ini.rpmnew Mocha:/etc/neutron/plugins/openvswitch # ovs-vsctl show 86d8448a-6eaa-4cf0-9557-3e67c0cb494e Bridge br-int fail_mode: secure Port br-int Interface br-int type: internal ovs_version: "2.1.3" Mocha:/etc/neutron/plugins/openvswitch # systemctl restart openstack- openstack-ceilometer-agent-compute.service openstack-neutron-openvswitch-agent.service openstack-nova-compute.service Mocha:/etc/neutron/plugins/openvswitch # systemctl restart openstack- openstack-ceilometer-agent-compute.service openstack-neutron-openvswitch-agent.service openstack-nova-compute.service Mocha:/etc/neutron/plugins/openvswitch # systemctl restart openstack-neutron-openvswitch-agent.service Mocha:/etc/neutron/plugins/openvswitch # ovs-vsctl show 86d8448a-6eaa-4cf0-9557-3e67c0cb494e Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port br-int Interface br-int type: internal ovs_version: "2.1.3" Mocha:/etc/neutron/plugins/openvswitch # ovs-vsctl show 86d8448a-6eaa-4cf0-9557-3e67c0cb494e Bridge br-tun Port "gre-ac106306" Interface "gre-ac106306" type: gre options: {df_default="true", in_key=flow, local_ip="172.16.99.4", out_key=flow, remote_ip="172.16.99.6"} Port "gre-ac106303" Interface "gre-ac106303" type: gre options: {df_default="true", in_key=flow, local_ip="172.16.99.4", out_key=flow, remote_ip="172.16.99.3"} Port "gre-ac106305" Interface "gre-ac106305" type: gre options: {df_default="true", in_key=flow, local_ip="172.16.99.4", out_key=flow, remote_ip="172.16.99.5"} Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Bridge br-int fail_mode: secure Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port br-int Interface br-int type: internal ovs_version: "2.1.3" Jeroen Groenewegen van der Weyden schreef op 30-10-2014 om 08:28:

Rossella Sblendido schreef op 29-10-2014 om 19:42:

...

See inline please.

...

1) the _core plugin have to be set otherwise no networks are created, checking with ip a and ip netns Did you install neutron on a clean machine? Was an older version of Neutron running there before? It would be useful if you could paste some

On 10/29/2014 05:24 PM, Jeroen Groenewegen van der Weyden wrote: part of the neutron server log. For example the network creation that you say it's failing. Well I was trying Icehouse before, but I could not get the networking functioning at all with icehouse. ip packets were not routing through gre tunnels and I had no idea why. I upgraded to Juno, and made fresh config files. I will reproduce some of the problems today.

...

2) the sym link I have to set otherwise the gre tunnels are not created, checking with ovs-vsctl the ml2_conf.ini is present I set a symlink from the ovs_neutron_plugin.ini config file to point to the ml2 config file.

error messages I had many, I am not sure which on belongs to what error. If you can spare the time I can go through it with you one by one.

Rossella Sblendido schreef op 29-10-2014 om 16:48:

...

Hello Jeroen,

...

...

I setup neutron according to [documentation](http://docs.openstack.org/juno/install-guide/install/zypper/content/ch_netwo...)

However it does not work for me this way. Can you give me more details? What's not working exactly? Do you see any error in the log? The config values in the documentation seems OK.

...

...

2) and I set a symlink from

ovs_neutron_plugin.ini -> ../ml2/ml2_conf.ini Why do you have to set a symlink? Is ml2_conf.ini not present?

cheers,

Rossella

...

-------- Forwarded Message -------- Subject: [opensuse-cloud] Juno neutron configuration from docs.openstack.org Date: Tue, 28 Oct 2014 16:15:02 +0100 From: Jeroen Groenewegen van der Weyden To: opensuse-cloud@opensuse.org

Hi,

I'm trying to set up a openstack installation with juno from the repository http://download.opensuse.org/repositories/Cloud:/OpenStack:/Juno/openSUSE_13....

I setup neutron according to [documentation](http://docs.openstack.org/juno/install-guide/install/zypper/content/ch_netwo...)

However it does not work for me this way. I have to change the following to get thing done:

1) In neutron.conf I have to use

core_plugin = neutron.plugins.ml2.plugin.Ml2Plugin

instead of `core_plugin = ml2`

service_plugins = neutron.services.l3_router.l3_router_plugin.L3RouterPlugin

instead of `service_plugins = router`

2) and I set a symlink from

ovs_neutron_plugin.ini -> ../ml2/ml2_conf.ini

otherwise no network or gre tunnels come up.

I am curious why my setup is not working configured using the installation guide mentioned before, any body any idea? I am afraid not to run in to other issues later on not going with the guidelines.

BR, jeroen

-- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org

On 10/30/2014 02:13 PM, Jeroen Groenewegen van der Weyden wrote:

when I add in the nova.conf vif_plugging_is_fatal: false vif_plugging_timeout: 0 the instances start and seem to work properly including network connectivity.

Nova waits for a notification from Neutron that confirms that the port for the VM is active before plugging the virtual interface of the VM. In your case it seems that Neutron does not notify back to Nova. Check you have the newest packages both for Nova and Neutron. Restart both services and if the problem persists I recommend to file a bug report in https://bugs.launchpad.net/openstack for Nova/Neutron, copying the traceback of the error and describing your deployment a bit, the Neutron plugin you are using, how many machines, etc. cheers, Rossella -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org

On 10/30/2014 04:50 PM, Jeroen Groenewegen van der Weyden wrote:

Do you think reporting a bug makes sense in this case?

If everything is up to date and you restarted the services and the problem persists, yes, I'd report it. -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org