0001144: active-active clustering support - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001144

PacketFence

core

public

2010-12-21 13:36

2015-02-13 15:42

Reporter

fgaudreault

Assigned To

Priority

normal

Severity

feature

Reproducibility

N/A

Status

closed

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0001144: active-active clustering support

Description

Explore the potential that PF can run in an active-active cluster setup. This will probably need some in-depth changes in the code (ie. How do you determine which PF handles administrative tasks?, What happens with the SNORT alerts?, etc). However, the basic functionality such as handle traps, assign VLAN using Radius, should be able to work as-is. We will need to test that at some point.

This mode is likely to target PF running on virtual environments rather than physical environments.

Potential Solutions :
- Primary/Primary DRBD (for PF and data) using a cluster-aware filesystem (OCFS2 or GFS).
- Multi-Master MySQL replication (for data)

We will start building something in the LAB for that using an HAProxy Load Balancer.

Tags

No tags attached.

fixed in git revision

fixed in mtn revision

Attached Files

Relationships

Notes
(0001798) fgaudreault (viewer) 2010-12-22 17:16	I worked on this topic, and I found interesting possibilities : - LVS using Direct Routing (Keepalived) with 3 VIPs - One for Management (Radius/SNMP/Admin UI) - One for Registration (HTTP/DNS) - One for Isolation (HTTP/DNS) - 2 x PF server running - MySQL Master-Master replication I am able to register devices, but having issues with the Foreign key constraints if a PF server restart. Still a work in progress, but it is moving in a very positive way.

(0002280) obilodeau (reporter) 2011-09-21 23:25	changing severity, this is definitely not a tweak! :)

(0003839) lmunro (administrator) 2015-02-13 15:42	These bugs have been sitting untouched since 2012. Closing them and possibly reopening in github tracker where relevant.

Issue History
Date Modified	Username	Field	Change
2010-12-21 13:36	fgaudreault	New Issue
2010-12-22 17:16	fgaudreault	Note Added: 0001798
2011-09-21 22:08	obilodeau	Target Version	3.0.0 => +2
2011-09-21 23:25	obilodeau	Note Added: 0002280
2011-09-21 23:25	obilodeau	Severity	tweak => feature
2012-02-29 10:58	obilodeau	Category	future => core
2015-02-13 15:42	lmunro	Note Added: 0003839
2015-02-13 15:42	lmunro	Status	new => closed