This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 37
Infrastructure
Devis Lucato edited this page Apr 3, 2018
·
2 revisions
The network configuration depends on the way microservices are deployed. Here's a quick summary.
- Microservices need to talk to each other. Provide the URL of the required services using environment variables, e.g.
PCS_IOTHUBMANAGER_WEBSERVICE_URLwith valuehttp://127.0.0.1:9002/v1 - When running the microservices manually from an IDE, Docker or Docker compose, for consistency use the corresponding ports below.
- When running the microservices with Kubernetes, each container has a dedicated IP, so there is no port conflict. Anyway, for consistency, use the corresponding ports below.
- When running the microservices with Mesos/Marathon, let Marathon assign the ports automatically (typically ports 10000+), and use the auto-generated environment variables to populate the microservices configuration.
Public services:
- 9000: PCS WebUI
- 9001: User Management web service
- 9002: IoT Hub Manager web service
- 9003: Device Simulation web service
- 9004: Device Telemetry web service
- 9005: PCS Configuration web service
- 9006: Customer Diagnostics web service
Internal services:
- 9021:
Authentication adapter web service(not used) - 9022: Storage Adapter web service
- 9023: Telemetry Agent web service
- 9024: ASA Manager web service