• Home
|
• About The OpenNMS Group
|
• Our Clients
|
• Pricing
|
• News + Events
|
• Contact Us

Enterprise Support: (877) ONMS-911

OpenNMS Platform

Get the Network to Work™

Try OpenNMS Today!

This Week in OpenNMS: ACLs: The New Hotness

by Benjamin Reed: April 12, 2010

It’s time for This Week in OpenNMS. In the last week we got a basic working ACL implementation, as well as some other updates.

Project Updates

• Stable: Current Release is 1.6.4
  1.6.4 is the current stable release, released (no kidding!) April 1st. It fixes a number of bugs, and adds a few features. For a full list, see the bugzilla 1.6.3 and 1.6.4 milestones. This is a recommended upgrade for anyone on OpenNMS versions older than 1.6.4.
• Unstable: Current Release is 1.7.2
  1.7.2 is the current unstable release, released alongside 1.6.4 on April 1st as well. It fixes a whole raft of bugs since 1.7.0, and barring still not handling newSuspect events, Provisiond is pretty solid. A 1.7.x overview is available in the release notes on the site.
• Trunk: ACL First Draft (+Hibernate Updates)
  A first working draft of the new ACL support is in-place as of this weekend. As part of this work, we’ve upgraded to the latest Hibernate and related tools. We’ll be fine-tuning it this week, and will hopefully have a 1.7.3 release out sometime this week so people can kick the tires.
• Trunk: RANCID Updates
  Some minor tweaks and cleanups were integrated into the RANCID web service. The RWS is now approaching a release version, and 0.92 is now available for download.
• Trunk: WMI Updates
  Some socket leaks in the WMI code were fixed, and Matt Raykowski also did some work cleaning up the CheckWmi command.

ACLs in Trunk

We finally have a long-requested feature implemented in trunk: being able to limit which devices/interfaces/etc. a user sees based on a certain criteria.
If you want to give ACLs a try, here’s what you need to do:

1. Enable ACLs
   You can do this by editing “$OPENNMS_HOME/etc/opennms.properties” and uncommenting/enabling the ACL line so it says, “org.opennms.web.aclsEnabled=true“.
2. Create a User
   In the admin UI, go to “Configure Users, Groups and Roles“, create a user in “Configure Users“, and then go back to “Configure Groups“, create a group, and put the user in that group. Also, make sure you have one or more node categories assigned to that group. That will map the user to the nodes he is allowed to interact with.
3. Assign Nodes to Node Categories
   To manually put nodes in a particular category, you can use the “Manage Surveillance Categories” to add nodes to the category, assign it directly in the provisiond configuration, or assign them automatically using the NodeCategorySettingPolicy (“Set Node Category” policy).

Once you log in as that user, you should see only the nodes in the categories assigned to that user’s group. This is still very early code, so if you find issues, please open a bug, we really want to work out the kinks.

Upcoming Events

Note: April training has been pushed back to May.

• May 4th-8th, 2009: OpenNMS training will be available through The OpenNMS Group at the OpenNMS training facility in Pittsboro, NC.

If you have anything to add to the events list, please let me know.

See You Next Week

As always, if there’s anything you’d like me to talk about in a future TWiO, or you just have a comment, criticism, or creative knitting technique you’d like to share, don’t hesitiate to say hi. Also, we’ve still got room for more Order of the Blue Polo members if you’d like to send your own testimonial.

Tags: acls, hibernate, rancid, training, wmi