Re: [DISCUSS] Leave Apache and the Incubator

[Brandon Gulla]

Not a committer but have been around the project since it's inception.

+1

On Thu, Jan 2, 2020 at 11:52 PM Javi Roman  wrote:

> Please vote to retire Myriad from the ASF Incubator. My take is that
> Myriad has failed to get adequate community traction in the ASF
> Incubator and the administrative work of the ASF is more of a burden
> than a benefit to the project. Exiting incubation right now seems like
> the obvious benefit to everyone -- the decision to return can always be
> made later and should be easier to execute the second time around.
>
> [ ] +1 to retire
> [ ] -1 Not retiring because..
>
> Here's my +1
>
> This will be open for at least 72 hours and is a Majority vote.
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> Apache Id: javiroman
>


-- 
Brandon

Re: Myriad 0.3.0 Release Planning

[Brandon Gulla]

Not a committer but happy to evaluate the release. Excited to see this
effort rise from the ashes.

On Tue, Nov 20, 2018 at 8:36 AM Darin Johnson 
wrote:

> I think the big issue here is going to be getting committers to vote on the
> release.  Suggest giving them plenty of time.
>
> On Sun, Nov 18, 2018, 7:09 AM Javi Roman 
> > I would like to offer myself as release manager for Myriad 0.3.0.
> > I guess, we have to try release a new version of Apache Myriad, and
> > try to follow a new release per quarter. This is the first serious
> > attempt of rebooting the project and this is a way of pulse the
> > reaction of the community regarding this project.
> >
> > I am hoping to cut the first release candidate for 0.3.0 in a few
> > days, so we are going to tag the includes JIRAs in the "Myriad 0.3.0"
> > version here [1]. Additionally we are going to follow the release
> > process in this document [2], in order to document the guidelines and
> > actions for this release.
> >
> > [1] https://issues.apache.org/jira/projects/MYRIAD/versions/12335763
> > [2]
> >
> https://docs.google.com/document/d/1ZZdBFVKyBtQlKRK_O1d_obi5wjRAfmoHFPo_sye7wQY/edit#heading=h.ouya5fmdjqg1
> > --
> > Javi Roman
> >
> > Twitter: @javiromanrh
> > GitHub: github.com/javiroman
> > Linkedin: es.linkedin.com/in/javiroman
> > Big Data Blog: dataintensive.info
> > Apache Id: javiroman
> >
>


-- 
Brandon

Re: Apache Slider and Apache Myriad

[Brandon Gulla]

Possible, maybe, the right thing to do? Probably not.

There are multiple container orchestration platforms these days, and the
pecking order is k8s -> mesos -> yarn. DC/OS has already implemented
support for kubernetes, but purely because it is seeing k8s as a competitor
and Mesosphere desires to make it as easy as possible to support hybrid
cloud solutions for their customers. While they may one day add k8s
scheduling functionality to Marathon (speculative), I highly doubt that
they would do the same for yarn.

A lot of Hadoop-ecosystems are now adding support for kubernetes directly,
look at the latest version of spark. You go where the customers are, and
YARN is still in third place and I would be shocked to see that change any
time soon.



On Tue, Apr 24, 2018 at 2:27 PM, Javi Roman 
wrote:

> Probably you are right, however thinking that we have Apache Mesos as
> coarse-grained scheduling, and generally we run at least one
> fine-grained "general purpose" or "meta-scheduler" such as Marathon,
> Aurora or even Kubernetes as framework. Why not apply the same
> rationale for Myriad, YARN as general purpose framework.
>
> I know this is probably crazy, but imagine a kind of DC/OS flavor with
> Apache Mesos + Apache Myriad + Apache Hadoop running as foundation for
> this flavor (without Marathon or kubernetes frameworks), you run
> Mesos, Myriad and Hadoop as system services, and the user can run
> Hadoop applications, Docker applications and whatever application.
> When you click the "Services"  tab at DC/OS interface you get the
> Myriad UI for run applications.
>
> It's crazy I know, but it would be possible? I really don't know.
>
>
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
>
>
> On Tue, Apr 24, 2018 at 8:04 PM, yuliya Feldman
>  wrote:
> >  Are you suggesting using Myriad as meta-scheduler for Mesos?
> > If yes, then:1. Why would one need Mesos or Myriad at all - use YARN for
> everything?2. Mesos scheduler is much more robust then YARN scheduler as
> it's based on the offers - it was done having multiple subsystems in mind
> unlike YARN
> > AFAIK Marathon serves very thin purpose in Myriad - literally just to
> spin up Myriad Master
> > Just my 2c.
> > Thanks,Yuliya
> > On Tuesday, April 24, 2018, 10:56:37 AM PDT, Javi Roman <
> jroman.espi...@gmail.com> wrote:
> >
> >  Hi!
> >
> > Thinking a little more deeply this YARN feature (Hadoop YARN Service
> > framework) could affect Apache Myriad regarding new development goals.
> > Apache Myriad based on YARN 3.x could be a possible substitute for
> > general purpose meta-scheduling Mesos frameworks such as Marathon or
> > Apache Aurora.  We can rewrite the Myriad UI in order to allow run
> > YARN native applications, Docker containers or regular applications.
> >
> > It's just a crazy idea: DC/OS + Apache Myriad (natively installed as
> > systemd unit) instead of Marathon, working as meta-scheduler for
> > Mesos.
> >
> > What do you think?
> > --
> > Javi Roman
> >
> > Twitter: @javiromanrh
> > GitHub: github.com/javiroman
> > Linkedin: es.linkedin.com/in/javiroman
> > Big Data Blog: dataintensive.info
> >
> >
> > On Mon, Apr 23, 2018 at 8:02 AM, Javi Roman 
> wrote:
> >> Hi Darin,
> >>
> >> You are right Slider is a kind of framework for long running
> >> applications into YARN, and it's a way of running applications on YARN
> >> without changing the application code, there is no need to develop a
> >> custom Application Master or other YARN code. Apparently you can run
> >> unmodified applications on YARN via Slider.
> >>
> >> This shift towards Hadoop code (instead of separate project, incubator
> >> slider) doesn't affect Myriad at all. However I was thinking any kind
> >> of collaboration with Slider project, and this collaboration is
> >> unclear right now, because of fuzzy continuity of Slider.
> >> --
> >> Javi Roman
> >>
> >> Twitter: @javiromanrh
> >> GitHub: github.com/javiroman
> >> Linkedin: es.linkedin.com/in/javiroman
> >> Big Data Blog: dataintensive.info
> >>
> >>
> >> On Mon, Apr 23, 2018 at 1:25 AM, Darin Johnson 
> wrote:
> >>> Javi can you explain how this effects myriad?  My understanding is that
> >>> slider is similar to marathon but for yarn.
> >>>
> >>> On Sat, Apr 21, 2018, 2:23 AM Javi Roman 
> wrote:
> >>>
>  FYI
> 
>  Regarding the recent conversation about YARN applications development
>  via Apache Slider, as a different approach for creating data services
>  applications on Apache Mesos (via Myriad,) "article 4" here [1], will
>  probably have to wait until the resolution of this discussion at
>  Apache Slider list [2]. Basically the Slider community is discussing
>  about the retirement of the project, because the Slider core is being
>  

Re: Please do not retire Myriad

[Brandon Gulla]

While I am not a committer at the moment, having contributed to Myriad in
the early days, I am able to help review potential PRs and changes down the
road.

On Fri, Feb 2, 2018 at 7:50 AM, Justin Mclean 
wrote:

> Hi,
>
> > 1. Try to convince to Apache managers (I don't now the correct term)
> > for an exception to allow you accept commits from external
> > contributors (like me).
>
> All and any contributions are welcome, that is not he issue here. The
> board requires oversight of at least 3 (P)PMC members. For incubating
> project generally the committers are the PPMC.
>
> > 2. Follow your first proposal, create a new github organization, for
> > example (github.com/myriad) and working there.
>
> As the software is under the Apache license anyone can do this, you don't
> need to ask for permission.
>
> > Maybe in the future we can try go to Apache incubation again.
>
> And I’m sure the Apache incubator would welcome that.
>
> > I guess we are three people with interest into continue the project,
> > you, Juan P. and myself. From my side I am working in a local fork for
> > enhancing some stuff.
>
> Alternatively if the people above have contributed and promoted the
> project (I’m sorry but I don’t know the full history here) and the currenrt
> PPMC recognise that and votes you in as PPMC members then that may be
> enough to continue the project at Apache.
>
> Thanks.
> Justin




-- 
Brandon

Re: [DISCUSS] Retire Myriad

[Brandon Gulla]

+1 vote to retire (non-committer)

On Sun, Nov 5, 2017 at 9:03 AM, John D. Ament  wrote:

> All,
>
> Based on the current state of Myriad and prior discussions I'd like to
> start the discussions around retiring the project.
>
> John
>



-- 
Brandon

Re: [Vote] Retire Myriad

[Brandon Gulla]

+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

Re: Website is updated, 0.2.0 is official!

[Brandon Gulla]

Woo great job everyone!

On Wed, Jun 29, 2016 at 5:05 PM, Darin Johnson 
wrote:

> http://myriad.apache.org/
>
> Tell your friends!
>



-- 
Brandon

[jira] [Created] (MYRIAD-230) Myriad Docker-Gradle integration broken with Docker for Mac beta

[Brandon Gulla (JIRA)]

Brandon Gulla created MYRIAD-230:


 Summary: Myriad Docker-Gradle integration broken with Docker for 
Mac beta
 Key: MYRIAD-230
 URL: https://issues.apache.org/jira/browse/MYRIAD-230
 Project: Myriad
  Issue Type: Bug
  Components: Scheduler
 Environment: OSX 10.X 
Docker for Mac Beta Version 1.12.0-rc2-beta16 (build: 9493)
Reporter: Brandon Gulla
Assignee: Brandon Gulla
Priority: Minor


Building image using context 
'/Users/gullatec/development/incubator-myriad/docker'.
Using tag 'mesos/myriad' for image.
java.lang.UnsatisfiedLinkError: Could not find library in classpath, tried: 
[libjunixsocket-macosx-1.8-x86_64.dylib, libjunixsocket-macosx-1.5-x86_64.dylib



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

Re: [Vote] Release apache-myriad-0.2.0-incubating (release candidate 4)

[Brandon Gulla]

+1

built and tested on a test cluster. great work guys.

On Thu, Jun 9, 2016 at 6:39 PM, mohit soni  wrote:

> +1 (Binding)
>
> - Verified signature
> - Verified MD5 and SHA512 hashes
> - Builds from source tar ball.
> - Installed Myriad on a Mesos cluster and ran sanity tests.
>
> Thanks
> Mohit
>
> On Thu, Jun 2, 2016 at 7:25 AM, John Yost  wrote:
>
> > I'm voting +1
> >
> > --John
> >
> > On Tue, May 24, 2016 at 10:46 PM, Darin Johnson  >
> > wrote:
> >
> > > I'm voting +1 (Binding)
> > >
> > > Verified md5/sha hashes.  Compiled with gradle build, gradle
> > buildRMDocker
> > > (on OSX with docker-machine).
> > >
> > > Ran remote distribution (with cgroups) on a 4 node cluster (Ubuntu,
> > > hadoop-2.6.0, hadoop 2.7.0) with one CGS NM and 3 FGS NM.  Ran 8
> > > simultaneous jobs.  Shut down Framework.  Restarted NodeManager, ran an
> > > additional 3 jobs.
> > >
> > > Ran the same with docker (minus cgroups).
> > >
> > > Darin
> > >
> > > On Tue, May 24, 2016 at 10:40 PM, Darin Johnson <
> dbjohnson1...@gmail.com
> > >
> > > wrote:
> > >
> > > > Hi All,
> > > >
> > > > I have created a source tar ball for Apache Myriad 0.2.0-incubating,
> > > > release candidate 3 based off the feed back received from release
> > > > candidate 1,2 & 3.  Thanks Sarjeet for a very thorough review!
> > > >
> > > > Here’s the release notes:
> > > > https://cwiki.apache.org/confluence/display/MYRIAD/Release+Notes
> > > >
> > > > The commit to be voted upon is tagged with
> > "myriad-0.2.0-incubating-rc4"
> > > > and is available here:
> > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-myriad.git;a=shortlog;h=refs/tags/myriad-0.2.0-incubating-rc
> > > > <
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-myriad.git;a=shortlog;h=refs/tags/myriad-0.2.0-incubating-rc4
> > > >
> > > > 4
> > > >
> > > > The artifacts to be voted upon are located below. Please note that
> this
> > > is
> > > > a source release:
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.2.0-incubating-rc4/
> > > >
> > > > Release artifacts are signed with the following key:
> > > > *https://home.apache.org/~darinj/gpg/2AAE9E3F.asc
> > > > *
> > > >
> > > > **Please note that the release tar ball does not include the gradlew
> > > script
> > > > to build. You need to install gradle in order to build.**
> > > >
> > > > Please try out the release candidate and vote. The vote is open for a
> > > > minimum of 3 business days (Friday May 27) or until the necessary
> > number
> > > > of votes (3 binding +1s)
> > > > is reached.
> > > >
> > > > If/when this vote succeeds, I will call for a vote with IPMC seeking
> > > > permission to release RC3 as Apache Myriad 0.2.0 (incubating).
> > > >
> > > > [ ] +1 Release this package as Apache Myriad 0.2.0-incubating
> > > > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks,
> > > > Darin
> > > >
> > >
> >
>



-- 
Brandon

Re: Myriad is 0.1.0

[Brandon Gulla]

Wooo! Great job everyone!

On Thu, Dec 10, 2015 at 4:42 AM, Adam Bordelon  wrote:

> Hooray! Time for champagne!
>
>
>
> On Thu, Dec 10, 2015 at 1:13 AM, Santosh Marella 
> wrote:
>
> > Hi All,
> >
> >   Congratulations on a the first Apache Myriad release..! Kudos to
> everyone
> > involved for making this happen.
> >
> >   As we now have IPMC's approval, there are a few things that I did to
> wrap
> > up the release:
> >   - Make 0.1.0 artifacts available from the release SVN repo [1].
> >   - Git tag the voted RC as the "0.1.0" release [2].
> >   - Delete the previously marked git RC tags.
> >   - Closed the remaining JIRAs marked for 0.1.0 version and marked the
> > 0.1.0 version as "released" [3].
> >   - Submitted a PR [4] with scripts to prepare a RC and release a RC
> > (automates the above git and svn steps)
> >   - Updated the release guide [5] with voting links to help future
> release
> > managers.
> >
> >   Here are a couple of things still remaining:
> >   - Update the downloads page on Myriad's website with links to 0.1.0
> > artifacts on svn, git tag, release notes.
> >   - Do an announcement blog post. Here is a draft [6]. Please suggest any
> > changes.
> >
> >   If I may be missing something for 0.1.0, appreciate if you could bring
> to
> > my notice.
> >
> >1.
> >
> >
> https://dist.apache.org/repos/dist/release/incubator/myriad/myriad-0.1.0-incubating/
> >2.
> >
> >
> https://github.com/apache/incubator-myriad/releases/tag/myriad-0.1.0-incubating
> >3.
> >
> >
> https://issues.apache.org/jira/browse/MYRIAD/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel
> >4. https://github.com/apache/incubator-myriad/pull/53
> >5. https://cwiki.apache.org/confluence/display/MYRIAD/Release+Guide
> >6.
> >
> >
> https://docs.google.com/document/d/1zCXnDlqzNhj0BL_CqRz5-poCap9QFah7R3tKkHdspYg/edit
> >
> > Thanks,
> > Santosh
> >
>



-- 
Brandon

Re: [TESTERS NEEDED] ResourceManager Docker

[Brandon Gulla]

Hey Prabhu! Thanks for the interest in testing the resource manager docker.
Myriad currently only supports officially supports hadoop-2.7.0 due to some
API changes in hadoop-2.7.1. I currently have some features baked into the
docker image where you can specify an alternative hadoop archive URL to use
but I need to test a few things before I test that out.

So feel free to try it with hadoop-2.7.0 or wait until next week when we
can try some experiments.

Thanks.


On Fri, Dec 4, 2015 at 1:54 PM, Prabhu Inbarajan <inbarajan.pra...@gmail.com
> wrote:

> I am running hadoop 2.7.1 , would be happy to test the resource manager
> container as well..
>
> Thanks
> Prabhu
>
> On Fri, Dec 4, 2015 at 8:44 AM, Sarjeet Singh <sarjeetsi...@maprtech.com>
> wrote:
>
> > Nice, Brandon!!
> >
> > I can give it a try today, probably. Send me any more details if required
> > or necessary, or I'll PM you if I run into any issues. Hope this is ok to
> > PM you directly (Don't want to spam myriad mailing list).
> >
> > -Sarjeet
> >
> > On Fri, Dec 4, 2015 at 7:17 AM, Brandon Gulla <gulla.bran...@gmail.com>
> > wrote:
> >
> > > I have built a new ResourceManager Docker that needs some testing love.
> > > Please test it out and let me know what bugs you may find. This is
> built
> > > for Apache Hadoop 2.7.0 and has not been tested with MapR
> distributions.
> > > You no longer have to do anything fancy, just mount the directory with
> > your
> > > yarn-site.xml and myriad-config and you should be good to go. Once we
> > feel
> > > good about it I can push it to the official mesos docker repo (Thanks
> > again
> > > Ken).
> > >
> > > https://hub.docker.com/r/bgulla/myriad/
> > >
> > > Also, I hooked the docker build into gradle for future building
> goodness
> > > but will wait to submit that PR until after we cut a release.
> > >
> > > Thanks!
> > >
> > >
> > > --
> > > Brandon
> > >
> >
>



-- 
Brandon

Re: Myriad's website is live!

[Brandon Gulla]

Great job!

On Thu, Dec 3, 2015 at 7:17 AM, Jim Klucar  wrote:

> Awesome. Hopefully we can push a post about the release soon!
>
> On Wed, Dec 2, 2015 at 10:14 PM, Sarjeet Singh 
> wrote:
>
> > Good one, Mohit. Kudos to make it work, and Others for contributing to
> > build the website!!
> >
> > Website looks great, and it has all necessary information to get it going
> > from here. Navigated around the website and it feels nice :)
> >
> > -Sarjeet
> >
> > On Wed, Dec 2, 2015 at 7:00 PM, mohit soni 
> > wrote:
> >
> > > Apache Myriad website is finally live, please go and checkout it out
> for
> > > real here !
> > >
> > > I was able to identify the root cause which was preventing jekyll from
> > > building the content correctly. Apparently, Jekyll does not like the
> > > comments place on top of the Liquid templates, for that matter it
> doesn't
> > > like anything (even newlines) before the triple dashes '' section.
> > Once
> > > I moved the triple dash section on top of the files, the rendering
> > started
> > > working just fine.
> > >
> > > Cheers!
> > > Mohit
> > >
> >
>



-- 
Brandon

Re: [VOTE] Release apache-myriad-0.1.0-incubating (release candidate 2)

[Brandon Gulla]

I'm late but tested officially +1
On Nov 16, 2015 6:07 PM, "Santosh Marella"  wrote:

> The vote for RC2 has concluded and passed. Thanks everyone for verifying
> the release and voting.
>
> *binding +1s (3)*
>
> Darin Johnson
> Santosh Marella
> Swapnil Daingade
>
> *non-binding +1s (4)*
>
> Aashreya Shankar
> Jim Klucar
> Sarjeet Singh
> Yuliya Feldman
>
> The next step is to submit the release for vote with the IPMC.
>
> Thanks,
> Santosh
>
> On Mon, Nov 16, 2015 at 1:42 PM, Santosh Marella 
> wrote:
>
> > Thanks for the suggestion, Justin.
> >
> > Santosh
> >
> > On Mon, Nov 16, 2015 at 1:05 PM, Justin Mclean  >
> > wrote:
> >
> >> Hi,
> >>
> >> > Agree with Adam and Darin. While Apache requires 72 hours of keeping
> the
> >> > vote open
> >>
> >> The requirement I believe is a minimum of 72 hours, but it’s not a hard
> >> one.
> >>
> >> A suggestion, you could say “open for a minimum of 72 hours or until we
> >> have enough binding votes” when starting the vote.
> >>
> >> Thanks,
> >> Justin
> >
> >
> >
>

Re: [VOTE] Release apache-myriad-0.1.0-incubating (release candidate 1)

[Brandon Gulla]

+1

On Tue, Nov 10, 2015 at 6:22 PM, Ken Sipe  wrote:

> +1 ship it!
>
> > On Nov 10, 2015, at 5:05 PM, Santosh Marella 
> wrote:
> >
> > Hi all,
> >
> > I have created a build for Apache Myriad 0.1.0-incubating, release
> > candidate 1.
> >
> > Thanks to everyone who has contributed to this release.
> >
> > Here’s the release notes:
> > https://cwiki.apache.org/confluence/display/MYRIAD/Release+Notes
> >
> > The commit to be voted upon is tagged with "myriad-0.1.0-incubating-rc1"
> > and is available here:
> >
> https://git1-us-west.apache.org/repos/asf/incubator-myriad/repo?p=incubator-myriad.git;a=commit;h=9f0fa15bfaa4fdc309ada27126567a2aa5bf296b
> >
> > The artifacts to be voted upon are located here:
> > *
> https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.1.0-incubating-rc1/
> > <
> https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.1.0-incubating-rc1/
> >*
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/smarella.asc
> >
> > Please vote on releasing this package as Apache Myriad 0.1.0-incubating.
> >
> > The vote is open for the next 72 hours and passes if a majority of
> > at least three +1 PPMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Myriad 0.1.0-incubating
> > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> > Here is my vote:
> > +1 (binding)
> >
> > Thanks,
> > Santosh
>
>


-- 
Brandon

Re: [VOTE] Release apache-myriad-0.1.0-incubating (release candidate 0)

[Brandon Gulla]

I am adjusting the version on the Dockerfiles as we speak and will be
submitting a PR very shortly.

2.7.1. -> 2.7.0

On Mon, Nov 9, 2015 at 4:29 AM, Adam Bordelon  wrote:

> Do we need to rev the version on the executor jars up to 0.1.0?
> Is there anywhere else we need to bump the version?
>
> $ grep -rin "myriad.*[^ \[\(0-9]0" . |grep -v Apache
> ./docker/Dockerfile:34:ADD /libs/myriad-executor-runnable-0.0.1.jar
> /usr/local/libexec/mesos/
> ./docker/ResourceManager.dockerfile:30:ADD
> /libs/myriad-executor-runnable-0.0.1.jar /usr/local/libexec/mesos/
> ./docker/build-myriad.sh:40:cp -rf
> ../myriad-executor/build/libs/myriad-executor-runnable-0.0.1.jar libs/
> ./docs/vagrant.md:100
> :/vagrant/myriad-scheduler/build/libs/myriad-executor-0.0.1.jar
> ./docs/vagrant.md:107:cp
> /vagrant/myriad-executor/build/libs/myriad-executor-0.0.1.jar
> $YARN_HOME/share/hadoop/yarn/lib/
> ./docs/vagrant.md:150:  path:
> file://localhost/usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> ./docs/myriad-dev.md:67:cp
> myriad-executor/build/libs/myriad-executor-0.0.1.jar
> /opt/hadoop-2.7.1/share/hadoop/yarn/lib/
> ./docs/myriad-remote-distribution-configuration.md:39:cp
> myriad-executor/build/libs/myriad-executor-0.0.1.jar
> /opt/hadoop-2.7.1/share/hadoop/yarn/lib/
> ./myriad-scheduler/src/main/resources/myriad-config-default.yml:55:  path:
> file:///usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> ./myriad-scheduler/src/main/resources/myriad-config-default.yml:58:  #path:
> hdfs://namenode:port/dist/myriad-executor-runnable-0.0.1.jar
>
> ./myriad-scheduler/src/main/java/org/apache/myriad/configuration/MyriadConfiguration.java:55:
> * path:
> file://localhost/usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> ./myriad-scheduler/src/test/resources/myriad-config-test-default.yml:31:
> path: file:///usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> ./myriad-scheduler/src/test/resources/myriad-config-test-default.yml:34:
> #path: hdfs://namenode:port/dist/myriad-executor-runnable-0.0.1.jar
>
>
> On Mon, Nov 9, 2015 at 1:20 AM, Santosh Marella 
> wrote:
>
> > I haven't created a git tag for the rc. I will try creating one in the
> > morning.
> >
> > --
> > Sent from mobile
> > On Nov 9, 2015 1:10 AM, "Adam Bordelon"  wrote:
> >
> > > Awesome! I'll try to build and run this myself this week.
> > > Is there a git tag I can sync to for 0.1.0-rc0?
> > >
> > > On Mon, Nov 9, 2015 at 1:01 AM, Santosh Marella  >
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > I have created a build for Apache Myriad 0.1.0-incubating, release
> > > > candidate 0.
> > > >
> > > > Thanks to everyone who has contributed to this release.
> > > >
> > > > Here’s the release notes:
> > > > https://cwiki.apache.org/confluence/display/MYRIAD/Release+Notes
> > > >
> > > > The commit to be voted upon is:
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-myriad/commit/343a11aceb0fc9b5c84f46bba43b2423643eff6f
> > > >
> > > > The artifacts to be voted on are located here:
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.1.0-incubating-rc0/
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/smarella.asc
> > > >
> > > > Please vote on releasing this package as Apache Myriad
> > 0.1.0-incubating.
> > > >
> > > > The vote is open for the next 72 hours and passes if a majority of
> > > > at least three +1 PPMC votes are cast.
> > > >
> > > > [ ] +1 Release this package as Apache Myriad 0.1.0-incubating
> > > > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > > > [ ] -1 Do not release this package because...
> > > >
> > > >
> > > > Here is my vote:
> > > > +1 (binding)
> > > >
> > > > Thanks,
> > > > Santosh
> > > >
> > >
> >
>



-- 
Brandon

Re: [VOTE] Release apache-myriad-0.1.0-incubating (release candidate 0)

[Brandon Gulla]

The PR was submitted this morning. We dont have to wait, but the docker
build previously used 2.7.1.

On Mon, Nov 9, 2015 at 2:33 PM, yuliya Feldman <yufeld...@yahoo.com.invalid>
wrote:

> Are you saying we should have rc1 after you are done?
>   From: Brandon Gulla <gulla.bran...@gmail.com>
>  To: dev@myriad.incubator.apache.org
>  Sent: Monday, November 9, 2015 5:33 AM
>  Subject: Re: [VOTE] Release apache-myriad-0.1.0-incubating (release
> candidate 0)
>
> I am adjusting the version on the Dockerfiles as we speak and will be
> submitting a PR very shortly.
>
> 2.7.1. -> 2.7.0
>
>
>
> On Mon, Nov 9, 2015 at 4:29 AM, Adam Bordelon <a...@mesosphere.io> wrote:
>
> > Do we need to rev the version on the executor jars up to 0.1.0?
> > Is there anywhere else we need to bump the version?
> >
> > $ grep -rin "myriad.*[^ \[\(0-9]0" . |grep -v Apache
> > ./docker/Dockerfile:34:ADD /libs/myriad-executor-runnable-0.0.1.jar
> > /usr/local/libexec/mesos/
> > ./docker/ResourceManager.dockerfile:30:ADD
> > /libs/myriad-executor-runnable-0.0.1.jar /usr/local/libexec/mesos/
> > ./docker/build-myriad.sh:40:cp -rf
> > ../myriad-executor/build/libs/myriad-executor-runnable-0.0.1.jar libs/
> > ./docs/vagrant.md:100
> > :/vagrant/myriad-scheduler/build/libs/myriad-executor-0.0.1.jar
> > ./docs/vagrant.md:107:cp
> > /vagrant/myriad-executor/build/libs/myriad-executor-0.0.1.jar
> > $YARN_HOME/share/hadoop/yarn/lib/
> > ./docs/vagrant.md:150:  path:
> >
> file://localhost/usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> > ./docs/myriad-dev.md:67:cp
> > myriad-executor/build/libs/myriad-executor-0.0.1.jar
> > /opt/hadoop-2.7.1/share/hadoop/yarn/lib/
> > ./docs/myriad-remote-distribution-configuration.md:39:cp
> > myriad-executor/build/libs/myriad-executor-0.0.1.jar
> > /opt/hadoop-2.7.1/share/hadoop/yarn/lib/
> > ./myriad-scheduler/src/main/resources/myriad-config-default.yml:55:
> path:
> > file:///usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> > ./myriad-scheduler/src/main/resources/myriad-config-default.yml:58:
> #path:
> > hdfs://namenode:port/dist/myriad-executor-runnable-0.0.1.jar
> >
> >
> ./myriad-scheduler/src/main/java/org/apache/myriad/configuration/MyriadConfiguration.java:55:
> > * path:
> >
> file://localhost/usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> > ./myriad-scheduler/src/test/resources/myriad-config-test-default.yml:31:
> > path: file:///usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> > ./myriad-scheduler/src/test/resources/myriad-config-test-default.yml:34:
> > #path: hdfs://namenode:port/dist/myriad-executor-runnable-0.0.1.jar
> >
> >
> > On Mon, Nov 9, 2015 at 1:20 AM, Santosh Marella <smare...@maprtech.com>
> > wrote:
> >
> > > I haven't created a git tag for the rc. I will try creating one in the
> > > morning.
> > >
> > > --
> > > Sent from mobile
> > > On Nov 9, 2015 1:10 AM, "Adam Bordelon" <a...@mesosphere.io> wrote:
> > >
> > > > Awesome! I'll try to build and run this myself this week.
> > > > Is there a git tag I can sync to for 0.1.0-rc0?
> > > >
> > > > On Mon, Nov 9, 2015 at 1:01 AM, Santosh Marella <
> smare...@maprtech.com
> > >
> > > > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > I have created a build for Apache Myriad 0.1.0-incubating, release
> > > > > candidate 0.
> > > > >
> > > > > Thanks to everyone who has contributed to this release.
> > > > >
> > > > > Here’s the release notes:
> > > > > https://cwiki.apache.org/confluence/display/MYRIAD/Release+Notes
> > > > >
> > > > > The commit to be voted upon is:
> > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-myriad/commit/343a11aceb0fc9b5c84f46bba43b2423643eff6f
> > > > >
> > > > > The artifacts to be voted on are located here:
> > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.1.0-incubating-rc0/
> > > > >
> > > > > Release artifacts are signed with the following key:
> > > > > https://people.apache.org/keys/committer/smarella.asc
> > > > >
> > > > > Please vote on releasing this package as Apache Myriad
> > > 0.1.0-incubating.
> > > > >
> > > > > The vote is open for the next 72 hours and passes if a majority of
> > > > > at least three +1 PPMC votes are cast.
> > > > >
> > > > > [ ] +1 Release this package as Apache Myriad 0.1.0-incubating
> > > > > [ ]  0 I don't feel strongly about it, but I'm okay with the
> release
> > > > > [ ] -1 Do not release this package because...
> > > > >
> > > > >
> > > > > Here is my vote:
> > > > > +1 (binding)
> > > > >
> > > > > Thanks,
> > > > > Santosh
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Brandon
>
>
>



-- 
Brandon

[jira] [Commented] (MYRIAD-171) Hadoop-2.7.1 UpdateFIle

[Brandon Gulla (JIRA)]

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

Brandon Gulla commented on MYRIAD-171:
--

Bingo.

Looks like I should be able to hit the RM rest-endpoint and pull the version 
from there. Hopefully there is another way that doesn't pose some race 
conditions, but I'll explore that further. 

https://github.com/apache/hadoop/blob/f8adeb712dc834c27cec15c04a986f2f635aba83/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/ResourceManagerRest.md

> Hadoop-2.7.1 UpdateFIle
> ---
>
> Key: MYRIAD-171
> URL: https://issues.apache.org/jira/browse/MYRIAD-171
> Project: Myriad
>  Issue Type: Bug
>Affects Versions: Myriad 0.1.0
>    Reporter: Brandon Gulla
>    Assignee: Brandon Gulla
>Priority: Blocker
>
> Hadoop 2.7.1 introduced an API changed that breaks Myriad when using HA 
> ResourceManager. They added an extra argument to the method that we are 
> currently using. 
> To get around this, switch hadoop version to 2.7.0 or wait for the impending 
> code change. 
> Hadoop 2.7.1
> https://github.com/apache/hadoop/blob/release-2.7.1/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/recovery/FileSystemRMStateStore.java
> Hadoop 2.7.0
> https://github.com/apache/hadoop/blob/release-2.7.0/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/recovery/FileSystemRMStateStore.java
> I1106 19:26:55.098060  5135 sched.cpp:164] Version: 0.25.0
> 15/11/06 19:26:55 INFO scheduler.MyriadDriver: Driver started with status: 
> DRIVER_RUNNING
> 15/11/06 19:26:55 INFO scheduler.MyriadDriverManager: Driver started with 
> status: DRIVER_RUNNING
> 15/11/06 19:26:55 INFO myriad.Main: started mesosDriver..
> 15/11/06 19:26:55 INFO interceptor.CompositeInterceptor: Registered 
> org.apache.myriad.policy.LeastAMNodesFirstPolicy into the registry.
> I1106 19:26:55.100406  5185 sched.cpp:262] New master detected at 
> master@172.31.45.229:5050
> I1106 19:26:55.100591  5185 sched.cpp:272] No credentials provided. 
> Attempting to register without authentication
> 15/11/06 19:26:55 INFO myriad.Main: Launching 1 NM(s) with profile medium
> I1106 19:26:55.102533  5179 sched.cpp:641] Framework registered with 
> 2f8adca0-12da-4200-867d-2b742955cabd-0004
> 15/11/06 19:26:55 INFO scheduler.MyriadOperations: Adding 1 NM instances to 
> cluster
> 15/11/06 19:26:55 INFO handlers.RegisteredEventHandler: Received event: 
> org.apache.myriad.scheduler.event.RegisteredEvent@6a005de5 with frameworkId: 
> value: "2f8adca0-12da-4200-867d-2b742955cabd-0004"
> Nov 06, 2015 7:26:55 PM com.lmax.disruptor.FatalExceptionHandler 
> handleEventException
> SEVERE: Exception processing: 0 
> org.apache.myriad.scheduler.event.RegisteredEvent@6a005de5
> java.lang.NoSuchMethodError: 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.MyriadFileSystemRMStateStore.updateFile(Lorg/apache/hadoop/fs/Path;[B)V
>   at 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.MyriadFileSystemRMStateStore.storeMyriadState(MyriadFileSystemRMStateStore.java:95)
>   at 
> org.apache.myriad.state.SchedulerState.updateStateStore(SchedulerState.java:374)
>   at 
> org.apache.myriad.state.SchedulerState.setFrameworkId(SchedulerState.java:362)
>   at 
> org.apache.myriad.scheduler.event.handlers.RegisteredEventHandler.onEvent(RegisteredEventHandler.java:42)
>   at 
> org.apache.myriad.scheduler.event.handlers.RegisteredEventHandler.onEvent(RegisteredEventHandler.java:30)
>   at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> 15/11/06 19:26:55 INFO handlers.ResourceOffersEventHandler: Received offers 3
> 15/11/06 19:26:55 ERROR yarn.YarnUncaughtExceptionHandler: Thread 
> Thread[pool-6-thread-1,5,main] threw an Exception.
> java.lang.RuntimeException: java.lang.NoSuchMethodError: 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.MyriadFileSystemRMStateStore.updateFile(Lorg/apache/hadoop/fs/Path;[B)V
>   at 
> com.lmax.disruptor.FatalExceptionHandler.handleEventException(FatalExceptionHandler.java:45)
>   at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:147)
>   at 
&

[jira] [Commented] (MYRIAD-171) Hadoop-2.7.1 UpdateFIle

[Brandon Gulla (JIRA)]

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

Brandon Gulla commented on MYRIAD-171:
--

2.7.0, Absolutely. The defined hadoop version in the docker build is 2.7.1 
currently but I can that patch tonight. 

I think taking our time with the reflection and setting up a ShimLoader will 
benefit us greater in the long run. 



> Hadoop-2.7.1 UpdateFIle
> ---
>
> Key: MYRIAD-171
> URL: https://issues.apache.org/jira/browse/MYRIAD-171
> Project: Myriad
>  Issue Type: Bug
>Affects Versions: Myriad 0.1.0
>    Reporter: Brandon Gulla
>    Assignee: Brandon Gulla
>Priority: Blocker
>
> Hadoop 2.7.1 introduced an API changed that breaks Myriad when using HA 
> ResourceManager. They added an extra argument to the method that we are 
> currently using. 
> To get around this, switch hadoop version to 2.7.0 or wait for the impending 
> code change. 
> Hadoop 2.7.1
> https://github.com/apache/hadoop/blob/release-2.7.1/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/recovery/FileSystemRMStateStore.java
> Hadoop 2.7.0
> https://github.com/apache/hadoop/blob/release-2.7.0/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/recovery/FileSystemRMStateStore.java
> I1106 19:26:55.098060  5135 sched.cpp:164] Version: 0.25.0
> 15/11/06 19:26:55 INFO scheduler.MyriadDriver: Driver started with status: 
> DRIVER_RUNNING
> 15/11/06 19:26:55 INFO scheduler.MyriadDriverManager: Driver started with 
> status: DRIVER_RUNNING
> 15/11/06 19:26:55 INFO myriad.Main: started mesosDriver..
> 15/11/06 19:26:55 INFO interceptor.CompositeInterceptor: Registered 
> org.apache.myriad.policy.LeastAMNodesFirstPolicy into the registry.
> I1106 19:26:55.100406  5185 sched.cpp:262] New master detected at 
> master@172.31.45.229:5050
> I1106 19:26:55.100591  5185 sched.cpp:272] No credentials provided. 
> Attempting to register without authentication
> 15/11/06 19:26:55 INFO myriad.Main: Launching 1 NM(s) with profile medium
> I1106 19:26:55.102533  5179 sched.cpp:641] Framework registered with 
> 2f8adca0-12da-4200-867d-2b742955cabd-0004
> 15/11/06 19:26:55 INFO scheduler.MyriadOperations: Adding 1 NM instances to 
> cluster
> 15/11/06 19:26:55 INFO handlers.RegisteredEventHandler: Received event: 
> org.apache.myriad.scheduler.event.RegisteredEvent@6a005de5 with frameworkId: 
> value: "2f8adca0-12da-4200-867d-2b742955cabd-0004"
> Nov 06, 2015 7:26:55 PM com.lmax.disruptor.FatalExceptionHandler 
> handleEventException
> SEVERE: Exception processing: 0 
> org.apache.myriad.scheduler.event.RegisteredEvent@6a005de5
> java.lang.NoSuchMethodError: 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.MyriadFileSystemRMStateStore.updateFile(Lorg/apache/hadoop/fs/Path;[B)V
>   at 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.MyriadFileSystemRMStateStore.storeMyriadState(MyriadFileSystemRMStateStore.java:95)
>   at 
> org.apache.myriad.state.SchedulerState.updateStateStore(SchedulerState.java:374)
>   at 
> org.apache.myriad.state.SchedulerState.setFrameworkId(SchedulerState.java:362)
>   at 
> org.apache.myriad.scheduler.event.handlers.RegisteredEventHandler.onEvent(RegisteredEventHandler.java:42)
>   at 
> org.apache.myriad.scheduler.event.handlers.RegisteredEventHandler.onEvent(RegisteredEventHandler.java:30)
>   at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> 15/11/06 19:26:55 INFO handlers.ResourceOffersEventHandler: Received offers 3
> 15/11/06 19:26:55 ERROR yarn.YarnUncaughtExceptionHandler: Thread 
> Thread[pool-6-thread-1,5,main] threw an Exception.
> java.lang.RuntimeException: java.lang.NoSuchMethodError: 
> org.apache.hadoop.yarn.server.resourcemanager.recovery.MyriadFileSystemRMStateStore.updateFile(Lorg/apache/hadoop/fs/Path;[B)V
>   at 
> com.lmax.disruptor.FatalExceptionHandler.handleEventException(FatalExceptionHandler.java:45)
>   at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:147)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor

Re: [DISCUSS] Release prep for Myriad 0.1.0

[Brandon Gulla]

I just found some badness that may be a blocker. A change happened in 2.7.1
that broke our API. See https://issues.apache.org/jira/browse/MYRIAD-171

I am going to try to submit the patch tonight.

On Fri, Nov 6, 2015 at 1:57 PM, Santosh Marella 
wrote:

> Sounds good, Adam.
>
> Santosh
>
> On Fri, Nov 6, 2015 at 10:32 AM, Adam Bordelon  wrote:
>
> > Website sources don't need to be in the release tarball (would bloat it
> > unnecessarily), and don't need to block the release of the 0.1.0
> binaries,
> > but we'll want the podling site up so we can announce our release on the
> > website.
> >
> > On Fri, Nov 6, 2015 at 10:15 AM, Santosh Marella 
> > wrote:
> >
> > > Starting this thread to discuss the last few items left before calling
> > out
> > > for a vote.
> > >
> > > * Blockers *
> > >- MYRIAD-170 [1], reported last night.
> > >- MYRIAD-144 [2] (Not sure if this is a blocker, please read below)
> > >
> > > *Current Status*
> > > - MYRIAD-170: Swapnil is working on a fix.
> > > - MYRIAD-144: Podling Website is not up yet.
> > > - needs "svn authorization template" filled in by a Mentor
> > > - ** Ben/Danese/Luciano/Ted: We seek your help **
> > > - A running document of release guide is being prepared at [3]
> > > - My GPG  public key is available at [4] and [5]
> > > - A *test* RC candidate was prepared and uploaded to [6].
> > >   (*This is not the final RC*. I prepared it to get familiar with
> the
> > > process)
> > >
> > > * Discussion topics *
> > > - MYRIAD-144
> > >Not sure if this is a blocker. Should the "website" sources
> > > necessarily part of the release tarball?
> > >If not, then the SVN issues can be resolved independent of the
> > > voting process on a RC.
> > > - Does anyone have any other topics ?
> > >
> > > [1] https://issues.apache.org/jira/browse/MYRIAD-170
> > > [2] https://issues.apache.org/jira/browse/MYRIAD-144
> > > [3]
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61324959
> > > [4] http://people.apache.org/keys/committer/smarella.asc
> > > [5] https://dist.apache.org/repos/dist/dev/incubator/myriad/KEYS
> > > [6]
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.1.0-incubating-rc0/
> > >
> > > Thanks,
> > > Santosh
> > >
> >
>



