1) Agree we can move to docker native solutions. Of course, this makes it impossible to test the bare metal deployments that some folks still care about. Otto also seems promising, it's ec2 native....
Now, If we think docker is better for testing, then relying on OS specific VMs, maybe that's telling us something about the future of production big data clusters as well.... 2) (rehash microservices rant) So..if we agree docker is sufficient for all our testing, why not just move (ok I admit this is a little extreme.. But)... entirely to microservices? That way we can focus on the interesting parts (like keeping up with the spark release cycle, Kafka integration , spark hbase Integration, and so on)... IMO Ultimately the similarity between deb and rpm containers is a lot higher than the similarity between deb and rpm packages. So containers are exactly what bigtop needs, at all levels of the stack, not just testing . > On Dec 27, 2015, at 2:09 PM, Olaf Flebbe <[email protected]> wrote: > > Hi Evans, > >> My personal reason for not keep implementing this is because I plan to drop >> vagrant and embrace docker's native solutions(machine, compose, swarm) for >> our docker provisioner. > > YES! PLEASE! That would be great! > > Olaf
