Re: [Incubator Wiki] Update of "August2016" by Franck Cuny

2016-08-04 Thread Henry Saputra
+1

On Thu, Aug 4, 2016 at 8:31 AM, Marvin Humphrey 
wrote:

> On Wed, Aug 3, 2016 at 7:41 PM, John D. Ament 
> wrote:
> > Part of me wants to revert this, but there have been other modifications
> > since.  Is there any option here?
>
> I'll take care of it.
>
> There's no magic way to deal with a mess like this once history piles
> up after it -- you just revert to the clean revision, then apply the
> subsequent changesets. It's not conceptually difficult, it just
> requires high attention to detail.
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: ARIA TOSCA Project Proposal

2016-08-04 Thread dsh
Hi,

just a note on the ARAI acronym if used as such. That acronym usually
refers to: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA
aka https://www.w3.org/TR/wai-aria/ .

Cheers
Daniel

On Thu, Aug 4, 2016 at 4:47 PM, Arthur Berezin 
wrote:

> Hi All
>
>
> I would like to propose ARIA TOSCA to be an Apache Incubator Project.
>
> ARIA TOSCA project offers an easily consumable Software Development
> Kit(SDK) and a Command Line Interface(CLI) to implement TOSCA(Topology and
> Orchestration Specification of Cloud Applications) based solutions which
> will help in driving adoption of TOSCA, and help in market consolidation
> around TOSCA based Orchestration.
>
> One of the key attributes of the TOSCA specification by OASIS is that it is
> a vendor neutral and technology agnostic specification, allowing to
> describe applications and then to orchestrate them using various
> technologies of choice, such as Amazon AWS, Google GCP, OpenStack, VMware,
> Puppet, Ansible Chef, etc’. The reality is such that TOSCA is a complex
> specification,making software vendors trying to implement the specification
> make implementation decisions, ending up with different and incompatible
> implementations, creating even more market segmentation instead of
> consolidating around a single standard for orchestration.
>
> ARIA a vendor neutral and technology agnostic(via plugins mechanism)
> reference implementation of the TOSCA specification. It is an open source
> python library that helps orchestrators and management tools in developing
> TOSCA enabled solutions. ARIA aims to become the main reference
> implementation of the OASIS TOSCA(Topology and Orchestration Specification
> for Cloud Applications) specification for orchestrating cloud applications.
>
> ARIA TOSCA targets NFV Orchestration and Hybrid/Multi Cloud orchestration
> as main use-cases it solves.
>
> ARIA can be executed via CLI to orchestrate application templates,
> additionally it allows embedding its python library for creating TOSCA
> compatible services, and includes rich set of plugins for Iaas
> orchestration, such as Amazon AWS, Google GCP, OpenStack and VMWare; It
> Includes plugins for Container orchestration, with Docker and Kubernetes
> plugins, configuration management tools(Puppet,Chef, Ansible) and a rich
> API that allows to create plugins for any new technology.
>
> ARIA also serves as a codebase that allows to test the TOSCA specification,
> and experiment with new approaches of modeling and orchestration of
> applications, providing feedback and real world use cases OASIS to further
> refine and advance the standard specification.
>
> Please find the full project proposal here:
> https://wiki.apache.org/incubator/AriaProposal
>
> *Champion:*
> Suneel Marthi
>
> *Nominated Mentors*
> Jakob Homan
> John D. Ament
> Suneel Marthi
>
>
>
>
> Thank You,
> Arthur Berezin
>


Re: [Incubator Wiki] Update of "August2016" by Franck Cuny

2016-08-04 Thread Marvin Humphrey
On Wed, Aug 3, 2016 at 7:41 PM, John D. Ament  wrote:
> Part of me wants to revert this, but there have been other modifications
> since.  Is there any option here?

I'll take care of it.

There's no magic way to deal with a mess like this once history piles
up after it -- you just revert to the clean revision, then apply the
subsequent changesets. It's not conceptually difficult, it just
requires high attention to detail.

Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [Incubator Wiki] Update of "August2016" by Franck Cuny

2016-08-04 Thread Gour Saha
Clearly this edit messed up a whole bunc of other project¹s edits
including Slider.

-Gour

On 8/4/16, 7:36 AM, "Craig Russell"  wrote:

