Re: Attendance for Mesos Developer Community Meeting (Nov 17)

2016-11-16 Thread Joseph Wu 
+0.9

Is there an agenda in case there are enough attendees?

On Wed, Nov 16, 2016 at 3:15 PM, James Peach  wrote:

>
> > On Nov 16, 2016, at 3:06 PM, Michael Park  wrote:
> >
> > If you're planning to attend this meeting, please reply to this before
> Nov
> > 17 8am PST. If there are less than 5 people planning to attend (including
> > me), we'll skip it.
>
> +1
>
> >
> > On Wed, Nov 16, 2016 at 11:02 AM, Haripriya Ayyalasomayajula <
> > aharipriy...@gmail.com> wrote:
> >
> >> +1.
> >>
> >> On Wed, Nov 16, 2016 at 10:58 AM, Michael Park 
> wrote:
> >>
> >>> Many people will be in China for MesosCon, so I'd like to get a quick
> >> count
> >>> for how many people are planning to join the developer community
> meeting
> >>> tomorrow.
> >>>
> >>> Please reply with a +1 if you're planning to attend.
> >>>
> >>
> >>
> >>
> >> --
> >> Regards,
> >> Haripriya Ayyalasomayajula
> >>
>
>

Re: Attendance for Mesos Developer Community Meeting (Nov 17)

2016-11-16 Thread James Peach 

> On Nov 16, 2016, at 3:06 PM, Michael Park  wrote:
> 
> If you're planning to attend this meeting, please reply to this before Nov
> 17 8am PST. If there are less than 5 people planning to attend (including
> me), we'll skip it.

+1

> 
> On Wed, Nov 16, 2016 at 11:02 AM, Haripriya Ayyalasomayajula <
> aharipriy...@gmail.com> wrote:
> 
>> +1.
>> 
>> On Wed, Nov 16, 2016 at 10:58 AM, Michael Park  wrote:
>> 
>>> Many people will be in China for MesosCon, so I'd like to get a quick
>> count
>>> for how many people are planning to join the developer community meeting
>>> tomorrow.
>>> 
>>> Please reply with a +1 if you're planning to attend.
>>> 
>> 
>> 
>> 
>> --
>> Regards,
>> Haripriya Ayyalasomayajula
>>

Re: Attendance for Mesos Developer Community Meeting (Nov 17)

2016-11-16 Thread Michael Park 
If you're planning to attend this meeting, please reply to this before Nov
17 8am PST. If there are less than 5 people planning to attend (including
me), we'll skip it.

On Wed, Nov 16, 2016 at 11:02 AM, Haripriya Ayyalasomayajula <
aharipriy...@gmail.com> wrote:

> +1.
>
> On Wed, Nov 16, 2016 at 10:58 AM, Michael Park  wrote:
>
> > Many people will be in China for MesosCon, so I'd like to get a quick
> count
> > for how many people are planning to join the developer community meeting
> > tomorrow.
> >
> > Please reply with a +1 if you're planning to attend.
> >
>
>
>
> --
> Regards,
> Haripriya Ayyalasomayajula
>

Re: Mesos V1 Operator HTTP API - Java Proto Classes

2016-11-16 Thread Joseph Wu 
Added.  Welcome to the contributors list :)

On Wed, Nov 16, 2016 at 9:49 AM, Vijay Srinivasaraghavan <
vijikar...@yahoo.com> wrote:

> I have created a JIRA and will submit a patch. Could someone please add me
> to the contributor list as I am not able to assign the JIRA to myself?
>
> https://issues.apache.org/jira/browse/MESOS-6597
>
>
>
>
> On Wednesday, November 16, 2016 9:00 AM, Anand Mazumdar 
> wrote:
>
>
> We wanted to move the project away from officially supporting anything
> other than C++ and discuss more on if we should be responsible for
> publishing to the various language specific channels. However, for the time
> being, we had decided to include the v1 protobufs in the mesos JAR itself.
> (it already contains the v1 Scheduler/Executor protos)
>
> Please file an issue as Zameer pointed out.
>
> -anand
>
> On Wed, Nov 16, 2016 at 8:34 AM, Zameer Manji  wrote:
>
> > I think this is a bug, I feel the jar should include all v1 protobuf
> files.
> >
> > Vijay, I encourage you to file a ticket.
> >
> > On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
> > vijikar...@yahoo.com.invalid> wrote:
> >
> >> I believe the HTTP API will use the same underlying message format
> (proto
> >> def) and hence the request/response value objects (java) needs to be
> >> auto-generated from the proto files for it to be used in Jersey based
> java
> >> rest client?
> >>
> >>On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
> >> jani...@gmail.com> wrote:
> >>
> >>
> >>  I suspect jar is deprecated and includes only old API used by mesoslib.
> >> The
> >> goal is to create HTTP API and stop supporting native libs (jars, so,
> >> etc).
> >> I think you shouldn't use that jar in your project.
> >>
> >> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
> >> vijikar...@yahoo.com> napisał:
> >>
> >> > Hello,
> >> >
> >> > I am writing a rest client for "operator APIs" and found that some of
> >> the
> >> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
> >> > "include/mesos/v1/master/master.proto") are not included in the mesos
> >> jar
> >> > file. While investigating, I have found that the "Make" file does not
> >> > include these proto definition files.
> >> >
> >> > I have updated the Make file and added the protos that I am interested
> >> in
> >> > and built a new jar file. Is there any reason why these proto
> >> definitions
> >> > are not included in the original build apart from the reason that the
> >> APIs
> >> > are still evolving?
> >> >
> >> > Regards
> >> > Vijay
> >> >
> >>
> >> --
> >> Zameer Manji
> >>
> >
>
>
>

Re: Attendance for Mesos Developer Community Meeting (Nov 17)

2016-11-16 Thread Haripriya Ayyalasomayajula 
+1.

On Wed, Nov 16, 2016 at 10:58 AM, Michael Park  wrote:

> Many people will be in China for MesosCon, so I'd like to get a quick count
> for how many people are planning to join the developer community meeting
> tomorrow.
>
> Please reply with a +1 if you're planning to attend.
>



-- 
Regards,
Haripriya Ayyalasomayajula

Attendance for Mesos Developer Community Meeting (Nov 17)

2016-11-16 Thread Michael Park 
Many people will be in China for MesosCon, so I'd like to get a quick count
for how many people are planning to join the developer community meeting
tomorrow.

Please reply with a +1 if you're planning to attend.

Re: Mesos V1 Operator HTTP API - Java Proto Classes

2016-11-16 Thread Vijay Srinivasaraghavan 
I have created a JIRA and will submit a patch. Could someone please add me to 
the contributor list as I am not able to assign the JIRA to myself?
https://issues.apache.org/jira/browse/MESOS-6597


 

On Wednesday, November 16, 2016 9:00 AM, Anand Mazumdar  
wrote:
 

 We wanted to move the project away from officially supporting anything
other than C++ and discuss more on if we should be responsible for
publishing to the various language specific channels. However, for the time
being, we had decided to include the v1 protobufs in the mesos JAR itself.
(it already contains the v1 Scheduler/Executor protos)

Please file an issue as Zameer pointed out.

-anand

On Wed, Nov 16, 2016 at 8:34 AM, Zameer Manji  wrote:

> I think this is a bug, I feel the jar should include all v1 protobuf files.
>
> Vijay, I encourage you to file a ticket.
>
> On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
> vijikar...@yahoo.com.invalid> wrote:
>
>> I believe the HTTP API will use the same underlying message format (proto
>> def) and hence the request/response value objects (java) needs to be
>> auto-generated from the proto files for it to be used in Jersey based java
>> rest client?
>>
>>    On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
>> jani...@gmail.com> wrote:
>>
>>
>>  I suspect jar is deprecated and includes only old API used by mesoslib.
>> The
>> goal is to create HTTP API and stop supporting native libs (jars, so,
>> etc).
>> I think you shouldn't use that jar in your project.
>>
>> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
>> vijikar...@yahoo.com> napisał:
>>
>> > Hello,
>> >
>> > I am writing a rest client for "operator APIs" and found that some of
>> the
>> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
>> > "include/mesos/v1/master/master.proto") are not included in the mesos
>> jar
>> > file. While investigating, I have found that the "Make" file does not
>> > include these proto definition files.
>> >
>> > I have updated the Make file and added the protos that I am interested
>> in
>> > and built a new jar file. Is there any reason why these proto
>> definitions
>> > are not included in the original build apart from the reason that the
>> APIs
>> > are still evolving?
>> >
>> > Regards
>> > Vijay
>> >
>>
>> --
>> Zameer Manji
>>
>

