I spent the weekend building this little DevOps demo for you. Please feel free to explore!
First up the marketing part. I selected Burst pizza because it has lots of marketing potential (like bursting with flavour etc), it is easy to remember and derives from "burst download of flavour". The logo is inspired by the representations of Cortana and mixed with the idea of high tech pizza.
Starting with the required feature list, I expanded the list with my own ideas of how a company like that would operate. I put together a more comprehensive list of features and then went about looking what IT systems would need to be created/implemented to support it.
Following this I spent some time thinking about the nature of the business, and how quickly it will expand. I split up the IT into in-shop and centrally provided services. I then designed a overview of those systems and where they fit in in a diagram.
Next up, was to zoom into a particular area of the business and build "something" to show my DevOps skills. I zoomed into the development team and created a diagram to show how that team would work.
As I chose to demonstrate my DevOps skills instead of my development skills. I put together an extremely basic skeleton (like v0.001) of the pizza shop's live CI/CD system. The idea is to show you that I understand the concepts and that I can apply them even in a very simple demo situation.
There are several folders numbered 1 to 4. These contain the documentation and the various aspects and configuration files that I used to create the solution.
Parts of the system are currently live on the Internet so that you can interact with them. They are hosted on one of my home servers - so feel free to mess around with them.
The url of the Jenkins system is:
http://home.wolfen.za.net:8081/
The url of the 'production' web server is:
http://home.wolfen.za.net/tsbtest/
The url of the source control (svn) server is:
http://home.wolfen.za.net/svn/tsbtest/
You require credentials to interact with SVN and Jenkins etc.
User: tsbtest
Ok, so now you've read all the documentation and you just want to see how this all works!
Check out the code using SVN:
svn co http://home.wolfen.za.net/svn/tsbtest/
I created a simple date.txt file that is part of the "website" to demonstrate the ability to change stuff.
date > date.txt; svn commit -m "Test commit"
Check in the hard work and observe the magic in Jenkins
svn commit -m "Worked on the date thing"
Open Jenkins and see 2 builds run automatically. The first checks out the code, 'tests' it, and then if the test 'passes', it checks in the artifacts for production deployment.
Then the production deployment jobs sees the commit, tests it and auto deploys it.
These are just barebones skeletons for now, but could obviously be extended as needed.
Jenkins URL Again: http://home.wolfen.za.net:8081/
Check the changes made have 'gone live'.
http://home.wolfen.za.net/tsbtest/date.txt
- Jenkins - The Automation Tool
- SVN - Source Control
- Apache - Web Server
- Iain Prior - Initial work
(c) All rights reserved. Any and all permissions granted implicitly or explicitly may be revoked without notice, for any reason. No warranty is given to the fullest extent permitted by law.
- TSB Bank for an awesome question, had fun building this
- Ubuntu server team for making this all possible
- The rest of the open source community - you guys rock!