>Hi John,
>
>Seems to me this edit is wrong and should be reverted. Any one wiki edit
>done by a project should relate to one project. Global changes like this
>should be done only by someone with a higher calling.
>
>Craig
>
>> On Aug3, 2016, at 7:41 PM, John D. Ament  wrote:
>> 
>> Part of me wants to revert this, but there have been other modifications
>> since.  Is there any option here?
>> 
>> On Wed, Aug 3, 2016 at 8:01 PM Apache Wiki  wrote:
>> 
>>> Dear Wiki user,
>>> 
>>> You have subscribed to a wiki page or wiki category on "Incubator Wiki"
>>> for hange notification.
>>> 
>>> The "August2016" page has been changed by Franck Cuny:
>>> 
>>>https://wiki.apache.org/incubator/August2016?action=diff=44=45
>>> 
>>> Comment:
>>> Move the DLog section at the correct location
>>> 
>>> 
>>>  DistributedLog has been incubating since 2016-06-24.
>>> 
>>> - Thee most important issues to address in the move towards
>>>graduation:
>>> -
>>> -   1.
>>> -   2.
>>> -   3.
>>> -
>>> - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>> - aware of?
>>> -
>>> -
>>> -
>>> - How has the community developed since the last report?
>>> -
>>> -
>>> -
>>> - How has the project developed since the last report?
>>> -
>>> -
>>> -
>>> - Date of last release:
>>> -
>>> -   -XX-XX
>>> -
>>> - When were the last committers or PMC members elected?
>>> ->>> -
>>> -
>>> - Signed-off-by:
>>> -
>>> -   [ ](distributedlog) Flavio Junqueira
>>> -   [ ](distributedlog) Chris Nauroth
>>> -   [ ](distributedlog) Henry Saputra
>>> -
>>> - Shepherd/Mentor notes:
>>> -
>>>-
>>> -
>>> - 
>>> - Eagle
>>> -
>>> - Apache Eagle (incubating) is an open source analytics solution for
>>> identifying security and performance issues instantly on big data
>>> platforms, e.g. Apache Hadoop, Apache Spark etc. It analyzes data
>>> activities, Yarn application, Hadoop JMX metrics and daemon logs etc.,
>>> provides state-of-the-art alert engine to identify security breach,
>>> performance issues and shows insights.
>>> -
>>> - Eagle has been incubating since 2015-10-26.
>>> -
>>> - Three most important issues to address in the move towards
>>>graduation:
>>> -
>>> -   1. Eagle community is discussing graduation and use Apache maturity
>>> assessment to measure the gap to graduation. That should be completed,
>>> seehttps://
>>> 
>>>cwiki.apache.org/confluence/display/EAG/Eagle+Podling+Maturity+Assessmen
>>>t
>>> -
>>> -   2. Complete one requirement from self assessment whih is to
>>>provide a
>>> well-documented channel to report security issues, along with a
>>>documented
>>> way of responding to them.
>>> -
>>> -   3. Identify other housekeeping before graduation, for example
>>> agreement on bylaws, PMC composition etc.
>>> -
>>> - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>> - aware of?
>>> - NIL
>>> -
>>> -
>>> - How has the community developed since the last report?
>>> - . Presented in Apache Con, May 2016
>>> -
>>> - . Presented in London Stratus + Hadoop, May 2016
>>> -
>>> - . Presented in San Jose Hadoop Summit, June 2016
>>> -
>>> - . Presented in DTCC2016 Beijing, China, May 2016
>>> -
>>> - . Presented in JavaCon, China, May 2016
>>> -
>>> - . Presented in Hadoop Summit, San Jose, China, June 2016
>>> -
>>> - . Presented in Data Asset Management Summit, Shangha, China, July
>>>2016
>>> -
>>> - Communities showed continuous interest in Apache Eagle project. Some
>>> company tried to integrate Eagle as part of whole solution and some
>>> contributed different use case to Eagle platform, for example MapR
>>>support,
>>> Oozie monitoring support etc.
>>> -
>>> -
>>> - How has the project developed since the last report?
>>> - Technically we added more documents for user to easily use Eagle
>>> -
>>> - Besides Hadoop security monitoring, we have started working on
>>> performance monitoring desin and development based on the requests
>>>from
>>> community.
>>> -
>>> - As we may have multiple different use cases running on top of Eagle,
>>>a
>>> design discussion and prototype is conducted to mak sure Eagle is a
>>> framework to host multiple use cases and user will use Eagle to manage
>>> those use cases.
>>> -
>>> - Alert engine is going to be decoupled from data processing so that
>>>alert
>>> engine will be multi-tenant and easy to be used by multiple use cases
>>>by
>>> incorporating well-designed metadata.
>>> -
>>> -
>>> - Date of last release:
>>> -
>>> -   2016-07-19
>>> -
>>> - When were the last committers or PMC members elected?
>>> - Daniel Zhou,2016-06-15
>>> - Michael Wu, 2016-06-17
>>> -
>>> -
>>> - Signed-off-by:
>>> -
>>> -   [ ](eagle) Owen O'Malley
>>> -   [ ](eagle) Henry Saputra
>>> -   [ ](eagle) Julian Hyde
>>> -   [ ](eagle) P. Taylor Goetz
>>> - 

ARIA TOSCA Project Proposal

2016-08-04 Thread Arthur Berezin
Hi All


I would like to propose ARIA TOSCA to be an Apache Incubator Project.

ARIA TOSCA project offers an easily consumable Software Development
Kit(SDK) and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions which
will help in driving adoption of TOSCA, and help in market consolidation
around TOSCA based Orchestration.

One of the key attributes of the TOSCA specification by OASIS is that it is
a vendor neutral and technology agnostic specification, allowing to
describe applications and then to orchestrate them using various
technologies of choice, such as Amazon AWS, Google GCP, OpenStack, VMware,
Puppet, Ansible Chef, etc’. The reality is such that TOSCA is a complex
specification,making software vendors trying to implement the specification
make implementation decisions, ending up with different and incompatible
implementations, creating even more market segmentation instead of
consolidating around a single standard for orchestration.

ARIA a vendor neutral and technology agnostic(via plugins mechanism)
reference implementation of the TOSCA specification. It is an open source
python library that helps orchestrators and management tools in developing
TOSCA enabled solutions. ARIA aims to become the main reference
implementation of the OASIS TOSCA(Topology and Orchestration Specification
for Cloud Applications) specification for orchestrating cloud applications.

ARIA TOSCA targets NFV Orchestration and Hybrid/Multi Cloud orchestration
as main use-cases it solves.

ARIA can be executed via CLI to orchestrate application templates,
additionally it allows embedding its python library for creating TOSCA
compatible services, and includes rich set of plugins for Iaas
orchestration, such as Amazon AWS, Google GCP, OpenStack and VMWare; It
Includes plugins for Container orchestration, with Docker and Kubernetes
plugins, configuration management tools(Puppet,Chef, Ansible) and a rich
API that allows to create plugins for any new technology.

ARIA also serves as a codebase that allows to test the TOSCA specification,
and experiment with new approaches of modeling and orchestration of
applications, providing feedback and real world use cases OASIS to further
refine and advance the standard specification.

Please find the full project proposal here:
https://wiki.apache.org/incubator/AriaProposal

*Champion:*
Suneel Marthi

*Nominated Mentors*
Jakob Homan
John D. Ament
Suneel Marthi




Thank You,
Arthur Berezin


Re: [Incubator Wiki] Update of "August2016" by Franck Cuny

2016-08-04 Thread Craig Russell
Hi John,

Seems to me this edit is wrong and should be reverted. Any one wiki edit done 
by a project should relate to one project. Global changes like this should be 
done only by someone with a higher calling.

Craig

> On Aug 3, 2016, at 7:41 PM, John D. Ament  wrote:
> 
> Part of me wants to revert this, but there have been other modifications
> since.  Is there any option here?
> 
> On Wed, Aug 3, 2016 at 8:01 PM Apache Wiki  wrote:
> 
>> Dear Wiki user,
>> 
>> You have subscribed to a wiki page or wiki category on "Incubator Wiki"
>> for change notification.
>> 
>> The "August2016" page has been changed by Franck Cuny:
>> https://wiki.apache.org/incubator/August2016?action=diff=44=45
>> 
>> Comment:
>> Move the DLog section at the correct location
>> 
>> 
>>  DistributedLog has been incubating since 2016-06-24.
>> 
>> - Three most important issues to address in the move towards graduation:
>> -
>> -   1.
>> -   2.
>> -   3.
>> -
>> - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> - aware of?
>> -
>> -
>> -
>> - How has the community developed since the last report?
>> -
>> -
>> -
>> - How has the project developed since the last report?
>> -
>> -
>> -
>> - Date of last release:
>> -
>> -   -XX-XX
>> -
>> - When were the last committers or PMC members elected?
>> -
>> -
>> -
>> - Signed-off-by:
>> -
>> -   [ ](distributedlog) Flavio Junqueira
>> -   [ ](distributedlog) Chris Nauroth
>> -   [ ](distributedlog) Henry Saputra
>> -
>> - Shepherd/Mentor notes:
>> -
>> -
>> -
>> - 
>> - Eagle
>> -
>> - Apache Eagle (incubating) is an open source analytics solution for
>> identifying security and performance issues instantly on big data
>> platforms, e.g. Apache Hadoop, Apache Spark etc. It analyzes data
>> activities, Yarn application, Hadoop JMX metrics and daemon logs etc.,
>> provides state-of-the-art alert engine to identify security breach,
>> performance issues and shows insights.
>> -
>> - Eagle has been incubating since 2015-10-26.
>> -
>> - Three most important issues to address in the move towards graduation:
>> -
>> -   1. Eagle community is discussing graduation and use Apache maturity
>> assessment to measure the gap to graduation. That should be completed,
>> seehttps://
>> cwiki.apache.org/confluence/display/EAG/Eagle+Podling+Maturity+Assessment
>> -
>> -   2. Complete one requirement from self assessment which is to provide a
>> well-documented channel to report security issues, along with a documented
>> way of responding to them.
>> -
>> -   3. Identify other housekeeping before graduation, for example
>> agreement on bylaws, PMC composition etc.
>> -
>> - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> - aware of?
>> - NIL
>> -
>> -
>> - How has the community developed since the last report?
>> - . Presented in Apache Con, May 2016
>> -
>> - . Presented in London Stratus + Hadoop, May 2016
>> -
>> - . Presented in San Jose Hadoop Summit, June 2016
>> -
>> - . Presented in DTCC2016 Beijing, China, May 2016
>> -
>> - . Presented in JavaCon, China, May 2016
>> -
>> - . Presented in Hadoop Summit, San Jose, China, June 2016
>> -
>> - . Presented in Data Asset Management Summit, Shanghai, China, July 2016
>> -
>> - Communities showed continuous interest in Apache Eagle project. Some
>> company tried to integrate Eagle as part of whole solution and some
>> contributed different use case to Eagle platform, for example MapR support,
>> Oozie monitoring support etc.
>> -
>> -
>> - How has the project developed since the last report?
>> - Technically we added more documents for user to easily use Eagle
>> -
>> - Besides Hadoop security monitoring, we have started working on
>> performance monitoring design and development based on the requests from
>> community.
>> -
>> - As we may have multiple different use cases running on top of Eagle, a
>> design discussion and prototype is conducted to make sure Eagle is a
>> framework to host multiple use cases and user will use Eagle to manage
>> those use cases.
>> -
>> - Alert engine is going to be decoupled from data processing so that alert
>> engine will be multi-tenant and easy to be used by multiple use cases by
>> incorporating well-designed metadata.
>> -
>> -
>> - Date of last release:
>> -
>> -   2016-07-19
>> -
>> - When were the last committers or PMC members elected?
>> - Daniel Zhou, 2016-06-15
>> - Michael Wu, 2016-06-17
>> -
>> -
>> - Signed-off-by:
>> -
>> -   [ ](eagle) Owen O'Malley
>> -   [ ](eagle) Henry Saputra
>> -   [ ](eagle) Julian Hyde
>> -   [ ](eagle) P. Taylor Goetz
>> -   [ ](eagle) Amareshwari Sriramdasu
>> -
>> - Shepherd/Mentor notes:
>> -
>> -
>> -
>> - 
>> - Fineract
>> -
>> - Fineract is an open source system for core banking as a platform.
>> -
>> - Fineract has been incubating since 2015-12-15.
>> -
>> - Three most important issues to address in the move towards graduation:
>> -

Re: [Incubator Wiki] Update of "August2016" by Franck Cuny

2016-08-04 Thread Mark Struberg
It's probably just a preparation and meant as a start for other community 
members to continue.
Of course if it stays that way, then it's surely not a candidate to win the 
'board report of the month' award ;)

LieGrue,
strub





