Re: [DRAFT] Incubator PMC Board Report - November 2017

2017-11-08 Thread John D. Ament
Hi,

Still missing sign off from: Guacamole and Ratis.  Please get these in
ASAP, to avoid being marked monthly (especially concerning for Guacamole
who's possibly graduating this month).

The following reports have not been filed, at this point I am assuming they
will be missed and roll over: iota (likely to retire), Milagro, Myriad
(also likely to retire).

John

On Mon, Nov 6, 2017 at 2:46 PM John D. Ament  wrote:

> 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 

Re: [DISCUSS] Retire Myriad

2017-11-08 Thread mohit soni
Sure. I'll work on creating the podling report and submitting it.

On Tue, Nov 7, 2017 at 6:05 PM, John D. Ament  wrote:

> Ok.  I'm willing to wait.  However, you'll need to follow up quickly.
> I'll also point out that the podling report is due, none submitted.
> Hopefully one can be provided soon.
>
> John
>
> On 2017-11-07 12:57, mohit soni  wrote:
> > I think we should be able to address the concerns around PR reviews and
> > releases while still being a part of the Incubator.
> >
> > Also, I am fine with driving future features with help of Darin and
> others
> > in the community.
> >
> > Honestly, I would prefer to keep the project in the Incubator for all the
> > benefits it provides. At the very least, we can give it another shot.
> >
> > If we are all fine with keeping the project alive in the Incubator, we
> can
> > then move on to discuss future features and releases.
> >
> > Best
> > Mohit
> >
> > On Tue, Nov 7, 2017 at 7:04 AM, John D. Ament 
> wrote:
> >
> > > Just so you are aware, it is completely feasible to fork the project to
> > > continue work on it outside of Apache, if you decide on retirement.  We
> > > generally don't even pursue naming issues for former podlings, since we
> > > would have not done anything to claim the TM.
> > >
> > > Maybe it is possible to build up the project outside of apache with
> just a
> > > couple of committers and roll your own releases.  Build up a strong
> enough
> > > community and come back (if it makes sense).
> > >
> > > John
> > >
> > > On 2017-11-06 14:56, Santosh Marella  wrote:
> > > > 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 <
> dbjohnson1...@gmail.com>
> > > > 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 <
> mohitsoni1...@gmail.com>
> > > > > 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 

Re: [jira] [Commented] (MYRIAD-256) Cannot launch with vagrant

2017-11-08 Thread Darin Johnson
Appears to be a Java version error.  Will need to upgrade that I guess.

On Nov 7, 2017 3:19 AM, "Kwang-in (Dennis) JUNG (JIRA)" 
wrote:

>
> [ https://issues.apache.org/jira/browse/MYRIAD-256?page=
> com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel=16241658#comment-16241658 ]
>
> Kwang-in (Dennis) JUNG commented on MYRIAD-256:
> ---
>
> I just change hadoop version to 2.7.4, and it causes other error like
> below.
>
> ==
> default: Running: /var/folders/hk/1t3k4z1d6jn71tzy08znymjrgn
> /T/vagrant-shell20171107-19945-cz51p0.sh
> ==> default: stdin: is not a tty
> ==> default: #!/bin/bash -v
> ==> default: #
> ==> default: # Licensed to the Apache Software Foundation (ASF) under one
> ==> default: # or more contributor license agreements.  See the NOTICE file
> ==> default: # distributed with this work for additional information
> ==> default: # regarding copyright ownership.  The ASF licenses this file
> ==> default: # to you under the Apache License, Version 2.0 (the
> ==> default: # "License"); you may not use this file except in compliance
> ==> default: # with the License.  You may obtain a copy of the License at
> ==> default: #
> ==> default: # http://www.apache.org/licenses/LICENSE-2.0
> ==> default: #
> ==> default: # Unless required by applicable law or agreed to in writing,
> ==> default: # software distributed under the License is distributed on an
> ==> default: # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> ==> default: # KIND, either express or implied.  See the License for the
> ==> default: # specific language governing permissions and limitations
> ==> default: # under the License.
> ==> default: #
> ==> default: set -e
> ==> default:
> ==> default: # Format NameNode
> ==> default: sudo -u hduser sh -c 'yes Y | /usr/local/hadoop/bin/hdfs
> namenode -format'
> ==> default: 17/11/07 08:05:40 INFO namenode.NameNode: STARTUP_MSG:
> ==> default: /
> ==> default: STARTUP_MSG: Starting NameNode
> ==> default: STARTUP_MSG:   host = vagrant-ubuntu-trusty-64/10.0.2.15
> ==> default: STARTUP_MSG:   args = [-format]
> ==> default: STARTUP_MSG:   version = 2.7.4
> ==> default: STARTUP_MSG:   classpath = /usr/local/hadoop/etc/hadoop:/
> usr/local/hadoop/share/hadoop/common/lib/htrace-core-3.1.0-
> incubating.jar:/usr/local/hadoop/share/hadoop/common/
> lib/avro-1.7.4.jar:/usr/local/hadoop/share/hadoop/common/
> lib/commons-codec-1.4.jar:/usr/local/hadoop/share/hadoop/
> common/lib/jetty-6.1.26.jar:/usr/local/hadoop/share/hadoop/
> common/lib/jetty-util-6.1.26.jar:/usr/local/hadoop/share/
> hadoop/common/lib/jackson-jaxrs-1.9.13.jar:/usr/local/
> hadoop/share/hadoop/common/lib/jaxb-api-2.2.2.jar:/usr/
> local/hadoop/share/hadoop/common/lib/jetty-sslengine-6.
> 1.26.jar:/usr/local/hadoop/share/hadoop/common/lib/netty-
> 3.6.2.Final.jar:/usr/local/hadoop/share/hadoop/common/
> lib/hamcrest-core-1.3.jar:/usr/local/hadoop/share/hadoop/
> common/lib/jsp-api-2.1.jar:/usr/local/hadoop/share/hadoop/
> common/lib/curator-recipes-2.7.1.jar:/usr/local/hadoop/
> share/hadoop/common/lib/api-util-1.0.0-M20.jar:/usr/local/
> hadoop/share/hadoop/common/lib/commons-io-2.4.jar:/usr/
> local/hadoop/share/hadoop/common/lib/jets3t-0.9.0.jar:/
> usr/local/hadoop/share/hadoop/common/lib/commons-httpclient-
> 3.1.jar:/usr/local/hadoop/share/hadoop/common/lib/
> zookeeper-3.4.6.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-
> configuration-1.6.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-
> collections-3.2.2.jar:/usr/local/hadoop/share/hadoop/
> common/lib/servlet-api-2.5.jar:/usr/local/hadoop/share/
> hadoop/common/lib/apacheds-i18n-2.0.0-M15.jar:/usr/local/
> hadoop/share/hadoop/common/lib/paranamer-2.3.jar:/usr/
> local/hadoop/share/hadoop/common/lib/jackson-xc-1.9.13.
> jar:/usr/local/hadoop/share/hadoop/common/lib/hadoop-
> annotations-2.7.4.jar:/usr/local/hadoop/share/hadoop/
> common/lib/commons-beanutils-1.7.0.jar:/usr/local/hadoop/
> share/hadoop/common/lib/jersey-json-1.9.jar:/usr/
> local/hadoop/share/hadoop/common/lib/httpcore-4.2.5.jar:
> /usr/local/hadoop/share/hadoop/common/lib/commons-
> digester-1.8.jar:/usr/local/hadoop/share/hadoop/common/
> lib/jsch-0.1.54.jar:/usr/local/hadoop/share/hadoop/
> common/lib/commons-compress-1.4.1.jar:/usr/local/hadoop/
> share/hadoop/common/lib/mockito-all-1.8.5.jar:/usr/
> local/hadoop/share/hadoop/common/lib/commons-beanutils-
> core-1.8.0.jar:/usr/local/hadoop/share/hadoop/common/
> lib/jackson-mapper-asl-1.9.13.jar:/usr/local/hadoop/share/
> hadoop/common/lib/curator-framework-2.7.1.jar:/usr/
> local/hadoop/share/hadoop/common/lib/xmlenc-0.52.jar:/
> usr/local/hadoop/share/hadoop/common/lib/commons-lang-2.6.
> jar:/usr/local/hadoop/share/hadoop/common/lib/junit-4.11.
> jar:/usr/local/hadoop/share/hadoop/common/lib/gson-2.2.4.
>