[Yahoo-eng-team] [Bug 1406052] [NEW] Missing host parameter in neutron conf files

Public bug reported: Version === Juno on rhel Description === When working on HA setups, we need to change host parameter in neutron.conf/L3 agent.conf "host = " is not present in any neutron conf files , and it will be great if we can add it as a comment ** Affects: neutron

[Yahoo-eng-team] [Bug 1369260] [NEW] network-vif-plugged events should be Info on nova compute

Public bug reported: Version === IceHouse on rhel Description === In order to track network-vif-plugged events across openetsack : Nova-API send event network-vif-plugged under AUDIT level , " AUDIT nova.api.openstack.compute.contrib.server_external_events [req- 7bd8ca07-a133-4b57-

[Yahoo-eng-team] [Bug 1325342] [NEW] VPNaaS Agent registered as L3 Agent

Public bug reported: Version === IceHouse on rhel Description === By default VPNaaS Agent registered as L3 agent instead of VPNaaS Agent [root@puma04 ~(keystone_admin)]# cat /var/log/neutron/vpn-agent.log 2014-06-01 12:27:02.470 696 INFO neutron.openstack.common.service [req-8bf4

[Yahoo-eng-team] [Bug 1323604] [NEW] Missing Floating IP status in Horizon

Public bug reported: Version === IceHouse on rhel Description === There is missing ability to see Floating IP status in Horizon The ability exist in CLI and was enhanced by https://blueprints.launchpad.net/neutron/+spec/fip-op-status ** Affects: horizon Importance: Undeci

[Yahoo-eng-team] [Bug 1322990] [NEW] Floating ip status is always down

Public bug reported: Version === IceHouse on rhel Description === floating ip status is down , it should have been solved by blueprint https://blueprints.launchpad.net/neutron/+spec/fip-op-status In the example below 10.35.180.21 is the floating ip an traffic ingress the VM using i

[Yahoo-eng-team] [Bug 1278105] [NEW] nova absolute-limit should include all system quota

Public bug reported: Version === IceHouse on rhel Description === There is not single place which holds entire tenant quota limits and its usage nova absolute-limit is not synced with neutron limits/usage as well doesn't show the info in a table were user can see the usage/amount l

[Yahoo-eng-team] [Bug 1265493] [NEW] RFE - Adding comments to each rule added to iptables

Public bug reported: Version === Havana on rhel Description === Each time a VM is created new rules are added into iptables, Same when modify security groups or floating ips It will be very helpful if to add comments per each rule , explaining what is the purpose and which sub-com

[Yahoo-eng-team] [Bug 1264087] [NEW] no-security-groups option is not working on neutron port-create

Public bug reported: Version === Havana on rhel , python-neutronclient Description === Creating a port with --no-security-groups option ,will still attached the default security group Logs = [root@puma04 ~(keystone_admin_tenant3)]$neutron security-group-list +