You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, our firewall rules use CIDR notation to define allowed IP address ranges. This makes it difficult to manage and update the rules, especially when IP addresses change or network segments are reorganized. To improve maintainability and readability, we need to update the firewall rules to use Ansible network variables instead of raw CIDR blocks.
Level of urgency
High
Moderate
Low
Why is this maintenance needed?
Action Items:
- Identify Firewall Rules: Review all existing firewall rules and identify those that use CIDR notation for network definitions.
- Define Ansible Network Variables:
- Create Ansible variables in the ufw_firewall to represent the relevant network segments.
- Use descriptive names for the variables (e.g., internal_network, libnet, vpn).
- Assign the corresponding CIDR blocks to these variables.
- Update Firewall Rules:
- Modify the firewall rules to replace CIDR blocks with the Ansible network variables.
- Ensure that the syntax for using variables within the firewall rules is correct
Acceptance criteria
swap out the rules in for abid-staging2.lib.princeton.edu
[ ]
[ ]
Implementation notes, if any
The text was updated successfully, but these errors were encountered:
What maintenance needs to be done?
Currently, our firewall rules use CIDR notation to define allowed IP address ranges. This makes it difficult to manage and update the rules, especially when IP addresses change or network segments are reorganized. To improve maintainability and readability, we need to update the firewall rules to use Ansible network variables instead of raw CIDR blocks.
Level of urgency
Why is this maintenance needed?
Action Items:
Acceptance criteria
Implementation notes, if any
The text was updated successfully, but these errors were encountered: