[jira] [Created] (MYRIAD-256) Cannot launch with vagrant

[Kwang-in (Dennis) JUNG (JIRA)]

Kwang-in (Dennis) JUNG created MYRIAD-256:
-

 Summary: Cannot launch with vagrant
 Key: MYRIAD-256
 URL: https://issues.apache.org/jira/browse/MYRIAD-256
 Project: Myriad
  Issue Type: Bug
Reporter: Kwang-in (Dennis) JUNG
Priority: Critical


Hello.
I cannot launch project via vagrant file.

```
$ vagrant up
...
==> default: sudo -u hduser sh -c 'cat /home/hduser/.ssh/id_rsa.pub >> 
/home/hduser/.ssh/authorized_keys'
==> default: #sudo -u hduser sh -c "ssh-keyscan -H $1 >> 
/home/hduser/.ssh/known_hosts"
==> default: sudo -u hduser sh -c "ssh-keyscan -H localhost >> 
/home/hduser/.ssh/known_hosts"
==> default: # localhost SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
==> default: # localhost SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
==> default: #sudo -u hduser sh -c "ssh-keyscan -H $2 >> 
/home/hduser/.ssh/known_hosts"
==> default: # Download Hadoop
==> default: HADOOP_VER="$1"
==> default: cd ~
==> default: if [ ! -f /tmp/hadoop-${HADOOP_VER}.tar.gz ]; then
==> default:wget 
http://apache.osuosl.org/hadoop/common/hadoop-${HADOOP_VER}/hadoop-${HADOOP_VER}.tar.gz
 -O /tmp/hadoop-${HADOOP_VER}.tar.gz
==> default: fi
==> default: --2017-11-07 07:24:00--  
http://apache.osuosl.org/hadoop/common/hadoop-2.7.0/hadoop-2.7.0.tar.gz
==> default: Resolving apache.osuosl.org (apache.osuosl.org)... 
==> default: 64.50.233.100
==> default: , 
==> default: 140.211.166.134
==> default: , 
==> default: 64.50.236.52
==> default: Connecting to apache.osuosl.org 
(apache.osuosl.org)|64.50.233.100|:80... 
==> default: connected.
==> default: HTTP request sent, awaiting response... 
==> default: 404 Not Found
==> default: 2017-11-07 07:24:01 ERROR 404: Not Found.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
```
It seems version 2.7.0 are not exists in 
'http://apache.osuosl.org/hadoop/common/'. There are 2.7.4, 2.8.0, etc. but no 
2.7.0.
How about changing hadoop version?

Thanks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [DISCUSS] Retire Myriad

[Santosh Marella]

Agree with Darin and Mohit. I think the project is still very relevant, but
there is no one actively working on it - I myself couldn't put time on it
as the problem space my employer operates in is very different from
Myriad's. If Mohit is willing to drive the future features and Darin is
ready to back him up, I honestly think this deserves another shot. We have
already seen other folks expressing interest to offer support (in terms of
code reviews, vetting releases etc).

Thanks,
Santosh.

On Mon, Nov 6, 2017 at 11:45 AM, Darin Johnson 
wrote:

> I certainly think the project is relevant but I'm concerned if it belongs
> in Apache.  When I was active it was difficult to get people to review pull
> requests and when releasing v0.2.0 it was hard to even get people to vote
> for a release.  If only a few people are going to work on it, maybe it's
> easier to develop outside the incubator until there's something stable?
>
> I'd be interested in potentially working on it again provided there's at
> least two other people actively working on it.
>
> Darin
>
> On Mon, Nov 6, 2017 at 1:13 PM, mohit soni 
> wrote:
>
> > The project's core idea of dynamic creation and management of YARN
> clusters
> > without creating static partitions is still relevant. This project and
> it's
> > community were one of the first movers in the still developing space of
> > stateful containerized distributed systems.
> >
> > I believe the project is currently lagging behind the fast paced
> > development of Apache Mesos ecosystem project and is currently not
> designed
> > to take advantage of the fast growing Kubernetes (Apache License 2.0)
> > ecosystem.
> >
> > I also believe the project is not just about the code which gets old once
> > it's written, unless tendered and cared for regularly, it's also about
> the
> > community, and the mindshare.
> >
> > Here are the things that we can do to bring life to the project again:
> > 1. Refactor the project codebase to take advantage of the advances in the
> > Apache Mesos Ecosystem, which from my direct experience, will simplify
> the
> > project codebase a lot, making it easier once again to maintain it, while
> > making it more relevant to the Apache Mesos community again.
> > 2. Extend the project to take advantage of Kubernetes project's and
> enable
> > dynamic creation and management of YARN clusters on Kubernetes.
> Kubernetes
> > project now has great support for building stateful containerized
> > applications. Refactoring work in Step #1 will lay the groundwork that
> will
> > make it easier to extend the project for the Kubernetes ecosystem.
> >
> > I'm happy to take a lead to drive both above initiatives, and can post a
> > detailed plan and design for accomplishing above in coming months. I am
> > also happy to take a lead on submitting monthly incubator reports.
> >
> > I truly believe that we should give the project one more chance to
> > recuperate and thrive.
> >
> > Best
> > Mohit
> >
> >
> > On Mon, Nov 6, 2017 at 5:06 AM, John D. Ament 
> > wrote:
> >
> > > Just to be clear, this is a discussion thread.  Not a vote thread.
> While
> > > I believe many people vote +1 because they feel its clear why, when you
> > > vote against the idea you should explain why.
> > >
> > > So please, treat this more like a discussion rather than a vote and
> > > explain why.
> > >
> > > On 2017-11-05 13:50, mohit soni  wrote:
> > > > -1 vote to not retire the project (committer, PMC)
> > > >
> > > > I believe the project is still relevant.
> > > >
> > > > On Sun, Nov 5, 2017 at 8:48 AM, Niels Basjes 
> wrote:
> > > >
> > > > > +1 vote to retire (non-committer)
> > > > >
> > > > > On Sun, Nov 5, 2017 at 3:16 PM, Brandon Gulla <
> > gulla.bran...@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > +1 vote to retire (non-committer)
> > > > > >
> > > > > > On Sun, Nov 5, 2017 at 9:03 AM, John D. Ament <
> > johndam...@apache.org
> > > >
> > > > > > 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
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards / Met vriendelijke groeten,
> > > > >
> > > > > Niels Basjes
> > > > >
> > > >
> > >
> >
>

[DRAFT] Incubator PMC Board Report - November 2017

[John D. Ament]

All,

Below is the current draft.  We have 7 podling reports missing/not signed
off.  Hopefully they can come soon.

Incubator PMC report for November 2017

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

October was a quieter month in the incubator.  We executed 4 podling
releases, had no changes in staff.  One new podling joined, and are having
graduation discussions for two podlings.  We expect Mnemonic to fully
graduate this month.

* Community

  New IPMC members:

  - None

  People who left the IPMC:

  - None

* New Podlings

  - SDAP

* Podlings that failed to report, expected next month



* Graduations

  The board has motions for the following:

  - Guacamole?
  - Impala?
  - Mnemonic
  - Your podling here?
  - Your podling here?

* Releases

  The following releases entered distribution during the month of
  October:

  - 2017-10-04 Apache Juneau 6.4.0
  - 2017-10-11 Apache Rya 3.2.11
  - 2017-10-13 Apache Pulsar 1.20.0
  - 2017-10-30 Apache MXNet 0.12.0

* IP Clearance



* Legal / Trademarks



* Infrastructure



* Miscellaneous



* Credits

--
   Table of Contents
Amaterasu
Daffodil
Edgent
Guacamole
Heron
Impala
iota
Joshua
Milagro
Myriad
PageSpeed
Ratis
S2Graph
Slider
Tamaya
Toree
Unomi

--


Amaterasu

Apache Amaterasu is a framework providing continuous deployment for Big
Data Pipelines.

It provides the following capabilities:

Continuous integration tools to package pipelines and run tests.
A repository to store those packaged applications: the applications
repository.
A repository to store the pipelines, and engine configuration (for
instance, the location of the Spark master, etc.): per environment - the
configuration repository.
A dashboard to monitor the pipelines.
A DSL and integration hooks allowing third parties to easily integrate.

Amaterasu has been incubating since 2017-09.

Three most important issues to address in the move towards graduation:

  1. Prepare the first release
  2. Grow up user and contributor communities
  3. Prepare documentation

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  * Talks have been given in different events to promote and give
visibility to Amaterasu

How has the project developed since the last report?

  * Code based was moved to the ASFs git box
  * One new pull request was issued

Date of last release:

  N/A

When were the last committers or PMC members elected?

  N/A


  [X] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  N/A

Signed-off-by:

  [X](amaterasu) Jean-Baptiste Onofré
 Comments:
  [ ](amaterasu) Olivier Lamy
 Comments:
  [X](amaterasu) Davor Bonaci
 Comments: Initial setup continues: codebase has moved to the ASF
repository.

IPMC/Shepherd notes:




Daffodil

Apache Daffodil is an implementation of the Data Format Description Language
(DFDL) used to convert between fixed format data and XML/JSON.

Daffodil has been incubating since 2017-08-27.

Three most important issues to address in the move towards graduation:

  1. Obtaining SGAs
  2. Establishing new apache-centric infrastructure
  3. Broadening base of contributors

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

- Only that chasing the SGAs down is going to take some time, though
this may be typical.

How has the community developed since the last report?

- Users: No change.

- Developers/Contributors: No change.

How has the project developed since the last report?

- Completed setup of the git repo.
- Started process of transfer of existing JIRA
tickets to Apache.
- Established our contributor/branch workflow and
published to wiki.
- Submitted Tresys SGA.
- Progress is being made on obtaining organizational
SGAs from NCSA and IBM.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [X] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?

- No changes yet - same as at our project incubator
inception

Signed-off-by:

  [X](daffodil) John D. Ament
 Comments:
  [X](daffodil) David Fisher
 Comments:

IPMC/Shepherd notes:




Edgent

Apache Edgent is a programming SDK and micro-kernel style runtime
that can be embedded in gateways and small footprint edge devices enabling
local, real-time, analytics on the continuous streams of data coming
from equipment, vehicles, systems, appliances, devices and sensors of
all kinds (for example, Raspberry 

Re: [DISCUSS] Retire Myriad

[Darin Johnson]

I certainly think the project is relevant but I'm concerned if it belongs
in Apache.  When I was active it was difficult to get people to review pull
requests and when releasing v0.2.0 it was hard to even get people to vote
for a release.  If only a few people are going to work on it, maybe it's
easier to develop outside the incubator until there's something stable?

I'd be interested in potentially working on it again provided there's at
least two other people actively working on it.

Darin

On Mon, Nov 6, 2017 at 1:13 PM, mohit soni  wrote:

> The project's core idea of dynamic creation and management of YARN clusters
> without creating static partitions is still relevant. This project and it's
> community were one of the first movers in the still developing space of
> stateful containerized distributed systems.
>
> I believe the project is currently lagging behind the fast paced
> development of Apache Mesos ecosystem project and is currently not designed
> to take advantage of the fast growing Kubernetes (Apache License 2.0)
> ecosystem.
>
> I also believe the project is not just about the code which gets old once
> it's written, unless tendered and cared for regularly, it's also about the
> community, and the mindshare.
>
> Here are the things that we can do to bring life to the project again:
> 1. Refactor the project codebase to take advantage of the advances in the
> Apache Mesos Ecosystem, which from my direct experience, will simplify the
> project codebase a lot, making it easier once again to maintain it, while
> making it more relevant to the Apache Mesos community again.
> 2. Extend the project to take advantage of Kubernetes project's and enable
> dynamic creation and management of YARN clusters on Kubernetes. Kubernetes
> project now has great support for building stateful containerized
> applications. Refactoring work in Step #1 will lay the groundwork that will
> make it easier to extend the project for the Kubernetes ecosystem.
>
> I'm happy to take a lead to drive both above initiatives, and can post a
> detailed plan and design for accomplishing above in coming months. I am
> also happy to take a lead on submitting monthly incubator reports.
>
> I truly believe that we should give the project one more chance to
> recuperate and thrive.
>
> Best
> Mohit
>
>
> On Mon, Nov 6, 2017 at 5:06 AM, John D. Ament 
> wrote:
>
> > Just to be clear, this is a discussion thread.  Not a vote thread.  While
> > I believe many people vote +1 because they feel its clear why, when you
> > vote against the idea you should explain why.
> >
> > So please, treat this more like a discussion rather than a vote and
> > explain why.
> >
> > On 2017-11-05 13:50, mohit soni  wrote:
> > > -1 vote to not retire the project (committer, PMC)
> > >
> > > I believe the project is still relevant.
> > >
> > > On Sun, Nov 5, 2017 at 8:48 AM, Niels Basjes  wrote:
> > >
> > > > +1 vote to retire (non-committer)
> > > >
> > > > On Sun, Nov 5, 2017 at 3:16 PM, Brandon Gulla <
> gulla.bran...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > +1 vote to retire (non-committer)
> > > > >
> > > > > On Sun, Nov 5, 2017 at 9:03 AM, John D. Ament <
> johndam...@apache.org
> > >
> > > > > 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
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards / Met vriendelijke groeten,
> > > >
> > > > Niels Basjes
> > > >
> > >
> >
>

Re: [DISCUSS] Retire Myriad

[mohit soni]

The project's core idea of dynamic creation and management of YARN clusters
without creating static partitions is still relevant. This project and it's
community were one of the first movers in the still developing space of
stateful containerized distributed systems.

I believe the project is currently lagging behind the fast paced
development of Apache Mesos ecosystem project and is currently not designed
to take advantage of the fast growing Kubernetes (Apache License 2.0)
ecosystem.

I also believe the project is not just about the code which gets old once
it's written, unless tendered and cared for regularly, it's also about the
community, and the mindshare.

Here are the things that we can do to bring life to the project again:
1. Refactor the project codebase to take advantage of the advances in the
Apache Mesos Ecosystem, which from my direct experience, will simplify the
project codebase a lot, making it easier once again to maintain it, while
making it more relevant to the Apache Mesos community again.
2. Extend the project to take advantage of Kubernetes project's and enable
dynamic creation and management of YARN clusters on Kubernetes. Kubernetes
project now has great support for building stateful containerized
applications. Refactoring work in Step #1 will lay the groundwork that will
make it easier to extend the project for the Kubernetes ecosystem.

I'm happy to take a lead to drive both above initiatives, and can post a
detailed plan and design for accomplishing above in coming months. I am
also happy to take a lead on submitting monthly incubator reports.

I truly believe that we should give the project one more chance to
recuperate and thrive.

Best
Mohit


On Mon, Nov 6, 2017 at 5:06 AM, John D. Ament  wrote:

> Just to be clear, this is a discussion thread.  Not a vote thread.  While
> I believe many people vote +1 because they feel its clear why, when you
> vote against the idea you should explain why.
>
> So please, treat this more like a discussion rather than a vote and
> explain why.
>
> On 2017-11-05 13:50, mohit soni  wrote:
> > -1 vote to not retire the project (committer, PMC)
> >
> > I believe the project is still relevant.
> >
> > On Sun, Nov 5, 2017 at 8:48 AM, Niels Basjes  wrote:
> >
> > > +1 vote to retire (non-committer)
> > >
> > > On Sun, Nov 5, 2017 at 3:16 PM, Brandon Gulla  >
> > > wrote:
> > >
> > > > +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
> > > >
> > >
> > >
> > >
> > > --
> > > Best regards / Met vriendelijke groeten,
> > >
> > > Niels Basjes
> > >
> >
>

Re: [DISCUSS] Retire Myriad

[John D. Ament]

Just to be clear, this is a discussion thread.  Not a vote thread.  While I 
believe many people vote +1 because they feel its clear why, when you vote 
against the idea you should explain why.

So please, treat this more like a discussion rather than a vote and explain why.

On 2017-11-05 13:50, mohit soni  wrote: 
> -1 vote to not retire the project (committer, PMC)
> 
> I believe the project is still relevant.
> 
> On Sun, Nov 5, 2017 at 8:48 AM, Niels Basjes  wrote:
> 
> > +1 vote to retire (non-committer)
> >
> > On Sun, Nov 5, 2017 at 3:16 PM, Brandon Gulla 
> > wrote:
> >
> > > +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
> > >
> >
> >
> >
> > --
> > Best regards / Met vriendelijke groeten,
> >
> > Niels Basjes
> >
> 

Re: [DISCUSS] Retire Myriad

[Niels Basjes]

I believe this project is a cool idea yet no one seems interested enough to
invest in it (myself included).

I checked and at this moment
- The last commit I could find is dated Oct 7, 2016 (read: 13 months
without ANY commits)
- In 2017: The mailing list (ignoring "Jira" emails and email sent to all
project like "Podling report") is so empty that I only see messages
discussing the lack of interest.
- In 2017: Only a hand full of Jira issues were touched and none led to any
pull request or commit.

If a project has relevance to anyone then I expect to see different things
than what I found.

Niels Basjes

On Sun, Nov 5, 2017 at 7:50 PM, mohit soni  wrote:

> -1 vote to not retire the project (committer, PMC)
>
> I believe the project is still relevant.
>
> On Sun, Nov 5, 2017 at 8:48 AM, Niels Basjes  wrote:
>
> > +1 vote to retire (non-committer)
> >
> > On Sun, Nov 5, 2017 at 3:16 PM, Brandon Gulla 
> > wrote:
> >
> > > +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
> > >
> >
> >
> >
> > --
> > Best regards / Met vriendelijke groeten,
> >
> > Niels Basjes
> >
>



-- 
Best regards / Met vriendelijke groeten,

Niels Basjes

Re: [DISCUSS] Retire Myriad

[Andre]

+1 to retire (non-committer)

On Mon, Nov 6, 2017 at 3:48 AM, Niels Basjes  wrote:

> +1 vote to retire (non-committer)
>
> On Sun, Nov 5, 2017 at 3:16 PM, Brandon Gulla 
> wrote:
>
> > +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
> >
>
>
>
> --
> Best regards / Met vriendelijke groeten,
>
> Niels Basjes
>