Hi folks. This last year we've made a lot of progress, - we can now easily build bigtop, - and we can test a fresh build in output/ it in vagrant boxes locally
Whats next? In my mind, there is only one last step, to make bigtop a consumer facing product: We need to make it so you can simply provision a cluster in the cloud. As you may recall, David (student at RPI, intern at analytics company last summer), asked how to do this, and spent about three weeks on it. Recently Ata Turk, working on the Massachusets Open Cloud @ Boston University, and former Yahoo researchers, also asked me the same thing. Alternative? Well we currently these docs about how to setup 0.7.0, 0.8.0, and so on, which mostly are an untested, human readable version of our vagrant recipes. yikes ! How to implement a ssh cloud bigtop installation ? We could roll our own deployer, but in doing so, we would have to make semantics for: - possible need for machiene reboots - syncing local folders to remote folders - installing (and reinstalling) luckily, our buddy Vagrant already does this for us (respectively , with the "reload","synced.folder", and "up" options). Additionally, *** I THINK *** we can literally use the exact same vagrant recipes which we are already using to test --- so we will have a great user experience, and really easy to reproduce bugs and test deployments. I';l hash out details in BIGTOP-1702 , any thoughts, questions, suggestions on the implementation or feature? I think it will be easy, but also, it will be one of the most powerful things we add to bigtop, basically allowing users to easily use the system... maybe even too easy :) -- jay vyas