[GitHub] mesos issue #182: Add TFMesos in frameworks.md

2016-11-16 Thread haosdent 
Github user haosdent commented on the issue:

https://github.com/apache/mesos/pull/182
  
@klueska may interest at this.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Build failed in Jenkins: Mesos » autotools,gcc,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6)&&(!ubuntu-eu2) #2933

2016-11-16 Thread Neil Conway 
Has there been any response from the ASF Infra folks on addressing the
VM/hardware issues? Seems like it will be difficult to get good signal
from the ASF CI in the absence of some improvements on the
infrastructure side.

Neil

On Wed, Nov 16, 2016 at 10:45 AM, Alex R  wrote:
> Looks like VM lag again: http://pastebin.com/GZhG4fuN
>
> What do folks think about removing future timeouts in tests altogether?
> Instead, we can time the whole suite differently on different CIs?
>
> On 16 November 2016 at 15:30, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
>> See > COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%
>> 20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=
>> ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-
>> us1)&&(!ubuntu-6)&&(!ubuntu-eu2)/2933/changes>
>>
>> Changes:
>>
>> [alexr] Added a comment about deprecation cycle of quota get authz.
>>
>> --
>> [...truncated 222325 lines...]
>> I1116 14:27:35.400284 30948 containerizer.cpp:202] Using isolation:
>> posix/cpu,posix/mem,filesystem/posix,network/cni
>> W1116 14:27:35.400846 30948 backend.cpp:76] Failed to create 'aufs'
>> backend: AufsBackend requires root privileges, but is running as user mesos
>> W1116 14:27:35.400980 30948 backend.cpp:76] Failed to create 'bind'
>> backend: BindBackend requires root privileges
>> I1116 14:27:35.405436 30978 slave.cpp:208] Mesos agent started on (644)@
>> 172.17.0.3:56829
>> I1116 14:27:35.405462 30978 slave.cpp:209] Flags at startup: --acls=""
>> --appc_simple_discovery_uri_prefix="http://; 
>> --appc_store_dir="/tmp/mesos/store/appc"
>> --authenticate_http_readonly="true" --authenticate_http_readwrite="true"
>> --authenticatee="crammd5" --authentication_backoff_factor="1secs"
>> --authorizer="local" --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" --credential="/tmp/Endpoint_SlaveEndpointTest_
>> AuthorizedRequest_1_6t56bO/credential" --default_role="*"
>> --disk_watch_interval="1mins" --docker="docker"
>> --docker_kill_orphans="true" --docker_registry="https://
>> registry-1.docker.io" --docker_remove_delay="6hrs"
>> --docker_socket="/var/run/docker.sock" --docker_stop_timeout="0ns"
>> --docker_store_dir="/tmp/mesos/store/docker" --docker_volume_checkpoint_
>> dir="/var/run/mesos/isolators/docker/volume" 
>> --enforce_container_disk_quota="false"
>> --executor_registration_timeout="1mins" 
>> --executor_shutdown_grace_period="5secs"
>> --fetcher_cache_dir="/tmp/Endpoint_SlaveEndpointTest_
>> AuthorizedRequest_1_6t56bO/fetch" --fetcher_cache_size="2GB"
>> --frameworks_home="" --gc_delay="1weeks" --gc_disk_headroom="0.1"
>> --hadoop_home="" --help="false" --hostname_lookup="true"
>> --http_authenticators="basic" --http_command_executor="false"
>> --http_credentials="/tmp/Endpoint_SlaveEndpointTest_
>> AuthorizedRequest_1_6t56bO/http_credentials" 
>> --image_provisioner_backend="copy"
>> --initialize_driver_logging="true" --isolation="posix/cpu,posix/mem"
>> --launcher="posix" --launcher_dir="/mesos/mesos-1.2.0/_build/src"
>> --logbufsecs="0" --logging_level="INFO" 
>> --max_completed_executors_per_framework="150"
>> --oversubscribed_resources_interval="15secs" --perf_duration="10secs"
>> --perf_interval="1mins" --qos_correction_interval_min="0ns"
>> --quiet="false" --recover="reconnect" --recovery_timeout="15mins"
>> --registration_backoff_factor="10ms" --resources="cpus:2;gpus:0;
>> mem:1024;disk:1024;ports:[31000-32000]" --revocable_cpu_low_priority="true"
>> --runtime_dir="/tmp/Endpoint_SlaveEndpointTest_AuthorizedRequest_1_6t56bO"
>> --sandbox_directory="/mnt/mesos/sandbox" --strict="true"
>> --switch_user="true" --systemd_enable_support="true"
>> --systemd_runtime_directory="/run/systemd/system" --version="false"
>> --work_dir="/tmp/Endpoint_SlaveEndpointTest_AuthorizedRequest_1_OjLwwx"
>> I1116 14:27:35.406361 30978 credentials.hpp:86] Loading credential for
>> authentication from '/tmp/Endpoint_SlaveEndpointTest_
>> AuthorizedRequest_1_6t56bO/credential'
>> I1116 14:27:35.406677 30978 slave.cpp:346] Agent using credential for:
>> test-principal
>> I1116 14:27:35.406782 30978 credentials.hpp:37] Loading credentials for
>> authentication from '/tmp/Endpoint_SlaveEndpointTest_
>> AuthorizedRequest_1_6t56bO/http_credentials'
>> I1116 14:27:35.407196 30978 http.cpp:895] Using default 'basic' HTTP
>> authenticator for realm 'mesos-agent-readonly'
>> I1116 14:27:35.407546 30978 http.cpp:895] Using default 'basic' HTTP
>> authenticator for realm 'mesos-agent-readwrite'
>> I1116 14:27:35.409431 30978 slave.cpp:533] Agent resources: cpus(*):2;
>> mem(*):1024; disk(*):1024; ports(*):[31000-32000]
>> I1116 14:27:35.409689 30978 slave.cpp:541] Agent attributes: [

Re: Mesos V1 Operator HTTP API - Java Proto Classes

2016-11-16 Thread Anand Mazumdar 
We wanted to move the project away from officially supporting anything
other than C++ and discuss more on if we should be responsible for
publishing to the various language specific channels. However, for the time
being, we had decided to include the v1 protobufs in the mesos JAR itself.
(it already contains the v1 Scheduler/Executor protos)

Please file an issue as Zameer pointed out.

-anand

On Wed, Nov 16, 2016 at 8:34 AM, Zameer Manji  wrote:

> I think this is a bug, I feel the jar should include all v1 protobuf files.
>
> Vijay, I encourage you to file a ticket.
>
> On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
> vijikar...@yahoo.com.invalid> wrote:
>
>> I believe the HTTP API will use the same underlying message format (proto
>> def) and hence the request/response value objects (java) needs to be
>> auto-generated from the proto files for it to be used in Jersey based java
>> rest client?
>>
>> On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
>> jani...@gmail.com> wrote:
>>
>>
>>  I suspect jar is deprecated and includes only old API used by mesoslib.
>> The
>> goal is to create HTTP API and stop supporting native libs (jars, so,
>> etc).
>> I think you shouldn't use that jar in your project.
>>
>> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
>> vijikar...@yahoo.com> napisał:
>>
>> > Hello,
>> >
>> > I am writing a rest client for "operator APIs" and found that some of
>> the
>> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
>> > "include/mesos/v1/master/master.proto") are not included in the mesos
>> jar
>> > file. While investigating, I have found that the "Make" file does not
>> > include these proto definition files.
>> >
>> > I have updated the Make file and added the protos that I am interested
>> in
>> > and built a new jar file. Is there any reason why these proto
>> definitions
>> > are not included in the original build apart from the reason that the
>> APIs
>> > are still evolving?
>> >
>> > Regards
>> > Vijay
>> >
>>
>> --
>> Zameer Manji
>>
>

Re: Mesos V1 Operator HTTP API - Java Proto Classes

2016-11-16 Thread Zameer Manji 
I think this is a bug, I feel the jar should include all v1 protobuf files.

Vijay, I encourage you to file a ticket.

On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
vijikar...@yahoo.com.invalid> wrote:

> I believe the HTTP API will use the same underlying message format (proto
> def) and hence the request/response value objects (java) needs to be
> auto-generated from the proto files for it to be used in Jersey based java
> rest client?
>
> On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
> jani...@gmail.com> wrote:
>
>
>  I suspect jar is deprecated and includes only old API used by mesoslib.
> The
> goal is to create HTTP API and stop supporting native libs (jars, so, etc).
> I think you shouldn't use that jar in your project.
>
> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
> vijikar...@yahoo.com> napisał:
>
> > Hello,
> >
> > I am writing a rest client for "operator APIs" and found that some of the
> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
> > "include/mesos/v1/master/master.proto") are not included in the mesos
> jar
> > file. While investigating, I have found that the "Make" file does not
> > include these proto definition files.
> >
> > I have updated the Make file and added the protos that I am interested in
> > and built a new jar file. Is there any reason why these proto definitions
> > are not included in the original build apart from the reason that the
> APIs
> > are still evolving?
> >
> > Regards
> > Vijay
> >
>
> --
> Zameer Manji
>

