We run a similar kind of script.
I think in most cases, a Floating IP means a publicly routable IP, and
those are now scarce resources. Because of that, I agree with what's been
mentioned about a conservative floating IP quota.
Since the other resource types aren't restricted by external availabi
We’ve encountered the same issue in our cloud. I wouldn’t be surprised if it
was quite common for systems with many tenants that are not active all the time.
You may be interested by this OSOps script:
https://git.openstack.org/cgit/openstack/osops-tools-generic/tree/neutron/orphan_tool/delete_o
Hello,
floating IPs is the real issue.
When using horizon it is very easy for users to allocate floating ips
but it is also very difficult to release them.
In our production cloud we had to change the default from 50 to 2. We
have to be very conservative with floatingips quota because our
experi
Hey there,
I noticed that Ihar started working on a change to increase the default quotas
values in Neutron[1]. Personally, I think that makes sense to change it but
I’d like to complement it. So, based on your experience, what should be the
most common quota value for networks, subnets, port