Re: Mesos 0.24.1 on Raspberry Pi 3
FYI ... We were not able to compile latest master or 0.28.1. What we saw was that the linking step ran out of memory - well beyond the 1G of physical and 1G of swap. We considered some linking options to trade off memory, but haven't tried them. On Tue, Jun 7, 2016 at 12:18 PM, Joris Van Remoortere wrote: > All versions of mesos *should* work without systemd. The intent was to add > *support* for systemd, not make it a requirement. > If specific version of mesos *don't* work without systemd then that is a > bug, and it would be awesome if you could share specific issues (we can > make JIRAs). > > The purpose of the `systemd_enable_support`flag was to prevent mesos from > thinking it should use systemd utilities when systemd was available on the > system (and therefore Mesos assumes it's being launched as a systemd unit). > > I want to make it very clear that there is no intent to make systemd a > requirement :-) We would need to have a significant conversation in the > community first if that were the case. > > I really enjoyed hearing this progress, so please do ping me on any JIRAs > where systemd made this project more difficult! > > Joris > > — > *Joris Van Remoortere* > Mesosphere > > On Tue, Jun 7, 2016 at 1:01 PM, james wrote: > >> Just the opposite, I'm mostly interested in mesos without systemd >> on bard metal, minimized linux systems. So with that temporal >> requirement, what is the latest version of mesos that one can run >> without systemd? >> >> James >> >> >> On 06/07/2016 10:35 AM, Joris Van Remoortere wrote: >> >>> It should be straightforward to apply the patch that adds the >>> `systemd_enable_support` flag to older releases. >>> Let me know if you need help! >>> >>> — >>> *Joris Van Remoortere* >>> Mesosphere >>> >>> On Tue, Jun 7, 2016 at 11:28 AM, haosdent >> <mailto:haosd...@gmail.com>> wrote: >>> >>> No, it is mandatory in 0.25. `systemd_enable_support` is added since >>> 0.27 https://issues.apache.org/jira/browse/MESOS-4675 >>> >>> On Tue, Jun 7, 2016 at 11:21 PM, Jan Schlicht >> <mailto:j...@mesosphere.io>> wrote: >>> >>> It's not mandatory. There's the `systemd_enable_support` flag to >>> enable some systemd related features on an agent but it can be >>> disabled. >>> >>> Cheers, >>> Jan >>> >>> On Tue, Jun 7, 2016 at 3:55 PM, james >> <mailto:gar...@verizon.net>> wrote: >>> >>> >>> I thought systemd was not mandatory in version 0.25 and >>> later? >>> >>> James >>> >>> >>> On 06/07/2016 07:42 AM, tommy xiao wrote: >>> >>> only 0.24 can work on it. 0.25 use systemd and can't >>> ignore it. >>> >>> 2016-06-07 7:50 GMT+08:00 Benjamin Mahler >>> mailto:bmah...@apache.org> >>> <mailto:bmah...@apache.org <mailto:bmah...@apache.org >>> >>>: >>> >>> Cool stuff Andrew, thanks for sharing! >>> >>> On Thu, Jun 2, 2016 at 11:50 AM, Andrew Spyker >>> >>> wrote: >>> >>> > FYI, based on the work others have done in the >>> past, Netflix was >>> able to >>> > get Mesos agent building and running on >>> Raspberry Pi natively and >>> under >>> > Docker containers. Please see this blog for the >>> information: >>> > >>> > bit.ly/TitusOnPi <http://bit.ly/TitusOnPi> >>> <http://bit.ly/TitusOnPi> >>> > >>> > -- >>> > Andrew Spyker (aspy...@netflix.com >>> <mailto:aspy...@netflix.com> <mailto:aspy...@netflix.com >>> <mailto:aspy...@netflix.com>>) >>> > Twitter: @aspyker Blog: ispyker.blogspot.com >>> <http://ispyker.blogspot.com> >>> <http://ispyker.blogspot.com> >>> > >>> >>> >>> >>> >>> -- >>> Deshi Xiao >>> Twitter: xds2000 >>> E-mail: xiaods(AT)gmail.com <http://gmail.com> >>> <http://gmail.com> >>> >>> >>> >>> >>> >>> -- >>> *Jan Schlicht* >>> Distributed Systems Engineer, Mesosphere >>> >>> >>> >>> >>> -- >>> Best Regards, >>> Haosdent Huang >>> >>> >>> >> > -- Andrew Spyker (aspy...@netflix.com) Twitter: @aspyker Blog: ispyker.blogspot.com
Mesos 0.24.1 on Raspberry Pi 3
FYI, based on the work others have done in the past, Netflix was able to get Mesos agent building and running on Raspberry Pi natively and under Docker containers. Please see this blog for the information: bit.ly/TitusOnPi -- Andrew Spyker (aspy...@netflix.com) Twitter: @aspyker Blog: ispyker.blogspot.com
Re: Running Mesos agent on ARM (Raspberry Pi)?
resending as I wasn't on the (user) mailing list ... sorry for the two emails. I hope this is useful. This is from a pi 3 running a slave process connecting to a master not running on pi. pi@pi1:~ $ uname -a Linux pi1 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux pi@pi1:~ $ file /sbin/init /sbin/init: symbolic link to /lib/systemd/systemd pi@pi1:~ $ file /lib/systemd/systemd /lib/systemd/systemd: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 2.6.32, BuildID[sha1]=2522b3d9033024e417036999161b98fa0b5d498f, stripped pi@pi1:~ $ export LD_LIBRARY_PATH=/usr/local/lib pi@pi1:~ $ /usr/local/sbin/mesos-slave --master= ec2-xx-xx-xx-xx.compute-1.amazonaws.com:7103 I0503 16:35:21.592422 12656 main.cpp:185] Build: 2016-04-29 03:52:47 by root I0503 16:35:21.593188 12656 main.cpp:187] Version: 0.24.1 I0503 16:35:21.593456 12656 main.cpp:190] Git tag: 0.24.1 I0503 16:35:21.593680 12656 main.cpp:194] Git SHA: 44873806c2bb55da37e9adbece938274d8cd7c48 I0503 16:35:21.595311 12656 containerizer.cpp:143] Using isolation: posix/cpu,posix/mem,filesystem/posix I0503 16:35:21.626055 12656 main.cpp:272] Starting Mesos slave I0503 16:35:21.630719 12656 slave.cpp:190] Slave started on 1)@xx.xx.xx.xx:5051 I0503 16:35:21.631299 12656 slave.cpp:191] Flags at startup: --appc_store_dir="/tmp/mesos/store/appc" --authenticatee="crammd5" --cgroups_cpu_enable_pids_and_tids_count="false" --cgroups_enable_cfs="false" --cgroups_hierarchy="/sys/fs/cgroup" --cgroups_limit_swap="false" --cgroups_root="mesos" --container_disk_watch_interval="15secs" --containerizers="mesos" --default_role="*" --disk_watch_interval="1mins" --docker="docker" --docker_kill_orphans="true" --docker_remove_delay="6hrs" --docker_socket="/var/run/docker.sock" --docker_stop_timeout="0ns" --enforce_container_disk_quota="false" --executor_registration_timeout="1mins" --executor_shutdown_grace_period="5secs" --fetcher_cache_dir="/tmp/mesos/fetch" --fetcher_cache_size="2GB" --frameworks_home="" --gc_delay="1weeks" --gc_disk_headroom="0.1" --hadoop_home="" --help="false" --initialize_driver_logging="true" --isolation="posix/cpu,posix/mem" --launcher_dir="/usr/local/libexec/mesos" --logbufsecs="0" --logging_level="INFO" --master=" ec2-xx-xx-xx-xx.compute-1.amazonaws.com:7103" --oversubscribed_resources_interval="15secs" --perf_duration="10secs" --perf_interval="1mins" --port="5051" --qos_correction_interval_min="0ns" --quiet="false" --recover="reconnect" --recovery_timeout="15mins" --registration_backoff_factor="1secs" --resource_monitoring_interval="1secs" --revocable_cpu_low_priority="true" --sandbox_directory="/mnt/mesos/sandbox" --strict="true" --switch_user="true" --version="false" --work_dir="/tmp/mesos" I0503 16:35:21.635468 12656 slave.cpp:354] Slave resources: cpus(*):4; mem(*):462; disk(*):649; ports(*):[31000-32000] I0503 16:35:21.636222 12656 slave.cpp:384] Slave hostname: pi1 I0503 16:35:21.636487 12656 slave.cpp:389] Slave checkpoint: true I0503 16:35:21.669493 12657 state.cpp:54] Recovering state from '/tmp/mesos/meta' I0503 16:35:21.669802 12657 state.cpp:690] Failed to find resources file '/tmp/mesos/meta/resources/resources.info' I0503 16:35:21.670243 12657 state.cpp:97] Failed to find the latest slave from '/tmp/mesos/meta' I0503 16:35:21.673004 12658 status_update_manager.cpp:202] Recovering status update manager I0503 16:35:21.674284 12661 containerizer.cpp:379] Recovering containerizer I0503 16:35:21.680462 12662 slave.cpp:4069] Finished recovery I0503 16:35:21.684356 12657 slave.cpp:684] New master detected at mas...@xx.xx.xx.xx:7103 I0503 16:35:21.684406 12660 status_update_manager.cpp:176] Pausing sending status updates I0503 16:35:21.686789 12657 slave.cpp:709] No credentials provided. Attempting to register without authentication I0503 16:35:21.687227 12657 slave.cpp:720] Detecting new master ^C pi@pi1:~ $ file /usr/local/sbin/mesos-slave /usr/local/sbin/mesos-slave: ELF 32-bit LSB executable, ARM, EABI5 version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 2.6.32, BuildID[sha1]=0854662e0417291f2335990decb4b7be79724122, not stripped On Tue, May 3, 2016 at 9:46 AM, Andrew Spyker wrote: > resending as I wasn't on the mailing list ... > > This is from a pi 3 running a slave process connecting to a master not > running on pi. > > pi@pi1:~ $ uname -a > Linux pi1 4.1.19-v
