tnx! Would like to hear opinions on how to categorise our solution and maybe restructure/rephrase this page:
Vamp is not so much “built on Mesos” but “makes use of Mesos” as it offers higher-level features using our Mesos/Marathon-driver. Maybe it’s semantics but i just wanted to check with the community. Also, we’re a Canary-testing and releasing framework, which doesn’t really seem to fit the current categories in the “built on Mesos” article. The most fitting category would be “Batch Scheduling” but that wouldn’t entirely fit the use-case of Vamp. My suggestion would be “Continuous deployment, testing and scaling”. Any thoughts/suggestions? tnx, Olaf > On 05 Jan 2016, at 02:54, Benjamin Mahler <[email protected]> wrote: > > There are two sections: 'Organizations Using Mesos' and 'Software projects > built on Mesos'. The latter links to the list of frameworks. > > If you fit either of these descriptions, then we can get you added, just > forward to us a pull request or reviewboard request. > > On Tue, Dec 8, 2015 at 10:34 PM, Olaf Magnetic <[email protected] > <mailto:[email protected]>> wrote: > Hi Benjamin, > > What are the criteria to be included on the powered by mesos list? Would love > to have our canary-test and release framework VAMP (www..vamp.io > <http://vamp.io/>) which runs on mesos/marathon on this list too. > > Cheers, Olaf > > > On 08 Dec 2015, at 22:36, Benjamin Mahler <[email protected] > <mailto:[email protected]>> wrote: > >> Thanks for sharing Arunabha! I'm a big fan of the multi-framework compute >> platform approach, please share your feedback along the way :) >> >> Would you like to be added to the powered by mesos list? >> https://github.com/apache/mesos/blob/master/docs/powered-by-mesos.md >> <https://github.com/apache/mesos/blob/master/docs/powered-by-mesos.md> >> >> On Mon, Dec 7, 2015 at 1:30 PM, Arunabha Ghosh <[email protected] >> <mailto:[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-1/> >> https://moz.com/devblog/introducing-rogeros-part-2/ >> <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 >> >> >> >
