Digital Rebar Provision (DRP) is the perfect technology partner for Ansible customers looking to automate their infrastructure setup before applying their orchestration tool of choice. DRP automatically generates a complete inventory of provisioned infrastructure which is a must have for Ansible to complete its orchestration. In addition, DRP is able to deploy Kubernetes clusters using Ansible and Kubespray as part of its standard Workflow automated process.
Together, DRP and Ansible enhance the automation, repeatability, and transparency for DevOps teams.
Learn more about DRP and Ansible in the demonstration video and podcasts below.
Demonstration Video of Kubespray with Digital Rebar Provision:
Learn more about Digital Rebar Provision and Ansible in this podcast:
Learn more about Digital Rebar Provision, Ansible and Kubernetes installation with Kubespray in this podcast:
Editorial Note: This was written in April 2014. Check out how we are using Docker in our latest architectures.
The new application portability darling, Docker, was so popular at this week’s Red Hat Summit that I was expecting Miley Cyrus’ flock of paparazzi to abandon in her favor of Ben Golub.
Personally, I find Docker to be a useful tool and we’ve been embedding it into our dev and test processes in useful ways for DefCore TCUP (at Conference), OpenCrowbar Admin and Dev Nodes. To me, these are concrete and clear use cases.
There are clearly a lot more great use-cases for Docker, but I can’t help but feel like it’s being thrown into architectural layer cakes and markitectures as a substitute for the non-words “cloud”, “amazing” and “revolutionary.”
How do I distinguish hot from hype? I look for places where Docker is solving just one problem set instead being a magic wand solution to a raft of systemic issues.
Places where I think Docker is potent and disruptive
- Creating a portable and consistent environment for dev, test and delivery
- Helping Linux distros keep updating the kernel without breaking user space (RHEL 7 anyone?)
- Reducing the virtualization overhead of tenant isolation (containers are lighter)
- Reducing the virtualization overhead for DevOps developers testing multi-node deployments
But I’m concerned that we’re expecting too many silver bullets
- Packaging is still tricky: Creating a locked box helps solve part of downstream problem (you know what you have) but not the upstream problem (you don’t know what you depend on).
- Container sprawl: Breaking deployments into more functional discrete parts is smart, but that means we have MORE PARTS to manage. There’s an inflection point between separation of concerns and sprawl.
- PaaS Adoption: Docker helps with PaaS but it does not solve neither the “you have to model your apps for a PaaS” nor the “PaaS needs scalable data services” problems
Speaking of Miley Cyrus, it’s not the container that matters, but what’s on the inside. Docker can take a lesson from Miley: attention is great but you’ve still got to be able to sing. I’m not sure about Miley, but I am digging the tracks that Docker is laying down. Docker is worth putting on your play list.