reviewing policy management in GUI
Lindy Foster <[email protected]> Fri, 09 Apr 2004 13:50:57 -0700
| Newsgroups | gmane.network.net-policy.user |
|---|---|
| Message-ID | <[email protected]> |
If I remember correctly, we never did much in managing policies. So far, you can select "Manage Policies"; select "create new" or a policy (by name) to manage. When managing a policy, you can add existing roles to the policy, or create a new role to add to the policy. You can't delete roles from a policy. There's also an option to "skip adding roles". I can't remember what good that did: anybody? If you skip adding roles, there's basically nothing else to do. I'm not sure I want to get into fleshing out what policy management is, because it could be quite a rat-hole and I'm not sure this has any priority now. But if all we're going to do at present is add roles, I ought to get rid of "skip adding roles". Also, do we want to also delete roles? This would not be real hard to do, since I've just refined how we do it in role admin. But are there more implications than just changing a couple of tables that we're not prepared to handle? I mean, deleting a role from a policy REALLY means going out to each host and undoing whatever policy that was; are there dependencies in that that we can't handle yet? I have a few other cleanup items I'm going to do in policy_admin.pm, so if folks feel that some of the above ought to be done too, let me know. Otherwise, I'll try not to change any functionality, just make things work a little better and have clearer confirmation messages. lindy ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click