pfSense

This probably can wait until the new carp time comes?

doesn't have any relation to what CARP is on the back end, just needs to be done in general.

Might be time to promote that to its own entry under System or Firewall, "Cluster Sync" or "HA Sync" or something like that, since those settings really don't have anything to do with CARP itself, but pfsync and xmlrpc sync. Could keep the old tab and just have it link to the new location as well for now.

Personally I'm still for coming up with a catchy name for HA/clustering rather than just lumping it all under the "carp" name but I still haven't managed to come up with a new one that doesn't sound childish :-)

And it may be nice to include some settings of "general settings" or "advanced settings":
- proxy settings
- load balancer settings
- firewall optimisation options
- max number of states
- etc..

Probably all settings could be synchronized, except the webgui SSL certificate ?

Pierre

Pierre POMES wrote:

And it may be nice to include some settings of "general settings" or "advanced settings":
- proxy settings
- load balancer settings
- firewall optimisation options
- max number of states
- etc..

Probably all settings could be synchronized, except the webgui SSL certificate ?

That's not related to this kind of change, really. That's expanding functionality. This is just renaming/moving things around with no functional change. If you want to open a separate ticket for that we can look into it, though most of those things probably need to be kept separate. That isn't a discussion for this ticket though.

Indeed, and calling it CARP Settings, IMO, contributes to the continued confusion about where the CARP heartbeats happen. At least once per week I find myself explaining to someone how the heartbeats happen on the interfaces with the VIPs, while the interfaces in the "CARP" settings are just for sync.

• HA Sync.
• Cluster Sync.
• Node Sync.
• Failover Sync. (Though that may be confused with Multi-WAN or server LB)
• Firewall Sync.
• Router Sync.

Might need to take this to one of the mailing lists for other input/votes.

As for the location, I'd vote for the System menu. And at least for one version (maybe two) keep the old tab in that links to the new page.

My 2c, I think 'High Availability Sync' (or HA Sync) best describes the use since pfSync is a protocol which provides HA and XMLRPC is there to provide an automatic sync of the configuration on another host thus best describing the setup as HA again.
A new tab under System->Advanced for that would make sense. The 2 sections could also be split into 2 pages (under System->HA) but a page just for pfSync might just be a waste.

Warren Baker wrote:

My 2c, I think 'High Availability Sync' (or HA Sync) best describes the use since pfSync is a protocol which provides HA and XMLRPC is there to provide an automatic sync of the configuration on another host thus best describing the setup as HA again.

Sounds good to me, or even just "Synchronization", if under System, sort of implies that as well "System > Synchronization" (though that may be too long to fit in the menu)

A new tab under System->Advanced for that would make sense. The 2 sections could also be split into 2 pages (under System->HA) but a page just for pfSync might just be a waste.

IMO think burying it on another tab would be a mistake, it's important enough to have its own menu entry, and it isn't like the System menu (or Firewall for that matter) is overflowing with options. A single page is still OK I think, given that pfsync's options are so few.

Jim P wrote:

Sounds good to me, or even just "Synchronization", if under System, sort of implies that as well "System > Synchronization" (though that may be too long to fit in the menu)

Hrmm yeah maybe even "pfSynchronization" (just to give it a pfSense feel) but probably to large for the menu. I still think High Availability best describes the section and what the options are for, Synchronization implies just syncing of configuration to an end user.
The word doesn't imply that "this is where you configure high availability for your environment".

IMO think burying it on another tab would be a mistake, it's important enough to have its own menu entry, and it isn't like the System menu (or Firewall for that matter) is overflowing with options. A single page is still OK I think, given that pfsync's options are so few.

Single page is fine, i guess if it is broken out into a single page i.e. System -> Synchronization/HA/Whatever then other tabs could be added. What these other tabs could be is another discussion.

do we use /etc/inc/upgrade_config.inc to upgrade the config.xml side?

is there any sort of tool for converting <packagegui> files like carp_settings.xml to a full-up regular page of its own?

Yes for the upgrade.

For the tool it does not exist.