...
- If creating one EAA for every tenant (logical cluster): micro-services on different edge clouds which are kubernetes clusters should be able to communicate with each other by registering the services to the EAA and consuming the services from the EAA on different edge clouds. For example: μs2 is stateful and needs to communicate with other μs2 on different edge clouds to synchronize the states.
- If creating one EAA for every kubernetes cluster, EAAs need to synchronize the states because EAAs are stateful: The certs of EAAs on different edge clouds has are signed by different Root CACAs which are generated by Openness ansible scripts. What’s more, producing application and consuming application will get certs from EAA and those certs are signed by EAA’s certcerts. And this will cause the producing application and consuming application on different edge cloud can’t communicate with each other because their certs are on different certificate chains. To solve this issue, the certs of EAAs should be signed by the same orchestrator. For example, ICN DCM (Distributed Cloud Manager) can take this role:
https://wiki.onap.org/pages/viewpage.action?pageId=76875956