Re: [Openstack-operators] Neutron not adding iptables rules for metadata agent

2018-06-29 Thread Radu Popescu | eMAG, Technology
o, > > I would suggest to open a bug on launchpad to track this issue. > > thank you > > Saverio > > 2018-06-18 12:19 GMT+02:00 Radu Popescu | eMAG, Technology > : >> Hi, >> >> We're using Openstack Ocata, deployed using Openstack

Re: [Openstack-operators] Neutron not adding iptables rules for metadata agent

2018-06-18 Thread Radu Popescu | eMAG, Technology
ss like a bug report. This you check existing open bugs for neutron ? Also what version of openstack are you running ? how did you configure enable_isolated_metadata and enable_metadata_network options ? Saverio 2018-06-13 12:45 GMT+02:00 Radu Popescu | eMAG, Technology mailto:radu.pope...@emag

[Openstack-operators] Neutron not adding iptables rules for metadata agent

2018-06-13 Thread Radu Popescu | eMAG, Technology
Hi all, So, I'm having the following issue. I'm creating a VM with floating IP. Everything is fine, namespace is there, postrouting and prerouting from the internal IP to the floating IP are there. The only rules missing are the rules to access metadata service: -A neutron-l3-agent-PREROUTING

Re: [Openstack-operators] attaching network cards to VMs taking a very long time

2018-05-30 Thread Radu Popescu | eMAG, Technology
lways monitor rabbitmq queues to identify bottlenecks !! :) Cheers Saverio Il gio 24 mag 2018, 11:07 Radu Popescu | eMAG, Technology mailto:radu.pope...@emag.ro>> ha scritto: Hi, did the change yesterday. Had no issue this morning with neutron not being able to move fast enough. Still,

Re: [Openstack-operators] attaching network cards to VMs taking a very long time

2018-05-24 Thread Radu Popescu | eMAG, Technology
anks a lot! Radu On Wed, 2018-05-23 at 10:08 +0000, Radu Popescu | eMAG, Technology wrote: Hi, actually, I didn't know about that option. I'll enable it right now. Testing is done every morning at about 4:00AM ..so I'll know tomorrow morning if it changed anything. Thanks, Radu On

Re: [Openstack-operators] attaching network cards to VMs taking a very long time

2018-05-23 Thread Radu Popescu | eMAG, Technology
he Openstack rootwrap configured to work in daemon mode ? please read this article: 2018-05-18 10:21 GMT+02:00 Radu Popescu | eMAG, Technology mailto:radu.pope...@emag.ro>>: Hi, so, nova says the VM is ACTIVE and actually boots with no network. We are setting some metadata that we use later

Re: [Openstack-operators] attaching network cards to VMs taking a very long time

2018-05-18 Thread Radu Popescu | eMAG, Technology
Hi, so, nova says the VM is ACTIVE and actually boots with no network. We are setting some metadata that we use later on and have cloud-init for different tasks. So, VM is up, OS is running, but network is working after a random amount of time, that can get to around 45 minutes. Thing is, is no

Re: [Openstack-operators] attaching network cards to VMs taking a very long time

2018-05-17 Thread Radu Popescu | eMAG, Technology
Hi, unfortunately, didn't get the reply in my inbox, so I'm answering from the link here: http://lists.openstack.org/pipermail/openstack-operators/2018-May/015270.html (hopefully, my reply will go to the same thread) Anyway, I can see the neutron openvswitch agent logs processing the interface

[Openstack-operators] attaching network cards to VMs taking a very long time

2018-05-16 Thread Radu Popescu | eMAG, Technology
Hi all, we have the following setup: - Openstack Ocata deployed with Openstack Ansible (v15.1.7) - 66 compute nodes, each having between 50 and 150 VMs, depending on their hardware configuration - we don't use Ceilometer (so not adding extra load on RabbitMQ cluster) - using Openvswitch HA with D