Showing posts with label Automation. Show all posts
Showing posts with label Automation. Show all posts

Thursday, October 12, 2017

The Cloudcast #316 - Automating to Improve Cloud Spending

Aaron and Brian talk with Jay Chapel (@parkmycloudjay, Co-Founder/CEO of ParkMyCloud) about the complexity of cloud pricing models, how IT and DevOps teams view spending differently, how to integrate monitoring and automation, and who is critical to making buying decisions in the cloud.

Show Links:

Show Notes
  • Topic 1 - Welcome to the show. Tell us about your background, why you started ParkMyCloud and how you’ve seen the market evolve since you got started (in 2015).
  • Topic 2 - ricing in the public cloud world has gotten both more complicated (e.g. no clouds do it the same way) and simpler (e.g. sustained usage discounts, free tiers, per-second billing, etc.). How do you see the market evolving, and how much of a barrier/burden is pricing “complexity” to public cloud adoption?
  • Topic 3 - You position ParkMyCloud separately for “For DevOps” and “For  IT”. How are you seeing those as two distinct use-cases or types of teams?
  • Topic 4 - ParkMyCloud not only monitors cloud costs and recommends areas for savings, but also includes automated tasks to take advantage of those optimizations. Tell us about the automation capabilities and how your customers get comfortable with that level of control in the platform.
  • Topic 5 - What are you seeing as the public cloud buying process these days? Who is involved, what criteria do they consider, and how do various stakeholders (CFO, Project Managers, Developers) continue to get cost visibility?

Wednesday, October 15, 2014

The Cloudcast #165 - DevOps Automation as a Service

Topic 1 - Tonight is interesting because we are pulling in pieces from a bunch of previous podcasts and past guest topics. We have spoken about the many emerging trends and use cases in DevOps, but a big problem has been how do you put all the pieces together. You hear about Jenkins, Docker, OpenStack, PagerDuty, Loggly, AWS, etc. A lot of moving pieces that we have to integrate together and then actually operate efficiently.

Let’s start at the start, what is the concept of Automation as a Service and what problem are we trying to solve?

Topic 2 - Quote from Blog: "because developers are in charge that every single API must be a first class citizen. They determine whether your API is inadequate very quickly. If you treat your APIs badly by deprecating them suddenly and without warning, you are essentially slapping developers that use your APIs in the face." - Very true. There is a presentation your company did on OpenStack vs. VMware and the idea of closed vs. open with some great analogies to history and advancements in efficient. How does AaaS help developers?

Topic 3 - Third Wave in IT. You present a potential framework:
  1. Docker automating tracking of all dependencies for an environment while providing efficient and very fast to deploy containers; 
  2. Jenkins automating QA testing; 
  3. OpenStack and Docker orienting orchestration solutions 
  4. Monitoring 
  5. StackStorm and others are focusing on automation as a service - Remediation through automation?
Topic 4 - Is AaaS the “glue” between a bunch of existing projects and frameworks to create an automation workflow through change management, remote execution? Not trying to replace Docker, Salt, Ansible, Chef, OpenStack, Jenkins, New Relic? Aren’t all these integrations points a nightmare? Is this an on-prem product, cloud offering?

Topic 5 - You mention machine learning and artificial intelligence. This sounds a bit like what VMturbo tries to do at the hypervisor level. In discussion with them I know getting people flipping the bit that enables full automation makes some folks uncomfortable. They start to think of SkyNet in Terminator and the machines taking over the world. Thoughts?