search

inverse-inc / packetfence

PacketFence is a fully supported, trusted, Free and Open Source network access control (NAC) solution. Boasting an impressive feature set including a captive-portal for registration and remediation, centralized wired and wireless management, powerful BYOD management options, 802.1X support, layer-2 isolation of problematic devices; PacketFence can be used to effectively secure networks small to very large heterogeneous networks.
https://packetfence.org
GNU General Public License v2.0
1.3k stars 276 forks source link

Implementing update engine #4086

Closed simbazad closed 5 years ago

simbazad commented 5 years ago

Hi All, Would you consider merging implementation of an update engine? Something like https://github.com/mendersoftware/mender

julsemaan commented 5 years ago

Like as a provisioner or scan engine you mean ?

simbazad commented 5 years ago

Like as a provisioner or scan engine you mean ?

No, i mean implementing an update engine which will update packetfence to a new version when available without the current complication (migrate scripts , database migration , configuration migration ...)

julsemaan commented 5 years ago

Although we'd be interested in doing easier updates, I believe that this work should be done by the Inverse team and not an external contributor given the very complex nature of it especially when considering the clusters.

I don't think we'll use something as complex as what you suggested and we'll probably adjust our packaging to do the upgrade steps during the "yum update" process

simbazad commented 5 years ago

@julsemaan Sure ! , Just keep in mind that implementing something like https://github.com/mendersoftware/mender isn't that hard and its definitely worth it (they even implemented quite clever rollback logic)