Understanding MIM deployment model and options.

[keyser]

The new MIM is quite interesting, but I would like to understand a little more about the intentions of this feature.

I understand it's not supposed to be a controller service on one particular firewall like in the current preview, but rather a selfcontained deployment package for lots of different platforms (win, Mac, linux, container). So:

1: Does that mean it will go away again as an option for running it on a pfSense instance?
2: Will the products final release require one/more pfSense Plus releases for additional API integration?
3: Will there be a "community version" available fx. limited to 3 pfSense Instances under management?
4: Will the MIM pfSense UI eventually become the standalone pfSense UI as well (replacing the old one)?

I guess Netgate is unlikely to give clear answers on these questions, but please at least post some intentions with some CLEAR disclaimers to avoid misunderstandings.

PS: I hope the question 1 answer is "YES". I think I becomes counterintuitive when the MIM server is one pfSense in the stack, and besides, I don't think centralized services like these should run of a firewall.

[AndyRH]

@keyser said in Understanding MIM deployment model and options.:

I don't think centralized services like these should run on a firewall.

Amen.

[stephenw10]

Indeed. But for demonstration purposes it makes it much easier to start testing and finding bugs.

[AndyRH]

@stephenw10 That is an understandable reason.

[jimp]

There are some relevant points and warnings in the Multi-Instance Management documentation already:

https://docs.netgate.com/pfsense/en/latest/mim/

[keyser]

@keyser Kind of strange that Netgate keeps the cards so close on this product…
I would think the point of MIM is to attract more customers to pfSense (and keep current customers aboard that might be looking for alternatives because of the “missing” MIM).

Why not just answer the 4 questions so we all know what to expect and can plan accordingly?

It’s hardly “subject to changes” or “undiscovered territory” type of questions. They must have debated those points LOTS of times before the product became an actual reality like its starting to become now.