Stelligent Amazon Pollycast
Here are the show notes:
DevOps on AWS News
- AWS Limit monitor – AWS Answers
- Keeping your Secrets Secret – AWS Secrets Manager and AWS CloudFormation to Automate Secrets Management
- Socket.io chat app production ready with Vue.js, DynamoDB, CodePipeline, and CodeBuild
- Dos and Don’ts for DevOps for Automation on AWS-Webinar
- AWS CodeBuild Supports VPC EndPoints
- AWS Machine Learning Blog – Build a serverless frontend for an Amazon SageMaker endpoint
- What is the composition and responsibilities of most teams at Netflix?
- (Build, Deploy, Test, Support, Run)
- (Internal, External, Centralized)
- What is Spinnaker and what’s the benefit you’re providing to customers?
- How has Spinnaker evolved?
- How does Spinnaker run builds?
- How do you provide Spinnaker to the product teams? Consumable service?
- Are other companies using Spinnaker in a similar way? Do you know of other companies like Armory providing a SaaS version of Spinnaker?
- What are the most common open source tools that you’ve developed at Netflix that the Spinnaker team uses internally?
- Open source philosophies at Netflix
- Let’s discuss everyday best practices when it comes to Continuous Delivery, what types of practices do you see most teams embracing?
- (Stop the line, committing often, pairing/reviews, automated canary analysis, production testing, blue/green [red/black], Rolling push, Rolling red/black, Highlander; product teams own lifecycle)
- Why do you deploy regionally at certain points of the day.
- Site reliability, When do teams get notified? How do the centralized teams and individual teams coordinate?
- What’s next in Continuous Delivery?
- Continuous Delivery with Spinnaker Fast, Safe, Repeatable Multi-Cloud Deployments
- How We Build Code at Netflix
- Netflix open source tools:
- Using Spinnaker for automated canary analysis
About DevOps on AWS Radio
On DevOps on AWS Radio, we cover topics around applying DevOps principles and practices such as Continuous Delivery on the Amazon Web Services (AWS) cloud. This is what we do at Stelligent for our customers. We’ll bring listeners into our roundtables and speak with engineers who’ve recently published on our blog and we’ll also be reaching out to the wider DevOps on AWS community to get their thoughts and insights.
The overall vision of this podcast is to describe how listeners can create a one-click (or “no click”) implementation of their software systems and infrastructure on the AWS so that teams can deliver software to users whenever there’s a business need to do so. The podcast will delve into the cultural, process, tooling, and organizational changes that can make this possible including:
- Automation of
- Networks (e.g. VPC)
- Compute (EC2, Containers, Serverless, etc.)
- Storage (e.g. S3, EBS, etc.)
- Database and Data (RDS, DynamoDB, etc.)
- Organizational and Team Structures and Practices
- Team and Organization Communication and Collaboration
- Cultural Indicators
- Version control systems and processes
- Deployment Pipelines
- Orchestration of software delivery workflows
- Execution of these workflows
- Application/service Architectures – e.g. Microservices
- Automation of Build and deployment processes
- Automation of testing and other verification approaches, tools and systems
- Automation of security practices and approaches
- Continuous Feedback systems
- Many other Topics…