Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sat, 8 Aug 2015 15:15:45 +0000 (UTC)
From: "Sumit Mohanty (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12853118.1439046931000.13187.1439046945745@Atlassian.JIRA>
In-Reply-To: <JIRA.12853118.1439046931000@Atlassian.JIRA>
References: <JIRA.12853118.1439046931000@Atlassian.JIRA>
 <JIRA.12853118.1439046931511@arcas>
Subject: [jira] [Created] (AMBARI-12682) Ambari repo file (e.g. ambari.repo)
 should not be required
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sumit Mohanty created AMBARI-12682:
--------------------------------------

             Summary: Ambari repo file (e.g. ambari.repo) should not be required
                 Key: AMBARI-12682
                 URL: https://issues.apache.org/jira/browse/AMBARI-12682
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.2.0
            Reporter: Sumit Mohanty
            Assignee: Nahappan Somasundaram
            Priority: Critical
             Fix For: 2.2.0


While it is common to have the repo file be available and even required if Ambari is to be used to add new hosts, for hosted deployments (where users have pre-prepared VM/docker images) the repo file is not necessary. This is because the image usually has ambari components deployed. Add host translates to bringing up a docker/VM instance and starting an agent instance. 


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