2014 was another year of transition for Garmin. Not only is the industry in flux with its devops and microservice methodologies, but so too is Garmin itself transitioning from a hardware company to a software company. We will take you on our journey as we have lived it. Our mistakes laid bare, our achievements held high, we will show you how we designed, architected and delivered Cloud Foundry to our production developers in under 2 weeks. Architectural Overview: A walkthrough of our attempt to do an active/active, multi-datacenter integration with two discrete Cloud Foundry installations using Akamai and F5 to seamlessly load balance for redundancy and high availability. Next up? Multiple availability zones per datacenter for even more redundancy. Integration and Implementation: What do you do when your developers don’t want to change their code to fit the Cloud Foundry standard url convention? Intercept and rewrite it, of course! We’ll also show you one method of using both Cloud Foundry applications and legacy applications in one big Prod farm using the F5 Load balancer. Monitoring Cloud Foundry Components: Alerting through Solarwinds and detailed metric analysis through VRealize Operations, we’ll walk you through our first attempt at understanding the internals of Cloud Foundry and how to make sure we have the tools necessary to troubleshoot when there is an issue as well as accurately scale and size our Cloud Foundry foundations for the future.
Monitoring Cloud Foundry Applications: We’ll also discuss the challenges found applying an established AppDynamics monitoring process to Cloud Foundry and how we worked with both AppDynamics and Pivotal to overcome those issues.
Logging (will complete later w/ Tylers help): - Changes to how we feed logs into Splunk - Legacy apps are all file-based
Service Bindings & Brokers: We’ll talk about our the considerations and conclusions we came to around service bindings. When/where User Provided Services make sense vs writing Custom Service Brokers
CI/CD Current & Future State: Garmin has long been a CI shop. Our goal is to be fully CI/CD and we will talk about our roadmap to get there
Green Field vs. Legacy Migration: We will discuss the factors we considered for an app to be eligible to run in the cloud