Re: Apache Myriad Project Status

[Ken Sipe]

I’m not sure if that checklist is still “officially” used… but yes.The main 
criteria is following the layout of version-3.x.   Making sure to use the 
resources.json for any external links (docker or tar balls)
There is a build script:  
https://github.com/mesosphere/universe/blob/version-3.x/scripts/build.sh 
<https://github.com/mesosphere/universe/blob/version-3.x/scripts/build.sh> to 
confirm some compliance.
I would focus on the readme at:  https://github.com/mesosphere/universe/ 
<https://github.com/mesosphere/universe/>

Ken 


> On Apr 17, 2018, at 12:46 AM, Javi Roman <jroman.espi...@gmail.com> wrote:
> 
> Ken,
> 
> Regarding Myriad at DC/Os are these instructions still valid?
> 
> https://bit.ly/2qElS7n
> 
> --
> Javi Roman
> 
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> 
> 
> On Mon, Apr 16, 2018 at 7:03 PM, Javi Roman <jroman.espi...@gmail.com> wrote:
>> On Mon, Apr 16, 2018 at 6:58 PM, Juan P <jpgg...@gmail.com> wrote:
>>> Hi, congratulations for the work and thank you very much. I think Myriad's
>>> rebound is a reality.
>>> 
>>> - In the list of articles, we could add one on the analysis of a dataset
>>> (Titanic) with Spark. Making the attempt to establish a reference
>>> architecture for analysis: SYM2 (Spark-Yarn-Myriad-Mesos)
>> 
>> Great idea, interesting acronym ;-)
>> 
>>> 
>>> - To release the version, we can generate a document with proposals. For me
>>> it would be interesting to upload the Mesos version as a first
>>> approximation. This would allow us to deploy with DCOS and the Mesos
>>> version that is installed.
>>> 
>> 
>> Totally agree, one of the first steps is test with Mesos 1.5
>> 
>>> Now I'm working on reviewing the old PRs to see what we can take advantage
>>> of, then I intend to regularize Jira's bugs and then start with the new
>>> functionality ...
>>> 
>>> 
>>> Thank you very much again
>> 
>> Many thanks for your contributions!
>> 
>>> 
>>> 
>>> On 15 April 2018 at 20:39, Javi Roman <jroman.espi...@gmail.com> wrote:
>>> 
>>>> Hi Ken,
>>>> 
>>>> Good news, slowly we will be able to evolve this interesting project. The
>>>> integration with DC/OS is a guarantee of framework success.
>>>> 
>>>> It would be interesting to know the requirements for getting Apache
>>>> Myriad into the community universe.
>>>> 
>>>> Many thanks for your help!
>>>> --
>>>> Javi Roman
>>>> 
>>>> Twitter: @javiromanrh
>>>> GitHub: github.com/javiroman
>>>> Linkedin: es.linkedin.com/in/javiroman
>>>> Big Data Blog: dataintensive.info
>>>> 
>>>> 
>>>> On Sat, Apr 14, 2018 at 11:01 PM, Ken Sipe <k...@mesosphere.io> wrote:
>>>>> Javi,
>>>>> 
>>>>> Well done and Nice work!
>>>>> 
>>>>> I am one of the original Apache committers on Myriad… however I have
>>>> been MIA for a long time.
>>>>> 
>>>>> I am willing and interested in helping.   At this time I am not able to
>>>> offer up a lot of time but will help where I can.
>>>>> As a part of Mesosphere,   I spent some time being the gatekeeper to the
>>>> DC/OS universe, have written a number CLI subcommands and system
>>>> integration tests and can help in those areas.
>>>>> 
>>>>> Additional areas I will make time for if needed/wanted:
>>>>> 1. PR reviews (and commits)
>>>>> 2. Getting into DCOS universe
>>>>> 3. Help with articles listed below (in particular 3 & 4)
>>>>> 
>>>>> Ken
>>>>> 
>>>>> 
>>>>>> On Apr 14, 2018, at 4:18 AM, Javi Roman <jroman.espi...@gmail.com>
>>>> wrote:
>>>>>> 
>>>>>> Hi all!
>>>>>> 
>>>>>> This is an e-mail for tracking the state of Apache Myriad Project.
>>>>>> Many things are happening and I am happy to say the project is
>>>>>> rebooting slowly but strongly. The following is a list of achievements
>>>>>> right now:
>>>>>> 
>>>>>> 1. We have got a Project Roadmap [1] that we are accomplishing happily.
>>>>>> 2. We have a chat c

Re: Apache Myriad Project Status

[Ken Sipe]

Javi,

Well done and Nice work!  

I am one of the original Apache committers on Myriad… however I have been MIA 
for a long time.

I am willing and interested in helping.   At this time I am not able to offer 
up a lot of time but will help where I can.
As a part of Mesosphere,   I spent some time being the gatekeeper to the DC/OS 
universe, have written a number CLI subcommands and system integration tests 
and can help in those areas.

Additional areas I will make time for if needed/wanted:
1. PR reviews (and commits)
2. Getting into DCOS universe
3. Help with articles listed below (in particular 3 & 4)

Ken 


