i didnt find information these issues regarding azure internal load balancer:
- adding inputendpoint lead ilb created not being accessible or functional
- using “only” ilb definition lead public default inputendpoint vanishes
- not transparent how long takes until ilb available. however, visible viewing available port cloud services web role. if public port available, ilb not, , vice versa.
so these questions:
- is expected behavior internal load balancer replaces public one?
- is public load balancer supported beside internal one/ can have public access web roles controlled internal load balancer?
- are multiple ports supported (e.g. https beside http or private/ public access)?
some details: internal load balancer connected via fixed ip vpn cloud service. configuration looks this:
<?xml version="1.0"?> <servicedefinition name="mycloudtest" xmlns="http://schemas.microsoft.com/servicehosting/2008/10/servicedefinition" schemaversion="2014-06.2.4"> <webrole name="mywebrole" vmsize="standard_d1"> <runtime executioncontext="elevated" /> <sites> <site name="web"> <bindings> <binding name="ilb-endpoint-http" endpointname="ilb-endpoint-http" /> <!--<binding name="ilb-endpoint-https" endpointname="ilb-endpoint-https" />--> <!--<binding name="public-http-binding" endpointname="public-http-endpoint" />--> </bindings> </site> </sites> <endpoints> <!--<inputendpoint name="public-http-endpoint" protocol="http" port="81" />--> <inputendpoint name="ilb-endpoint-http" protocol="http" localport="8080" port="8080" loadbalancer="my-ilb" /> <!--<inputendpoint name="ilb-endpoint-https" protocol="https" localport="*" port="8443" loadbalancer="my-ilb" />--> </endpoints>
this part of serviceconfiguration defining ilb pointing vpn fixed ip.
<networkconfiguration> <virtualnetworksite name="myvpn" /> <addressassignments> <instanceaddress rolename="mywebrole"> <subnets> <subnet name="intra" /> </subnets> </instanceaddress> </addressassignments> <loadbalancers> <loadbalancer name="my-ilb"> <frontendipconfiguration type="private" subnet="intra" staticvirtualnetworkipaddress="172.28.0.27" /> </loadbalancer> </loadbalancers>
every hint highly appreciated.
1.is expected behavior internal load balancer replaces public one?
it same implementation ilb restricted own private space (your vnet) see https://azure.microsoft.com/en-us/documentation/articles/load-balancer-overview/
2.is public load balancer supported beside internal one/ can have public access web roles controlled internal load balancer?
yes can have both in same deployment
3.are multiple ports supported (e.g. https beside http or private/ public access)?
you can add multiple endpoints. endpoint has public port , private port. multiple public ports cannot share same private port
Comments
Post a Comment