Geek Answers Handbook

Azure Multiple Public IPs in a Virtual Machine Set Using Resource Manager

We are trying to migrate our platform from the classic IIS host to the service network microservice architecture. Thus, we learned that the service fabric lives on a virtual machine scale and uses a load balancer to communicate with the outside world.

The problem we are facing right now is that we have different access points to our application. As one for the browser, one for the mobile application. Both use the standard https port, but these are different applications.

In iis, we could use host headers for direct traffic for one or another application. But with the service we can’t. the easiest way for us would be to have some public IP addresses. We could handle dns with this. We considered a couple of solutions without success.

  • Load balancer with several public ips. Problem: it seems that this only works with cloud services, and we need to work with the new Resource Manager World there, it seems, it is not possible to have several open ips.

  • Multiple load balancer. Problem: Scale sets are accepted only for the load balancing parameter for load balancing.

  • Application Gateway. It does not seem to support multiple public mapping of IP addresses or hosts.

  • Mapping path. Problem: we have the same path in different applications.

My questions:

- IP- ?

?

, ?

+4
2

ARM Service Fabric IP-. :

  • IP- (, copy) - , IP .
  • :
    • frontendIPConfigurations, IP-
    • loadBalancingRules , , IP- .

, API- HTTP- Windows (. ). , , ( URL) URL- HTTP ( OWIN/ASP.NET Core).

+1

, , Eli: , -, http.sys, VIP, Katana WebListener ASP.NET Core 1.

, Service Fabric, - ServiceManifest.xml. Fabric Windows, , URL- ACL URL-, . , HTTP ServiceManifest.xml, Service Fabric ACL . , Service Fabric "+", , .

, , , netsh URL- ACL .

ServiceManifest.xml, .

+2

More articles:


All Articles