In this episode, Paul Duvall speaks with VP of Engineering & Delivery Casey Lee on a brief preview of next months episode. Casey touches on some of the new features and updates added to open-source, full-stack DevOps on AWS tool mu. Paul Duvall also speaks with James Martin, an Automation Engineering Manager at 3M HIS on team structure, his philosophies behind choosing services, and some lessons learned.
Here are the show notes:
Episode Topics
- What’s new with mu, with Casey Lee
- James Martin intro and background
- Describe 3M HIS
- Team Structure – evolution to automation and product teams
- Tooling – Deployment Pipeline Factory
- Philosophy – Service-Full Architecture (AWS Managed Services) and Why?
- Tooling – AWS Service Catalog
- Blue/Green Deployment
- Team governance
- Speeding up Feedback loops
- Accelerate, Nicole Forsgren
- Identifying Bottlenecks
- Tips and recommendations
- Out of Jenkins to CodeBuild
- Lessons Learned
Additional Resources
- James Martin | LinkedIn, Twitter
- Casey Lee | LinkedIn, Twitter
- Paul Duvall | LinkedIn, Twitter
- GitHub: 3M-Company/ aws-pipeline-dashboard
- 3M Health Information Systems Provisions Development Pipelines in Minutes Using AWS Service Catalog
- How 3M HIS Uses AWS Service Catalog to Flatten the Learning Curve for Continuous Delivery
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 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 in the Amazon Web Services cloud 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…
|
Stelligent Amazon Pollycast
 |
