[
https://issues.apache.org/jira/browse/AMBARI-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795230#comment-13795230
]
Tom Beerbower commented on AMBARI-3266:
---------------------------------------
[~mahadev],
So the LICENSE file can be removed because the one at the Ambari project root
applies?
Are you saying that the text of MSPL-LICENSE file should be included in the
NOTICE.txt file at the Ambari project root? Should the MSPL-LICENSE file stay
under contrib/ambari-scom/ or be removed also?
I thought that including the MSPL-LICENSE file in the project was sufficient.
If this is true, should we add it to NOTICE.txt? From the Apache legal
reference ...
{quote}
It is important to keep NOTICE as brief and simple as possible, as each
addition places a burden on downstream consumers. Do not add anything to NOTICE
which is not legally required.
{quote}
> Contribute Ambari-SCOM
> ----------------------
>
> Key: AMBARI-3266
> URL: https://issues.apache.org/jira/browse/AMBARI-3266
> Project: Ambari
> Issue Type: Task
> Components: Ambari-SCOM
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Attachments: AMBARI-3266-1.2.5.patch, AMBARI-3266.patch
>
>
> Purpose : Allow for the use of Apache Hadoop with Microsoft System Center
> Operations Manager and the Ambari SCOM Management Pack.
> The Ambari-SCOM contribution will provide for the following :
> # A method for collecting metrics is required in place of Ganglia for a
> Windows deployment of Hadoop. A custom Metrics2 sink is used to capture
> metrics to a SQLServer database.
> # Custom metrics provider for Ambari that will access the metrics stored in
> the SQLServer database.
> # Custom resource providers which will read the Hadoop cluster configuration
> from the artifacts of a Windows deployment of Hadoop.
> # The Ambari-SCOM management pack which provides for monitoring of Hadoop
> resources via the Ambari REST API.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
