Allocator slack channel

[Guangya Liu]

Hi,

I created an #allocator slack channel in mesos.slack.com, please join this
if you want to have some discussion for allocator related issues, such as
allocator performance, optimistic offer, revocable resource etc.

@bmahler and @vinodkone,

I also posted a RR here https://reviews.apache.org/r/49660/ for adding this
to "Resource Allocation" working group, can you please help check?

Thanks,

Guangya

[GitHub] mesos pull request #128: Add mr-redis to frameworks.md

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #128: Add mr-redis to frameworks.md

[dhilipkumars]

Github user dhilipkumars commented on a diff in the pull request:

https://github.com/apache/mesos/pull/128#discussion_r69636046
  
--- Diff: docs/frameworks.md ---
@@ -40,3 +40,4 @@ layout: documentation
 * [Cassandra](https://github.com/mesosphere/cassandra-mesos) is a 
performant and highly available distributed database. Linear scalability and 
proven fault-tolerance on commodity hardware or cloud infrastructure make it 
the perfect platform for mission-critical data.
 * [ElasticSearch](https://github.com/mesos/elasticsearch) is a distributed 
search engine. Mesos makes it easy to run and scale.
 * [Hypertable](https://code.google.com/p/hypertable/wiki/Mesos) is a high 
performance, scalable, distributed storage and processing system for structured 
and unstructured data.
+* [MrRedis](https://github.com/mesos/mr-redis) an apache mesos framework 
for provisioning [redis](http://redis.io/) in-memory cache instances.  This 
provides auto redis master election, auto recovery of slaves and comes with the 
CLI and a UI. 
--- End diff --

Its updated now ;-) . Thanks in Advance


---
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 #128: Add mr-redis to frameworks.md

[tillt]

Github user tillt commented on a diff in the pull request:

https://github.com/apache/mesos/pull/128#discussion_r69632803
  
--- Diff: docs/frameworks.md ---
@@ -40,3 +40,4 @@ layout: documentation
 * [Cassandra](https://github.com/mesosphere/cassandra-mesos) is a 
performant and highly available distributed database. Linear scalability and 
proven fault-tolerance on commodity hardware or cloud infrastructure make it 
the perfect platform for mission-critical data.
 * [ElasticSearch](https://github.com/mesos/elasticsearch) is a distributed 
search engine. Mesos makes it easy to run and scale.
 * [Hypertable](https://code.google.com/p/hypertable/wiki/Mesos) is a high 
performance, scalable, distributed storage and processing system for structured 
and unstructured data.
+* [MrRedis](https://github.com/mesos/mr-redis) an apache mesos framework 
for provisioning [redis](http://redis.io/) in-memory cache instances.  This 
provides auto redis master election, auto recovery of slaves and comes with the 
CLI and a UI. 
--- End diff --

The PR is not updated though, or am I missing something? ;-)


---
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 #128: Add mr-redis to frameworks.md

[dhilipkumars]

Github user dhilipkumars commented on a diff in the pull request:

https://github.com/apache/mesos/pull/128#discussion_r69630222
  
--- Diff: docs/frameworks.md ---
@@ -40,3 +40,4 @@ layout: documentation
 * [Cassandra](https://github.com/mesosphere/cassandra-mesos) is a 
performant and highly available distributed database. Linear scalability and 
proven fault-tolerance on commodity hardware or cloud infrastructure make it 
the perfect platform for mission-critical data.
 * [ElasticSearch](https://github.com/mesos/elasticsearch) is a distributed 
search engine. Mesos makes it easy to run and scale.
 * [Hypertable](https://code.google.com/p/hypertable/wiki/Mesos) is a high 
performance, scalable, distributed storage and processing system for structured 
and unstructured data.
+* [MrRedis](https://github.com/mesos/mr-redis) an apache mesos framework 
for provisioning [redis](http://redis.io/) in-memory cache instances.  This 
provides auto redis master election, auto recovery of slaves and comes with the 
CLI and a UI. 
--- End diff --

I totally agree. :-) my bad i should have done that in the first place. Now 
its more clearer. 

```
MrRedis is a Mesos framework for provisioning Redis in-memory cache 
instances. The scheduler provides auto Redis master election, auto recovery of 
Redis slaves and comes with the CLI and a UI.
```



---
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 #128: Add mr-redis to frameworks.md

[tillt]

Github user tillt commented on a diff in the pull request:

https://github.com/apache/mesos/pull/128#discussion_r69628598
  
--- Diff: docs/frameworks.md ---
@@ -40,3 +40,4 @@ layout: documentation
 * [Cassandra](https://github.com/mesosphere/cassandra-mesos) is a 
performant and highly available distributed database. Linear scalability and 
proven fault-tolerance on commodity hardware or cloud infrastructure make it 
the perfect platform for mission-critical data.
 * [ElasticSearch](https://github.com/mesos/elasticsearch) is a distributed 
search engine. Mesos makes it easy to run and scale.
 * [Hypertable](https://code.google.com/p/hypertable/wiki/Mesos) is a high 
performance, scalable, distributed storage and processing system for structured 
and unstructured data.
+* [MrRedis](https://github.com/mesos/mr-redis) an apache mesos framework 
for provisioning [redis](http://redis.io/) in-memory cache instances.  This 
provides auto redis master election, auto recovery of slaves and comes with the 
CLI and a UI. 
--- End diff --

We commonly use capital initials for product/project and organization 
names. Maybe clarifying that we are not trying to "revert" our slave->agent 
naming scheme here :). Then also trying to adjust the style a bit for 
consistency of this document...

How about this?

```
MrRedis is a Mesos framework for provisioning Redis in-memory cache 
instances. This provides auto Redis master election, auto recovery of Redis 
slaves and comes with the CLI and a UI.
```



---
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.
---

Pull request [apache/mesos] Add mr-redis to frameworks.md

[mesosprbot]

Add mr-redis to frameworks.md
By dhilipkumars 
Adding Redis Framework for Apache mesos to the list of frameworks. Should we 
create a separate heading and call it Cache instead of marking it 
under Data Storage ?
July 5, 2016 at 12:43PM
via GitHub http://ift.tt/29uJSV6

[GitHub] mesos pull request #128: Add mr-redis to frameworks.md

[dhilipkumars]

GitHub user dhilipkumars opened a pull request:

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

Add mr-redis to frameworks.md

Adding Redis Framework for Apache mesos to the list of frameworks. Should 
we create a separate heading and call it "Cache" instead of marking it under 
"Data Storage" ?

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

$ git pull https://github.com/dhilipkumars/mesos addRedisFrameworktoDOCS

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

https://github.com/apache/mesos/pull/128.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 #128


commit ad4f48e021b0d42c38581a3063a91ead3e83bd6f
Author: Dhilip 
Date:   2016-07-05T19:40:20Z

Add mr-redis to frameworks.md

Adding Redis Framework for Apache mesos to the list of frameworks. Should 
we create a separate heading and call it "Cache" instead of marking it under 
"Data Storage" ?




---
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 #125: Add Piksel to powered-by-mesos

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #118: Make Mesos healtchecks compatible with Marathon

[brat002]

Github user brat002 commented on a diff in the pull request:

https://github.com/apache/mesos/pull/118#discussion_r69314525
  
--- Diff: src/health-check/main.cpp ---
@@ -132,16 +132,14 @@ class HealthCheckerProcess : public 
ProtobufProcess
   {
 VLOG(1) << "Check passed";
 
-// Send a healthy status update on the first success,
-// and on the first success following failure(s).
-if (initializing || consecutiveFailures > 0) {
-  TaskHealthStatus taskHealthStatus;
--- End diff --

Could anybody make correct pull request? I am not C programmer and not 100% 
sure in these changes. 


---
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: ScyllaDB

[vincent gromakowski]

+1
Le 5 juil. 2016 17:38, "José Guilherme Vanz"  a
écrit :

> Hi guys!
>
> Have you ever consider make ScyllaDB  run on
> Mesos?
> I took a look on it, it seems very powerful and cool! It would be nice run
> it on Mesos =)
>
> Thanks
>

Does isolator expect DNS to be reachable in all cases?

[Eduard Serra]

Hi all,

We've been developing a CNI plugin for Mesos. During testing the plugin
seems to perform fine, and I actually see Mesos calling it and getting an
IP from it. However, just afterwards the isolate() returns the Executor,
the executor reports to have exited, hence destroying the container.

I0702 02:38:45.207439   209 cni.cpp:1069] Got assigned IPv4 address '
10.1.1.100/24' from CNI network 'CNI-test-onboard' for container
e67c7678-f6b4-4de7-85c1-2b40a80fc80d
I0702 02:38:45.208228   208 cni.cpp:805] Unable to find DNS nameservers for
container e67c7678-f6b4-4de7-85c1-2b40a80fc80d. Using host
'/etc/resolv.conf'
// +5sec
I0702 02:38:50.459604   206 containerizer.cpp:1821] Executor for container
'e67c7678-f6b4-4de7-85c1-2b40a80fc80d' has exited
I0702 02:38:50.459709   206 containerizer.cpp:1585] Destroying container
'e67c7678-f6b4-4de7-85c1-2b40a80fc80d'


Q: Is this expected? Currently our implementation does not provide DNS, can
this be the cause? Consider that the slave has no visibility/access to the
network where the container/s are being onboarded on (aiming to be a
network overlay between containers only).


We are running Mesos (latest master), we create the container  through
Marathon (latest master) with:
{
"id": "basic-0",
"cmd": "while [ true ] ; do echo 'Hello Marathon' ; sleep 5 ; done",
"cpus": 0.1,
"mem": 10.0,
"instances": 1,
"ipAddress": {
"networkName": "CNI-test-onboard"
}
}

A Redis Framework for Apache Mesos

[Dhilip Kumar S]

Hello All,

We have built a framework for provisioning redis-servers in Apache Mesos 
enabled infrastructure. It would be awesome to get communities feedback. While 
mesos ecosystem is strengthening its capability in storage layer, redis could 
be an addition to the lineup.  This is primarily intended for providers who 
would like to host redis as a service in their infrastructure.

There is an elaborate README about the project which should help in setting it 
up: https://github.com/mesos/mr-redis. Please let us know if there is anything 
missing in the documentation by raising a PR or opening an issue or even 
writing to us.

This project is also packaged as  mr-redis with DCOS so should be pretty 
straight forward to install it via DCOS CLI or DCOS GUI.

(A Step by Step guide is provided in the README for your convenience)

Salient Features of this project include:

1)  Create multiple redis clusters (Master-Slave Cluster) with ease

2)  Redis instances recover in seconds and not in minutes

3)  If a Master fails a slaves is automatically promoted as the New master, 
all the old slaves now replicate from the newly master plus a new slave is 
added to the cluster.  All this without using redis-sentinel in your datacenter 
and all these happens in a couple of seconds.

4)  A CLI to perform basic operations such as create / status / delete 
redis instances on the fly.  CLI is cross compiled for Windows and Darwin users 
too.

5)  Scheduler is a HTTP REST server which also can respond to simple 
Angular UI we have built to get started with.  Instructions on how to setup the 
UI is here. https://github.com/mesos/mr-redis/tree/master/ui/app

We also had an opportunity to talk about this during the recent MesosCon 2016: 
https://www.youtube.com/watch?v=xe-Gom5tOl0=32=PLGeM09tlguZQVL7ZsfNMffX9h1rGNVqnC

Future Work:

* Implement a proxy technique to expose one single endpoint for the 
redis instance.

* Implement Memory Cgroups per redis PROCS

* Add support for Redis 3.0 cluster instances (Adding shards to a 
running redis instance)

* Implement integration test suite and benchmarking suite to the 
framework.

Special thanks to Adobe.io team who expressed interest in collaborating in the 
development of this product. I'm sure it's going to be great working with all 
of you folks.

Advanced happy Independence day America and happy weekend rest of the world.

Looking forward to hear from you all,
Dhilip

[GitHub] mesos pull request #124: Added self to contributors.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #95: Added Raleigh/Durham User Group

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #125: Add Piksel to powered-by-mesos

[sgran]

GitHub user sgran opened a pull request:

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

Add Piksel to powered-by-mesos



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

$ git pull https://github.com/pikselpalette/mesos Add_Piksel

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

https://github.com/apache/mesos/pull/125.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 #125


commit e6cf76d75d032c6c47f160ee4c49a5446daedb0f
Author: Stephen Gran 
Date:   2016-07-01T07:04:39Z

Add Piksel to powered-by-mesos




---
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 #89: Update ElasticSearch repo

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #78: Update architecture.md

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #123: Add Cook to frameworks.md

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #122: docs: frameworks list: use correct URL for storm-me...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #123: Add Cook to frameworks.md

[dgrnbrg]

GitHub user dgrnbrg opened a pull request:

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

Add Cook to frameworks.md

This adds the Cook framework to the framework list.

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

$ git pull https://github.com/dgrnbrg/mesos-1 add-cook-to-frameworks

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

https://github.com/apache/mesos/pull/123.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 #123


commit 3a0f19707107e63efcbc37b6515c19b3d698a286
Author: David Greenberg 
Date:   2016-06-30T23:38:26Z

Add Cook to 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 #122: docs: frameworks list: use correct URL for storm-me...

[erikdw]

GitHub user erikdw opened a pull request:

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

docs: frameworks list: use correct URL for storm-mesos framework



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

$ git pull https://github.com/erikdw/mesos framework-docs-storm

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

https://github.com/apache/mesos/pull/122.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 #122


commit b532cf32172f8db4839845eed6e31c1022d958b7
Author: Erik Weathers 
Date:   2016-06-30T23:32:09Z

docs: frameworks list: use correct URL for storm-mesos framework




---
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 #121: Addition of ndustrial.io to Mesos User List

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #121: Addition of ndustrial.io to Mesos User List

[jrcrawfo]

GitHub user jrcrawfo opened a pull request:

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

Addition of ndustrial.io to Mesos User List



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

$ git pull https://github.com/jrcrawfo/mesos patch-2

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

https://github.com/apache/mesos/pull/121.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 #121


commit 7e84431969ab3b5ed324596de94b3069be2adc2f
Author: John Crawford 
Date:   2016-06-30T23:21:21Z

Addition of ndustrial.io to Mesos User List




---
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 #119: Added gigawatt.io to "powered by".

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #120: Add Opera to "Powered by Mesos" list

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #120: Add Opera to "Powered by Mesos" list

[mlowicki]

GitHub user mlowicki opened a pull request:

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

Add Opera to "Powered by Mesos" list



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

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

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

https://github.com/apache/mesos/pull/120.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 #120


commit fd8023a32518317ff14a6306dff275d3e700a145
Author: Michał Łowicki 
Date:   2016-06-30T20:52:49Z

Add Opera to "Powered by Mesos" list




---
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 #119: Added gigawatt.io to "powered by".

[jaytaylor]

GitHub user jaytaylor opened a pull request:

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

Added gigawatt.io to "powered by".



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

$ git pull https://github.com/GigawattIO/mesos jay/gigawattio

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

https://github.com/apache/mesos/pull/119.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 #119


commit 03ffbb46805642e008bff1bb8021e74e56b69406
Author: Jay Taylor 
Date:   2016-06-30T20:51:03Z

Added gigawatt.io




---
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 issue #111: Have maven run in batch mode

[drcrallen]

Github user drcrallen commented on the issue:

https://github.com/apache/mesos/pull/111
  
Filed https://reviews.apache.org/r/49422/


---
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 #111: Have maven run in batch mode

[drcrallen]

Github user drcrallen closed the pull request at:

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


---
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: [Tech-debt] Introduce regex into Mesos

[haosdent]

>As Joseph said, regex works well in llvm 7.3 & gcc 5.3, but does not work
in gcc 4.8.4; also try "" in gc 4.8.4, but "ld" failed :(.

I think we just need to update the bundled boost and use the regex headers
from boost as what I do in
https://reviews.apache.org/r/40053/diff/3#index_header

On Mon, Jun 13, 2016 at 9:58 PM, Klaus Ma  wrote:

> As discussed in the RR, we'll enhance current code to handle port ranges
> as a short term solution.
>
>
> I've logged MESOS-5602 (Introduce expression grammar library)<
> https://issues.apache.org/jira/browse/MESOS-5602> to trace the long term
> solution for Mesos defined data format, e.g. resources.
>
>
> 
>
> Da (Klaus), Ma (??), PMP®| Advisory Software Engineer
> Platform DCOS Development & Support, STG, IBM GCG
> +86-10-8245 4084 | mad...@cn.ibm.com | http://k82.me
>
> 
>
>
> 
> From: Klaus Ma 
> Sent: Saturday, June 11, 2016 2:09 AM
> To: dev
> Subject: Re: [Tech-debt] Introduce regex into Mesos
>
> As Joseph said, regex works well in llvm 7.3 & gcc 5.3, but does not work
> in gcc 4.8.4; also try "" in gc 4.8.4, but "ld" failed :(.
>
>
> 
>
> Da (Klaus), Ma (??), PMP(r)| Advisory Software Engineer
> Platform DCOS Development & Support, STG, IBM GCG
> +86-10-8245 4084 | mad...@cn.ibm.com | http://k82.me
>
> 
> 
> From: Joseph Wu 
> Sent: Friday, June 10, 2016 8:15:51 PM
> To: dev
> Subject: Re: [Tech-debt] Introduce regex into Mesos
>
> Same here.
>
> Mesos currently requires GCC 4.8.1+.  Regex support was implemented in GCC
> 4.9.0, see [1].
>
> [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53631
>
> On Fri, Jun 10, 2016 at 11:39 AM, Kevin Klues  wrote:
>
> > By compiler errors, I mean "internal compiler errors"
> >
> > On Fri, Jun 10, 2016 at 11:38 AM, Kevin Klues  wrote:
> > > I've run into compiler errors using simple regex stuff from the
> > > standard library on our supported version of gcc.
> > >
> > > On Thu, Jun 9, 2016 at 7:30 PM, Klaus Ma 
> wrote:
> > >> Hi team,
> > >>
> > >>
> > >> We're discussing to introduce regex into Mesos when investigating
> > MESOS-4627; so I'd
> like
> > to ask whether anyone has experience on regex after C++11? for example,
> > supported compiler, compatibility, performance and so on :).
> > >>
> > >>
> > >> 
> > >>
> > >> Da (Klaus), Ma (??), PMP(r)| Advisory Software Engineer
> > >> Platform DCOS Development & Support, STG, IBM GCG
> > >> +86-10-8245 4084 | mad...@cn.ibm.com | http://k82.me
> > >>
> > >> 
> > >
> > >
> > >
> > > --
> > > ~Kevin
> >
> >
> >
> > --
> > ~Kevin
> >
>



-- 
Best Regards,
Haosdent Huang

Re: [GitHub] mesos pull request #127: added DevOps category and Vamp

[Alex Rukletsov]

Pushed.

On Tue, Jul 5, 2016 at 7:10 PM, haosdent  wrote:

> Github user haosdent commented on a diff in the pull request:
>
> https://github.com/apache/mesos/pull/127#discussion_r69601291
>
> --- Diff: docs/frameworks.md ---
> @@ -4,6 +4,10 @@ layout: documentation
>  ---
>  # Software Projects Built on Mesos
>
> +## DevOps tooling
> +
> +* [Vamp](http://http://vamp.io) is a deployment and workflow tool
> for container orchestration systems, including Mesos/Marathon. It brings
> canary releasing, A/B testing, auto scaling and self healing through a web
> UI, CLI and REST API.
> --- End diff --
>
> I post a quick fix at https://reviews.apache.org/r/49641/
>
>
> ---
> 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 #127: added DevOps category and Vamp

[haosdent]

Github user haosdent commented on a diff in the pull request:

https://github.com/apache/mesos/pull/127#discussion_r69601291
  
--- Diff: docs/frameworks.md ---
@@ -4,6 +4,10 @@ layout: documentation
 ---
 # Software Projects Built on Mesos
 
+## DevOps tooling
+
+* [Vamp](http://http://vamp.io) is a deployment and workflow tool for 
container orchestration systems, including Mesos/Marathon. It brings canary 
releasing, A/B testing, auto scaling and self healing through a web UI, CLI and 
REST API.
--- End diff --

I post a quick fix at https://reviews.apache.org/r/49641/


---
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 #127: added DevOps category and Vamp

[haosdent]

Github user haosdent commented on a diff in the pull request:

https://github.com/apache/mesos/pull/127#discussion_r69599122
  
--- Diff: docs/frameworks.md ---
@@ -4,6 +4,10 @@ layout: documentation
 ---
 # Software Projects Built on Mesos
 
+## DevOps tooling
+
+* [Vamp](http://http://vamp.io) is a deployment and workflow tool for 
container orchestration systems, including Mesos/Marathon. It brings canary 
releasing, A/B testing, auto scaling and self healing through a web UI, CLI and 
REST API.
--- End diff --

The path incorrect here?


---
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 issue #127: added DevOps category and Vamp

[mpark]

Github user mpark commented on the issue:

https://github.com/apache/mesos/pull/127
  
```
commit bb965cf48ad742ef09ef7c1019db7c221139ecd3
Author: Gina 
Date:   Tue Jul 5 18:07:30 2016 +0200

Added DevOps category and Vamp.

This closes #127
```


---
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: GPU channel on slack

[haosdent]

https://mesos-slackin.herokuapp.com/

On Tue, Jul 5, 2016 at 8:48 PM, Thomas Runyon  wrote:

> Vinod set up an automated signup for people:   https://mesos
> -slackin.herokuapp.com/
>
> You should be able to sign up there and get an invite from him directly.
>
> On Tue, Jul 5, 2016 at 8:45 AM mandeep gandhi 
> wrote:
>
> > So how new members join this group. Only people having certain domains
> can
> > create a slack account it seems.
> >
> > Can someone help?
> >
> > Thanks.
> >
> > On Thu, Jun 30, 2016 at 9:14 PM, Kevin Klues  wrote:
> >
> > > If you are interested in the ongoing GPU work on Mesos, please join the
> > > #gpus channel at mesos.slack.com. The big announcements for the GPU
> work
> > > will still happen on this mailing list, but the day to day discussions
> > will
> > > likely happen on the slack channel going forward.
> > >
> >
>



-- 
Best Regards,
Haosdent Huang

ScyllaDB

[José Guilherme Vanz]

Hi guys!

Have you ever consider make ScyllaDB  run on
Mesos?
I took a look on it, it seems very powerful and cool! It would be nice run
it on Mesos =)

Thanks

Re: GPU channel on slack

[Thomas Runyon]

Vinod set up an automated signup for people:   https://mesos
-slackin.herokuapp.com/

You should be able to sign up there and get an invite from him directly.

On Tue, Jul 5, 2016 at 8:45 AM mandeep gandhi 
wrote:

> So how new members join this group. Only people having certain domains can
> create a slack account it seems.
>
> Can someone help?
>
> Thanks.
>
> On Thu, Jun 30, 2016 at 9:14 PM, Kevin Klues  wrote:
>
> > If you are interested in the ongoing GPU work on Mesos, please join the
> > #gpus channel at mesos.slack.com. The big announcements for the GPU work
> > will still happen on this mailing list, but the day to day discussions
> will
> > likely happen on the slack channel going forward.
> >
>

Re: GPU channel on slack

[mandeep gandhi]

So how new members join this group. Only people having certain domains can
create a slack account it seems.

Can someone help?

Thanks.

On Thu, Jun 30, 2016 at 9:14 PM, Kevin Klues  wrote:

> If you are interested in the ongoing GPU work on Mesos, please join the
> #gpus channel at mesos.slack.com. The big announcements for the GPU work
> will still happen on this mailing list, but the day to day discussions will
> likely happen on the slack channel going forward.
>

Pull request [apache/mesos] added DevOps category and Vamp

[mesosprbot]

added DevOps category and Vamp
By gggina 
July 5, 2016 at 03:49AM
via GitHub http://ift.tt/29gWtXA

[GitHub] mesos pull request #127: added DevOps category and Vamp

[gggina]

GitHub user gggina opened a pull request:

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

added DevOps category and Vamp



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

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

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

https://github.com/apache/mesos/pull/127.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 #127


commit 3a8ef62bea1afe6e277de903c3d19165dc4ac448
Author: Gina 
Date:   2016-07-05T10:49:33Z

added DevOps category and Vamp




---
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.
---