Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 26 Sep 2014 17:14:34 +0000 (UTC)
From: "Jayush Luniya (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12744175.1411690419000.132560.1411751674979@Atlassian.JIRA>
In-Reply-To: <JIRA.12744175.1411690419000@Atlassian.JIRA>
References: <JIRA.12744175.1411690419000@Atlassian.JIRA>
 <JIRA.12744175.1411690419893@arcas>
Subject: [jira] [Commented] (AMBARI-7504) Ambari support for Windows
 platform
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/AMBARI-7504?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D141=
49658#comment-14149658 ]=20

Jayush Luniya commented on AMBARI-7504:
---------------------------------------

[Robert Levas]
Thanks for your feedback and for the pointer. I agree with you, we need to =
update AMBARI-7204 to handle Windows scenarios. FYI, we are working on flus=
hing out security scenarios on Windows and will be tackling them in Phase 2=
. Will update the Epic once we have details flushed out on the security sce=
narios.=20

> Ambari support for Windows platform
> -----------------------------------
>
>                 Key: AMBARI-7504
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7504
>             Project: Ambari
>          Issue Type: Epic
>          Components: ambari-agent, ambari-server, ambari-web
>    Affects Versions: 1.7.0
>         Environment: Windows
>            Reporter: Jayush Luniya
>            Assignee: Jayush Luniya
>             Fix For: 2.0.0
>
>
> The purpose of this umbrella JIRA is to enable Ambari on Windows support =
so as to enable provisioning/managing and monitoring of Hadoop clusters on =
Windows. The work will be divided into two phases as outlined below.=20
> *Software Requirements*=20
> - Windows Server 2008, Windows Server 2012, Windows Server 2012 R2
> - Python x64 (2.6 or later)
> - Python pywin32  Extensions
> - Python WMI module
> - Microsoft Visual C++ 2010 Redistributable Package (64-bit)
> - Microsoft .NET Framework 4.0
> - Java JDK 7, OpenJDK7
> - Visual Studio 2008 x64 redistributable package=20
> - OpenSSL
> - JDBC Driver for MS SQL Server
> - MS SQL Server
> *Setup*
> - Enable Ambari-Server and Ambari-Agent, Ambari-Web support on Windows
> - Ambari Server and Ambari Agent will be packaged as MSIs.
> - Ambari Server Setup
>     Phase 1: Focus on setup + start. No advanced configurations.
>     Phase 2: Advanced configuration options (LDAP/AD auth, HTTPS, encrypt=
ion).=20
> - Bootstrapping Agents
>     Phase 1: In Linux,  agent is pushed by the server to all the hosts us=
ing SSH. In phase 1, we will not support automatic bootstrapping of agents =
and will require manual installation of ambari agents on all hosts.=20
>     Phase 2: To enable automatic bootstrapping of agents, we will leverag=
e powershell remoting.
> *Database*
> - Ambari Server DB --- Use existing SQL Server=20
> - Hive, Oozie --- Use existing SQL Server
> - MetricsSink (Phase 1) --- Use existing SQL Server
> *Provisioning*
> - Ambari should support deploying Hadoop cluster on Windows through Ambar=
i REST API as well as Ambari Web portal.
> - Ambari should automatically install Windows Hadoop MSI on all hosts.=20
> *Managing*=20
> - Ambari should support managing and monitoring hosts, services and host =
components.=20
>       - Add/Delete services
>       - Add/Delete hosts
>       - Run service checks
>       - Start/Stop/Restart/Rolling Restart services and service component=
s on a host.
>       - Enable/disable Maintenance mode.
>       - Configs and Config Groups
> *Metrics*
> - Phase 1: Reuse Metrics Sink package from Ambari SCOM project. In phase =
1, we will only report service-level metrics. https://cwiki.apache.org/conf=
luence/display/AMBARI/2.+Installation
> - Phase 2: Integrate new metrics service proposed in AMBARI-5707. In phas=
e 2, we will enable both service-level and host-level metrics.=20
> *Alerts*=20
> - Phase 1: In phase 1, we won=E2=80=99t add support for alerts.=20
> - Phase 2: Integrate new alerting service proposed in AMBARI-6354


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