|
Tree
Augur 4's Configuration Editor looks like a file explorer window.
Each node in the tree structure represents a configurable object,
such as a user, rule group, server, etc.
Permissions
Each node has read/write/browse permissions assigned to owner/group/other,
similar to a Unix filesystem.
So realms of administration responsibility can be enforced.
Intermediate Containers
For large networks, there are several optional
abstraction layers that provide reusable building blocks.
For example, in a small system, individual element patterns can be listed
as a filter.
In a larger network,
an administrator will likely list elements only in
intermediate "locale" groups,
which can be referenced as building blocks to larger locales.
So when elements change or are added/deleted,
there may be only one definition (a small locale)
to update.
|
Concurrent Editing
An unlimited number of administrators
can edit the configuration simultaneously.
Edit "leases" are granted per selected tree branch.
As changes are made to parts of the tree, all other editors
are automatically updated with the latest version.
This system supports distributed administration:
markets can manager their worlds while corporate departments
can manage the national rules,
with minimal coordination.
Change Log
All committed branch changes permanently log the
editing user name, date, and a user-entered description.
This history can be used to document changes,
and help to target any necessary rollback.
Rollback
If a serious configuration problem is discovered,
the configuration can be rolled back to the last good version.
Every saved change is reversible if necessary.
Save/Load Branches
Any arbitrary branch within the configuration tree
can be saved to local disk.
The branch can be stored as a backup,
or emailed elsewhere (e.g. to an administrator, or a support vendor).
The branch can be loaded from disk into the clipboard,
then pasted back into the tree in the configuration editor.
For companies with distributed expertise,
and occasional need to outsource development pieces,
the ability to cut/paste parts will ease the overall
administration burden.
Anecdotal Evidence
Augur is very fast to configure.
For example, consider a cell phone company's proprietary system that
contained over 2,400 unique events.
With Augur, it required only 2 weeks (one developer) to build from scratch.
Configuring the same rules with a leading vendor's proprietary
script-based rules language cost multiple consultants and months of time.
|
Documents