architecture-analysis
architecture-analysis copied to clipboard
sodafoundation
Multi Cloud HA Analysis
What type of PR is this?
Uncomment only one
/kind <>line, hit enter to put that in a new line, and remove leading whitespace from that line:
Analysis of HA for Multi Cloud.
What this PR does / why we need it: Provided Analysis of HA for Multi cloud
Which issue(s) this PR fixes:
Fixes #
Test Report Added?: NA
Test Report:
Special notes for your reviewer:
@rajat-soda Do we finalize to go Kubernetes way or is there any data point for comparison?
@rajat-soda Do we finalize to go Kubernetes way or is there any data point for comparison?
@kumarashit : As discussed in the meeting on 3rd, it was concluded that we do the PoC with kubernetes. Not sure what the plan beyond the PoC
Overall, it seems very high level, recommend to get into current design level and functional details now, else it will blow up during execution...in case of a HA solution (given that you do not want server to fail and they rarely fail for HA to kick in), achieving a balance of effort+cost vs. ROI (when that rare failure happens) is quite complex
@rajat-soda is it possible to keep this in the template for architecture-analysis?
@rajat-soda is it possible to keep this in the template for architecture-analysis?
The Analysis doc doesn't entirely fit into the design doc format..as it's more of a deployment and lift n shift of services to K8s. Along with comparative study of k8s vs other solutions So not sure if the Analysis doc really fits into the template
@rajat-soda we need to update at least the architecture diagram (most of them), as the focus project multi-cloud is not really marked well. Also NBP missing, drivers are marked as plugins...so it is not consistent with the existing arch. So can confuse readers. We need to update before the merge.
@rajat-soda we need to update at least the architecture diagram (most of them), as the focus project multi-cloud is not really marked well. Also NBP missing, drivers are marked as plugins...so it is not consistent with the existing arch. So can confuse readers. We need to update before the merge.
Ok, will do