List view
Deploy services across both the IU and TACC instances of Jetstream Note it is not a good idea to try to spread a Kubernetes cluster across two data centers. Using concepts presented in class, show how you can failover to TACC with no disruption of services if all your IU VMs go down. This may be caused by a network failure. Using concepts discussed in class, show how you use TACC and IU for “blue-green” deployments. Show that you can switch from IU (blue) to TACC (green) while keeping IU online Show that you can switch back to IU without loss of messages, state, etc. You would need to do this if you found a bug in your “green” deployment after testing and needed to switch back to “blue” Summarize your learnings. Include also descriptions of architectural changes you needed to make to complete the assignment.
Overdue by 5 year(s)•Due by April 30, 2021•5/5 issues closed- Jmeter Load & Performance Testing - Spike Testing - Fault Tolerance
Overdue by 5 year(s)•Due by April 14, 2021•4/4 issues closed- Dockerizing services - Implementing CI/CD using Jenkins & Kubernetes cluster on IU Jetstream cloud instances
Overdue by 5 year(s)•Due by March 28, 2021•18/18 issues closedImplementing each microservice in a polyglot environment.
Overdue by 5 year(s)•Due by February 21, 2021•10/10 issues closedDeliverables: 1] README 2] Architecture Diagram 3] Napkin Diagram 4] Adding Milestone1 Page into Wiki 5] UX Design 6] User journey Diagram
Overdue by 5 year(s)•Due by February 7, 2021•17/17 issues closed