> > 1) The refactoring of resource management should make it easier to model > custom resources. I can see why the resource model is bounded & strongly > typed, and not free form (i.e. config based). Is the refactoring planned > for commit/merge any time soon?
It's currently in progress. If you are curious about the direction, below is the list of the relevant changes so far (most recent first): https://reviews.apache.org/r/47261/ https://reviews.apache.org/r/47050/ https://reviews.apache.org/r/46997/ https://reviews.apache.org/r/46948/ https://reviews.apache.org/r/46810 https://reviews.apache.org/r/46716/ https://reviews.apache.org/r/46459/ https://reviews.apache.org/r/46064/ https://reviews.apache.org/r/46057/ 2) For supporting custom (operator privileged) pre/post task launch steps > on a host, I'm considering extending/replacing thermos (based on my initial > understanding). I'm assuming that since the executor runs external to the > container that is used to launch tasks, it'd have the privilege & > visibility to carry out such operator-specified administrative steps. > Thoughts? As mentioned above, the executor has to be packed into the user volume at this point. Joshua Cohen is currently exploring the possibility of running executor externally, so perhaps he could give you more details when/if he has some results. On Wed, May 11, 2016 at 3:46 PM, Mauricio Garavaglia < [email protected]> wrote: > > > On Tue, May 10, 2016 at 10:47 PM, Bharath Ravi Kumar <[email protected]> > wrote: > >> Hi Maxim, >> >> Thanks for responding. >> >> 1) The refactoring of resource management should make it easier to model >> custom resources. I can see why the resource model is bounded & strongly >> typed, and not free form (i.e. config based). Is the refactoring planned >> for commit/merge any time soon? >> >> 2) For supporting custom (operator privileged) pre/post task launch steps >> on a host, I'm considering extending/replacing thermos (based on my initial >> understanding). I'm assuming that since the executor runs external to the >> container that is used to launch tasks, it'd have the privilege & >> visibility to carry out such operator-specified administrative steps. >> Thoughts? >> > > Not really, the executors runs internally in the container. > > >> >> Thanks, >> Bharath >> >> On Mon, May 9, 2016 at 10:23 PM, Maxim Khutornenko <[email protected]> >> wrote: >> >>> These steps need to run external to the docker container being launched. >>>> Based on the documentation, I couldn't find a way to achieve these in >>>> Apache Aurora. Can someone let me know if this is indeed possible? >>> >>> >>> There is no support for this sort of functionality in Aurora, at least >>> not yet (ideas/proposals are welcome!). You can accomplish *some* of >>> that by configuring your custom logic to run within your task image though. >>> >>> I also wanted to know if arbitrary resources modeled in Mesos can be >>>> expressed in an Aurora job definition, assuming that resource isolation is >>>> handled externally. >>> >>> >>> We are currently working on generalizing resource management in Aurora >>> to simplify adding new resource types. That said, having a fully dynamic >>> (e.g. config file driven) support for adding arbitrary resource types is >>> not our goal at the moment. You can find more details here >>> <https://docs.google.com/document/d/1J9SIswRMpVKQpnlvJAMAJtKfPP7ZARFknuyXl-2aZ-M> >>> . >>> >>> On Fri, May 6, 2016 at 6:51 AM, Bharath Ravi Kumar <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> I need the ability to run a few pre-lauch steps (e.g. create a custom >>>> work directory) and post launch steps (e.g. docker inspect) on the physical >>>> host when launching a docker container. These steps need to run external to >>>> the docker container being launched. Based on the documentation, I couldn't >>>> find a way to achieve these in Apache Aurora. Can someone let me know if >>>> this is indeed possible? >>>> >>>> I also wanted to know if arbitrary resources modeled in Mesos can be >>>> expressed in an Aurora job definition, assuming that resource isolation is >>>> handled externally. >>>> >>>> Thanks, >>>> Bharath >>>> >>> >>> >> >
