![]() ![]() The team of 25 SEs are completely out of luck and unable to do any demos or training without their shared AWS account. The account is flagged for abuse, and AWS shuts the entire account down, taking the entire demo framework with it. Within minutes hundreds of instances are created to mine cryptocurrency. Immediately a cryptocurrency mining bot picks them up and takes over the team’s shared demo account. Then one day, Kira’s coworker Anthony accidentally copies his secret keys to the demo Git repository. New employees have to spend several weeks absorbing the tribal knowledge and trying not to run out of resources in their shared cloud account. There are known bugs, and the process for standing up a new demo environment is not easy to understand. The SE team has now grown to 25, and the demo environments are in desperate need of an upgrade. The team knows that it will have to be rewritten from scratch, but they just keep kicking that can down the road… The Demo Environment Breaking Point ![]() Nobody really has time to fix the issues with the demo framework anyway. It’s not perfect, it has some rough edges, and the data is over a year old, but at least it works. The demo framework now runs in a shared account on AWS. The SE team shares the original demo that Kira built. The developers are as busy as ever creating new features and fixing bugs. Initech has grown, and now there are eight sales reps and four sales engineers. (Fast forward 12 months) Growing Pains and Technical Debt The sales demo with Alice goes great, and Alice says, “You’re a wizard, Kira.” She doesn’t have a whole lot of time to invest in building the demo environment, so she cuts some corners to get it done before the next day’s meetings. The whole thing is built by hand, but that’s ok because Kira is the only SE on the team. The demo framework consists of a bunch of virtual machines that Kira runs from her laptop. She goes to work building the first iteration of what we will call the “demo framework”. Automation Game Demo how to#As a former developer, Kira knows how to write Code, and she’s installed and set up the Initech software a few times. She will have to build a demo environment because the company doesn’t have one yet, and the devs are too busy fixing bugs to work on this. Kira closes the chat window and accepts her fate. ![]() You just work your magic and sprinkle some of that special Kira DevOps dust on it. Normally we do some requirements gathering first…Īlice: Oh, I’m not worried. Kira: Uh…I don’t really have anything prepared. Sorry about the short notice, but this is the only time the prospect was free. Salespeople Gonna SellĪlice: Hey Kira, I scheduled a sales demo for tomorrow morning at 8am. Peter, Michael and Samir are developers who create and manage the application. They have a small sales team consisting of Alice, enterprise account manager, Bob, Alice’s manager, and Kira, sales engineer. ![]() Initech provides accounting software for large enterprise organizations. Our imaginary tale begins with a software company called Initech. Why is that? In this post, we’ll explore the evolution of a demo environment and some ways to automate them. Demo and training environments, on the other hand, are almost always built manually. DevOps teams use tools like Terraform or Ansible to build cloud resources and virtual machines. Automation Game Demo code#Infrastructure as Code is becoming more common in modern IT organizations. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |