You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myriad.apache.org by "Santosh Marella (JIRA)" <ji...@apache.org> on 2015/11/10 21:40:11 UTC

[jira] [Updated] (MYRIAD-83) Finished modifications to allow remote binary distribution.

     [ https://issues.apache.org/jira/browse/MYRIAD-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Santosh Marella updated MYRIAD-83:
----------------------------------
    Fix Version/s:     (was: Myriad 0.1.0)

> Finished modifications to allow remote binary distribution.
> -----------------------------------------------------------
>
>                 Key: MYRIAD-83
>                 URL: https://issues.apache.org/jira/browse/MYRIAD-83
>             Project: Myriad
>          Issue Type: Improvement
>            Reporter: DarinJ
>            Assignee: DarinJ
>
> Now correctly downloads a tarball, extracts the contents and calls the executor.  After this permissions are properly set and the nodemanager is run.  Created a document explaining how to setup myriad and the tarball for this deployment.
> Addresses issue MYRIAD-52 and MYRIAD-47(due to necessity).
> Tested, reasonable POC though not production ready.  Also tested to ensure if the config is left as original, it still functions as before.
> There are concerns with setting permissions this way.  Unfortunately, no way around this as container-executor needs to be set suid.
> Todo:
> 1. Get config files via URI's.
> 2. Write script to automate making the tarball.
> These will be addressed in the near future, but I felt it best to submit this now.
> Comments welcome.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)