-- 
Brandon

Re: New committer: Darin J

[Brandon Gulla]

woo! Well deserved!

On Thu, Nov 5, 2015 at 8:45 AM, Jim Scott  wrote:

> That is great news. Welcome Darin!
>
> On Thu, 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-
> >
>
>
>
> --
> *Jim Scott*
> Director, Enterprise Strategy & Architecture
> +1 (347) 746-9281
> @kingmesal 
>
> 
> [image: MapR Technologies] 
>
> Now Available - Free Hadoop On-Demand Training
> <
> http://www.mapr.com/training?utm_source=Email_medium=Signature_campaign=Free%20available
> >
>



-- 
Brandon

[jira] [Created] (MYRIAD-146) Add hadoop distribution override for RM Docker image

[Brandon Gulla (JIRA)]

Brandon Gulla created MYRIAD-146:


 Summary: Add hadoop distribution override for RM Docker image
 Key: MYRIAD-146
 URL: https://issues.apache.org/jira/browse/MYRIAD-146
 Project: Myriad
  Issue Type: Bug
Reporter: Brandon Gulla
Assignee: Brandon Gulla


An issue was brought up a few weeks ago on the call that there is a desire to 
make the Hadoop distribution targz configurable for the RM docker image. 

I'll knock this out and test against Apache Hadoop and MapR's distribution. 



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