> On Thursday, 4 August 2016, 4:42, John D. Ament  wrote:
> > Part of me wants to revert this, but there have been other modifications
> since.  Is there any option here?
> 
> On Wed, Aug 3, 2016 at 8:01 PM Apache Wiki  wrote:
> 
>>  Dear Wiki user,
>> 
>>  You have subscribed to a wiki page or wiki category on "Incubator 
> Wiki"
>>  for change notification.
>> 
>>  The "August2016" page has been changed by Franck Cuny:
>> 
> https://wiki.apache.org/incubator/August2016?action=diff=44=45
>> 
>>  Comment:
>>  Move the DLog section at the correct location
>> 
>> 
>>DistributedLog has been incubating since 2016-06-24.
>> 
>>  - Three most important issues to address in the move towards graduation:
>>  -
>>  -   1.
>>  -   2.
>>  -   3.
>>  -
>>  - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>  - aware of?
>>  -
>>  -
>>  -
>>  - How has the community developed since the last report?
>>  -
>>  -
>>  -
>>  - How has the project developed since the last report?
>>  -
>>  -
>>  -
>>  - Date of last release:
>>  -
>>  -   -XX-XX
>>  -
>>  - When were the last committers or PMC members elected?
>>  -
>>  -
>>  -
>>  - Signed-off-by:
>>  -
>>  -   [ ](distributedlog) Flavio Junqueira
>>  -   [ ](distributedlog) Chris Nauroth
>>  -   [ ](distributedlog) Henry Saputra
>>  -
>>  - Shepherd/Mentor notes:
>>  -
>>  -
>>  -
>>  - 
>>  - Eagle
>>  -
>>  - Apache Eagle (incubating) is an open source analytics solution for
>>  identifying security and performance issues instantly on big data
>>  platforms, e.g. Apache Hadoop, Apache Spark etc. It analyzes data
>>  activities, Yarn application, Hadoop JMX metrics and daemon logs etc.,
>>  provides state-of-the-art alert engine to identify security breach,
>>  performance issues and shows insights.
>>  -
>>  - Eagle has been incubating since 2015-10-26.
>>  -
>>  - Three most important issues to address in the move towards graduation:
>>  -
>>  -   1. Eagle community is discussing graduation and use Apache maturity
>>  assessment to measure the gap to graduation. That should be completed,
>>  seehttps://
>>  cwiki.apache.org/confluence/display/EAG/Eagle+Podling+Maturity+Assessment
>>  -
>>  -   2. Complete one requirement from self assessment which is to provide a
>>  well-documented channel to report security issues, along with a documented
>>  way of responding to them.
>>  -
>>  -   3. Identify other housekeeping before graduation, for example
>>  agreement on bylaws, PMC composition etc.
>>  -
>>  - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>  - aware of?
>>  - NIL
>>  -
>>  -
>>  - How has the community developed since the last report?
>>  - . Presented in Apache Con, May 2016
>>  -
>>  - . Presented in London Stratus + Hadoop, May 2016
>>  -
>>  - . Presented in San Jose Hadoop Summit, June 2016
>>  -
>>  - . Presented in DTCC2016 Beijing, China, May 2016
>>  -
>>  - . Presented in JavaCon, China, May 2016
>>  -
>>  - . Presented in Hadoop Summit, San Jose, China, June 2016
>>  -
>>  - . Presented in Data Asset Management Summit, Shanghai, China, July 2016
>>  -
>>  - Communities showed continuous interest in Apache Eagle project. Some
>>  company tried to integrate Eagle as part of whole solution and some
>>  contributed different use case to Eagle platform, for example MapR support,
>>  Oozie monitoring support etc.
>>  -
>>  -
>>  - How has the project developed since the last report?
>>  - Technically we added more documents for user to easily use Eagle
>>  -
>>  - Besides Hadoop security monitoring, we have started working on
>>  performance monitoring design and development based on the requests from
>>  community.
>>  -
>>  - As we may have multiple different use cases running on top of Eagle, a
>>  design discussion and prototype is conducted to make sure Eagle is a
>>  framework to host multiple use cases and user will use Eagle to manage
>>  those use cases.
>>  -
>>  - Alert engine is going to be decoupled from data processing so that alert
>>  engine will be multi-tenant and easy to be used by multiple use cases by
>>  incorporating well-designed metadata.
>>  -
>>  -
>>  - Date of last release:
>>  -
>>  -   2016-07-19
>>  -
>>  - When were the last committers or PMC members elected?
>>  - Daniel Zhou, 2016-06-15
>>  - Michael Wu, 2016-06-17
>>  -
>>  -
>>  - Signed-off-by:
>>  -
>>  -   [ ](eagle) Owen O'Malley
>>  -   [ ](eagle) Henry Saputra
>>  -   [ ](eagle) Julian Hyde
>>  -   [ ](eagle) P. Taylor Goetz
>>  -   [ ](eagle) Amareshwari Sriramdasu
>>  -
>>  - Shepherd/Mentor notes:
>>  -
>>  -
>>  -
>>  - 
>>  - Fineract
>>  -
>>  - Fineract is an open source system for core