Hi,
I have some tasks that need to run on different types of agents. I don’t
want the tasks to run unless I am going to have all the resources. Can someone
suggest how I could accomplish that with mesos. I read about reservations
here: http://mesos.apache.org/documentation/latest/reservat
HI Rinaldo,
I think that you can use dynamic reservation feature to achieve this: You
can launch your tasks after reservation succeeds. Actually, all of the
dynamic reservation feature with endpoint has been finished except ACL
part, so you can use this feature now if you do not care ACL part.
T
On Sep 21, 2015, at 19:33, Guangya Liu
mailto:gyliu...@gmail.com>> wrote:
HI Rinaldo,
I think that you can use dynamic reservation feature to achieve this: You can
launch your tasks after reservation succeeds. Actually, all of the dynamic
reservation feature with endpoint has been finished e
Hi Rinaldo,
The dynamic reservation endpoint support was introduced in 0.25.0, you may
want to use the latest code to build.
If build fails on Oracle Linux, please go ahead to file a JIRA ticket to
get some support.
Thanks,
Guangya
On Tue, Sep 22, 2015 at 8:01 AM, DiGiorgio, Mr. Rinaldo S. <
r
Rinaldo,
or you may try to install or port svn libs and check whether it works.
On Tue, Sep 22, 2015 at 2:25 AM, Guangya Liu wrote:
> Hi Rinaldo,
>
> The dynamic reservation endpoint support was introduced in 0.25.0, you may
> want to use the latest code to build.
>
> If build fails on Oracle L
On Sep 21, 2015, at 7:33 PM, Guangya Liu
mailto:gyliu...@gmail.com>> wrote:
HI Rinaldo,
I think that you can use dynamic reservation feature to achieve this: You can
launch your tasks after reservation succeeds. Actually, all of the dynamic
reservation feature with endpoint has been finished
Hi Rinaldo,
sorry about the trouble you're having in getting this to work!
If I got this one right, the original requirement was...
I have some tasks that need to run on different types of agents.
for that, I think you can use either (or both) of `roles` and `attributes`
(see the Configuration
On Sep 28, 2015, at 5:27 PM, Marco Massenzio
mailto:ma...@mesosphere.io>> wrote:
Hi Rinaldo,
sorry about the trouble you're having in getting this to work!
If I got this one right, the original requirement was...
I have some tasks that need to run on different types of agents.
for that, I thi
On Sep 28, 2015, at 5:27 PM, Marco Massenzio
mailto:ma...@mesosphere.io>> wrote:
Hi Rinaldo,
sorry about the trouble you're having in getting this to work!
If I got this one right, the original requirement was...
I have some tasks that need to run on different types of agents.
for that, I thi
Hi Rinaldo,
I'd like to point out a small error in your ACLs.
If you want to specify "ANY", you should set the "type" field. i.e. For
the RegisterFramework ACL:
"register_frameworks": [
{
"principals": { "values": "mesos-mach5-beta" },
"roles": { "type": 1 }
}
]
The ANY "type" is pa
On Sep 28, 2015, at 8:03 PM, Joseph Wu
mailto:jos...@mesosphere.io>> wrote:
Hi Rinaldo,
I'd like to point out a small error in your ACLs.
If you want to specify "ANY", you should set the "type" field. i.e. For the
RegisterFramework ACL:
"register_frameworks": [
{
"principals": { "value
Rinaldo,
The principle is taken from authentication, rather than from the body of
the resources. In this case, you'll be using Basic Authentication:
https://en.wikipedia.org/wiki/Basic_access_authentication#Client_side
With curl, you'd add something like: -H "Authorization: Basic
bWVzb3MtbWFjaDU
Joseph,
I thought I tried that. So I must still not following the directions. Here
is what I have?
mesos master running on OS X 10.10.5 mesos 0.26
I perform the following curl operation below.
server reads credentials file
I0929 10:48:42.062871 291536896 credentials.hpp:37] Loading crede
Hi Rinaldo,
Sorry that you're having trouble using dynamic reservations.
I see that you're specifying the *mesos-mach5-beta* principal on the
resources, but I'm not sure if your framework is registered with the
*mesos-mach5-beta* principal? The framework must set the
*FrameworkInfo::principal* to
MPark,
Thanks for your identification of something that was not configured. I am
using the mesos-plugin in Jenkins. I had not specified a principal. I added the
principal and it appears to register with that principal if I don’t provide a
password from the meson-plugin. When I try to perform
I'll look into what's happening with the framework registration, but
meanwhile I've also taken a look at what's going on with the master
endpoints.
It looks like the issue is around authentication rather than the dynamic
reservation endpoints.
When using *JSON-based* credentials file, the passwor
Oops, that should've been:
* {*
*"credentials": [*
* {*
*"principal": "mesos-mach5-beta",*
*"secret": " cGFzc3dvcmQ="*
* }*
*]*
* }*
On Tue, Sep 29, 2015 at 8:20 PM Michael Park wrote:
> I'll look into what's happening with the framework registration, but
> m
Regarding the credentials file behavior, it seems to be a bug. I've filed:
https://issues.apache.org/jira/browse/MESOS-3560
On Tue, Sep 29, 2015 at 8:28 PM Michael Park wrote:
> Oops, that should've been:
>
> * {*
> *"credentials": [*
> * {*
> *"principal": "mesos-mach5-beta",*
18 matches
Mail list logo
