Spinnaker is an open source multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence. It is a leading CI/CD tool and provides core feature sets for cluster and deployment management. Created by Netflix and Google, it combines a powerful and flexible pipeline management system with integrations to the major cloud providers. As Spinnaker developed new features and integrations, many of Spot by NetApp customers adopted it as part of their DevOps stack.
While Spot by Netapp allows organizations to reliably and affordably run production environments on spot instances, operation teams always want to be alerted about any events of interest that occur in their environment. Over the last 5 years, Spot by NetApp customers have been using our existing notification mechanism and have shared excellent feedback for various enhancements and new capabilities.
When designing a highly available compute environment one needs to determine the infrastructure layout required for uninterrupted application runtime even in the event of component failure. One key factor to be considered when planning for this is the geographic locations of all relevant resources. One must maintain physical separation between different compute resources with identical roles so that if a single datacenter goes down, applications remain operational.
Chances are if you’re a developer or part of a DevOps team you’ve had a polarizing conversation or two about containers versus serverless. In this post we recap a debate hosted by NetApp on this topic. Arguing for containers is Kevin McGrath, Chief Technology Officer, Spot by NetApp. On the side of serverless is Forrest Brazeal, Director of Content and Community at A Cloud Guru. In this post we will cover the key arguments on both sides. YouTube An error occurred.