> On Apr 14, 2018, at 4:18 AM, Javi Roman  wrote:
> 
> Hi all!
> 
> This is an e-mail for tracking the state of Apache Myriad Project.
> Many things are happening and I am happy to say the project is
> rebooting slowly but strongly. The following is a list of achievements
> right now:
> 
> 1. We have got a Project Roadmap [1] that we are accomplishing happily.
> 2. We have a chat channel at [2]. Not much activity yet (only 7 users
> right now) but this is only the beginning.
> 3. This list is getting activity again with new active users.
> 4. A separate document [3] for tracking up the unlocking of JIRA
> issues and pending PRs. Special thanks to Alvaro for the initiative
> and Juan P. for working in this necessary housekeeping.
> 5. We have already a nice local development environment based on
> Vagrant for Apache Mesos, and for DC/OS community platform.
> 6. We have new activity at Apache Myriad Twitter account [4]. We are
> trying to publish at least one post a day. We have to create Apache
> Myriad own content for creating really interesting Twitter posts.
> 
> No ready yet, but planning:
> 
> 1. A set of articles in order to get new users. This is the planning:
> 
> Article 1 - Apache Myriad (Hadoop YARN on Mesos) Reboot
> 
> This article explains the state of the project and sets up the targets
> for the new releases. We need a new release (0.3.0) in order to follow
> the open-source motto "release early, release often".
> 
> Article 2 - Apache Myriad Development Environment Based on Apache Mesos
> 
> This article is a way to get new users as easily as possible with an
> local environment ready for hacking.
> 
> Article 3 - Apache Myriad Development Environment Based on Apache Mesos
> 
> This article explains a way for developing Apache Myriad using Docker
> and Mesosphere Marathon on top of DC/OS. Probably if Apache Myriad is
> executed in production at some time will be at DC/OS.
> 
> Article 4 - Apache Mesos Data Services a Different Approach
> 
> This is a more advance article explaining a different way of data
> service development on Apache Mesos. Probably the current approach is
> to create data services (such as Kafka, Spark, Elastic ...) based on
> Apache Mesos Frameworks. The focus of development is to create native
> frameworks for each technology. Mesosphere does a very good work on
> that direction with DC/OS SDK (dcos-commons).
> 
> The different approach explained in this article is to shift the
> development focus towards only one Apache Mesos Framework to maintains
> (Apache Myriad) and create applications based on YARN by means of
> Apache Slider (a "kind" of YARN SDK). This is really ambitious,
> however really interesting point of view from my perspective.
> 
> 2. It's the time for planning the new release (0.3.0). We have to
> discuss the minimal features to include for a new release. This is
> really important for the next months.
> 
> We have a lot work to do, however I really guess the risk of retiring
> this podling is far way right now.
> 
> Please, feel free to comment, feedback is welcome!
> 
> [1] https://goo.gl/xtD5oT
> [2] https://gitter.im/apache-myriad/dev
> [3]  https://goo.gl/u7RMFY
> [4] https://twitter.com/apachemyriad
> --
> Javi Roman
> 
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info

Re: [Vote] Retire Myriad

[Ken Sipe]

I’ve been busy keeping up with a number of things and disengaged for some 
time.. I would like to come back to active status as a committer and I’m 
willing to commit to:
1. Review and merge of code.
2. Vet releases 

Ken 

> On Jun 20, 2017, at 10:26 AM, yuliya Feldman  
> wrote:
> 
> Sorry for chiming in late. I was out of town.
> I think we should keep the project going if there is an activity on the 
> project.
> I can definitely contribute time to vet the release, review and merge. I may 
> not be able to actively work on the project as it is not inline with my 
> current work schedule.
> Thanks,Yuliya
> 
>  From: Darin Johnson 
> To: Dev  
> Sent: Tuesday, June 20, 2017 11:19 AM
> Subject: Re: [Vote] Retire Myriad
> 
> Swapnil: I only counted myself and Adam, if there's two additional
> committers who are willing to vet the release AND merge commits I'll
> consider changing my vote.
> 
> Darin
> 
> On Tue, Jun 20, 2017 at 12:54 PM, Swapnil Daingade <
> swapnil.daing...@gmail.com> wrote:
> 
>> I am trying to understand what changed since the last discussion.
>> 
>> If I remember correctly, Ted asked for 3-5 committers to vet the next
>> release.
>> 4 committers said they were willing. Did I miss something ?
>> 
>> Regards
>> Swapnil
>> 
>> 
>> 
>> On Tue, Jun 20, 2017 at 7:35 AM, John Yost  wrote:
>> 
>>> +1
>>> 
>>> On Tue, Jun 20, 2017 at 10:22 AM, Klaus Ma 
>> wrote:
>>> 
 +1
 
 On Tue, Jun 20, 2017 at 10:13 PM Brandon Gulla <
>> gulla.bran...@gmail.com>
 wrote:
 
> +1 (if the vote is open to non-comitters)
> 
> 
> 
> On Tue, Jun 20, 2017 at 9:22 AM, Darin Johnson 
 wrote:
