[Ussuri][neutron] How to accomplish what allow_same_net_traffic did

Slawek Kaplonski skaplons at redhat.com
Tue May 4 08:07:21 UTC 2021


Dnia wtorek, 4 maja 2021 09:40:31 CEST Eugen Block pisze:
> Hi *,
> I was wondering how other operators deal with this. Our cloud started
> somewhere in Kilo or Liberty version and in older versions the option
> allow_same_net_traffic allowed to control whether instances in our
> shared network could connect to each other between different projects.
> That option worked for us but is now deprecated and the Pike release
> notes [1] state:
> > Given that there are other better documented and better tested ways
> > to approach this, such as through use of neutron’s native port
> > filtering or security groups, this functionality has been removed.
> > 
> > > Users should instead rely on one of these alternatives.
> Does that mean all security groups need to be changed in a way that
> this specific shared network is not reachable? That would be a lot of
> work if you have many projects. Is there any easier way?
> Regards,
> Eugen
> [1] https://docs.openstack.org/releasenotes/nova/pike.html

I don't know about this option TBH but from the quick search it looks for me 
that it's Nova's option. So you are probably using nova-network still. Is that 
correct? If yes, I think You need to migrate to Neutron in never versions and 
in Neutron each "default" SG has got rule to allow ingress traffic from all 
other ports which uses same SG.
If that will not help You, I think that You will need to add own rules to Your 
SGs to achieve that.

Slawek Kaplonski
Principal Software Engineer
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210504/4f5c3701/attachment-0001.sig>

More information about the openstack-discuss mailing list