Hi guys, I would like your opinion about a future feature proposal.
Currently, we can use HTTP API to list all our tasks running in our cluster
using /master/tasks, but you have to list all tasks or limit/offset this
list, we cannot filter this. I would like to filter this, using labels, for
+1
It'll also reduce master's workload; but instead of label, I'd like to make
master simpler: return tasks page by page and let framework/dashboard to
filter it themself.
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
Platform Symphony/DCOS Development & Support, STG, IBM GCG
It seems Kubernetes is down; would you help to check kubernetes's status
(km)?
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
Platform Symphony/DCOS Development & Support, STG, IBM GCG
+86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me
On Mon, Dec 28, 2015 at 6:35 PM, Nan
Hi all,
Greetings from me!
I am trying to follow this tutorial
(https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/mesos.md)
to deploy "k8s on Mesos" on local machines: The k8s is the newest
master branch, and Mesos is the 0.26 edition.
After running Mesos
Hi Fred,
hm, if the bug dependents on Ubuntu version, my random guess is that it's
systemd related. Were you able to solve the problem? If not, it would be
helpful if you provide more context and describe a minimal setup that
reproduces the issue.
On Thu, Dec 10, 2015 at 10:15 AM, Frederic LE
Craig,
mind elaborating, how exactly do you run elasticsearch in Marathon?
On Mon, Dec 28, 2015 at 8:36 PM, craig w wrote:
> In terms of discovery, elasticsearch provides that out of the box
>
Eric—
give me a chance to answer that before you fall into frustration : ).
Also, you can directly write to framework developers
(mesos...@container-solutions.com) and they either confirm or bust my
guess. Or maybe one of the authors — Frank — will chime in in this
thread.
Marathon has no idea
Perhaps we could also support HTTP PATCH so you could just update one small
thing vs's PUT's get and set method.
On Thursday, December 17, 2015, Adam Bordelon wrote:
> First off, if we're going to have a /reservations endpoint, we should
> follow the same PUT+DELETE pattern
In terms of discovery, elasticsearch provides that out of the box
https://www.elastic.co/guide/en/elasticsearch/reference/1.4/modules-discovery.html.
We deploy elasticsearch via Marathon and it works great.
On Mon, Dec 28, 2015 at 2:17 PM, Eric LEMOINE wrote:
> On Mon,
On Mon, Dec 28, 2015 at 7:55 PM, Alex Rukletsov wrote:
> Eric—
>
> give me a chance to answer that before you fall into frustration : ).
> Also, you can directly write to framework developers
> (mesos...@container-solutions.com) and they either confirm or bust my
> guess. Or
Hi Klaus,
Firstly, thanks very much for your answer!
The km processes are all live:
root 129474 128024 2 22:26 pts/000:00:00 km apiserver
--address=15.242.100.60 --etcd-servers=http://15.242.100.60:4001
--service-cluster-ip-range=10.10.10.0/24 --port=
--cloud-provider=mesos
11 matches
Mail list logo