0001475: Refactor the Bandwidth accounting violation process - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001475

PacketFence

core

public

2012-06-21 10:46

2012-07-19 11:09

Reporter

fgaudreault

Assigned To

fgaudreault

Priority

low

Severity

tweak

Reproducibility

N/A

Status

resolved

Resolution

fixed

Platform

OS Version

Product Version

devel

Target Version

Fixed in Version

Summary

0001475: Refactor the Bandwidth accounting violation process

Description

Instead of using sliding window, we should be more precise in the way we calculate the time interval for the bandwidth usage.

Example.
If I define a violation to trap user that are doing more than 20GB/month of bandwidth transfer. Say I hit that limit after 3 days. It should block the user until day 1 of next month if auto-enable if disabled or if auto-enable is enabled, it should start the bandwidth calculation from the violation release date instead of the beginning of the month for the next violation.

Tags

No tags attached.

fixed in git revision

fixed in mtn revision

Attached Files

Relationships

related to	0001474	closed	fgaudreault	Release Date should be added automatically when closing a violation if nothing is specified in the field
related to	0001476	resolved	fgaudreault	Close violation when release_date is reached

Notes
(0002846) fgaudreault (viewer) 2012-07-19 11:09	Fixed in acct_violations branch. Will be merged shortly.

Issue History
Date Modified	Username	Field	Change
2012-06-21 10:46	fgaudreault	New Issue
2012-06-21 10:46	fgaudreault	Relationship added	related to 0001474
2012-06-21 10:57	fgaudreault	Relationship added	related to 0001476
2012-07-19 11:09	fgaudreault	Note Added: 0002846
2012-07-19 11:09	fgaudreault	Status	new => resolved
2012-07-19 11:09	fgaudreault	Resolution	open => fixed
2012-07-19 11:09	fgaudreault	Assigned To	=> fgaudreault