Re: Jira issue

[Brandon Gulla]

Jim, I just tried to assign it to you but for some reason your name did not
autocomplete to allow me to assign.

!Adam, can you check the user settings for Mr. Jimbo?


On Fri, Oct 2, 2015 at 7:48 AM, Jim Klucar  wrote:

> Looks like I can't assign issues to myself in JIRA. Someone help?
>



-- 
Brandon

[jira] [Assigned] (MYRIAD-141) Include myriad framework name into task name

[Brandon Gulla (JIRA)]

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

Brandon Gulla reassigned MYRIAD-141:


Assignee: Brandon Gulla

> Include myriad framework name into task name
> 
>
> Key: MYRIAD-141
> URL: https://issues.apache.org/jira/browse/MYRIAD-141
> Project: Myriad
>  Issue Type: Improvement
>  Components: Scheduler
>Affects Versions: Myriad 0.1.0
>Reporter: Yuliya Feldman
>    Assignee: Brandon Gulla
>
> when people plan to run multiple myriad clusters under same Mesos it is very 
> hard to figure out which task belongs to which framework when getting list of 
> active tasks



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

Re: Myriad site demo

[Brandon Gulla]

I have yet to check out the desktop-version of the site, but it looks great
on my phone. Good theming!

On Mon, Sep 28, 2015 at 11:25 AM, Jim Klucar  wrote:

