DZone
Cloud Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Cloud Zone > Azure Service Fabric Cluster Behind a Firewall

Azure Service Fabric Cluster Behind a Firewall

Hosting a Service Fabric cluster on Azure for internet-hosted clients requires it to be deployed behind a load balancer with public IP. By default, the services will not have any network listeners configured; so, each service needs to implement its own listener by overriding CreateCommunicationListener() defined in StatefulServiceBase and StatelessServiceBase classes. Read on and see how it's done.

Hanu Kommalapati user avatar by
Hanu Kommalapati
·
Mar. 15, 16 · Cloud Zone · Tutorial
Like (1)
Save
Tweet
2.56K Views

Join the DZone community and get the full member experience.

Join For Free

Hosting a Service Fabric cluster on Azure for internet-hosted clients requires it to be deployed behind a load balancer with public IP. By default, the services will not have any network listeners configured; so, each service needs to implement its own listener by overriding CreateCommunicationListener() defined in StatefulServiceBase and StatelessServiceBase classes. The signature is shown below:

protected override ICommunicationListener CreateCommunicationListener() { ... } 

See Service Communications Model for guidance on implementing your own communications stack.

WcfCommunicationListner is provided by the Service Fabric SDK for hosting WCF endpoints inside stateful and stateless services. The usage of the listener is documented at WCF Communication Listener.

Current implementation of WcfCommunicationListener is not aware of the public IP address/FQDN; so, for NetTcpBinding it generates the following communication endpoint with private IP address:

net.tcp://10.0.0.5:8080/7854ce3f-4e30-4949-b5e4-22cdcbd477c1/8f4106a5-0d38-4f30-aaf0-e435688e5ed6-130808019994632301 

This will work fine if the client is also located in the same network; however, for internet based access, the local IP address will have to be replaced with the load balancer’s public IP/FQDN.

To fix this issue, I used the following listener implementation that extended WcfCommunicationListener:

//WcfFabricCommunicationsListener.cs  
using Microsoft.ServiceFabric.Services.Wcf; 
using System; 
using System.Collections.Generic;   
using System.Linq;  
using System.Text;  
using System.Threading.Tasks;  
using System.Fabric;  
using System.Threading;  
using System.ServiceModel;  
using System.ServiceModel.Description;  
public class WcfFabricCommunicationsListener: WcfCommunicationListener 
{ 
  private string _gatewayFQDN; 
  public WcfFabricCommunicationsListener(Type communicationInterfaceType, object service) : base(communicationInterfaceType, service) { } 
  public WcfFabricCommunicationsListener(Type communicationInterfaceType, Type communicationImplementationType) : base(communicationInterfaceType, communicationImplementationType) { }  
  public override void Initialize(ServiceInitializationParameters serviceInitializationParameters)  
  {  
     ConfigurationPackage configPackage = serviceInitializationParameters.CodePackageActivationContext.GetConfigurationPackageObject("Config");  
     var infrastructureSection = configPackage.Settings.Sections["Infrastructure"];  
     _gatewayFQDN = infrastructureSection.Parameters["Gateway"].Value;  
     base.Initialize(serviceInitializationParameters);  
}  
public async override Task<string> OpenAsync(CancellationToken cancellationToken)  
{  
  string partitionUrl = await base.OpenAsync(cancellationToken);  
  if (_gatewayFQDN == null)  
  {  
   return partitionUrl;  
  }  
  UriBuilder ub = new UriBuilder(partitionUrl);  
   ub.Host = _gatewayFQDN;  
   return ub.ToString(); 

  } 
}

Initialize() expects the definition of the FQDN of the gateway through Config package as shown in the following snippet of Settings.xml: <!– Settings.xml located in the Config directory of the service project –>

<Settings>  
<!– other stuff –>  
   <Section Name=”Infrastructure”>  
   <Parameter Name=”Gateway” Value=”mycluster.cloudapp.net” />  
  </Section>  
</Settings>

OpenAsync() merely replaces the host IP address with the FQDN of the load balancer.

cluster azure Firewall (computing)

Published at DZone with permission of Hanu Kommalapati, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Roles in Data Science Teams
  • The Difference Between Artificial Intelligence, Machine Learning, and Deep Learning
  • API Security Weekly: Issue 173
  • How to Integrate a Distributed Database With Event Streaming

Comments

Cloud Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo