Bonded Internet 3.2 release notes¶

October 29, 2010

Additions¶

Configuration change commands are now executed in an asynchronous queue. This makes the user interface more responsive and enables failed commands to be retried. It uses RabbitMQ and the Celery Python module.
SSL is now used for both the administration interface and XML-RPC.
Forms are more strongly validated. For example, a netmask and gateway must be provided for a leg, unless it runs PPPoE.
The page for a bond has been split in two: one page for viewing the bond details and configuration command status, and one page for editing it.
When editing a bond, a user may click Save (to commit changes and return to the bond details page) or Apply (to save changes and continue editing).
There is an icon for each possible leg state- disabled, up, down, failover, etc.
There is a system information page that shows the version of server software and its major dependencies.
Users can request password resets from the login page.

The list of bonds is no longer split onto multiple pages. Each bond is now listed on a single page.
Most URLs on the configuration server have changed.
Leg icons have been changed and the leg information tooltips now show more information.
When disabling a bond, the user is given a warning about the action and given a chance to cancel it.
Upgraded dependencies on the config server: Django 1.2.3, Grappelli trunk (revision 1265), Python 2.6, and Debian Squeeze.

The server no longer gives errors when submitting more than one new leg at a time, or when submitting empty leg forms.
Bonding no longer hangs when shutting down. It is now killed by the init script if it doesn’t quit after 10 seconds. The init script also has an option to wait instead of killing Bonding, mostly for use on aggregators.
Bonders no longer encounter the “Arptables resource temporarily unavailable” error.
When bonders update their config each hour, the email from cron is suppressed.
Browsers with out-of-date data in forms can no longer overwrite the software version of a bonder in the database.
Numerous small fixes in the administration interface.

When deleting legs, WAN IPs, and routes, the user who submits the change is not logged.
Forms don’t validate data between objects. For example, a user could give a bonder two legs with the same interface.
The configuration file cached on a bonder gets stale when its configuration is changed and before the file is downloaded again by cron.
As a consequence of the cached config file getting stale, the the legids script can report out-of-date information.