Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E198AF49D for ; Thu, 28 Mar 2013 05:57:16 +0000 (UTC) Received: (qmail 5742 invoked by uid 500); 28 Mar 2013 05:57:16 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 5635 invoked by uid 500); 28 Mar 2013 05:57:16 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 5611 invoked by uid 99); 28 Mar 2013 05:57:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Mar 2013 05:57:15 +0000 Date: Thu, 28 Mar 2013 05:57:15 +0000 (UTC) From: "sandeepbaldawa (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-1738) Quick start guide MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 sandeepbaldawa created AMBARI-1738: -------------------------------------- Summary: Quick start guide Key: AMBARI-1738 URL: https://issues.apache.org/jira/browse/AMBARI-1738 Project: Ambari Issue Type: Bug Components: documentation Affects Versions: 1.2.2 Environment: Rhel 6.3 64 bit Reporter: sandeepbaldawa Priority: Critical Currently the documentation lacks a quick start guide i.e. the minimum number of steps required for a user to setup his ambari environment. It might be nice to have the same and move the optional/advance steps into a different section. This way as a newbie might be easy to quick start amabari instalaltion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira