azure-service-fabric

I have a service fabric cluster deployed with a domain of foo.northcentralus.cloudapp.azure.com It has a single node type with a single public ip address / load balancer. Lets say I have the following two apps deployed: http://foo.northcentralus.cloudapp.azure.com:8101/wordcount/ http://foo.northcentralus.cloudapp.azure.com:8102/visualobjects/ How can I set this up so I can have multiple domains each hosted on port 80? (assuming I own both of these domains obviously) http://www.wordcount.com http://www.visualobjects.com Do I need more than one public ip address in my cluster to support this?

I am trying to upgrade my Service Fabric application via Visual Studio. I ended up having to use the diff package approach to ensure that only the services I change are in the upgrade. I did this via a command file which removed the non-required files. Now I have walked into another error which is annoying with its lack of detail: Start-ServiceFabricApplicationUpgrade : Default service descriptions can not be modified as part of upgrade. Modified 2>default service: fabric:/MYAPPLICATION/MYSERVICE. To allow it, set 2>EnableDefaultServicesUpgrade to true. Where exactly do I put this? Please note

I would like to use ASP.NET Core's default DI container to setup DI for my Service Fabric project. //This is what I've got so far, and it works great ServiceRuntime.RegisterServiceAsync( "MyServiceType", context => new MyService(context, new MyMonitor() ).GetAwaiter().GetResult(); //This is how I use it public MyService(StatefulServiceContext context, IMonitor myMonitor) : base(context) { this._myMonitor = myMonitor; } How would I set up DI, if MyMonitor class has a dependency on a ConfigProvider class, like this: public MyMonitor(IConfigProvider configProvider) { this._configProvider =

I've created a stateless service within Service Fabric. It has a SingletonPartition, but multiple instances (InstanceCount is -1 in my case). I want to communicate with a specific replica of this service. To find all replica's I use: var fabricClient = new FabricClient(); var serviceUri = new Uri(SERVICENAME); Partition partition = (await fabricClient.QueryManager.GetPartitionListAsync(serviceUri)).First(); foreach(Replica replica in await fabricClient.QueryManager.GetReplicaListAsync(partition.PartitionInformation.Id)) { // communicate with this replica, but how to construct the proxy? //var

How can I pass along auditing information between clients and services in an easy way without having to add that information as arguments for all service methods? Can I use message headers to set this data for a call? Is there a way to allow service to pass that along downstream also, i.e., if ServiceA calls ServiceB that calls ServiceC, could the same auditing information be send to first A, then in A's call to B and then in B's call to C? yoape There is actually a concept of headers that are passed between client and service if you are using fabric transport for remoting. If you are using

I'm trying to get a little follow up to this question that's already been answered... Service Fabric multi-tenant If I were to setup my tenants as Azure Service Fabric Stateless Services (they'll get their state out-of-band), how can I put more than one tenant on each node in the cluster? In testing, it seems that Service Fabric gags if you try and make your instance count greater than the node count. These tenants are very lightweight, so I should be able to run dozens of them on each node (we will have hundreds overall), and I don't want to have to do a node for each one. Specifically, the