What is the best way to manage a ruleset with more than 1000 rules? #368
Replies: 3 comments 3 replies
|
Thank you for the info. |
|
Hi Superstes,
What I'm not really enthusiast is when a rule must be removed or added, my ansible re-calculate the sequence number of all next rules, purge and re add them. Let me put a quick example bellow just to be clear. Let's imagine I've the following running policy and I need to remove the rule C. So the candidate policy is as follow (rule C removed and rule D and E sequence number recalculted) In that case, my Ansible is going to execute a purge task with So with more that 1000 rules it could be a really a long time to just remove 1 rule due to the fact that my Ansible re-add a lot of rules due to the change of the sequence number. Probably my approach is not really the most efficient one. Thank you for sharing your point of view.. |
|
As the API is not designed for mass-management, we can only do so much.. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I'm working to create a set of Ansible tasks to manage the policy about more than 1000 rules.
I want to have the rules described in the inventory with the following structure. So all the rules combined in 1 inventory file.
My Ansible seems no to be really optimised. When I try from scratch to all all the rules, it takes more than 30min. So not really ready for a production environment.
Please note that I'm using the _multi modules and the last version 25.7.8 of the collection and OPNsense 25.7.2.
So I probably need to review it or to review my process.
Does someone is managing his firewall policy with Ansible ?
Thank you for you feedbacks,
Have a nice day,
All reactions