> 
>> Based on previous discussions it seems the best course of action.
>>> I'm
>> holding the vote open for 3 business days.
>> 
>> I'm +1 binding.
>> 
>> Darin
>> 
> 
> 
> 
> --
> Brandon
> 
 --
 
 Regards,
 
 Da (Klaus), Ma (马达), PMP® | Software Architect
 IBM Platform Development & Support, STG, IBM GCG
 +86-10-8245 4084 | mad...@cn.ibm.com | http://k82.me
 
>>> 
>> 
> 

Re: Myraid Slack

[Ken Sipe]

Darin try one more time… I think we had a miss configuration
> On Jun 29, 2016, at 11:15 AM, Darin Johnson <dbjohnson1...@gmail.com> wrote:
> 
> Still no luck off wifi or cell.
> On Jun 29, 2016 12:11 PM, "Ken Sipe" <k...@mesosphere.io> wrote:
> 
>> https://plus.google.com/hangouts/_/mesosphere.io/myriad <
>> https://plus.google.com/hangouts/_/mesosphere.io/myriad>
>> 
>> 
>>> On Jun 29, 2016, at 11:08 AM, yuliya Feldman <yufeld...@yahoo.com.INVALID>
>> wrote:
>>> 
>>> no luck joining so far
>>> 
>>> From: Ken Sipe <k...@mesosphere.io>
>>> To: dev@myriad.incubator.apache.org
>>> Sent: Wednesday, June 29, 2016 9:04 AM
>>> Subject: Re: Myraid Slack
>>> 
>>> I am on
>>>> On Jun 29, 2016, at 11:04 AM, Darin Johnson <dbjohnson1...@gmail.com>
>> wrote:
>>>> 
>>>> Having issues getting on, is anybody else able to connect?
>>>> On Jun 28, 2016 10:34 PM, "Adam Bordelon" <a...@mesosphere.io> wrote:
>>>> 
>>>>> (Next dev sync is tomorrow, 9am Pacific time)
>>>>> 
>>>>> On Tue, Jun 28, 2016 at 12:32 PM, Darin Johnson <
>> dbjohnson1...@gmail.com>
>>>>> wrote:
>>>>> 
>>>>>> We also have a dev sync every other Wednesday via Google Hangouts:
>>>>>> https://plus.google.com/hangouts/_/mesosphere.io/myriad
>>>>>> 
>>>>>> Darin
>>>>>> 
>>>>>> On Thu, Jun 23, 2016 at 3:01 AM, Swapnil Daingade <
>>>>>> swapnil.daing...@gmail.com> wrote:
>>>>>> 
>>>>>>> Hi Sam,
>>>>>>> 
>>>>>>> Myriad is a fairly new project. The IPMC vote for Myriad 0.2 just
>>>>> passed
>>>>>>> this week.
>>>>>>> Given we are early in the incubation stage, its not uncommon for one
>> or
>>>>>>> two vendors
>>>>>>> to back the project.
>>>>>>> 
>>>>>>> I'll let other community members talk about their experiences
>> deploying
>>>>>>> Myriad
>>>>>>> but Its really great that you are considering deploying Myriad in
>>>>>>> production.
>>>>>>> Your feedback will definitely help shape the road map for Myriad
>> going
>>>>>>> forward.
>>>>>>> 
>>>>>>> Regards
>>>>>>> Swapnil
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> On 06/22/2016 11:24 PM, Sam Chen wrote:
>>>>>>> 
>>>>>>>> Hi Swapnil,
>>>>>>>> MapR is one company to give Myriad support, right?  Any reference ?
>>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> Sam
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Sent from my iPhone
>>>>>>>> 
>>>>>>>> On Jun 23, 2016, at 10:39 AM, Swapnil Daingade <
>>>>>>>>> swapnil.daing...@gmail.com> wrote:
>>>>>>>>> 
>>>>>>>>> MapR supports Myriad 0.1 currently
>>>>>>>>> 
>>>>>>>>> https://www.mapr.com/products/whats-included
>>>>>>>>> https://www.mapr.com/products/product-overview/apache-myriad
>>>>>>>>> 
>>>>>>>>> Regards
>>>>>>>>> Swapnil
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On Wed, Jun 22, 2016 at 6:51 PM, Sam Chen <
>> rc...@linkernetworks.com>
>>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>> Hi Darin,
>>>>>>>>>> Thanks for you reply. Makes sense to use Slack. Btw, we are going
>> to
>>>>>> use
>>>>>>>>>> Myriad in production, any company have capability to support this
>> ?
>>>>>> And
>>>>>>>>>> is
>>>>>>>>>> there any reference in production ?
>>>>>>>>>> 
>>>>>>>>>> Regards,
>>>>>>>>>> Sam
>>>>>>>>>> 
>>>>>>>>>> Sent from my iPhone
>>>>>>>>>> 
>>>>>>>>>> On Jun 23, 2016, at 2:30 AM, Darin Johnson <
>> dbjohnson1...@gmail.com
>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Sam,
>>>>>>>>>>> 
>>>>>>>>>>> I don't believe so.  But we do have an IRC channel #myriad on
>>>>>> FreeNode.
>>>>>>>>>>> 
>>>>>>>>>> I
>>>>>>>>>> 
>>>>>>>>>>> know the mesosphere guys set up slackbots to interact with it.
>> I'm
>>>>>>>>>>> only
>>>>>>>>>>> there occasionally or by appointment. I did notice Kudu now uses
>>>>>> slack,
>>>>>>>>>>> 
>>>>>>>>>> so
>>>>>>>>>> 
>>>>>>>>>>> maybe slack makes more sense than IRC these days, or Gitter Chat.
>>>>>>>>>>> 
>>>>>>>>>>> Darin
>>>>>>>>>>> 
>>>>>>>>>>> On Wed, Jun 22, 2016 at 1:55 AM, Sam Chen <
>>>>> rc...@linkernetworks.com>
>>>>>>>>>>>> 
>>>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> Guys,
>>>>>>>>>>>> Do we have Slack for Myraid?
>>>>>>>>>>>> 
>>>>>>>>>>>> Regards ,
>>>>>>>>>>>> Sam
>>>>>>>>>>>> 
>>>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>>> 
>> 
>> 

Re: Myraid Slack

[Ken Sipe]

https://plus.google.com/hangouts/_/mesosphere.io/myriad 
<https://plus.google.com/hangouts/_/mesosphere.io/myriad>


> On Jun 29, 2016, at 11:08 AM, yuliya Feldman <yufeld...@yahoo.com.INVALID> 
> wrote:
> 
> no luck joining so far
> 
>  From: Ken Sipe <k...@mesosphere.io>
> To: dev@myriad.incubator.apache.org 
> Sent: Wednesday, June 29, 2016 9:04 AM
> Subject: Re: Myraid Slack
> 
> I am on
>> On Jun 29, 2016, at 11:04 AM, Darin Johnson <dbjohnson1...@gmail.com> wrote:
>> 
>> Having issues getting on, is anybody else able to connect?
>> On Jun 28, 2016 10:34 PM, "Adam Bordelon" <a...@mesosphere.io> wrote:
>> 
>>> (Next dev sync is tomorrow, 9am Pacific time)
>>> 
>>> On Tue, Jun 28, 2016 at 12:32 PM, Darin Johnson <dbjohnson1...@gmail.com>
>>> wrote:
>>> 
>>>> We also have a dev sync every other Wednesday via Google Hangouts:
>>>> https://plus.google.com/hangouts/_/mesosphere.io/myriad
>>>> 
>>>> Darin
>>>> 
>>>> On Thu, Jun 23, 2016 at 3:01 AM, Swapnil Daingade <
>>>> swapnil.daing...@gmail.com> wrote:
>>>> 
>>>>> Hi Sam,
>>>>> 
>>>>> Myriad is a fairly new project. The IPMC vote for Myriad 0.2 just
>>> passed
>>>>> this week.
>>>>> Given we are early in the incubation stage, its not uncommon for one or
>>>>> two vendors
>>>>> to back the project.
>>>>> 
>>>>> I'll let other community members talk about their experiences deploying
>>>>> Myriad
>>>>> but Its really great that you are considering deploying Myriad in
>>>>> production.
>>>>> Your feedback will definitely help shape the road map for Myriad going
>>>>> forward.
>>>>> 
>>>>> Regards
>>>>> Swapnil
>>>>> 
>>>>> 
>>>>> 
>>>>> On 06/22/2016 11:24 PM, Sam Chen wrote:
>>>>> 
>>>>>> Hi Swapnil,
>>>>>> MapR is one company to give Myriad support, right?  Any reference ?
>>>>>> 
>>>>>> Regards,
>>>>>> Sam
>>>>>> 
>>>>>> 
>>>>>> Sent from my iPhone
>>>>>> 
>>>>>> On Jun 23, 2016, at 10:39 AM, Swapnil Daingade <
>>>>>>> swapnil.daing...@gmail.com> wrote:
>>>>>>> 
>>>>>>> MapR supports Myriad 0.1 currently
>>>>>>> 
>>>>>>> https://www.mapr.com/products/whats-included
>>>>>>> https://www.mapr.com/products/product-overview/apache-myriad
>>>>>>> 
>>>>>>> Regards
>>>>>>> Swapnil
>>>>>>> 
>>>>>>> 
>>>>>>> On Wed, Jun 22, 2016 at 6:51 PM, Sam Chen <rc...@linkernetworks.com>
>>>>>>>> wrote:
>>>>>>>> 
>>>>>>>> Hi Darin,
>>>>>>>> Thanks for you reply. Makes sense to use Slack. Btw, we are going to
>>>> use
>>>>>>>> Myriad in production, any company have capability to support this ?
>>>> And
>>>>>>>> is
>>>>>>>> there any reference in production ?
>>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> Sam
>>>>>>>> 
>>>>>>>> Sent from my iPhone
>>>>>>>> 
>>>>>>>> On Jun 23, 2016, at 2:30 AM, Darin Johnson <dbjohnson1...@gmail.com
>>>> 
>>>>>>>>>> 
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> Sam,
>>>>>>>>> 
>>>>>>>>> I don't believe so.  But we do have an IRC channel #myriad on
>>>> FreeNode.
>>>>>>>>> 
>>>>>>>> I
>>>>>>>> 
>>>>>>>>> know the mesosphere guys set up slackbots to interact with it.  I'm
>>>>>>>>> only
>>>>>>>>> there occasionally or by appointment. I did notice Kudu now uses
>>>> slack,
>>>>>>>>> 
>>>>>>>> so
>>>>>>>> 
>>>>>>>>> maybe slack makes more sense than IRC these days, or Gitter Chat.
>>>>>>>>> 
>>>>>>>>> Darin
>>>>>>>>> 
>>>>>>>>> On Wed, Jun 22, 2016 at 1:55 AM, Sam Chen <
>>> rc...@linkernetworks.com>
>>>>>>>>>> 
>>>>>>>>> wrote:
>>>>>>>> 
>>>>>>>>> Guys,
>>>>>>>>>> Do we have Slack for Myraid?
>>>>>>>>>> 
>>>>>>>>>> Regards ,
>>>>>>>>>> Sam
>>>>>>>>>> 
>>>>>>>>>> Sent from my iPhone
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
> 
> 

Re: Will not attend today's dev sync

[Ken Sipe]

I'm out today as  well

Sent from my iPhone

> On Mar 9, 2016, at 8:53 AM, Santosh Marella  wrote:
> 
> --
> Sent from mobile

Re: Introduction

[Ken Sipe]

awesome!  welcome aboard Zach!

Some of the build issue JIRAs should be easy knock outs and we need them for 
the 0.2.0 release.   

ken

> On Feb 24, 2016, at 3:27 PM, Zachary Jaffee  wrote:
> 
> Hi Everyone,
> 
> Maybe you have seen a few of my recent JIRA comments or PRs, but I wanted
> to more formally introduce myself. I'm an undergrad at Case Western, and
> I'm also involved with another incubating projects as a committer. However,
> I've wanted to begin contributing to myriad, as both an attempt to improve
> my overall knowledge about resource managers (YARN and Mesos particularly),
> but also to help continue to build out a project that I believe has a lot
> of potential.
> 
> Anyways, I'm interested in diving in head first so to speak, so if there
> are any moderate to larger tasks that need to be worked on, please send
> them my way.
> 
> Best,
> Zach
> 
> -- 
> Zach Jaffee
> B.S. Computer Science
> Case Western Reserve University Class of 2017
> Operations Director | WRUW FM 91.1 Cleveland
> (917) 881-0646
> zjaffee.com
> linkedin.com/in/zjaffee
> github.com/ZJaffee

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

[Ken Sipe (JIRA)]

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

Ken Sipe commented on MYRIAD-165:
-

thanks for script... here is the command for removing the branches from apache:

`git push apache --delete multi-project`

`apache` is the name of git remote to the official git repo
and the `origin/` doesn't work... just `` on the `--delete`

> 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
>    Assignee: Ken Sipe
>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

[Ken Sipe (JIRA)]

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

Ken Sipe commented on MYRIAD-165:
-

for reference:

```
git remote -v
apache  https://kens...@git-wip-us.apache.org/repos/asf/incubator-myriad.git 
(fetch)
apache  https://kens...@git-wip-us.apache.org/repos/asf/incubator-myriad.git 
(push)
origin  g...@github.com:apache/incubator-myriad.git (fetch)
origin  g...@github.com:apache/incubator-myriad.git (push)
```

> 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
>    Assignee: Ken Sipe
>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] [Closed] (MYRIAD-181) Build failure due to dependency on zookeeper test jar

[Ken Sipe (JIRA)]

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

Ken Sipe closed MYRIAD-181.
---
Resolution: Fixed
  Assignee: Ken Sipe

> 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
>Assignee: Ken Sipe
> 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] [Updated] (MYRIAD-165) Cleanup old branches in git

[Ken Sipe (JIRA)]

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

Ken Sipe updated MYRIAD-165:

Assignee: Ken Sipe

> 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
>    Assignee: Ken Sipe
>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)

dev sync

[Ken Sipe]

https://plus.google.com/hangouts/_/mesosphere.io/myriad 


we are getting ready to begin

Re: New Committer: Swapnil Daingade

[Ken Sipe]

congrats Swapnil!

> On Nov 5, 2015, at 6:38 AM, Adam Bordelon  wrote:
> 
> The Podling Project Management Committee (PPMC) for Apache Myriad has asked
> Swapnil Daingade to become a committer and PPMC member and we are pleased
> to announce that he has accepted.
> 
> Please join me in welcoming Swapnil as a Myriad committer, and let's thank
> him for all his contributions so far. Looking forward to more!
> 
> Cheers,
> -Adam-

Re: New committer: Darin J

[Ken Sipe]

congrats Darin!   

> On Nov 5, 2015, at 6:36 AM, Adam Bordelon  wrote:
> 
> The Podling Project Management Committee (PPMC) for Apache Myriad has asked
> Darin to become a committer and PPMC member and we are pleased to announce
> that he has accepted.
> 
> Please join me in welcoming Darin as a Myriad committer, and let's thank
> him for all his contributions so far. Looking forward to more!
> 
> Cheers,
> -Adam-

Re: apache rat plugin

[Ken Sipe]

late to the conversation… gradle does NOT use maven plugins but for anything 
popular there is a gradle plugin.  Gradle can use ANT plugins tho… 

In this case:  https://plugins.gradle.org/plugin/org.nosphere.apache.rat 


ken


> On Oct 15, 2015, at 3:15 PM, Jim Klucar  wrote:
> 
> I assume gradle can use Maven plugins? If so, there's a rat (Release Audit
> Tool) plugin that checks file headers for licenses. What do you think about
> using it?
> 
> http://creadur.apache.org/rat/apache-rat-plugin/
> 
> Jim

Re: myriad.js

[Ken Sipe]

It was part of your check in:)if it is a generated file we shouldn’t check 
it in at all.

ken
> On Oct 16, 2015, at 10:39 AM, Jim Klucar <klu...@gmail.com> wrote:
> 
> Why were you reviewing that file? That file is cobbled together by gulp
> from all the other .js files. Anything in /public is generated by gulp.
> 
> I searched for santosh and ashankar in my repo and couldn't find anything.
> what branch?
> 
> 
> On Fri, Oct 16, 2015 at 11:35 AM, Ken Sipe <k...@mesosphere.io> wrote:
> 
>> team,
>> 
>> I was forced to review myriad.js today…
>> 
>> there are many references to ashankar and santosh in that file….   can we
>> have these removed?
>> 
>> ken

Re: Google Hangout Link

[Ken Sipe]

I sent an invite… and BTW… the sync notes have the hangout link at the top:  
https://docs.google.com/document/d/1JGmJrgeg98bHw_0_sSRmyX6WiAe13OdErcFlaz6Aa04/edit#heading=h.rnolkdpzfc8u
 
https://docs.google.com/document/d/1JGmJrgeg98bHw_0_sSRmyX6WiAe13OdErcFlaz6Aa04/edit#heading=h.rnolkdpzfc8u

ken
 On Aug 26, 2015, at 11:04 AM, Brandon Gulla gulla.bran...@gmail.com wrote:
 
 Can someone send out the active google hangout link please?
 
 thanks
 
 -- 
 Brandon

Re: Documentation Comments

[Ken Sipe]

john,

the details of where to send it on in the pdf that must be filled out and 
signed.   the fastest way is to send the ICLA to secret...@apache.org 
mailto:secret...@apache.org

