[jira] [Commented] (MYRIAD-181) Build failure due to dependency on zookeeper test jar

[Zachary Jaffee (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYRIAD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153761#comment-15153761
 ] 

Zachary Jaffee commented on MYRIAD-181:
---

I found a work around, but it isn't likely that this solution is the best 
practice to follow long term, likely we need to figure out how to rewrite the 
gradle build such that we don't use mavelLocal(), which is what is causing the 
issue. I'm about to make a PR now with my fix. 

> Build failure due to dependency on zookeeper test jar 
> --
>
> Key: MYRIAD-181
> URL: https://issues.apache.org/jira/browse/MYRIAD-181
> Project: Myriad
>  Issue Type: Bug
>Affects Versions: Myriad 0.1.0
>Reporter: Santosh Marella
> Fix For: Myriad 0.2.0
>
>
> Myriad build is failing at times with the following error:
> * What went wrong:
> Could not resolve all dependencies for configuration
> ':myriad-scheduler:compile'.
> > Could not find zookeeper-tests.jar (org.apache.zookeeper:zookeeper:3.4.6).
>   Searched in the following locations:
> file:/Users/jnadeau/.m2/repository/org/apache/zookeeper/zookeeper/3.4.6/zookeeper-3.4.6-tests.jar
> rm -rf ~/.m2/repository/org/apache/zookeeper/zookeeper/3.4.6 fixes the 
> problem, but we need to figure out a proper fix.



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

[jira] [Comment Edited] (MYRIAD-165) Cleanup old branches in git

[Zachary Jaffee (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYRIAD-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153469#comment-15153469
 ] 

Zachary Jaffee edited comment on MYRIAD-165 at 2/19/16 1:04 AM:


I'm not a committer to myriad, so I cant take care of it, but should you be 
already within a local git repository that has its remote set directly to the 
apache github repo, you can run the following bash script. Feel free to modify 
the variable list as needed for the various items you want to have deleted.
{noformat}
#!/bin/bash
list=("origin/constraints"  "origin/docker-image" 
"origin/executor-only-application" "origin/issue_14" "origin/issue_16" 
"origin/multi-project" "origin/myriadha" "origin/phase1")
for i in ${list[@]}; do
git push origin --delete ${i}
done
{noformat}


was (Author: zjaffee):
I'm not a committer to myriad, so I cant take care of it, but should you be 
already within a local git repository that has its remote set directly to the 
apache github repo, you can run the following bash script. Feel free to modify 
the variable list as needed for the various items you want to have deleted.
{noformat}
#/bin/bash
list=("origin/constraints"  "origin/docker-image" 
"origin/executor-only-application" "origin/issue_14" "origin/issue_16" 
"origin/multi-project" "origin/myriadha" "origin/phase1")
for i in ${list[@]}; do
git push origin --delete ${i}
done
{noformat}

> Cleanup old branches in git
> ---
>
> Key: MYRIAD-165
> URL: https://issues.apache.org/jira/browse/MYRIAD-165
> Project: Myriad
>  Issue Type: Improvement
>Reporter: Jim Klucar
>Priority: Trivial
> Fix For: Myriad 0.2.0
>
>
> The git repo contains several old branches that are out of date and/or have 
> been merged into master. We should review the published branches and prune 
> what's not needed.



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

[jira] [Commented] (MYRIAD-165) Cleanup old branches in git

[Zachary Jaffee (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYRIAD-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153469#comment-15153469
 ] 

Zachary Jaffee commented on MYRIAD-165:
---

I'm not a committer to myriad, so I cant take care of it, but should you be 
already within a local git repository that has its remote set directly to the 
apache github repo, you can run the following bash script. Feel free to modify 
the variable list as needed for the various items you want to have deleted.

#/bin/bash
list=("origin/constraints"  "origin/docker-image" 
"origin/executor-only-application" "origin/issue_14" "origin/issue_16" 
"origin/multi-project" "origin/myriadha" "origin/phase1")
for i in ${list[@]}; do
git push origin --delete ${i}
done

> Cleanup old branches in git
> ---
>
> Key: MYRIAD-165
> URL: https://issues.apache.org/jira/browse/MYRIAD-165
> Project: Myriad
>  Issue Type: Improvement
>Reporter: Jim Klucar
>Priority: Trivial
> Fix For: Myriad 0.2.0
>
>
> The git repo contains several old branches that are out of date and/or have 
> been merged into master. We should review the published branches and prune 
> what's not needed.



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

Re: Mesos and Myriad Kerberos Support

[Adam Bordelon]

We at Mesosphere have a proprietary implementation of Kerberos ticket
forwarding using various Mesos hooks/modules, but this is specific to a
particular customer use case. We're actively working on a way to pass
keytabs/credentials to spark-submit so that it can forward them on to HDFS
or other services. While this is still a specific use case (Spark -> HDFS),
we're exploring how to generalize this approach beyond just Kerberos.

On Wed, Feb 10, 2016 at 5:56 PM,  wrote:

> Hello guys,
>
> I wanted to follow up a little further on today’s Hangouts call about
> Kerberos. For everyone else who may have not been on the call the idea is
> if you have Spark, Myriad and some task running top of Mesos and it needs
> access to some third party service like HDFS that needs kerberos
> credentials how will that work?
>
> Adam has mentioned one solution he’s seen. This was to have credentials
> cached on the master that will then intercept the calls and annotate the
> task with their credentials and wrap the calls with something that unwraps
> the credentials and puts it into place to authenticate. This will require
> update the TGT as they expire.
>
> Adam, you’ve mentioned that is Mesosphere doing in this space as well, do
> you know if that is specific to Kerberos or something else? Any other
> suggestion will be helpful!
>
> Thanks!
>
>
> *Known Jiras regarding this adding kerberos support for Mesos
>
> https://issues.apache.org/jira/browse/MESOS-907
>
> > Miguel Bernadin Accenture Technology Labs – System Engineering
> Contact: W (408) 817-2742 | M (631) 835-6345 |
> miguel.berna...@accenture.com
>
> 
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy.
>
> __
>
> www.accenture.com
>