Showing posts with label SLAs. Show all posts
Showing posts with label SLAs. Show all posts

Wednesday, May 22, 2019

How Big is your Public Cloud bill?

SHOW: 399

DESCRIPTION: Aaron and Brian continue the "Four for Four Hundred" shows, with a focus on following the money in cloud computing. Then Brian talks with Corey Quinn (@QuinnyPig, Cloud Economist @ Duckbill Group) about the economic realities of being all-in on the public cloud.

SHOW SPONSOR LINKS:

SHOW INTERVIEW LINKS:

SHOW NOTES:

Topic 1 - Welcome back to the show. You’ve become a multi-media star since your last appeared (newsletter, podcasting, stand-up comedy, co-hosting theCUBE, live blogger, etc.). 

Topic 2 - In case you haven’t noticed, revenues in the public cloud have grown quite a bit in the last few years. And not a day goes by without some web company announcing their monthly AWS spend. Walk us through the world of an organization that is a reasonably heavy spender in the public cloud. Are there steak dinners and rounds of golf still involved? 

Topic 3 - We hear about long-term contracts being negotiated with public cloud providers. How do these negotiations go, and where are customer’s leverage points?

Topic 4 - What are the typical stages of Cloud Adoption and Cloud Grief? 

  • Excitement - bypass IT, everything seems cheap
  • Curiosity - so many new services to explore and use
  • Confusion - so many services, they don’t all fit on the dashboard, where are the neglected services running?
  • Fear - the bills come in and they are more than we expected

Topic 5 - Do you find that legacy IT is actually brought along on the journey to large-scale public cloud usage? If so, what is the transition process for people/groups used to CAPEX and Hardware and ELAs and Data Centers? 

FEEDBACK?

Thursday, March 28, 2019

Real-World SRE Perspectives

SHOW: 391

DESCRIPTION: Brian talks with Gustavo Franco (@stratus, Customer Reliability Engineer at Google) about real-world experience as SRE/SRE Manager and CRE Manager, a discussion about how to measure SRE success, as well as how to onboard the SRE/CRE concepts and processes to new teams. 

SHOW SPONSOR LINKS:

CLOUD NEWS OF THE WEEK:

SHOW INTERVIEW LINKS:

Gustavo's Background: https://conferences.oreilly.com/velocity/vl-ca/public/schedule/speaker/150125

SHOW NOTES:

Topic 1 - Welcome to the show. Tell us about your background, and some of the things you work on today as it relates to SRE and CRE teams. 

Topic 2 - Let's talk about what SRE is intended to do, and maybe how it differs (or is the same) from existing teams that might be labeled "Ops" or "DevOps". Maybe we can also talk about some of the types of skills that highlight what SRE does.

Topic 3 - What are some of the ways to avoid an SRE (or CRE) team just becoming the band-aid team to fix all the things that developers don't want to put into code because they are under deadlines (security, bug fixed, scalability, etc.)?

Topic 4 - We're hearing more about these terms "AIOps" and "ChaosEngineering". How much can SRE/CRE teams augment applications through tools that either bring deeper insight (e.g. AIOps) or create scenarios that developers can't emulate (e.g. Chaos)?

Topic 5 - You've been around SRE/CRE for a while now. What are some of the positive and negative lessons you've learned and could share with the audience?

FEEDBACK?