Re: Build failed in Jenkins: Mesos » autotools,gcc,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6)&&(!ubuntu-eu2) #2933

2016-11-16 Thread Alex R 
Looks like VM lag again: http://pastebin.com/GZhG4fuN

What do folks think about removing future timeouts in tests altogether?
Instead, we can time the whole suite differently on different CIs?

On 16 November 2016 at 15:30, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> See  COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%
> 20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=
> ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-
> us1)&&(!ubuntu-6)&&(!ubuntu-eu2)/2933/changes>
>
> Changes:
>
> [alexr] Added a comment about deprecation cycle of quota get authz.
>
> --
> [...truncated 222325 lines...]
> I1116 14:27:35.400284 30948 containerizer.cpp:202] Using isolation:
> posix/cpu,posix/mem,filesystem/posix,network/cni
> W1116 14:27:35.400846 30948 backend.cpp:76] Failed to create 'aufs'
> backend: AufsBackend requires root privileges, but is running as user mesos
> W1116 14:27:35.400980 30948 backend.cpp:76] Failed to create 'bind'
> backend: BindBackend requires root privileges
> I1116 14:27:35.405436 30978 slave.cpp:208] Mesos agent started on (644)@
> 172.17.0.3:56829
> I1116 14:27:35.405462 30978 slave.cpp:209] Flags at startup: --acls=""
> --appc_simple_discovery_uri_prefix="http://; 
> --appc_store_dir="/tmp/mesos/store/appc"
> --authenticate_http_readonly="true" --authenticate_http_readwrite="true"
> --authenticatee="crammd5" --authentication_backoff_factor="1secs"
> --authorizer="local" --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" --credential="/tmp/Endpoint_SlaveEndpointTest_
> AuthorizedRequest_1_6t56bO/credential" --default_role="*"
> --disk_watch_interval="1mins" --docker="docker"
> --docker_kill_orphans="true" --docker_registry="https://
> registry-1.docker.io" --docker_remove_delay="6hrs"
> --docker_socket="/var/run/docker.sock" --docker_stop_timeout="0ns"
> --docker_store_dir="/tmp/mesos/store/docker" --docker_volume_checkpoint_
> dir="/var/run/mesos/isolators/docker/volume" 
> --enforce_container_disk_quota="false"
> --executor_registration_timeout="1mins" 
> --executor_shutdown_grace_period="5secs"
> --fetcher_cache_dir="/tmp/Endpoint_SlaveEndpointTest_
> AuthorizedRequest_1_6t56bO/fetch" --fetcher_cache_size="2GB"
> --frameworks_home="" --gc_delay="1weeks" --gc_disk_headroom="0.1"
> --hadoop_home="" --help="false" --hostname_lookup="true"
> --http_authenticators="basic" --http_command_executor="false"
> --http_credentials="/tmp/Endpoint_SlaveEndpointTest_
> AuthorizedRequest_1_6t56bO/http_credentials" 
> --image_provisioner_backend="copy"
> --initialize_driver_logging="true" --isolation="posix/cpu,posix/mem"
> --launcher="posix" --launcher_dir="/mesos/mesos-1.2.0/_build/src"
> --logbufsecs="0" --logging_level="INFO" 
> --max_completed_executors_per_framework="150"
> --oversubscribed_resources_interval="15secs" --perf_duration="10secs"
> --perf_interval="1mins" --qos_correction_interval_min="0ns"
> --quiet="false" --recover="reconnect" --recovery_timeout="15mins"
> --registration_backoff_factor="10ms" --resources="cpus:2;gpus:0;
> mem:1024;disk:1024;ports:[31000-32000]" --revocable_cpu_low_priority="true"
> --runtime_dir="/tmp/Endpoint_SlaveEndpointTest_AuthorizedRequest_1_6t56bO"
> --sandbox_directory="/mnt/mesos/sandbox" --strict="true"
> --switch_user="true" --systemd_enable_support="true"
> --systemd_runtime_directory="/run/systemd/system" --version="false"
> --work_dir="/tmp/Endpoint_SlaveEndpointTest_AuthorizedRequest_1_OjLwwx"
> I1116 14:27:35.406361 30978 credentials.hpp:86] Loading credential for
> authentication from '/tmp/Endpoint_SlaveEndpointTest_
> AuthorizedRequest_1_6t56bO/credential'
> I1116 14:27:35.406677 30978 slave.cpp:346] Agent using credential for:
> test-principal
> I1116 14:27:35.406782 30978 credentials.hpp:37] Loading credentials for
> authentication from '/tmp/Endpoint_SlaveEndpointTest_
> AuthorizedRequest_1_6t56bO/http_credentials'
> I1116 14:27:35.407196 30978 http.cpp:895] Using default 'basic' HTTP
> authenticator for realm 'mesos-agent-readonly'
> I1116 14:27:35.407546 30978 http.cpp:895] Using default 'basic' HTTP
> authenticator for realm 'mesos-agent-readwrite'
> I1116 14:27:35.409431 30978 slave.cpp:533] Agent resources: cpus(*):2;
> mem(*):1024; disk(*):1024; ports(*):[31000-32000]
> I1116 14:27:35.409689 30978 slave.cpp:541] Agent attributes: [  ]
> I1116 14:27:35.409821 30978 slave.cpp:546] Agent hostname: 5817a5b56afb
> I1116 14:27:35.411998 30970 state.cpp:57] Recovering state from
> '/tmp/Endpoint_SlaveEndpointTest_AuthorizedRequest_1_OjLwwx/meta'
> I1116 14:27:35.412678 30968 status_update_manager.cpp:203] Recovering
> status update manager
> I1116 14:27:35.413048 30975 containerizer.cpp:561] Recovering containerizer
>