ken

 On Aug 19, 2015, at 1:56 PM, John Omernik j...@omernik.com wrote:
 
 Happy to sign the ICLA.  Who do I send it to? Ruth, I defer to your writing
 skills and suggestions on how to help.  Happy to help in the way that you'd
 find easiest.
 
 
 John
 
 On Wed, Aug 19, 2015 at 1:48 PM, Ruth Harris rhar...@maprtech.com wrote:
 
 hi John,
 
 Thank you for your feedback. I'm the assigned technical writer for the
 Myriad project. I'll also be working on updating the information.
 
 I'm also ok with what Adam indicated: directly editing or adding a John's
 page. But please be aware that I'll also be working on the content. Last
 week I did some cleanup work on the original files in GitHub and then
 brought them into the Wiki, although, I still have some more work in terms
 of organizing and identifying holes.
 
 If you like, I can create a John's comments page and then work on
 incorporating some of the obvious things that you mentioned.
 
 Thanks, Ruth
 
 Ruth Harris
 Sr. Tech. Writer
 rhar...@mapr.com
 
 On Wed, Aug 19, 2015 at 11:37 AM, John Omernik j...@omernik.com wrote:
 
 Thanks Adam, I signed up with mandoskippy.
 
 I am honored to help in this capacity, for updating etc, do we go through
 some kind of review? Is it better to ask questions on the dev list then
 update when consensus occurs? How about when I'd like to post a page and
 then have someone review the work? If I have a comment on the page, is
 that
 public or can I just send to author? Just curious on any guidelines I
 should be following in that regard.
 
 John
 
 
 
 On Wed, Aug 19, 2015 at 1:29 PM, Adam Bordelon a...@mesosphere.io
 wrote:
 
 John, thanks a ton for your valuable feedback! We're glad to have your
 perspective as a user of the project, and I'm ready+willing to give you
 edit access to the wiki if you want to update it with your learnings,
 elaborate anything that's unclear, or add a new John's tips page.
 Just
 sign up for a wiki account, send me your accountId, and I'll grant you
 edit
 access.
 (I'll let others answer your specific questions)
 
 On Wed, Aug 19, 2015 at 6:28 AM, John Omernik j...@omernik.com
 wrote:
 
 Today, I will be playing the role of the fool/jester trying to get
 Myriad
 running. Basically, since getting Myriad running with Santosh quite a
 while
 ago, and now trying again with new versions of Hadoop, MapR, and
 Myriad,
 I
 wanted to hit up the wiki (
 https://cwiki.apache.org/confluence/display/MYRIAD/Myriad+Home) and
 outline
 points that as a non-dev living the code, are unclear to someone
 trying
 to
 utilize myriad or understand it's operation.
 
 Obviously, some of my points can be answered with look here in the
 code
 or look at this page, but I will try to outline my thought processes
 as I
 reviewed the current docs.  Sometimes the way I approached the
 problem
 led
 me down a path of to a certain page, missing the answer in a
 different
 page, and thus some cross linking could be helpful.
 
 Please do not let my points be taken as anything other than a desire
 to
 improve how accessible Myriad is to the community, this is not a
 critique
 of the hard work everyone has done on the project.  I also understand
 that
 given the work load and other issues, that fixing these issues in
 documentation may not be a priority.  I am listing them out here, so
 that
 those folks who are SMEs on various points may be able to quickly add
 stuff
 and we'll organize it later.
 
 
 *Remote Distribution: *
 
 
 
 
 https://cwiki.apache.org/confluence/display/MYRIAD/Myriad+Remote+Distribution
 
 This whole section could use some work from a standpoint of what runs
 where
 and where that component gets its files.  For example, I think it
 would
 help people to understand that the whole tarball created in step 6
 has
 all
 the files for node managers and resource managers.  Basically,
 everything
 runs from there. Here is a small example I am currently working with:
 
 
 Starting Myriad:
 Option 1: Use Marathon (provide example json, here is mine)
 {
 cmd: env  export
 
 
 
 
 YARN_RESOURCEMANAGER_OPTS=-Dyarn.resourcemanager.hostname=myriad.marathon.mesos
  hadoop-2.7.0/bin/yarn resourcemanager,
 uris: [maprfs:///mesos/myriad/hadoop-2.7.0.tar.gz],
 cpus: 1.0,
 mem: 1024,
 id: myriad,
 instances: 1,
 user: mapr
 }
 
 In this case, Marathon grabs the hadoop tarball and pulls it down,
 this
 tarball also has the Myriad yml file. When it executes the resource
 manager, it is brought up in Myriad and ready to run node managers by
 pulling the tarball to the slave nodes and executing the nodemanager.
 (I
 would imagine the work with history server etc would also use this
 tarball?).
 
 From here it will us NMInstances to launch a node manager.  (Note,
 this
 is
 different from when I originally set things up... before, I could run
 the
 

Re: Question about build

[Ken Sipe]

Hey Patrick,

I was the one that refactored myriad in to a multi-project structure.   I took 
what was originally there and tried to maintain the semantics into the new 
structure (meaning it was my intention to not change anything other than the 
structure).  At first glance this appears to be a miss on my part.   There is 
no main class in the scheduler.  The scheduler is a YARN resource manager.

Looking it over in more detail, I’m not sure we even need the application 
plugin for the executor.  It is required for the building of the capsule, but 
that could be declared in the capsule instead of using the configuration of the 
application.  It is worth more investigation.

As for long, there are no other projects other than the executor that need the 
application plugin.  I have refactored this and have submitted it as PR-120:  
https://github.com/mesos/myriad/pull/120 
https://github.com/mesos/myriad/pull/120

Thanks for helping to identify this.

Ken

 On Jul 17, 2015, at 3:50 PM, Patrick Wong pw...@maprtech.com wrote:
 
 Hello Myriad Team,
 
 I noticed that the application plugin is applied to all subprojects. Does
 this mean that you are supposed to be able to run gradle installDist to
 get a working local installation for each subproject, and gradle run to
 run them?
 
 -- 
 Patrick Wong
 510.386.7205
 
 mapr.com

Re: Docker Hub Docker submission

[Ken Sipe]

I just checked… docker hub security doesn’t have fine grain controls.the 
next level of access for the group you are in would be admin.   It appears that 
writing a desc requires admin rights (based on what your feedback).

Are you indicating you are not able to edit this:  
https://registry.hub.docker.com/u/mesos/myriad/settings/ 
https://registry.hub.docker.com/u/mesos/myriad/settings/

If you provide the desc, I can post it

ken
 On Jun 11, 2015, at 9:07 AM, Brandon Gulla gulla.bran...@gmail.com wrote:
 
 Dev,
 I have pushed the myriad resource-manager docker to the Docker Registry
 Hub. It seems that I have pushing abilities but not the ability to write
 descriptions/documentation on the hub. Maybe @kensipe can provide me with
 said access.
 
 https://registry.hub.docker.com/u/mesos/myriad/
 
 -- 
 Brandon

Re: May board report

[Ken Sipe]

Justin,

Thanks for the detailed feedback.   As someone involved with the project here 
is my understanding:

1. we do have a hangout to discuss the project every 2 weeks.   Is this not 
appropriate?It really helps to sync up with where we are in the process.
 Would it help if we had meeting minutes and posted that the email list?

2.  most of the work and PR are in a non ASF git repo at the moment.  I believe 
we were waiting for eBay to officially donate the code (tied up in legal last I 
remember).   At the time the donation is official we were going to change the 
package namespace and move to the ASF repo.

3. I would need to review in more detail.

We really appreciate your involvement and feedback!  Looking forward to more 
clarification if you have thoughts on my questions.

ken
 On May 6, 2015, at 11:56 PM, Justin Mclean jus...@classsoftware.com wrote:
 
 Hi,
 
 I’ve been appointed shepherd for Myriad this month and while doing a review  
 I noticed a couple of minor things that you may wish to address in your board 
 report and/or on this dev list.
 
 Please note that this is just from a casual glance and you certainly know 
 your project better that I do and I may of missed something/there may not be 
 any issues at all.
 
 1. Conversations seems to be happening off list [1].
 2. Git report has been created but there’s no code in it [2]. Pull requests 
 are still happening on non ASF github.
 3. May need some clarity around making releases in this way [3] I suggest you 
 carefully read [4] [5]. Note that Under no circumstances are unapproved 
 builds a substitute for releases.
 
 Again I’m not involved in this project and it up to the PMC (with the Mentors 
 help) to decide what to do and don’t do, so feel free to ignore the above if 
 you don’t think there’s any issue here.
 
 Thanks,
 Justin
 
 1. 
 http://mail-archives.apache.org/mod_mbox/incubator-myriad-dev/201504.mbox/%3ccakoqndusesuoko4yraqwsjblvjrhstbcqghcngwynuhzym7...@mail.gmail.com%3e
 2. https://git-wip-us.apache.org/repos/asf?p=incubator-myriad.git;a=summary
 3. 
 http://mail-archives.apache.org/mod_mbox/incubator-myriad-dev/201504.mbox/%3c985b60f3-eb09-4b54-8b4a-6a791c151...@mesosphere.io%3e
 4. http://www.apache.org/dev/release.html#what-must-every-release-contain
 5. http://www.apache.org/dev/release.html#what

Re: Recommending or requiring mesos dns?

[Ken Sipe]

John,

1. +1 to mesos-dns aware
2. all tasks deployed by mesos are already in mesos-dns.  so all the nm are 
there (we should make sure they have good names.
3. the RM is not usually started with mesos… if it was it would also be listed 
in mesos-dns, however a process started outside mesos is not currently added to 
mesos-dns.  At some point mesos-dns will allow for out of band server 
registration… but it isn’t there today.
4. I would like to see multi-yarn clusters on mesos supported with 
multi-myriad.  Each myriad would managed it’s cluster and would register with a 
unique framework id.

ken

 On May 7, 2015, at 5:51 AM, John Omernik j...@omernik.com wrote:
 
 I've implemented mesos-dns and use marathon to launch my myriad framework.
 It shows up as myriad.marahon.mesos and makes it easy to find what node the
 framework launched the resource manager on.
 
 What if we made myriad mesos-dns aware, and prior to launching the yarn
 rm, it could register in mesos dns. This would mean both the ip addresses
 and the ports (we need to figure out multiple ports in mesos-dns). Then it
 could write out ports and host names in the nm configs by checking mesos
 dns for which ports the resource manager is using.
 
 Side question:  when a node manager registers with the resource manager
 are the ports the nm is running on completely up to the nm? Ie I can run my
 nm web server any port, Yarn just explains that to the rm on registration?
 Because then we need a mechanism at launch of the nm task to understand
 which ports mesos has allocated to the nm and update the yarn-site for that
 nm before launch Perhaps mesos-dns as a requirement isn't needed, but I
 am trying to walk through options that get us closer to multiple yarn
 clusters on a mesos cluster.
 
 John
 
 
 -- 
 Sent from my iThing

docker hub repo

[Ken Sipe]

I’ve created a docker repo for myriad under the mesos namespace:   
https://registry.hub.docker.com/u/mesos/myriad/ 
https://registry.hub.docker.com/u/mesos/myriad/

provide me with users that need push rights

thanks,
ken

Re: docker hub repo

[Ken Sipe]

 On Apr 8, 2015, at 2:48 PM, Santosh Marella smare...@maprtech.com wrote:
 
 Is anyone aware of a free public docker repository that can be used for
 hosting docker images for dev/test?

I don’t understand this question.   we have a free public docker repository.  
add dev/test can be tags on the docker images.  Am I missing something?

 
 Santosh
 
 On Wed, Apr 8, 2015 at 12:38 PM, Ken Sipe k...@mesosphere.io wrote:
 
 
 On Apr 8, 2015, at 2:33 PM, Luciano Resende luckbr1...@gmail.com
 wrote:
 
 How is this repo going to be used ?
 
 It will be the pull location for myriad… at least for the scheduler.
 docker pull mesos/myriad
 
 Will Apache consider things that get pushed to these repos (particularly
 outside of ASF) a release, and thus
 will need to go trough the release process ?
 
 Great question… I don’t know what Apache considers here.   We have a need
 to have dockerized releases.  That is what this is intended for.  I expect
 that initially it will be less structured and manual.   I expect that
 eventually it will be part of the release process and hopefully automated.
 
 Ken
 
 
 On Wed, Apr 8, 2015 at 10:42 AM, Ken Sipe k...@mesosphere.io wrote:
 
 I’ve created a docker repo for myriad under the mesos namespace:
 https://registry.hub.docker.com/u/mesos/myriad/ 
 https://registry.hub.docker.com/u/mesos/myriad/
 
 provide me with users that need push rights
 
 thanks,
 ken
 
 
 
 
 --
 Luciano Resende
 http://people.apache.org/~lresende
 http://twitter.com/lresende1975
 http://lresende.blogspot.com/