The DevOps Platform (aka ADOP) is an integration of open source tools that is designed to provide the capability to perform continuous delivery.
Out of the box, the platform contains tools to store, version, build, test and release application and infrastructure code via continuous delivery pipelines. The platform also supports two forms of extensibility: platform extensions to add more tools; cartridges to load into the platform example code; and automation jobs for a particular application.
For evaluation purposes, the whole platform can be run on one machine using this quick start script, or you can jump straight to running an instance in a multi-availability zone Docker Swarm using this Cloud Formation script.
Within 30 minutes anyone using ADOP can:
Stand up all of the tools;
Load-in an application and the associated pipelines, automated tests and environment creation automation;
Make code changes to the application;
Watch those changes get deployed to the environments via a continuous delivery pipeline.
This allows you to perform continuous delivery-first development (as opposed to first writing code and then wondering about environments and release automation later).
For example, you might choose to:
Stand up ADOP in AWS;
Load the Spring Petclinic Java cartridge;
Create a test and production environment;
Clone the Petclinic code from the ADOP instance, update the user interface in the Petclinic application and push it back to ADOP;
Watch the continuous delivery pipeline compile the code; run the unit tests; perform static code analysis; perform a deployment; run functional, security and performance tests; and deploy the code to half of production (as it waits for confirmation on whether to deploy to the other half).
Not bad for 30 minutes!
|Why did we create this?
Back in 2012, we found ourselves repeatedly installing tools like Jenkins, Gerrit, etc., for different projects. We were also exploring Chef, and decided to try using it to stand-up the tools. We had some success doing this; however, installations were often fraught with problems due to the cookbooks failing to download dependencies. This method also required initial effort to provision the Chef server and the other servers, and then to bootstrap them to Chef (so that the servers could converge and install the tools). From end to end, the process took several hours.
By mid-2014, we ported to Cloud Formation and Docker, and the ease and predictability with which this allowed us to stand-up the tools was game-changing. We spotted an opportunity to use ADOP as a lab environment on our training courses where every student would get their own instance. As more use cases arose, we responded tactically by bolting new things onto the platform. Eventually we built the extensibility framework in the form of cartridges and platform extensions.
These days we find ADOP extremely valuable for:
Bringing the concepts of continuous delivery and infrastructure code to life (almost instantly and almost anywhere);
Allowing people to learn how to use and extend the tools;
Starting real development knowing continuous delivery is the goal from day one;
Sharing automation such as the ability to create particular environments, build great continuous delivery pipelines or develop strong automated deployments and testing.
What is in the box?
By default (at the time of writing) ADOP comes with:
Gerrit (to manage Git repositories and peer review life cycles if required)
Jenkins (as the orchestrator of all automation within the platform including loading platform extensions and cartridges)
Various things that Jenkins is able to run such as:
Adding to the box
Platform extensions to date include:
A Chef server
A generic create AWS instance from an AMI runner
Cartridges we have so far include:
Java Spring Petclinic (cliched we know)
A Chef cookbook pipeline
A Docker image pipeline
Naturally, we have tried to make getting started as simple as possible. The instructions for quick start are here. Once you are familiar with the tools and have loaded the extensions and cartridges you need, the next step is either to consider whether you need a more resilient instance, for example, by using our Docker Swarm version Cloud Formation script here. Then you are free to start using ADOP to power your delivery, or even to start building new platform extensions or cartridges.
As we continue to find increased interest and users of the platform, we are driving improvements in the following ways:
Adding more cartridges with the intention that more and more technologies and sample applications can be bootstrapped on the tool (for continuous delivery-first development).
Adding more platform extensions; for example, a Puppet Server or Ansible Tower.
Extending the cartridge and platform extension loaders to make writing them easier and more efficient. Note: We are committed to doing this in a backwards-compatible manner and do not expect to render existing cartridge and platform extensions unloadable.
Proving more hosting providers. Storage and compute resources permitting, theoretically ADOP will run out of the box anywhere Docker is installed, be that a single machine, a Docker Swarm, or a container PaaS that supports Docker-compose. However, so far we have only used it on single instances in AWS, Azure, GCP and on premise, and in a Docker Swarm on AWS and Azure.
Improving the operability of the platform. While many people will choose to first experience ADOP by installing it on a single machine, we also have been enhancing the AWS Cloud Formation script to provide a more resilient architecture.