Re: [DISCUSS] handling roles in Myriad code

I can help on this discussion; I used to be Mesos contributor for a year :). Mesos allocate regular resources based on role by DRF; and role is also used for reservation & quotas. So, the framework (like Myriad), may get two kind of resources: "*" or "myriad-s role". When Myriad launch tasks, it

Re: [DISCUSS] handling roles in Myriad code

I really would like Mesosphere guys to comment here. I had a chat with Adam today morning and I did not get the same impression Thanks, Yuliya > On Oct 19, 2016, at 8:50 PM, Darin Johnson wrote: > > We use roles extensively to ensure different frameworks can (or

Re: [DISCUSS] handling roles in Myriad code

We use roles extensively to ensure different frameworks can (or can't) get resources via mechanisms such as reserved resorces and quotas. Also if you don't pay attention you can miss a lot of the resources you're given. I wish it was we didn't have to do all the book keeping our selves, but I

Re: [DISCUSS] handling roles in Myriad code

I am not sure we should care about role being set or not, what if in the future we will have multiple rolesNot even sure if presence/absence of role should play role (no pun intended :) ). From: Darin Johnson To: Dev ; yuliya

Re: [DISCUSS] handling roles in Myriad code

I'd really like to see if Mohit could answer how the dcos-commons library might be able to help here. Also can dcos commons work with vanilla mesos or just dcos? On Wed, Oct 19, 2016 at 9:51 PM, Klaus Ma wrote: > And for the role, we also need to handle the principal

Re: [DISCUSS] handling roles in Myriad code

Yuyiya, Yes on master a lot of refactoring was done, in particular you specify ports other than 0 in the myriad-default.yaml, it will only return those ports (not random ones). This was done in part because the we were attempting the use the JHS on a port like 32001, but it the port was already

[DISCUSS] Using defined ports versus provided by Mesos

Hello there, I wanted to discuss usage of hardcoded ports instead of ones provided by Mesos as a resource.On master branch - probably due to significant code refactoring we pretty much do NOT allow any ports (range resource) that is NOT provided by Mesos. Earlier on we could have "reserved"

Re: [DISCUSS] Using defined ports versus provided by Mesos

To add to the previous - in case of work preserving NodeManager we would also need consistent port assignment in case NM restarts. From: yuliya Feldman To: Dev Sent: Wednesday, October 19, 2016 12:34 PM Subject: [DISCUSS] Using

[DISCUSS] handling roles in Myriad code

Hello there, I wanted to discuss current handling of roles in Myriad code. Specifically on "master" branch. Most likely due to heavy refactoring. As far as I can see we try to handle presence or absence of a role on a resource(s) based on the fact that framework may or may not have a role.On the