essentially revoking all access to data forever.
>
> On Mon, Nov 27, 2017 at 11:34 PM Hendrik Haddorp
> wrote:
>
>> As said, I only use persistent volumes with my only scheduler straight
>> on Mesos so do not exactly know how this works in Marathon...
>>
>> The p
least. MOUNT volumes can be configured to map to "real" devices which
can provide normal write failures when exceeding disk limits instead of
essentially revoking all access to data forever.
On Mon, Nov 27, 2017 at 11:34 PM Hendrik Haddorp
wrote:
> As said, I only use persistent vo
As said, I only use persistent volumes with my only scheduler straight
on Mesos so do not exactly know how this works in Marathon...
The persistent volume is created on a Mesos agent and basically ends up
being a folder on that hosts disk. So yes, you can not use the volume on
a different
wrote:
> I have my own scheduler that is performing a create operation. As you are
> using Marathon this call would have to be done by Marathon.
> Did you read https://mesosphere.github.io/marathon/docs/persistent-volume
> s.html ?
>
> On 27.11.2017 14:59, Dino Lokmic wrote:
>
&
"my-volume-227927c2-3266-412b-8572-92c5c93c051a" volume?
On Mon, Nov 27, 2017 at 7:59 AM, Hendrik Haddorp
mailto:hendrik.hadd...@gmx.net>> wrote:
Hi,
I'm using persistent volumes directly on Mesos, without Marathon.
For that the scheduler (like Marathon) has
@hendrik
How did you create this "my-volume-227927c2-3266-412b-8572-92c5c93c051a"
volume?
On Mon, Nov 27, 2017 at 7:59 AM, Hendrik Haddorp
wrote:
> Hi,
>
> I'm using persistent volumes directly on Mesos, without Marathon. For that
> the scheduler (like Marathon) has
Thanks, for answers
yes I use Marathon and Mesos.
On Mon, Nov 27, 2017 at 7:59 AM, Hendrik Haddorp
wrote:
> Hi,
>
> I'm using persistent volumes directly on Mesos, without Marathon. For that
> the scheduler (like Marathon) has to first reserve disk space and then
> create
Hi,
I'm using persistent volumes directly on Mesos, without Marathon. For
that the scheduler (like Marathon) has to first reserve disk space and
then create a persistent volume with that. The next resource offer
message then contain the volume in "disk" resource part of the
Are you using DC/OS or "vanilla" Mesos and Marathon, without DC/OS? If you
are using Mesos, you might get a better answer on the Mesos mailing list
<http://mesos.apache.org/community/#mailing-lists>, and you can also check
out these docs on persistent volumes
<http://mesos.apach
I have few machines on Linode and I run Mesos there. Can someone explain to
me, how to set volumes right.
Now I run taks via marathon like this
...
"constraints": [
[
"hostname",
"CLUSTER",
"HOSTNAME"
]
],
"container": {
"type": "DOCKER",
"volumes": [
Hendrik,
Sorry about the late response on that. I am glad that you figured it out
yourself.
Currently, for local persistent volumes (consumes 'disk' resources on the
agent), the container_path has to be relative. We made that decision based
on a couple of reasons:
1) not all the sys
write a Mesos framework that should create persistent
> volumes and then start a Docker container that uses this. So far I was
> able to dynamically reserve resources (cpu, memory and disk) and create
> a persistent volume in the reserved disk space. I'm also able to launch
> a Docker
Hi Guangya,
that seems to be pretty much the same that Vaibhav pointed me to, that
is using Docker volume drivers to mount external storage. I would like
to leverage the build in Mesos persistent volumes but mount them at any
position, just like you can with normal docker volumes from the host
abstracts the volume
> creation. Please check this out and it should work with your scheduler …
>
>
> https://github.com/emccode/mesos-module-dvdi
>
> Thx
>
>
>
> On Thu, Jun 23, 2016 at 7:56 AM, Hendrik Haddorp
> wrote:
>
>> Hi,
>>
>> I'm
gmx.net>> wrote:
>
> Hi,
>
> I'm trying to write a Mesos framework that should create persistent
> volumes and then start a Docker container that uses this. So far I was
> able to dynamically reserve resources (cpu, memory and disk) and
> cr
> I'm trying to write a Mesos framework that should create persistent
> volumes and then start a Docker container that uses this. So far I was
> able to dynamically reserve resources (cpu, memory and disk) and create
> a persistent volume in the reserved disk space. I'm also able to
Hi,
I'm trying to write a Mesos framework that should create persistent
volumes and then start a Docker container that uses this. So far I was
able to dynamically reserve resources (cpu, memory and disk) and create
a persistent volume in the reserved disk space. I'm also able to launc
Awesome! Thanks for the info.
Sent from my iPhone
> On Feb 29, 2016, at 10:45 AM, Neil Conway wrote:
>
> Hi Zhitao,
>
> We just implemented this feature; it will appear in Mesos 0.28. You
> will be able to list all the information about the persistent volumes
> and reserv
Hi Zhitao,
We just implemented this feature; it will appear in Mesos 0.28. You
will be able to list all the information about the persistent volumes
and reservations at every slave in the cluster by examining the
master's "/slaves" endpoint. For more information, see:
https://is
Hi,
Is there a HTTP url to list and view existing persistent volume created so
far? I'm running 0.27.1 and couldn't find how to obtain such info.
Thanks!
--
Cheers,
Zhitao Li
20 matches
Mail list logo