> Also, its a responsive design, so check it out on your phone. ;)
>
> On Mon, Sep 28, 2015 at 11:25 AM, Jim Klucar  wrote:
>
> > Hey everyone,
> >
> > Since I sent out the site mockups, Brandon put a bug in my ear about
> > Google material design. So that's what I've been mucking with.
> >
> > Because I did the site with Jekyll, github pages will host it, so I put
> up
> > a demo here:
> >
> > http://klucar.github.io/myriad-site/
> >
> > Not everything is there yet content-wise, some colors are odd, but the
> > layout and nav is there. I also went through the Apache site requirements
> > and I think it's compliant. Let me know what else you would like to see,
> if
> > you hate it, etc etc.
> >
> > Cheers
> > Jim
> >
>



-- 
Brandon

Re: Site Layout

[Brandon Gulla]

Hey Jim, thanks for putting these together. I am personally a fan of the
layout and style of Option 1.



On Thu, Sep 24, 2015 at 1:36 PM, Jim Klucar  wrote:

> Hi everyone,
>
> I started in on mocking up the site. I got tired of the bootstrap navbar on
> top approach so I came up with a few mock ups. Don't worry about the colors
> not being right or whatever details that are off.
>
> 1) http://imgur.com/Or5Fkbx
> 2) http://imgur.com/2ok8T98
> 3) http://imgur.com/al0gGht
>
> More importantly, I plan on implementing it using Jekyll (
> https://jekyllrb.com/) This is how github pages is done.
> https://pages.github.com/
>
> Basically Jekyll parses markdown files and injects them into HTML templates
> and generates a static site. The main advantage is it is really blog-aware
> so we can create new release notices, blog entries, etc by writing a
> standalone markdown file and recompiling the site. The other advantage is
> we can redesign the website later and all the content won't have to be
> ported. Jekyll will just inject the markdown content into the new site
> design.
>
> Let me know what you think. If there aren't any objections to Jekyll I can
> get started and we can quibble about design later.
>
> Jim
>



-- 
Brandon

Docker Hub Docker submission

[Brandon Gulla]

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: mesoDriver.stop()

[Brandon Gulla]

https://mail-archives.apache.org/mod_mbox/mesos-user/201503.mbox/%3c4c43b840-2108-49e4-95a8-f976ad375...@mesosphere.io%3E


may be related


On Thu, Apr 9, 2015 at 12:00 PM, Paul Read pdread...@gmail.com wrote:


 In testing the shutdown service I decided to go from manually stopping the
 tasks and executor to using the mesosDriver.stop() API which indicates it
 will do just that, stop the tasks and executor. And it does, however at
 that point forward you cannot restart the RM and have it communicate with
 mesos. This seems odd to me. If I restart mesos I can then start a RM and
 flex up/down tasks.

 The mesosDriver.abort() does not shutdown the tasks and/or executor.

 So is this a mesos bug or feature?

 Thanks.




-- 
Brandon