Class Rules Management

We're going to make the same set of rules available to all DHCP pools in our system. So before we assign a specific rule to any of our DHCP pools, we first need to define this rule. We do this so that the users will be able to reuse existing rules. This approach is good if you have same rules reused in many different subnets. If your rules are very specific and unlikely to be reused, however, this is not the best approach as you will end up with a large number of one-off entries, and the list soon becomes unmanageable.

If that is the case, you might want to think about defining categories for rules and subnets, so that they can be grouped automatically. Then when you create a new DHCP network, you'll pick which categories you want to see.

Previously we created Add, Modify, Delete, and Display views for all models we had in our system. It seems to be a repetitive process, don't you think? It would be nice if there was a way to automatically perform tasks like basic creation, modification, and deletion of the objects. And the Django framework provides this functionality—it is called generic views.

Was this article helpful?

0 0

Post a comment