Re: Running Mesos agent on ARM (Raspberry Pi)?
Did anybody try to build and run Mesos on a Raspberry Pi3? Will that work out of the box (due to the 64bit ARM)? On Sat, Apr 30, 2016 at 5:54 AM, haosdent wrote: > >The master has problem running with this build on the Pi > You need launch master with `--registry=in_memory`, replicated_log with > leveldb has problem in Mesos master. > > On Sat, Apr 30, 2016 at 4:09 AM, Sharma Podila > wrote: > > > Fyi- Things are progressing, we have a build on Pi. The agent was able to > > come up and register with a master running on a regular Linux server. > > > > https://twitter.com/aspyker/status/725923864031559681 > > > > The master has problem running with this build on the Pi, but, that isn't > > a goal for us. We are running Mesos 0.24.1 for now. We'll document our > > build steps, etc. here soon. > > > > > > > > On Mon, Apr 25, 2016 at 10:21 AM, Sharma Podila > > wrote: > > > >> This is for an internal hackday project, not for a production setup. > >> > >> > >> On Mon, Apr 25, 2016 at 1:05 AM, Aaron Carey wrote: > >> > >>> Out of curiosity... is this for fun or production workloads? I'd be > >>> curious to hear about raspis being used in production! > >>> > >>> -- > >>> > >>> Aaron Carey > >>> Production Engineer - Cloud Pipeline > >>> Industrial Light & Magic > >>> London > >>> 020 3751 9150 > >>> > >>> -- > >>> *From:* Sharma Podila [spod...@netflix.com] > >>> *Sent:* 22 April 2016 17:53 > >>> *To:* user@mesos.apache.org; dev > >>> *Subject:* Running Mesos agent on ARM (Raspberry Pi)? > >>> > >>> We are working on a hack to run Mesos agents on Raspberry Pi and are > >>> wondering if anyone here has done that before. From the Google search > >>> results we looked at so far, it seems like it has been compiled, but we > >>> haven't seen an indication that anyone has run it and launched tasks on > >>> them. And does it sound right that it might take 4 hours or so to > compile? > >>> > >>> We are looking to run just the agents. The master will be on a regular > >>> Ubuntu laptop or a server. > >>> > >>> Appreciate any pointers. > >>> > >>> > >>> > >> > > > > > -- > Best Regards, > Haosdent Huang >
Re: Mesos metrics -> influxdb
@Michael: Great tutorial on KairosDB & Cassandra! On Thu, Feb 25, 2016 at 7:11 PM, vincent gromakowski < vincent.gromakow...@gmail.com> wrote: > +1 for Telegraph > Le 25 févr. 2016 19:08, "Pradeep Chhetri" a > écrit : > >> Telegraf already has a input plugin to push mesos metrics to influxdb ( >> https://github.com/influxdata/telegraf/tree/master/plugins/inputs/mesos) >> >> >> On Thu, Feb 25, 2016 at 5:32 PM, Aaron Carey wrote: >> >>> Has anyone had a good experience recording mesos metrics into influxdb? >>> >>> I've found a couple of options, a collectd plugin which doesn't appear >>> to work with version 0.24.x and a more up to date containerised option >>> which randomly crashes regularly and doesn't appear to actually post any >>> stats. >>> >>> Anyone have any good solutions? >>> >>> >>> >> >> >> -- >> Pradeep Chhetri >> >> In the world of Linux, who needs Windows and Gates... >> >
Re: Managing Persistency via Frameworks (HDFS, Cassandra)
Hi Tommy, thanks a lot for sharing. And yes, that is what I figured. For PoC/Testing environments the frameworks work just fine. -- Andreas On Tue, Feb 9, 2016 at 1:01 PM, tommy xiao wrote: > Hi Andreas, > > I have recommend my customer to build a hdfs pool resources outside mesos > cluster in general concerns. But in development or stage environment, use > mesos to manage your hdfs culster is ideal purpose. when mesos community > give more production case, then we can upgrade the develop cluster to > production cluster easily. > > > 2016-02-09 14:50 GMT+08:00 Andreas Fritzler : > >> Hi Klaus, >> >> thanks for your reply. I am aware of the frameworks provided by >> mesosphere and I already tried them out in a POC setup. From looking at the >> HDFS documentation [1] however, the framework seems to be still in beta. >> >> "HDFS is available at the beta level and not recommended for Mesosphere >> DCOS production systems." >> >> I think what my questions are boiling down to is the following: should I >> use a Mesos framework to manage persistency within my Mesos cluster or >> should I do it outside with other means - e.g. using Ambari to setup a >> shared HDFS etc. >> >> If I would use those frameworks, how is your experience regarding the >> life cycle management? Scaling out instances, upgrading to newer versions >> etc. >> >> Regards, >> Andreas >> >> [1] https://docs.mesosphere.com/manage-service/hdfs/ >> >> On Tue, Feb 9, 2016 at 1:05 AM, Klaus Ma wrote: >> >>> Hi Andreas, >>> >>> I think Mesosphere has done some work on your questions, would you check >>> related repos at https://github.com/mesosphere ? >>> >>> >>> On Mon, Feb 8, 2016 at 9:43 PM Andreas Fritzler < >>> andreas.fritz...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I have a couple of questions around the persistency topic within a >>>> Mesos cluster: >>>> >>>> 1. Any takes on the quality of the HDFS [1] and the Cassandra [2] >>>> frameworks? Does anybody have any experiences in running those frameworks >>>> in production? >>>> >>>> 2. How well are those frameworks performing if I want to use them to >>>> separate tenants on one Mesos cluster? (HDFS is not dockerized yet?) >>>> >>>> 3. How about scaling out/down existing framework instances? Is that >>>> even possible? Couldn't find anything in the docs/github. >>>> >>>> 4. Upgrading a running instance: wondering how that is managed in those >>>> frameworks. There is an open issue for the HDFS [3] part. For cassandra the >>>> scheduler update seems to be smooth, however changing the underlying >>>> Cassandra version seems to be tricky [4]. >>>> >>>> Regards, >>>> Andreas >>>> >>>> [1] https://github.com/mesosphere/hdfs >>>> [2] https://github.com/mesosphere/cassandra-mesos >>>> [3] https://github.com/mesosphere/hdfs/issues/23 >>>> [4] https://github.com/mesosphere/cassandra-mesos/issues/137 >>>> >>> -- >>> >>> Regards, >>> >>> Da (Klaus), Ma (马达), PMP® | Advisory Software Engineer >>> IBM Platform Development & Support, STG, IBM GCG >>> +86-10-8245 4084 | mad...@cn.ibm.com | http://k82.me >>> >> >> > > > -- > Deshi Xiao > Twitter: xds2000 > E-mail: xiaods(AT)gmail.com >
Re: Managing Persistency via Frameworks (HDFS, Cassandra)
Hi Klaus, thanks for your reply. I am aware of the frameworks provided by mesosphere and I already tried them out in a POC setup. From looking at the HDFS documentation [1] however, the framework seems to be still in beta. "HDFS is available at the beta level and not recommended for Mesosphere DCOS production systems." I think what my questions are boiling down to is the following: should I use a Mesos framework to manage persistency within my Mesos cluster or should I do it outside with other means - e.g. using Ambari to setup a shared HDFS etc. If I would use those frameworks, how is your experience regarding the life cycle management? Scaling out instances, upgrading to newer versions etc. Regards, Andreas [1] https://docs.mesosphere.com/manage-service/hdfs/ On Tue, Feb 9, 2016 at 1:05 AM, Klaus Ma wrote: > Hi Andreas, > > I think Mesosphere has done some work on your questions, would you check > related repos at https://github.com/mesosphere ? > > > On Mon, Feb 8, 2016 at 9:43 PM Andreas Fritzler < > andreas.fritz...@gmail.com> wrote: > >> Hi, >> >> I have a couple of questions around the persistency topic within a Mesos >> cluster: >> >> 1. Any takes on the quality of the HDFS [1] and the Cassandra [2] >> frameworks? Does anybody have any experiences in running those frameworks >> in production? >> >> 2. How well are those frameworks performing if I want to use them to >> separate tenants on one Mesos cluster? (HDFS is not dockerized yet?) >> >> 3. How about scaling out/down existing framework instances? Is that even >> possible? Couldn't find anything in the docs/github. >> >> 4. Upgrading a running instance: wondering how that is managed in those >> frameworks. There is an open issue for the HDFS [3] part. For cassandra the >> scheduler update seems to be smooth, however changing the underlying >> Cassandra version seems to be tricky [4]. >> >> Regards, >> Andreas >> >> [1] https://github.com/mesosphere/hdfs >> [2] https://github.com/mesosphere/cassandra-mesos >> [3] https://github.com/mesosphere/hdfs/issues/23 >> [4] https://github.com/mesosphere/cassandra-mesos/issues/137 >> > -- > > Regards, > > Da (Klaus), Ma (马达), PMP® | Advisory Software Engineer > IBM Platform Development & Support, STG, IBM GCG > +86-10-8245 4084 | mad...@cn.ibm.com | http://k82.me >
Managing Persistency via Frameworks (HDFS, Cassandra)
Hi, I have a couple of questions around the persistency topic within a Mesos cluster: 1. Any takes on the quality of the HDFS [1] and the Cassandra [2] frameworks? Does anybody have any experiences in running those frameworks in production? 2. How well are those frameworks performing if I want to use them to separate tenants on one Mesos cluster? (HDFS is not dockerized yet?) 3. How about scaling out/down existing framework instances? Is that even possible? Couldn't find anything in the docs/github. 4. Upgrading a running instance: wondering how that is managed in those frameworks. There is an open issue for the HDFS [3] part. For cassandra the scheduler update seems to be smooth, however changing the underlying Cassandra version seems to be tricky [4]. Regards, Andreas [1] https://github.com/mesosphere/hdfs [2] https://github.com/mesosphere/cassandra-mesos [3] https://github.com/mesosphere/hdfs/issues/23 [4] https://github.com/mesosphere/cassandra-mesos/issues/137
