Re: [Openstack-operators] [openstack-dev] [neutron] neutron ipv6 radvd sends out link-local or nothing as def gw (L3 HA issue?)

On Mon, Aug 20, 2018 at 6:06 AM, Tobias Urdin wrote: > When I removed those ips and set accept_ra to 0 on the backup router: > > ip netns exec qrouter-0775785e-a93a-4501-917b-be92ff03f36a sysctl -w > net.ipv6.conf.qr-7fad6b1b-c9.accept_ra=0 > ip netns exec

Re: [Openstack-operators] Bandwidth limitations

On Wed, Jun 29, 2016 at 12:43 PM, Joseph Bajin wrote: > Hi there, > > It looks like QOS is already available within the Mitaka release. Maybe it > doesn't have all the features you need, but looks to be a good start. >

Re: [Openstack-operators] [nova] Do you, or your users, have input on how get-me-a-network should work in Nova?

On Mon, Feb 22, 2016 at 10:58 AM, Matt Riedemann wrote: > > > On 2/20/2016 5:29 PM, Matt Riedemann wrote: >> >> >> >> On 2/19/2016 4:48 PM, Kris G. Lindgren wrote: >>> >>> >>> >>> ___ >>> Kris Lindgren >>>

Re: [Openstack-operators] [Neutron][DVR] point of encapsulation/locating routing tables

I wrote a fairly comprehensive blog series about DVR: assafmuller.com/category/dvr/ On Tue, Feb 16, 2016 at 2:47 PM, Adam Lawson wrote: > Hi everyone: > > Got a quick question for those of you with some knowledge of OVS and > namespaces within the context of DVR. > > I'm

Re: [Openstack-operators] Router associated with multiple l3 agents

ly seen this when the environment has been > built using terraform. This particular customer re-creates the issue every > time they rebuild. I don't know anything about Terraform so I can't help you there. I don't imagine there's any interesting errors/traces in the neutron-server logs? >

Re: [Openstack-operators] Router associated with multiple l3 agents

The HA routers feature we merged in Juno, and those are scheduled to multiple agents. If you source admin credentials and 'neutron router-show 951c8ec9-9a6c-4c6d-9d6d-049b3dee7f6f' is the 'HA' flag set to True? Otherwise, this is a really weird bug which I've never seen before. On Tue, Nov 24,

Re: [Openstack-operators] [openstack-operators][osops] Listing orphaned Neutron objects via listorphans.py

Are you aware of https://github.com/openstack/ospurge? On Wed, Nov 11, 2015 at 11:49 AM, Nick Jones wrote: > A while ago I knocked up a quick-and-dirty Python script to list various > ‘orphaned’ Neutron objects. By orphans I mean objects that OpenStack is > aware

Re: [Openstack-operators] IP - availability monitoring

On Sun, Aug 23, 2015 at 8:23 PM, Daniel Speichert dan...@speichert.pl wrote: On 8/22/2015 23:24, Balaji Narayanan (பாலாஜி நாராயணன்) wrote: Hello Operators, In the capacity management discussions at the Ops Summit last week, I thought there was a some discussion on monitoring of fixed /

Re: [Openstack-operators] Can't launch docker instance, Unexpected vif_type=binding_failed.

Also can you paste the configuration for both the OVS agent and your neutron server? Binding failure is almost always a configuration mismatch. - Original Message - Is the neutron openvswitch agent running on host compute2? What do the logs say for the agent there? On Jul 22, 2015

Re: [Openstack-operators] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

Are you running the same version of the code on both nodes? - Original Message - On 26-05-2015 11:15, Eren Türkay wrote: May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: ip address associated with VRID not present in received packet : 169.254.0.1 May 26 10:54:15 neutron-ha-2

[Openstack-operators] [Neutron] Floating IPs / Router Gateways

- Original Message - Hi folks, Looking for a bit of advice on how to accomplish something with Neutron. Our setup uses OVS+GRE with isolated tenant networks. Currently, we have one large network servicing our Floating IPs as well as our external router interfaces. What we're

[Openstack-operators] [Neutron] The specs process, effective operators feedback and product management

for this to be viable, the system would have to be a *non binding*, *additional* form of input. The top proposal *could* be declined for the same reasons that specs are currently being declined. It would not replace any of our current systems or processes. Assaf Muller, Cloud Networking Engineer Red Hat

[Openstack-operators] [Neutron] Deprecating the use_namespaces option - Now's the time to speak up!

as to why, and if it would be difficult to migrate such a setup to use namespaces. I'm asking because use_namespaces complicates Neutron code for what I gather is an option that has not been relevant for years. I'd like to deprecate the option for Kilo and remove it in Liberty. Assaf Muller

[Openstack-operators] Rolling upgrades and Neutron

the board for other services as well? Thank you. Assaf Muller, Cloud Networking Engineer Red Hat ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators