BROADCASTS.com

b'How do you encourage businesses to pick Google Cloud over Amazon and other providers? How do you advocate for selecting Google Cloud to be successful on that platform? Google Cloud is not just a toy with fun features, but is a a capable Cloud service.\\nToday, we\\u2019re talking to Seth Vargo, a Senior Staff Developer Advocate at Google. Previously, he worked at HashiCorp in a similar advocacy role and worked very closely with Terraform, Vault, Consul, Nomad, and other tools. He left HashiCorp to join Google Cloud and talk about those tools and his experiences with Chef and Puppet, as well as communities surrounding them. He wants to share with you how to use these tools to integrate with Google Cloud and help drive product direction.\\nSome of the highlights of the show include:\\n\\nStrengths related to Google Cloud include its billing aspect. You can work on Cloud bills and terminate all billable resources. The button you click in the user interface to disable billing across an entire project and delete all billable resources has an API. You can build a chat bot or script, too. It presents anything you\\u2019ve done in the Consul by clicking and pointing, as well as gives you what that looks like in code form. \\nYou can expose that from other people\\u2019s accounts because turning off someone else\\u2019s Website as a service can be beneficial. You can invite anyone with a Google account, not just \\u2018@gmail.com\\u2019 but \\u2018@\\u2019 any domain and give them admin or editor permissions across a project. They\\u2019re effectively part of your organization within the scope of that project. For example, this feature is useful for training or if a consultant needs to see all of your different clients in one dashboard, but your clients can\\u2019t see each other.\\nGoogle is a household name. However, it\\u2019s important to recognize that advocacy is not just external advocacy, there\\u2019s an internal component to it. There\\u2019s many parts of Google and many features of Google Cloud that people aren\\u2019t aware of. As an advocate, Seth\\u2019s job is to help people win. \\nBesides showing people how they can be successful on Google Cloud, Seth focuses on strategic complaining. He is deeply ingrained in several DevOps and configuration management communities, which provide him with positive and negative feedback. It\\u2019s his job to take that feedback and convert it into meaningful action items for product teams to prioritize and put on roadmaps. Then, the voice of the communities are echoed in the features and products being internally developed.\\nAmazon has been in the Cloud business for a long time. What took Google so long? For a long time, Google was perceived as being late to the party and not able to offer as comprehensive and experienced services as Amazon. Now, people view Google Cloud as not being substandard, but not where serious business happens. It\\u2019s a fully feature platform and it comes down to preferences and pre-existing features, not capability.\\nSmall and mid-size companies typically pick a Cloud provider and stick with their choice. Larger companies and enterprises, such as Fortune 50 and Fortune 500 companies, pick multiple Clouds. This is usually due to some type of legal compliance issues, or there are Cloud providers that have specific features. \\nExternally at Google, there is the Deployment Manager tool at cloud.google.com. It\\u2019s the equivalent of CloudFormation, and teams at Google are staffed full time to perform engineering work on it. Every API that you get by clicking a button on cloud.google.com are viewing the API Docs accessible via the Deployment Manager. \\nGoogle Cloud also partners with open source tools and corresponding companies. There are people at Google who are paid by Google who work full time on open source tools, like Terraform, Chef, and Puppet. This allows you to provision Google Cloud resources using the tools that you prefer. \\nAccording to Seth, there\\u2019s five key pillars of DevOps: 1) Reduce organizational silos and break down barriers between teams; 2) Accept failures; 3) Implement gradual change; 4) Tooling and automation; and 5) Measure everything.\\nThink of DevOps as an interface in programming language, like Java, or a type of language where it doesn\\u2019t actually define what you do, but gives you a high level of what the function is supposed to implement.\\nWith the SRE discipline, there\\u2019s a prescribed way for performing those five pillars of DevOps. Specific tools and technologies used within Google, some of which are exposed publicly as part of Google Cloud, enable the kind of DevOps culture and DevOps mindset that occur. \\nA reason why Google offers abstract classes in programming is that there\\u2019s more than one way to solve a problem, and SRE is just one of those ways. It\\u2019s the way that has worked best for Google, and it has worked best for a number of customers that Google is working with. But there are some other ways, too. Google supports those ways and recognizes that there isn\\u2019t just one path to operational success, but many ways to reach that p...'