t; 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
Tomek's Mesos on ARM seems out of date, and it is a bit painful to set up
a Raspberry Pi development environment in x86 machine.
So I create a docker image `haosdent/raspberry` to simple this and document
how to patch, compile and running mesos on the Raspberry Pi in this [post](
slave process. We would prefer to set all of these system-wide and have
>> mesos-slave observe them.
>>
>> Can you please advise where you are setting your ulimits for the
>> mesos-slave if it is working for you?
>>
>> Thanks,
>> June Taylor
>> System Administrator, Minnesota Population Center
>> University of Minnesota
>>
>
>
--
Best Regards,
Haosdent Huang
the upstart script, per the
>> > Mesos documentation, isn't working for the file block limit. We're still
>> > getting 8MB useable, and as a result executors fail when attempting to
>> write
>> > larger files.
>> >
>> >
>> > Than
instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy.
>
> __
>
> www.accenture.com
>
--
Best Regards,
Haosdent Huang
stand the mechanism.
> I understood that i don't have to specify a command in "Command" field,
> but i don't know how to fill the dockers fields in marathon UI to launch
> wordpress container.
> Could you please help me or tell me where i can find a clearer
> documentation?
>
> Thanks.
>
--
Best Regards,
Haosdent Huang
versity of Minnesota
>
> On Mon, Apr 25, 2016 at 9:48 PM, haosdent wrote:
>
>> According my test, it works in my side.
>>
>> * Before add it to /etc/init/mesos-slave.conf
>>
>> ```
>> cat /proc/16550/limits
>> Limit
a
>>>>>>>>>
>>>>>>>>> On Tue, Apr 26, 2016 at 9:20 AM, Stefano Bianchi <
>>>>>>>>> jazzist...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Thanks *Rad* Gruchalski
the columns: ID, Host, CPUs,
> Mem, Disk, Registered and Re-Registered.
> But in the "Offers" tab there is two times Mem. : ID, Framework, Host,
> Cpus, Mem, Mem.
> The second Mem should be Disk instead.
>
> I suppose that should be easy to fix.
>
> Regards,
> Julian
>
--
Best Regards,
Haosdent Huang
;>>> services to any persons who are prohibited from receiving such information
>>>> under applicable law. The contents of this communication may not
>>>> be accurate or complete and are subject to change without notice. As such,
>>>> Orchard App, Inc. (including its subsidiaries and affiliates, "Orchard")
>>>> makes no representation regarding the accuracy or completeness of the
>>>> information contained herein. The intended recipient is advised to consult
>>>> its own professional advisors, including those specializing in legal, tax
>>>> and accounting matters. Orchard does not provide legal, tax or accounting
>>>> advice.
>>>>
>>>>
>>>>
>>> *NOTICE TO RECIPIENTS*: This communication is confidential and intended
>>> for the use of the addressee only. If you are not an intended recipient of
>>> this communication, please delete it immediately and notify the sender
>>> by return email. Unauthorized reading, dissemination, distribution or
>>> copying of this communication is prohibited. This communication does not
>>> constitute
>>> an offer to sell or a solicitation of an indication of interest to purchase
>>> any loan, security or any other financial product or instrument, nor is it
>>> an offer to sell or a solicitation of an indication of interest to purchase
>>> any products or services to any persons who are prohibited from receiving
>>> such information under applicable law. The contents of this communication
>>> may not be accurate or complete and are subject to change without notice.
>>> As such, Orchard App, Inc. (including its subsidiaries and affiliates,
>>> "Orchard") makes no representation regarding the accuracy or
>>> completeness of the information contained herein. The intended recipient is
>>> advised to consult its own professional advisors, including those
>>> specializing in legal, tax and accounting matters. Orchard does not
>>> provide legal, tax or accounting advice.
>>>
>>
>>
--
Best Regards,
Haosdent Huang
ed, 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
end: 3887 } range { begin: 3889 end: 5049 }
> range { begin: 5052 end: 6326 } range { begin: 6328 end: 8079 } range {
> begin: 8082 end: 8180 } } role: "*" } resources { name: "disk" type: SCALAR
> scalar { value: 41497.0 } role: "*" } resources { name: "cpus" type: SCALAR
> scalar { value: 1.0 } role: "*" } resources { name: "mem" type: SCALAR
> scalar { value: 896.0 } role: "*" } url { scheme: "http" address {
> hostname: "10.132.46.84" ip: "10.132.46.84" port: 5051 } path: "/slave(1)"
> }] (mesosphere.mesos.TaskBuilder:marathon-akka.actor.default-dispatcher-19)
>
> can anyone help me with this?
>
> thank you.
>
>
> GaoJin CAO
> ChinaMobile(Suzhou) R&D
> Phone：18896723732
> Mail：caogaojin at cmss.chinamobile.com
>
>
>
--
Best Regards,
Haosdent Huang
And why you add
```
"reservation": {}
```
in the resource define? Which role you used when start Marathon?
On Sun, May 1, 2016 at 2:28 AM, haosdent wrote:
> Why you send reserve request to http://10.132.46.81:5050/unreserve, is it
> should be "http://10.132.46.81:5050/
; name: "mem" type: SCALAR scalar { value: 1743.0 } role: "dev" reservation {
>> } } resources { name: "ports" type: RANGES ranges { range { begin: 1025
>> end: 2180 } range { begin: 2182 end: 3887 } range { begin: 3889 end: 5049 }
>> range { begin: 5052 end: 6326 } range { begin: 6328 end: 8079 } range {
>> begin: 8082 end: 8180 } } role: "*" } resources { name: "disk" type: SCALAR
>> scalar { value: 41497.0 } role: "*" } resources { name: "cpus" type: SCALAR
>> scalar { value: 1.0 } role: "*" } resources { name: "mem" type: SCALAR
>> scalar { value: 896.0 } role: "*" } url { scheme: "http" address {
>> hostname: "10.132.46.84" ip: "10.132.46.84" port: 5051 } path: "/slave(1)"
>> }] (mesosphere.mesos.TaskBuilder:marathon-akka.actor.default-dispatcher-19)
>>
>> can anyone help me with this?
>>
>> thank you.
>>
>>
>> GaoJin CAO
>> ChinaMobile(Suzhou) R&D
>> Phone：18896723732
>> Mail：caogaojin at cmss.chinamobile.com
>>
>>
>
--
Best Regards,
Haosdent Huang
e to solve your concerns.
On Sun, May 1, 2016 at 12:12 PM, Marco Massenzio
wrote:
> @haosdent - thanks for doing this, very useful indeed!
>
> On a related issue [0], I'd like to that one on:
>
> - can anyone comment if that's a good idea/bad idea; and
> - would anyone
0/reserve
2. start Marathon with dev role
```
./bin/start --master 127.0.0.1:5050 --zk zk://10.10.120.61:2181/marathon
--mesos_role dev
```
3. start task
```
$ cat task.json
{
"id": "/test-health",
"cmd": "sleep 200",
"cpus": 1.0,
&quo
could you show the result of curl 10.132.46.71:5050/
<http://10.132.46.71:5050/slaves>roles It shows consume "dev" in my side.
On Sun, May 1, 2016 at 3:04 PM, caogaojin
wrote:
> @Haosdent, by the way, i’m using mesos:0.28.1, not the master branch. and
> marathon version
under finding the root cause of it.
On Sun, May 1, 2016 at 4:24 PM, caogaojin
wrote:
> @Haosdent, what does http://10.132.46.71:5050/roles mean? shouldn’t that
> tell us all resources that framework with `dev` role takes, both from `dev`
> and `*` role? It doesn’t mean resources are cons
e.com/forum/?hl=en#!forum/marathon-framework . Thanks a
lot!
On Sun, May 1, 2016 at 5:07 PM, haosdent wrote:
> hmm, I am still digging more information in marathon. It may delay because
> I am not familiar with marathon's code and sick today, but I would inform
> you once have result. My
;. This is why
your task works in static reservation while could not work in dynamic
reservation.
On Mon, May 2, 2016 at 9:10 AM, caogaojin
wrote:
> @Haosdent, sorry for delay; i’m not familiar with scala, the compilation
> takes me some time. you are right, after changing the file you told
accepted?
>
> Thx
>
--
Best Regards,
Haosdent Huang
o schedule a task which consume all resources of a
> machine.
>
> Do you have some advises how to implement such a scheduler. Is there
> another scheduler which already implemented something similar?
>
> Thank you and best regards
> Christoph
>
--
Best Regards,
Haosdent Huang
x27; of framework
> e093b9e5-ad72-40e0-b686-9d41691141e5-1265' because it did not register
> within 1mins
>
> stderr shows some files being unzipped
>
>
> Rinaldo
--
Best Regards,
Haosdent Huang
it sets those tasks to TASK_LOST causing the
>> master to kill them on partition heal. It also means the scheduler gets
>> bogged down when you have many tasks with many healthchecks defined.
>>
>> Can this feature get a Shepard as would be useful for making mesos task
that others it will save
> countless hours of debugging IMO. I realize OSX is an odd system -- linux
> at times, Apple specific at times in areas that conflict with Linux but
> this will only get more complicated when Windows agents become available.
>
>
>
> Rinaldo
--
Best Regards,
Haosdent Huang
ubmit anyway.
>>
>>
>> Should I:
>>
>> * Bundle spark-submit tool along my app
>>
>> * Make sure spark-submit command is available on all mesos-slave
>>
>> * Forget this and do something better
>>
>>
>> Thanks in advance,
>>
>>
>> Best regards, Adam.
>>
>>
>>
>>
>
--
Best Regards,
Haosdent Huang
ubject to the terms and conditions in any governing
> contract. If you have received this e-mail in error, please immediately
> contact the sender and delete the e-mail.
>
--
Best Regards,
Haosdent Huang
radar.com
>
> Many thanks
>
> Lee
>
--
Best Regards,
Haosdent Huang
and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy.
>
> __
>
> www.accenture.com
>
--
Best Regards,
Haosdent Huang
led state.
>>>> 5月 16 15:30:42 chenqiang-worker-dev004-XXX systemd[1]:
>>>> dcos-mesos-slave.service failed.
>>>>
>>>> but can't find the root cause that make mesos-slave ABRT.
>>>>
>>>> On 2016年05月16日 14:38, 陈强 wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>>
>>>>> I installed a DC/OS cluster, but found that no agents were shown/found
>>>>> in cluster after finishing GUI installer.
>>>>> Other components are OK. Does someone met the issue? thanks.
>>>>>
>>>>>
>>>>> Best Regards.
>>>>> Chen, Qiang
>>>>>
>>>>>
>>>>
>>
> --
> 陈强
>
> 技术产品中心 计算云 弹性计算
> 手机：＋86 15900964316
> 分机：8377
>
>
--
Best Regards,
Haosdent Huang
it would be nice to do a website
> refresh.
>
> Please reply to this email if you are interested.
>
> Thanks,
> Vinod
>
--
Best Regards,
Haosdent Huang
xcept that it loads the cni isolator.
>
> Is there some user documentation for this feature? If not I am happy
> to write documentation once I figure out how this feature works.
>
> Cheers,
>
> Frank
>
--
Best Regards,
Haosdent Huang
ject: Re: Mesos Calico CNI
>
> >
> > Thanks. I now like to run that unit test via the debugger from the
> > Mesos source try in CLion. Is there a doc on how to build Mesos in
> > CLion and debug a unit test?
> >
> > Also, where does net::links() come from? Ca
nks all for your help.
>
>
> On 2016年05月17日 23:18, Chengwei Yang wrote:
>
>> ABRT generally means that something crittical happened and you may not
>> found
>> that from stdout/stderr, so as journalctl.
>>
>> You may try to run ExecXXX in its ervice file from console manually to
>> see what
>> will happen and get some hints.
>>
>>
>
--
Best Regards,
Haosdent Huang
I can take to avoid this mildly calamitous
>occurrence?
>- (Also, I'd be grateful for more clarity on anything in steps 1-4
>above that is a bit hand-wavy!)
>
> As always, thanks.
>
> -Paul
>
>
>
--
Best Regards,
Haosdent Huang
gt;
> >> > Frank Scholten wrote on 05/17/2016 20:47:12:
> >> >
> >> >> From: Frank Scholten
> >> >> To: user@mesos.apache.org
> >> >> Cc: Qian AZ Zhang/China/IBM@IBMCN, avin...@mesosphere.io
> >> >> Date: 05/17/2016 20:48
> >
/0x400
>
> May 16 20:06:53 71 kernel: [193339.890967] [] ?
> wake_up_state+0x10/0x20
>
> May 16 20:06:53 71 kernel: [193339.890970] [] ?
> wake_futex+0x66/0x90
>
> May 16 20:06:53 71 kernel: [193339.890972] [] ?
> futex_wake+0x1b1/0x1d0
>
> May 16 20:06:53 71 kern
//www.cmcrc.com/
>
> Regards,
> Guillermo
>
>
--
Best Regards,
Haosdent Huang
0 36 11.111.111.111:22 11.154.185.216:52468
> ESTABLISHED
> tcp0 0 11.111.111.111:65066148.87.19.20:80
> TIME_WAIT
> tcp0 0 11.111.111.111:868 11.211.137.101:2049
> ESTABLISHED
> tcp0 0 11.111.111.111:6200111.128.128.94:58906
> ESTABLISHED
> tcp0 0 11.111.111.111:6543711.139.163.164:80
> TIME_WAIT
>
>
--
Best Regards,
Haosdent Huang
wrote:
>
> On May 20, 2016, at 09:38, haosdent wrote:
>
> Sorry, confusing here, you mentioned that you use OSX.
>
> >I am not using network isolation, since it doesn’t appear to be
> supported on OSX.
>
> Which conflict with
>
> >I have configured some Linux
t shows that it is using =
> the master I expected. =20
>
> 1) Node is running with master A
> 2) Node is stopped and attached to master B
>
> The node is now showing in both frameworks.
>
>
> Rinaldo
>
--
Best Regards,
Haosdent Huang
16, at 11:27, haosdent wrote:
>
> Hi, @DiGiorgio. Do master A and master B belongs to different clusters?
>
>
> Hi Haosdent Huang,
>
> You are a wealth of answers. I have been not naming the cluster. I assume
> that I need to name the clusters.
>
>
> Rinaldo
>
&g
> Zurich
>
> This e-mail message contains confidential information which is for the
> sole attention and use of the intended recipient. Please notify us at once
> if you think that it may not be intended for you and delete it immediately.
>
--
Best Regards,
Haosdent Huang
to run a framework scheduler on a Mesos slave node. I
> that possible?Does mesos-slave know how to pass scheduler requests back
> to a Mesos master node? Does one have to have mesos-master running on
> slave nodes to do this? Am I smoking bad stuff?
>
> Advice appreciated.
>
> - Kent
--
Best Regards,
Haosdent Huang
I remember last year have live streaming. :-)
On Wed, May 25, 2016 at 8:57 PM, Tomek Janiszewski
wrote:
> Hi
>
> Will the event be transmitted?
> It will be great to enable Mesos Users Groups from Europe to watch
> Keynotes live.
>
> Best
> Tomek
>
--
Best Regards,
Haosdent Huang
Oh, I remember it now. Someone use Periscope to live #MesosCon at that time
https://twitter.com/TonyDong3/status/634824541244493824 , so I could see
the scene from their share links.
On Wed, May 25, 2016 at 9:08 PM, Tomek Janiszewski
wrote:
> @haosdent Are you sure? I remember that everyth
r wrote:
>>
>>> Has anyone successfully taken the Mesos-related log messages that appear
>>> in /var/log/messages and moved them to another file? Not just duplicated
>>> them, but removed them.
>>>
>>> Thanks,
>>> June Taylor
>>> System Administrator, Minnesota Population Center
>>> University of Minnesota
>>>
>>
>>
>
--
Best Regards,
Haosdent Huang
the VM is getting it. Are there any ideas on how I can
> connect these VM's to the Mesos master, and why do they die out with
> internal IP's and a public interface mapping?
>
>
> best,
>
> O
>
>
--
Best Regards,
Haosdent Huang
pgrade from 0.21.0 to 0.25.0, we need to upgrade
the cluster to 0.22 first, then upgrade to 0.23, 0.24 and 0.25.0.
On Wed, May 25, 2016 at 10:54 AM, Qiang Chen wrote:
>
>
> On 2016年05月25日 10:11, haosdent wrote:
>
> > but come to step 3, why the running containers become KILLED o
at ports are needed by the master and slave
> to communicate?
>
> -O
>
>
> On 5/25/2016 12:11 PM, Stefano Bianchi wrote:
>
>> uld also edit the hosts file where you associate the hostnames of e
>>
>
>
--
Best Regards,
Haosdent Huang
the sole use of the intended
> recipient(s). Any review, use or distribution that has not been expressly
> authorized by Stem, Inc. is strictly prohibited. If you are not the
> intended recipient, please contact the sender and delete all copies. Thank
> you.
>
--
Best Regards,
Haosdent Huang
tachments contain Stem, Inc. confidential and
>> proprietary information and material for the sole use of the intended
>> recipient(s). Any review, use or distribution that has not been expressly
>> authorized by Stem, Inc. is strictly prohibited. If you are not the
>> intended
point is not connected [107]
> E0121 21:29:34.231999 11368 socket.hpp:174] Shutdown failed on fd=13:
> Transport endpoint is not connected [107]
>
>
--
Best Regards,
Haosdent Huang
ceptionsInMethodIfSupported<>()
> @ 0x18c2e17
> testing::internal::HandleExceptionsInMethodIfSupported<>()
> @ 0x18a12e4 testing::Test::Run()
> @ 0x18a1b34 testing::TestInfo::Run()
> @ 0x18a21cd testing::TestCase::Run()
> @ 0x18a9354 testing::internal::UnitTestImpl::RunAllTests()
> @ 0x18c9203
> testing::internal::HandleSehExceptionsInMethodIfSupported<>()
> @ 0x18c3a49
> testing::internal::HandleExceptionsInMethodIfSupported<>()
> @ 0x18a7ef2 testing::UnitTest::Run()
> @ 0xf2bb72 RUN_ALL_TESTS()
> @ 0xf2b70a main
> @ 0x7f5158b13ac0 (unknown)
> @ 0xa4e229 _start
> Makefile:10386: recipe for target 'check-local' failed
> make[3]: *** [check-local] Aborted (core dumped)
> make[3]: Leaving directory '/opt/mesos-0.28.1/build/src'
> Makefile:9724: recipe for target 'check-am' failed
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory '/opt/mesos-0.28.1/build/src'
> Makefile:9728: recipe for target 'check' failed
> make[1]: *** [check] Error 2
> make[1]: Leaving directory '/opt/mesos-0.28.1/build/src'
> Makefile:730: recipe for target 'check-recursive' failed
> make: *** [check-recursive] Error 1
>
--
Best Regards,
Haosdent Huang
should not be logged at the ERROR level. But as of
>> the current code, these log lines can't be silenced without losing all of
>> your logging verbosity :(
>>
>> BTW, the log line has been moved since 0.26, but it will still show up in
>> a different form:
>>
>
t;>> >>
> > >>> >> On Wednesday, May 25, 2016, Vinod Kone
> wrote:
> > >>> >>
> > >>> >>> Hi folks,
> > >>> >>>
> > >>> >>> As discussed in the previous community sync, we plan to cut a
> release
> > >>> >>> candidate for our next release (1.0) early next week.
> > >>> >>>
> > >>> >>> 1.0 is mainly centered around new APIs for Mesos. Please take a
> look
> > >>> at
> > >>> >>> MESOS-338 <https://issues.apache.org/jira/browse/MESOS-338> for
> > >>> >>> blocking issues. We got some great design and testing feedback
> for
> > >>> the v1
> > >>> >>> scheduler and executor APIs. Please do the same for the
> in-progress
> > >>> v1
> > >>> >>> operator API
> > >>> >>> <
> > >>>
> https://docs.google.com/document/d/1XfgF4jDXZDVIEWQPx6Y4glgeTTswAAxw6j8dPDAtoeI/edit?pref=2&pli=1#
> > >>> >
> > >>> >>> .
> > >>> >>>
> > >>> >>> Since this is a 1.0, we would like to do the release a little
> > >>> >>> differently.
> > >>> >>>
> > >>> >>> First, the voting period for vetting the release candidate would
> be a
> > >>> >>> few weeks (2-3 weeks) instead of the typical 3 days.
> > >>> >>>
> > >>> >>> Second, we are wiling to make major changes (scalability fixes,
> API
> > >>> >>> fixes) if there are any issues reported by the community.
> > >>> >>>
> > >>> >>> We are doing these because we really want the community to
> thoroughly
> > >>> >>> test the 1.0 release and give feedback.
> > >>> >>>
> > >>> >>> Thanks,
> > >>> >>>
> > >>> >>
> > >>> >>
> > >>> >> --
> > >>> >> Text by Jeff, typos by iPhone
> > >>> >>
> > >>> >
> > >>> >
> > >>>
> > >>
> > >>
> > >
>
--
Best Regards,
Haosdent Huang
the release is available at:
> >
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2-rc1
> >
> >
> >
>
> >
> > The candidate for Mesos 0.28.2 release is available at:
> >
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz
> >
> > The tag to be voted on is 0.28.2-rc1:
> >
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.28.2-rc1
> >
> > The MD5 checksum of the tarball can be found at:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz.md5
> >
> > The signature of the tarball can be found at:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.28.2-rc1/mesos-0.28.2.tar.gz.asc
> >
> > The PGP key used to sign the release is here:
> > https://dist.apache.org/repos/dist/release/mesos/KEYS
> >
> > The JAR is up in Maven in a staging repository here:
> > https://repository.apache.org/content/repositories/orgapachemesos-1140
> >
> > Please vote on releasing this package as Apache Mesos 0.28.2!
> >
> > The vote is open until Wed Jun 1 16:51:42 PDT 2016 and passes if a
> > majority of at least 3 +1 PMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Mesos 0.28.2
> > [ ] -1 Do not release this package because ...
> >
> > Thanks,
> > - Jie
> >
> >
> >
> >
> >
>
--
Best Regards,
Haosdent Huang
rpose of backwards compatibility.
>>
>>
>>
>>
>>
>> * [MESOS-5015] - Changes Call and Event Type enums in executor.proto
>>
>>
>> from required to optional for the purpose of backwards compatibility.
>>
>>
>>
>>
>>
>> * [MESOS-5029] - Added 'labels' to ExecutorInfo.
>>
>>
>>
>>
>>
>> * [MESOS-5030] - Added non-terminal task metadata to the container
>> resource
>>
>> usage information.
>>
>>
>>
>>
>>
>> * [MESOS-5408] - Deleted the /observe HTTP endpoint.
>>
>>
>>
>>
>>
>> 3rd Party Upgrades:
>>
>>
>> * [MESOS-4805] - Upgraded vendored ry-http-parser-1c3624a to
>> nodejs/http-parser 2.6.1.
>>
>> * [MESOS-4678] - Upgraded vendored protobuf 2.5.0 to 2.6.1.
>>
>>
>> * [MESOS-4803] - Upgraded vendored libev 4.15 to 4.22.
>>
>>
>> * [MESOS-4612] - Upgraded vendored ZooKeeper 3.4.5 to 3.4.8.
>>
>>
>>
>>
>>
>> Binary API Changes:
>>
>>
>> * [MESOS-5055] - Slave/Agent Rename Phase I - Update strings in the log
>> message
>>
>> and standard output.
>>
>>
>> * [MESOS-3782] - Slave/Agent Rename Phase I - Duplicate/Rename
>> binaries.
>>
>> * [MESOS-5057] - Slave/Agent Rename Phase I - Update strings in error
>> messages and
>>
>> other strings.
>>
>>
>> * [MESOS-5230] - Slave/Agent Rename Phase I: Rename
>> '/include/mesos/slave' folder
>>
>>
>> The CHANGELOG for the release is available at:
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.0-rc1
>>
>>
>>
>>
>>
>> The candidate for Mesos 1.0.0 release is available at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc1/mesos-1.0.0.tar.gz
>>
>>
>> The tag to be voted on is 1.0.0-rc1:
>>
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.0.0-rc1
>>
>>
>> The MD5 checksum of the tarball can be found at:
>>
>>
>> https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc1/mesos-1.0.0.tar.gz.md5
>>
>>
>> The signature of the tarball can be found at:
>>
>>
>> https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc1/mesos-1.0.0.tar.gz.asc
>>
>>
>> The PGP key used to sign the release is here:
>>
>> https://dist.apache.org/repos/dist/release/mesos/KEYS
>>
>>
>> The JAR is up in Maven in a staging repository here:
>>
>> https://repository.apache.org/content/repositories/orgapachemesos-1142
>>
>>
>> Please vote on releasing this package as Apache Mesos 1.0.0!
>>
>>
>> The vote is open until *Wed Jun 22 12:00 PM PST 2016* and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>>
>>
>> [ ] +1 Release this package as Apache Mesos 1.0.0
>>
>> [ ] -1 Do not release this package because ...
>>
>>
>> Thanks,
>>
>
>
--
Best Regards,
Haosdent Huang
r from reducing the length of offers or is
> there any way I can obtain the list of all available offers before the
> allocator sends them to the framework?
>
> Thanks.
> Regards,
> Nihal
>
--
Best Regards,
Haosdent Huang
t; loop 63 delay 10 ms
> loop 64 delay 10 ms
> loop 65 delay 11 ms
> loop 66 delay 10 ms
> loop 67 delay 10 ms
> loop 68 delay 10 ms
> loop 69 delay 10 ms
> loop 70 delay 10 ms
> loop 71 delay 10 ms
> loop 72 delay 11 ms
> loop 73 delay 10 ms
> loop 74 delay 10 ms
> loop 75 delay 10 ms
> loop 76 delay 11 ms
> loop 77 delay 10 ms
> loop 78 delay 10 ms
> loop 79 delay 10 ms
> loop 80 delay 11 ms
> loop 81 delay 10 ms
> loop 82 delay 10 ms
> loop 83 delay 10 ms
> loop 84 delay 10 ms
> loop 85 delay 10 ms
> loop 86 delay 10 ms
> loop 87 delay 10 ms
> loop 88 delay 10 ms
> loop 89 delay 10 ms
> loop 90 delay 10 ms
> loop 91 delay 10 ms
> loop 92 delay 10 ms
> loop 93 delay 10 ms
> loop 94 delay 10 ms
> loop 95 delay 10 ms
> loop 96 delay 10 ms
> loop 97 delay 10 ms
> loop 98 delay 10 ms
> loop 99 delay 10 ms
> total time = 1035 ms
>
>
>
>
--
Best Regards,
Haosdent Huang
env; sleep 2; done, that LIBPROCESS_IP is defined in the
> environment. However, when running a docker image this variable is not
> defined.
>
> Is there a way to have marathon pass along all environment variables
> defined by mesos?
> Thanks
> Eli
>
> On 4 Apr 2016, at 14:12, Eli
;>>>
>>>> mesos-docker-executor: error while loading shared libraries:
>>>> libmesos-0.28.2.so: cannot open shared object file: No such file or
>>>> directory
>>>>
>>>> Just like for Mesos 0.28.1 where it works, libmesos-0.28.2 is in
>>>> /usr/local/lib
>>>> There is also symlink libmesos.so -> libmesos-0.28.2.
>>>> /etc/ld.so.conf.d/libc.conf contains /usr/local/lib entry.
>>>> I have also tried exporting LD_LIBRARY_PATH in startup scripts, no luck.
>>>>
>>>> Thanks,
>>>> Kamil
>>>>
>>>>
>>>
>>
>
--
Best Regards,
Haosdent Huang
nks James and Haosdent,
>
> I built my own version of mesos 1.0 and installed it on 10.11.5 and I am
> getting the same results as 10.10.5 with 0.28.1
>
> Do either of you remember what you may have set on your OSX machines to
> default some of the desktop settings that may be causi
yes, mine is a laptop.
On Mon, Jun 6, 2016 at 11:23 PM, DiGiorgio, Mr. Rinaldo S. <
rdigior...@pace.edu> wrote:
>
> On Jun 6, 2016, at 11:08, haosdent wrote:
>
> I use OS X 10.11.4 but I think it should not related to this minor
> different on OS X version.
> For set
functionIFN7process6FutureI7NothingEERKN5mesos8internal8RegistryEEERKSt10shared_ptrINS1_7PromiseIS3_EEERKNS2_IS7_EEESB_SH_St12_PlaceholderILi16__callIvISM_EILm0ELm1ELm2T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
>> >>>@ 0x7f4b8050fa3b std::_Bind<>::operator()<>()
>> >>>@ 0x7f4b804f94e3 std::_Function_handler<>::_M_invoke()
>> >>>@ 0x7f4b8050fc69 std::function<>::operator()()
>> >>>@ 0x7f4b804f9609
>> >>>
>> >>
>> _ZZNK7process6FutureIN5mesos8internal8RegistryEE5onAnyIRSt8functionIFvRKS4_EEvEES8_OT_NS4_6PreferEENUlS8_E_clES8_
>> >>>@ 0x7f4b80517936
>> >>>
>> >>
>> _ZNSt17_Function_handlerIFvRKN7process6FutureIN5mesos8internal8RegistryZNKS5_5onAnyIRSt8functionIS8_EvEES7_OT_NS5_6PreferEEUlS7_E_E9_M_invokeERKSt9_Any_dataS7_
>> >>>@ 0x7f4b8050fc69 std::function<>::operator()()
>> >>>@ 0x7f4b8056b1b4 process::internal::run<>()
>> >>>@ 0x7f4b80561672 process::Future<>::fail()
>> >>>@ 0x7f4b8059bf5f std::_Mem_fn<>::operator()<>()
>> >>>@ 0x7f4b8059757f
>> >>>
>> >>
>> _ZNSt5_BindIFSt7_Mem_fnIMN7process6FutureIN5mesos8internal8RegistryEEEFbRKSsEES6_St12_PlaceholderILi16__callIbIS8_EILm0ELm1T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
>> >>>@ 0x7f4b8058fad1
>> >>>
>> >>
>> _ZNSt5_BindIFSt7_Mem_fnIMN7process6FutureIN5mesos8internal8RegistryEEEFbRKSsEES6_St12_PlaceholderILi1clIJS8_EbEET0_DpOT_
>> >>>@ 0x7f4b80585a41
>> >>>
>> >>
>> _ZZNK7process6FutureIN5mesos8internal8RegistryEE8onFailedISt5_BindIFSt7_Mem_fnIMS4_FbRKSsEES4_St12_PlaceholderILi1bEERKS4_OT_NS4_6PreferEENUlS9_E_clES9_
>> >>>@ 0x7f4b80597605
>> >>>
>> >>
>> _ZNSt17_Function_handlerIFvRKSsEZNK7process6FutureIN5mesos8internal8RegistryEE8onFailedISt5_BindIFSt7_Mem_fnIMS8_FbS1_EES8_St12_PlaceholderILi1bEERKS8_OT_NS8_6PreferEEUlS1_E_E9_M_invokeERKSt9_Any_dataS1_
>> >>>@ 0x49d257 std::function<>::operator()()
>> >>>@ 0x49837f
>> >>>
>> >>
>> _ZN7process8internal3runISt8functionIFvRKSsEEJS4_EEEvRKSt6vectorIT_SaIS8_EEDpOT0_
>> >>>@ 0x7f4b8056164a process::Future<>::fail()
>> >>>@ 0x7f4b8055a378 process::Promise<>::fail()
>> >>>
>> >>> I tried both Zookeeper 3.4.8 and 3.4.6 with latest code of Mesos, but
>> no
>> >>> luck for both. Any ideas about what happened? Thanks.
>> >>>
>> >>>
>> >>>
>> >>> Thanks,
>> >>> Qian Zhang
>> >>
>>
>>
>
--
Best Regards,
Haosdent Huang
to use a routable IP address.”
>>>
>>> I tried setting LIBPROCESS_IP to ‘0.0.0.0’ and
>>> LIBPROCESS_ADVERTISE_IP=‘the public ip’ and this works. But the host
>>> variations don’t seem to work. (i.e. set LIBPROCESS_IP=0.0.0.0 and
>>> LIBPROCESS_ADVERTISE_H
ew Spyker (aspy...@netflix.com <mailto:aspy...@netflix.com>)
>>> > Twitter: @aspyker Blog: ispyker.blogspot.com
>>> <http://ispyker.blogspot.com>
>>> >
>>>
>>>
>>>
>>>
>>> --
>>> Deshi Xiao
>>> Twitter: xds2000
>>> E-mail: xiaods(AT)gmail.com <http://gmail.com>
>>>
>>
>>
>
>
> --
> *Jan Schlicht*
> Distributed Systems Engineer, Mesosphere
>
--
Best Regards,
Haosdent Huang
t;>>>>> 11:29:42---Hi folks, I am proposing moving our content in Wiki (e.g.,
>>>>>>> wor]Jie
>>>>>>> Yu ---2016-06-06 上午 11:29:42---Hi folks, I am proposing moving our
>>>>>>> content
>>>>>>> in Wiki (e.g., working groups, release
>>>>>>>
>>>>>>> From: Jie Yu
>>>>>>> To: mesos , "user@mesos.apache.org" <
>>>>>>> user@mesos.apache.org>
>>>>>>> Date: 2016-06-06 上午 11:29
>>>>>>> Subject: Proposal: move content in Wiki to docs in code repo
>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi folks,
>>>>>>>
>>>>>>> I am proposing moving our content in Wiki (e.g., working groups,
>>>>>>> release
>>>>>>> tracking, etc.) to our docs in the code repo. I personally found
>>>>>>> that wiki
>>>>>>> is hard to use and there's no reviewing process for changes in the
>>>>>>> Wiki.
>>>>>>> The content in Wiki historically received less attention than that
>>>>>>> in the
>>>>>>> docs.
>>>>>>>
>>>>>>> What do you think?
>>>>>>>
>>>>>>> - Jie
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Deshi Xiao
>>>> Twitter: xds2000
>>>> E-mail: xiaods(AT)gmail.com
>>>>
>>>
>>>
--
Best Regards,
Haosdent Huang
e and the Windows work. His formal committer
>>> checklist
>>> is here
>>> <
>>> https://docs.google.com/document/d/1o7qLQJQ7TZCaf49gSNc6SSl29qAFagYH2STDfhHDDPw/edit?usp=sharing
>>> >
>>> .
>>>
>>> Please join me in congratulating them on their new roles and especially
>>> responsibilities :)
>>>
>>> On behalf of the PMC,
>>> Vinod
>>>
>>
>>
>
--
Best Regards,
Haosdent Huang
find your logs there.
>>>> Otherwise, the logs will be in stderr.
>>>> If you launched the master via a systemd service, use: journalctl -u
>>>> mesos-master
>>>>
>>>>
>>>> On Fri, Jun 10, 2016 at 9:45 AM, Stefano Bianchi
>>>> wrote:
>>>>
>>>>> Actually i don't have the access to the Mesos UI so i need to find the
>>>>> log within CentOS VM.
>>>>> Please can you tell me where can i find the master log file ?
>>>>>
>>>>> 2016-06-10 17:50 GMT+02:00 Jie Yu :
>>>>>
>>>>>> Can u create a jira ticket and paste the master log? Thanks for
>>>>>> reporting!
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>> On Jun 10, 2016, at 8:44 AM, Stefano Bianchi
>>>>>> wrote:
>>>>>>
>>>>>> Hi all
>>>>>> i'm re installing my platform on another openstack tenant.
>>>>>> I downloaded all the needed softwares, zookeeper-server, mesos 0.28.2
>>>>>> marathon 1.1.1 and chronos 2.4.0.
>>>>>> i have configured all correctly the i started zookeeper-server and it
>>>>>> works fine.
>>>>>> when i type: service mesos-master start
>>>>>> it seems to start but if i check the status with: service
>>>>>> mesos-master status
>>>>>> i obtain the following:
>>>>>>
>>>>>> [root@master ~]# service mesos-master status
>>>>>>
>>>>>> Redirecting to /bin/systemctl status mesos-master.service
>>>>>>
>>>>>> ● mesos-master.service - Mesos Master
>>>>>>
>>>>>>Loaded: loaded (/usr/lib/systemd/system/mesos-master.service;
>>>>>> enabled; vendor preset: disabled)
>>>>>>
>>>>>>Active: activating (auto-restart) (Result: signal) since ven
>>>>>> 2016-06-10 15:39:36 UTC; 3s ago
>>>>>>
>>>>>> Process: 12163 ExecStart=/usr/bin/mesos-init-wrapper master
>>>>>> *(code=killed,
>>>>>> signal=ABRT)*
>>>>>>
>>>>>> Main PID: 12163 (code=killed, signal=ABRT)
>>>>>>
>>>>>>
>>>>>> Any one knows why i have this issue?
>>>>>>
>>>>>> Thanks in advance.
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
--
Best Regards,
Haosdent Huang
re:
>> server.1=192.168.100.3:2888:3888
>> server.2=192.168.100.4:2888:3888
>> server.3=192.168.10.3:2888:3888
>>
>> these are the correct IPs i have set in this file.
>>
>> 2016-06-11 15:36 GMT+02:00 haosdent :
>>
>>> If 10.250.0.12:
to make a
>> group specializing in technologies built around Mesos platform.
>> On my full time job, I manage an in-house mesos cluster and write various
>> utilities, such as our scaling platform.
>>
>> I would appreciate if you add our group to the list of MUGs
>> http://mesos.apache.org/community/user-groups/ and make it official.
>> --
>> *Ioannis Petrousov*
>>
>
>
--
Best Regards,
Haosdent Huang
by login or sudo when running as a user, but I can't
> seem to find a way to use these to set up a proper environment as the
> target user. Is there a reason we don't call getpwuid() to set a
> $HOME during setup of execlp() from executor.cpp? (Oh, and might as well
> populate $USER while we're at it)
>
> Thanks,
> -Hansel
>
--
Best Regards,
Haosdent Huang
0615 15:01:43.325469 4172 mem.cpp:722] Started listening on low memory
> > pressure events for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc
> > I0615 15:01:43.326004 4172 mem.cpp:722] Started listening on medium
> > memory pressure events for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc
> > I0615 15:01:43.326539 4172 mem.cpp:722] Started listening on critical
> > memory pressure events for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc
> >
> > ```
> >
> > Did someone suffer this? thanks.
> >
> > --
> > Best Regards,
> > Chen, Qiang
> >
> >
>
--
Best Regards,
Haosdent Huang
18, 2016 at 12:08 AM, wrote:
> Hi Haosdent,
>
> Yes, I had confirmed that setuid does get called correctly, and the shell
> environment is not set up. My question is more along the lines of "is this
> expected? is it a bug? is it intentional?"
> If it wasn't inten
the guide about submitting a patch described here
> http://mesos.apache.org/documentation/latest/submitting-a-patch/
> or it's just a simple merge?
>
> On 16/6/2016 10:50 πμ, Ioannis Petrousov wrote:
>
> Hello, @Haosdent
>
> I was suspecting that I should've done a pull
g started guide and the support/docker_build.sh scripts have
> > been updated appropriately, but you may need to update your local
> > environment if you don't yet have these packages installed.
> >
> > --
> > ~Kevin
> >
>
>
>
> --
> Cheers,
>
> Zhitao Li
>
--
Best Regards,
Haosdent Huang
Mesos yet -- we just
>> >> added the libelf dependence in anticipation of it.
>> >>
>> >>
>> >>
>> >>
>> >> On Mon, Jun 20, 2016 at 12:59 PM, Yan Xu wrote:
>> >>> It's not immediately clear form the ticket why
allow executors to reject killing
> requests entirely?
>
> This could be quite useful to stateful services where data
> replication/backfilling latencies are not known in advance and as such
> 'grace_period' may not fit or would result in artificially inflated
> timeout
and notify the sender by
> return email. Unauthorized reading, dissemination, distribution or copying
> of this communication is prohibited. This communication does not constitute
> an offer to sell or a solicitation of an indication of interest to purchase
> any loan, security or any other financial product or instrument, nor is it
> an offer to sell or a solicitation of an indication of interest to purchase
> any products or services to any persons who are prohibited from receiving
> such information under applicable law. The contents of this communication
> may not be accurate or complete and are subject to change without notice.
> As such, Orchard App, Inc. (including its subsidiaries and affiliates,
> "Orchard") makes no representation regarding the accuracy or completeness
> of the information contained herein. The intended recipient is advised to
> consult its own professional advisors, including those specializing in
> legal, tax and accounting matters. Orchard does not provide legal, tax or
> accounting advice.
>
--
Best Regards,
Haosdent Huang
;
> `delegate=true` explicitly in mesos-slave.service when using centos 7 after
> mesos version 0.25.0 ?
>
> thanks.
>
> --
> Best Regards,
> Chen, Qiang
>
>
--
Best Regards,
Haosdent Huang
rote:
> but in the bottom of
> http://mesos.apache.org/documentation/latest/agent-recovery/
>
> it recommends to use `KillMode=control-group` now.
>
>
> On 2016年06月28日 11:32, haosdent wrote:
>
> According to
> https://github.com/mesosphere/mesos-deb-packaging/blob/mas
d up by the executor:
>
> *FileNotFoundError: [Errno 2] No such file or directory:
> '"\\/home\\/john\\/temp_output\\/test.csv"'*
>
> *I0629 10:13:13.814870 14025 exec.cpp:390] Executor asked to shutdown*
>
> Are other people experiencing this? What is the method to avoid it?
> Thanks,
> June Taylor
> System Administrator, Minnesota Population Center
> University of Minnesota
>
--
Best Regards,
Haosdent Huang
executor end?
>>
>>
>> Thanks,
>> June Taylor
>> System Administrator, Minnesota Population Center
>> University of Minnesota
>>
>> On Wed, Jun 29, 2016 at 2:02 PM, haosdent wrote:
>>
>>> Hi, @Taylor I use
>>>
>>> ```
ot;: "/home/john/temp_output/test.csv"}'': syntax error at
> line 1 near: '{"MY_FILEPATH": "/home/john/temp_output/test.csv"}'
>
>
> We're using the Bash shell. Is anyone else passing file-paths within their
> environment variabl
ommand=/home/john/anaconda3/bin/python /home/john/mesos/error_msg.py
>>> read
>>>
>>> Similarly how is the shell to know that you *don't* want to end this
>>> command and start a new one when you have a bare semicolon?
>>>
>>> --resou
; Thanks,
> June Taylor
> System Administrator, Minnesota Population Center
> University of Minnesota
>
> On Thu, Jun 30, 2016 at 12:28 PM, Chris Baker
> wrote:
>
>> +1
>>
>> On Thu, Jun 30, 2016 at 1:15 PM haosdent wrote:
>>
>>> Actually you c
have a custom executor to return large size
> (~200mb) value (e.g. matrix array, or numpy array) ?
>
> B.R
> Bryan
>
--
Best Regards,
Haosdent Huang
Hi, @Bryan. So far mesos fetcher only support
* ftps,ftp,https,http (via libcurl)
* hdfs, hftp, s3, s3n (via hadoop client)
On Wed, Jul 6, 2016 at 9:41 AM, Bryan Fok wrote:
> Hi all
>
> Is it possible to do scp over the mesos fetcher?
>
> BR
> Bryan
>
--
Best Regards,
Haosdent Huang
+1
Tested on CentOS 7.
- sudo make check
- upgrade from 0.28.2 to 1.0.0-rc2
On Fri, Jul 15, 2016 at 7:47 PM, Alex Rukletsov wrote:
> Haosdent investigated the issue, and it seems that health checks do work
> for docker executor. Hence I retract my negative vote.
>
> On Fri, Jul 15
OT_NS8_6PreferEEUlS1_E_E9_M_invokeERKSt9_Any_dataS1_
> @ 0x4a4833 std::function<>::operator()()
> @ 0x49f0eb
>
> _ZN7process8internal3runISt8functionIFvRKSsEEJS4_EEEvRKSt6vectorIT_SaIS8_EEDpOT0_
> @ 0x7fe6f9176ecc process::Future<>::fail()
> @ 0x7fe6f916feac process::Promise<>::fail()
>
>
>
> error logs is
> Log file created at: 2016/07/19 11:50:25
> Running on machine: oss-mesos-master-bjc-001
> Log line format: [IWEF]mmdd hh:mm:ss.uu threadid file:line] msg
> F0719 11:50:25.262277 5381 master.cpp:1662] Recovery failed: Failed to
> recover registrar: Failed to perform fetch within 2mins
> can you help me.thanks
>
--
Best Regards,
Haosdent Huang
What I'm doing wrong?
>
> Is anyone else experiencing the same issue?
>
> I'm running the following mesos/marathon version on centos 7u2:
>
> [root@cluster1-headnode1 ~]# rpm -qa |grep -Ew 'mesos|marathon'
> marathon-1.1.1-1.0.472.el7.x86_64
> mesos-0.28.1-2.0.20.centos701406.x86_64
>
> Thanks in advance.
>
> Cheers,
> Matteo
>
>
--
Best Regards,
Haosdent Huang
nt server
>
>
> -- 原始邮件 ------
> *发件人:* "haosdent";;
> *发送时间:* 2016年7月19日(星期二) 下午5:05
> *收件人:* "user";
> *主题:* Re: mesos crash
>
> Hi,
> >I start two master node :
> Did you start them in a same server with same work di
; Best regards,
>
> Attila Szarvas
> Research Engineer
> Nokia Bell Labs, Budapest
--
Best Regards,
Haosdent Huang
t;
> >
> >
> >
> > * [MESOS-4424] - Support for using Nvidia GPUs as a resource in the
> >
> >
> > Mesos "unified" containerizer. This support includes running
> > containers
> >
> > with and without filesystem isolation (i.e. running both imageless
> >
> >
> > containers as well as containers using a docker image). Frameworks
> > must
> >
> > opt-in to receiving GPU resources via the GPU_RESOURCES framework
> >
> >
> > capability (see the scarce resource problem in MESOS-5377). We
> > support
> >
> > 'nvidia-docker'-style docker containers by injecting a volume that
> >
> >
> > contains the Nvidia libraries / binaries when the docker image has
> >
> >
> > the 'com.nvidia.volumes.needed' label. Support for the docker
> >
> >
> > containerizer will come in a future release.
> >
> >
> >
> > * [MESOS-5724] - SSL certificate validation allows for additional IP
> > address
> >
> > subject alternative name extension verification.
> >
> > The CHANGELOG for the release is available at:
> >
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.0-rc4
> >
> >
> >
>
> >
> >
> > The candidate for Mesos 1.0.0 release is available at:
> >
> >
> https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc4/mesos-1.0.0.tar.gz
> >
> >
> > The tag to be voted on is 1.0.0-rc4:
> >
> > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.0.0-rc4
> >
> >
> > The MD5 checksum of the tarball can be found at:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc4/mesos-1.0.0.tar.gz.md5
> >
> >
> > The signature of the tarball can be found at:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc4/mesos-1.0.0.tar.gz.asc
> >
> >
> > The PGP key used to sign the release is here:
> >
> > https://dist.apache.org/repos/dist/release/mesos/KEYS
> >
> >
> > The JAR is up in Maven in a staging repository here:
> >
> > https://repository.apache.org/content/repositories/orgapachemesos-1153
> >
> >
> > Please vote on releasing this package as Apache Mesos 1.0.0!
> >
> >
> > [ ] +1 Release this package as Apache Mesos 1.0.0
> >
> > [ ] -1 Do not release this package because ...
> >
> >
> > Thanks,
> >
>
--
Best Regards,
Haosdent Huang
t the EXPOSE directive in Dockerfiles?
>
>
> What must be done in order to network docker containers properly? (Esp.
> with the Aurora framework)
>
>
>
> Thank you!
>
>
>
--
Best Regards,
Haosdent Huang
nshakeable conclusion as container technology is
> evolving at an ever faster pace, but the whole community, especially
> newbies like myself, would profoundly benefit from a clear plan and
> priority for next 3-6 months.
>
> Cheers,
> /Jay
>
>
--
Best Regards,
Haosdent Huang
- is there a way to "link" the cgroup id to the mesos task id?
>
>
> Thanks for any clue.
>
>
> And a good sysadmin appreciation day!
>
>
> Aurélien.
>
>
--
Best Regards,
Haosdent Huang
to root `/`.
>
> Thanks for the answer.
> --
> *De :* haosdent
> *Envoyé :* vendredi 29 juillet 2016 16:21:07
> *À :* user
> *Objet :* Re: Cadvisor and Mesos: cgroup monitoring
>
> >- is there a way to "link" the cgroup id to the m
ent Docker bridge/user mode with Mesos is far more easy to
>> setup/use.
>>
>> Olivier
>>
>>
>>
>> I would appreciate it if you could either share your ideas or vote on
>> these items, and we will discuss it in next community sync.
>>
>> We may not have an unshakeable conclusion as container technology is
>> evolving at an ever faster pace, but the whole community, especially
>> newbies like myself, would profoundly benefit from a clear plan and
>> priority for next 3-6 months.
>>
>> Cheers,
>> /Jay
>>
>>
>>
>
>
> --
> Cheers,
>
> Zhitao Li
>
--
Best Regards,
Haosdent Huang
301 - 400 of 512 matches
Mail list logo
