PacketFence - BTS - PacketFence
View Issue Details
0001144PacketFencecorepublic2010-12-21 13:362015-02-13 15:42
fgaudreault 
 
normalfeatureN/A
closedopen 
 
 
0001144: active-active clustering support
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.
No tags attached.
Issue History
2010-12-21 13:36fgaudreaultNew Issue
2010-12-22 17:16fgaudreaultNote Added: 0001798
2011-09-21 22:08obilodeauTarget Version3.0.0 => +2
2011-09-21 23:25obilodeauNote Added: 0002280
2011-09-21 23:25obilodeauSeveritytweak => feature
2012-02-29 10:58obilodeauCategoryfuture => core
2015-02-13 15:42lmunroNote Added: 0003839
2015-02-13 15:42lmunroStatusnew => closed

Notes
(0001798)
fgaudreault   
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   
2011-09-21 23:25   
changing severity, this is definitely not a tweak! :)
(0003839)
lmunro   
2015-02-13 15:42   
These bugs have been sitting untouched since 2012.
Closing them and possibly reopening in github tracker where relevant.