Thanks, Vinod. I'm not worried too much about scaling the core, you guys have done the hard work on that end :-). The other parts of the system can definitely run into issues when running at larger scales. We've some ideas about what these are and what the mitigation plan is. Others, of course we'll discover in time. Still not worried too much though, the community has been fantastic and we hope to leverage it's collective wisdom in helping us improve the system.
Arunabha On Mon, Dec 7, 2015 at 7:37 PM, Vinod Kone <[email protected]> wrote: > Really cool to see a multi-framework compute platform. Let us know how > things work for you guys as you scale! > > On Mon, Dec 7, 2015 at 7:24 PM, Arunabha Ghosh <[email protected]> > wrote: > >> We're definitely open to merging the changes to Bamboo back upstream if >> the changes we made prove useful to Bamboo. The changes we made were pretty >> specific to our needs and we anticipate making quite a few changes as we >> evolve the platform, so a separate repo seemed to be a better idea till the >> codebase stabilized somewhat and we could offer a concrete view of the >> changes we wanted. >> >> Arunabha >> >> On Mon, Dec 7, 2015 at 7:03 PM, Jeff Schroeder < >> [email protected]> wrote: >> >>> From a quick skim, this looks excellent. Are there any plans to try >>> getting the bamboo changes back upstream, or is it going to be a permanent >>> fork? >>> >>> >>> On Monday, December 7, 2015, Arunabha Ghosh <[email protected]> >>> wrote: >>> >>>> Hi Folks, >>>> We, at Moz have been working for a while on RogerOS, our >>>> next gen application platform built on top of Mesos. We've reached a point >>>> in the project where we feel it's ready to share with the world :-) >>>> >>>> The blog posts introducing RogerOS can be found at >>>> >>>> https://moz.com/devblog/introducing-rogeros-part-1/ >>>> https://moz.com/devblog/introducing-rogeros-part-2/ >>>> >>>> I can safely say that without Mesos, it would not have been possible >>>> for us to have built the system within the constraints of time and >>>> resources that we had. As we note in the blog >>>> >>>> " We are very glad that we chose Mesos though. It has delivered on all >>>> of its promises and more. We’ve had no issues with stability, >>>> extensibility, and performance of the system and it has allowed us to >>>> achieve our goals with a fraction of the development resources that would >>>> have been required otherwise. " >>>> >>>> We would also like to thank the wonderful Mesos community for all the >>>> help and support we've received. Along the way we've tried to contribute >>>> back to the community through talks at Mesoscon and now through open >>>> sourcing our efforts. >>>> >>>> Your feedback and thoughts are always welcome ! >>>> >>>> Thanks, >>>> Arunabha >>>> >>>> >>>> >>> >>> >>> -- >>> Text by Jeff, typos by iPhone >>> >> >> >
