Page Comparison

...

1. Client creates logical cloud using logical cloud creation API and the following documents are created in the DCM collection
   • The core module parses the Json and creates a new document for the logical cloud in the mongodb DCM collection.
   • The core module also creates a cluster document in the DCM collection
   • The user module parses the Json and creates a new document for user 
   • The namespace module parses the Json and creates a new document for namespace
2. Associates logical cloud with clusters (this API is called multiple times)Add quota for logical cloud
   • The
   client talks to the core module  and at each step the core module calls the specific modules which then take the information and store it in the required section in the database. For examle, the namespace module will store the namespace for the logical cloud in the DB.
   • core module uses the traffic controller library to get the kubeconfig of the cluster added to the logical cloud
   • Updates the cluster document with the cluster name, loadbalancer ip and kubeconfig of the cluster
3. Add quota for logical cloud
   • The quota module creates a quota document containing the quota details
4. Apply API is called
   • Service mesh module gets CA bundle from CA controller
   • Service mesh module gets names of logical cloud and creates a new namespace name using name of logical cloud name
   • Service mesh module creates helm template/istioctl
   manifest and stores it in the database with the namespace to use
   • manifest 
   • Service mesh module creates
   k8s coredns file for coredns of control plane for each cluster i.e, there is a coredns deployment file, configmap, service account etc for each cluster per control plane (logical cloud)
   • service mesh document in the DCM collection and stores the above (CA bundle contents, istio namespace, istioctl manifest) in the document
5. DCM informs the resource synchronizer to start the logical cloud creation via gRPC and the resource synchronizer starts reading from the DB
6. The DCM gets status from the resource synchronizer via gRPC

...