forked from ThreeMammals/Ocelot
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make Ocelot work with service fabric DNS and naming service for guest…
… exe and stateless (ThreeMammals#242) * test for issue * added service fabric sample * working!! * changed sample naming to Ocelot * removed files we dont need * removed files we dont need * updated sample gitignore * updated sample gitignore * getting ocelot to work with service fabric using the reverse proxy * ThreeMammals#238 - added support for service fabric discovery provider, proxies requests through naming service, wont work on partioned service fabric services yet * ThreeMammals#238 - Manually tested service fabric using sample..all seems OK. Made some changes after testing, added docs * ThreeMammals#238 - added docs for servic fabric
- Loading branch information
1 parent
9cb25ab
commit 454ba3f
Showing
71 changed files
with
2,394 additions
and
484 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
Service Fabric | ||
============== | ||
|
||
If you have services deployed in Service Fabric you will normally use the naming service to access them. | ||
|
||
The following example shows how to set up a ReRoute that will work in Service Fabric. The most important thing is the ServiceName which is made up of the | ||
Service Fabric application name then the specific service name. We also need to set UseServiceDiscovery as true and set up the ServiceDiscoveryProvider in | ||
GlobalConfiguration. The example here shows a typical configuration. It assumes service fabric is running on localhost and that the naming service is on port 19081. | ||
|
||
The example below is taken from the samples folder so please check it if this doesnt make sense! | ||
|
||
.. code-block:: json | ||
{ | ||
"ReRoutes": [ | ||
{ | ||
"DownstreamPathTemplate": "/api/values", | ||
"UpstreamPathTemplate": "/EquipmentInterfaces", | ||
"UpstreamHttpMethod": [ | ||
"Get" | ||
], | ||
"DownstreamScheme": "http", | ||
"ServiceName": "OcelotServiceApplication/OcelotApplicationService", | ||
"UseServiceDiscovery" : true | ||
} | ||
], | ||
"GlobalConfiguration": { | ||
"RequestIdKey": "OcRequestId", | ||
"ServiceDiscoveryProvider": { | ||
"Host": "localhost", | ||
"Port": 19081, | ||
"Type": "ServiceFabric" | ||
} | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.