You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Roeland Kuipers (JIRA)" <ji...@apache.org> on 2014/01/21 15:43:20 UTC
[jira] [Created] (CLOUDSTACK-5919) Add "Removed" field and/or
versioning and/or rollback on Firewall/Nat/FB rules
Roeland Kuipers created CLOUDSTACK-5919:
-------------------------------------------
Summary: Add "Removed" field and/or versioning and/or rollback on Firewall/Nat/FB rules
Key: CLOUDSTACK-5919
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5919
Project: CloudStack
Issue Type: New Feature
Security Level: Public (Anyone can view this level - this is the default.)
Components: Network Controller
Affects Versions: 4.2.0
Reporter: Roeland Kuipers
Fix For: Future
To power of an IaaS cloud is that everything can be automated like network changes. This comes with a huge risk in case of human error or malfunctioning code.
For example a cookbook which contains a bug and instead of adding a rule removes all fw/nat/lb rules.
Currently this means that if you cannot restore this from your cfg mgmt system that you need to restore these rules from a database backup, which is a somewhat lengthy and complex process.
A way to mitigate this risk is to add a removed field to the fw/nat/lb rules tables. This seams common practice on a lot of CS tables. But not on these specific tables. A nicer implementation would be to add a versioning system behind these configurations.
This might look like a corner case but unfortunately this is real live experience.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)