...
5. At this moment, orchestrator can start to monitor and manage the life-cycle of traffic controller.
controller. And the way/APIs of monitor and manage need to be clarified. (Is HA is required for traffic controller?)
6. The requests from users/admin can be sent to traffic controller from now on.
users/admin are allowed to send their request to running uServices directly by REST.
7of monitor and manage need to be clarified.
(Is HA is required for traffic controller?)
6. Users/admin are allowed to send their request to create uServices or access the running
uServices directly via REST, like the inbound/client services creation. After traffic controller
convert the intents to service description, the generated yml files which will be used by istio
to create uSevices should be given to workload scheduler/placement helper to place and
instantiate these uService on edge cloud clusters. Namely, traffic controller need to inform
the workload scheduler/placement helper that there are some uServices to be placed and
instantiated on edge cloud clusters.
7. Traffic controller need to call DNS module to expose the domain names of services to external world,
after it is aware of these uServices have been instantiated on edge cloud clusters. (how is traffic controller
aware of the accomplishment of of uServices instantiation?)
8. Traffic controller may need to manage the lifecycle of uServices (or done by some modules within orchestrator?)
by a way e.g. detecting the heartbeat from various uServices periodically e.g. one check per 10 seconds.
89. Considering the HA, traffic controller should instantiate at least 2 of those plugins, and should be
able to monitor the health of those instances of plugins. when any of instances is down, traffic controller
can restart/recreate one for it again.
...