This proposal Looks like more flexible for the network traffic security.
For current FW V2, we support 2 security levels for a single Neutron port.
One is security group, the other is firewall group, but this looks like
support more. And the firewall depolyer/dispatcher need to own some network
Currently, neutron agent report its state through rpc. The message will be
fetched by neutron server and store the latest info into db.
There may be some problems found in the scenarios of public cloud.[1].
Neutron & its agents and nova & its services(nova compute) may hit the same
problem. So
Hi guys,
Could you give some good ideas about add neutron common attributes into db
table 'standardattributes'? Like timestamp, it must be a common one should be
added.
The table 'standardattributes' is imported from [1]. It must be neutron common
attrs should be added into this table in the
. Are there some issues ?
Thank you anyone could help for confirm this issue , and wish you return the
message asap.
ZhaoBo
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
Hi ,
Could anyone please check the bug below?
https://bugs.launchpad.net/neutron/+bug/1467791
This bug description:
When the created network contains one ipv4 subnet and an ipv6 subnet which
turned on slaac or stateless.
When I create a port use cmd like:
neutron port-create --fixed-ip