[GitHub] mesos pull request #183: Add PyMesos in api-client-libraries.md

2016-11-16 Thread windreamer 
GitHub user windreamer opened a pull request:

https://github.com/apache/mesos/pull/183

Add PyMesos in api-client-libraries.md



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/windreamer/mesos-1 windreamer-patch-3

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/183.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #183


commit 82f4a53c47dbb7e4286847bd93c54564d01ac387
Author: windreamer 
Date:   2016-11-16T14:10:36Z

Update




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #182: Add TFMesos in frameworks.md

2016-11-16 Thread windreamer 
GitHub user windreamer opened a pull request:

https://github.com/apache/mesos/pull/182

Add TFMesos in frameworks.md



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/windreamer/mesos-1 windreamer-patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/182.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #182


commit b3a14195bf70e001da5812b07a0271cee24428ed
Author: windreamer 
Date:   2016-11-16T13:53:31Z

Update frameworks.md




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #181: Add elastic-job -cloud description into frameworks....

2016-11-16 Thread terrymanu 
GitHub user terrymanu opened a pull request:

https://github.com/apache/mesos/pull/181

Add elastic-job -cloud description into frameworks.md



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/terrymanu/mesos master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/181.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #181


commit 781dd84262ec4538240207d077577511d499acd3
Author: 张亮 
Date:   2016-11-16T13:27:14Z

Update frameworks.md




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---