shutit

I wrote a framework for these kind of things, a wrapper on top of (p)expect: https://github.com/ianmiell/shutit

I wrote a tool to do that: https://github.com/ianmiell/shutit Among many other things I use it to test Kubernetes/OpenShift clusters in Vagrant for Chef recipes: https://github.com/ianmiell/shutit-openshift-cluster/blob/ma... and here's some others in a more 'native' python format: https://github.com/ianmiell/shutit-scripts/ https://github.com/ianmiell/shutit-scripts/blob/master/logme... https://github.com/ianmiell/shutit-scripts/blob/master/gnupl...

Source is here: https://github.com/ianmiell/shutit More background here: https://ianmiell.github.io/shutit/ This is used, for example, to automate kubernetes cluster tests for Chef scripts for OpenShift: Chef scripts: https://github.com/IshentRas/cookbook-openshift3 https://github.com/ianmiell/shutit-openshift-cluster https://zwischenzugs.wordpress.com/2017/03/04/a-complete-ope...

I use pexpect as the basis of an automation framework I use a lot: https://github.com/ianmiell/shutit/blob/master/README.md Recently I used it to migrate an etcd cluster within OpenShift reproducibly: https://medium.com/@zwischenzugs/migrating-an-openshift-etcd...

code at https://github.com/ianmiell/shutit

You could try mine :) https://github.com/ianmiell/shutit/blob/master/README.md https://github.com/ianmiell/shutit/blob/master/README.md#con...

Thanks! I may use those as templates to improve this: https://github.com/ianmiell/shutit/blob/master/library/ansib...

Dockerfiles are deliberately dumb to let other tools take over as necessary, is my understanding. My experience (over the last year) is that they're so limited as to be pretty useless. They don't even do what they're advertised to do, ie give you a reliable way to reproduce a build, and they're inflexible for my idea of real-world work with Docker. Where they're good is in giving everyone a point of reference. I had a discussion with the maintainers last year about this: https://groups.google.com/forum/#!topic/docker-user/3pcVXU4h... I have a problem with most CM tools in that they're for moving target systems, not immutable ones. Ansible is the closest, but our experience has been that development on it is slow relative to the tool we use (see below). It's saved us a ton of money. I blog on this and similar topics here: http://zwischenzu

Have a look at this: http://ianmiell.github.io/shutit/ which is a means of capturing this complexity for automation purposes. https://github.com/ianmiell/shutit I'm working on a "shutitdist" to compile "everything" from source: https://github.com/ianmiell/shutitdist ShutIt can (among many other things) produce depgraphs like this: https://raw.githubusercontent.com/ianmiell/shutitdist/master...

In terms of building LLVM and clang, I wrote this ShutIt module a while back when trying to learn it myself: https://github.com/ianmiell/shutit/blob/master/library/llvm/...

ShutIt script here: https://github.com/ianmiell/shutit/blob/master/library/osque... There are deps on thrift and rocksdb modules defined at the bottom. Should be useful for those looking to port to other CM tools. cf: http://ianmiell.github.io/shutit/

docker run -t -i imiell/osquery /bin/bash history for my gory details. I'll post a shutit script with the lot in tomorrow probably. The rocksdb dep is already done: https://github.com/ianmiell/shutit/blob/master/library/rocks... but bed beckons. In the meantime IYI: https://github.com/ianmiell/shutit/blob/master/library/osque... Thrift is another dep: https://github.com/ianmiell/shutit/blob/master/library/thrif...