Build a provisioning tool for all cloud providers that 90% of developers could use

11:30 AM Bretton Woods

Background: Now it’s the cloud computing era. Developers want to build infrastructure as code so they can repeat and reproduce the same provisioning processes. Challenge: 1. Provisioning processes need to be recorded 2. Few tools are designed just for provisioning 3. Existing provisioning tools are too complicated (i.e. Ansible) 4. Workflows vary from different cloud providers and each uses different command-line tools. Developers need one tool that works for all cloud providers. Solution: We made LinchPin! According to the Pareto principle, roughly 80% of the effects come from 20% of the causes. Now developers can spend a small percent of their development time migrating to LinchPin as a provisioning tool and LinchPin could solve most of their provisioning problems. Introduction: LinchPin provides a command-line interface and a Python API for provisioning and managing resources across various infrastructures. Multiple infrastructure resource types can be defined with a single topology file. LinchPin can also generate inventory files for use with additional Ansible playbooks. These are applied using an inventory layout file. (in YAML) I’ll cover the benefits below in detail. 1.The very flat learning curve 2. It is designed for solving the provisioning problem, so we simplified many steps compared to pure Ansible or the cloud provider’s REST API. 3. It’s written in Python (the most popular language now) and Ansible (extensible) and is open-source, so it could be easily imported into your project as a provisioner by importing the LinchPin Python API. 4. Using the REST API (currently in development) you could also deploy it as a microservice soon. 5. LinchPin is for all cloud providers. You only need to know one standard for provisioning, then you can provision anywhere. I’ll also cover, demo: Provision VM on Azure with just VM name, DEEP CLEAN a VM after provision Provision VM on AWS, then destroy it.