pfSense

Jim Pingle wrote:

Having any kind of fully automated update function is very dangerous. Since the process can be triggered from the console/ssh, if you want to script something for your own use, feel free, but it is unlikely to be crafted as a built-in function.

Thank you for looking into this. To be more clear. I'm not searching for a fully automatic update/ upgrade. I still want it to be started manually each time. The only part is that i want it to run within 12 hours from now so there is no or less impact on the business. What i have in mind is that i can go to the version update page and hit update after xyz (drop down with 12 options, eacht stands for one hour).
The second part is an updation that if it is a cluster or master/ slave setup that i have to option to update this unit first or the second unit first. Then install only one and after that is back again and the update is finished it starts to update the other one.

So in short, not looking for a automated update at all time option but a delayed install/ upgrade option without a user interaction at that delayed time.

That is still very dangerous. An upgrade should always be directly monitored by the admin in case it does not go as planned.

And again, you could script that remotely. For example, set an at/cron job on a management workstation which connects via ssh and runs the upgrade.

It's not something that would likely be included in the GUI as it's not a practice that should be encouraged.

Jim Pingle wrote:

That is still very dangerous. An upgrade should always be directly monitored by the admin in case it does not go as planned.

And again, you could script that remotely. For example, set an at/cron job on a management workstation which connects via ssh and runs the upgrade.

It's not something that would likely be included in the GUI as it's not a practice that should be encouraged.

I cannot see the danger. Now we don't have this option the system reboots on not wished moments and the cluster is not updated as cluster. To reffer to other update and upgrades, we update our core routers and switches (500+) each 4 months and we stay in bed as our monitoring tool wakes us up if needed. In case stuff don't go as planned i understand the issues that can occur but that is up to the one that uses this option. Also using features of the pfsense box can give dangerous behavior. i can change bgp core routes etc. I understand that things needs to be done if they make sense, thats why we call it pfsense ;-) but because it feels dangerous it don't have to be dangerous. Using an option to always update and upgrade feels more dangerous but even with that, a lot of other brands are now on a ongoing release and always update/ upgrade strategy.

I know we can cron etc. but that is more danger as not all sysadmins now that as wel as the gui.

I think it is a practise that schould be encouraged. Even more, i would like to see a central pfsense management tool to manage a bulk load of pfsense units that we also can update/ upgrade central.

It is greate to discuss this option, as i'm convinced that this can be a major usability improvement that we are waiting for for a couple of years.