@iNecas@Marek_Hulan So I’ve left it a month on the support/users forum section, User Survey: Supporting HA Smart Proxies, it doesn’t seem like anyone has been forthcoming with feedback, I’m not sure why maybe its because the subject is fairly complicated, maybe its because nobody cares
Anyway, I purpose we move ahead with this, I think it’s fair to say most are onboard with this implementation.
TBH, there are still some gaps in my understanding on how the re-designed version will look look, and especially, how the user interaction will look like.
Could you prepare a deep-dive, that would go again through the proposal, but focus at the differences in the workflow, both in UI and CLI, before and after the change. I’m interested in two scenarios:
a user that wants to have the HA smart proxies
a user that doesn’t want any HA
Looking at this from user perspective can hopefully put more lights at this also for the users to see what this proposal is about.
Let’s make it a panel? Based on this thread, I think we’d need @sean797, @iNecas, @lzap and @Marek_Hulan? I’ll figure out a time we can all make and we can discuss it in (virtual) person
One note while I am working on a customer request: Can we support IP addresses as smart proxy pool names? They have an environment without DNS and setting that up today is tricky. This could support it from the day one maybe. Just a thought.
Yes! That’s one of the nice things about smart proxy pools, they are no constrained. Smart Proxy URLs rightly have constraints because they are used for foreman <-> proxy communication, but smart proxy pools are free!
It’ll just require the certificate to validate it subjectAltName = IP:10.0.0.10