Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 8 May 2013 16:29:16 +0000 (UTC)
From: "Animesh Chaturvedi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12630643.1359986400549.288151.1368030556926@arcas>
In-Reply-To: <JIRA.12630643.1359986400549@arcas>
References: <JIRA.12630643.1359986400549@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-1147) cloud-setup-* should be removed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Animesh Chaturvedi updated CLOUDSTACK-1147:
-------------------------------------------

    Fix Version/s:     (was: 4.2.0)
                   Future
    
> cloud-setup-* should be removed
> -------------------------------
>
>                 Key: CLOUDSTACK-1147
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1147
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>    Affects Versions: 4.0.0
>            Reporter: Wido den Hollander
>             Fix For: Future
>
>
> The tools like cloud-setup-databases, cloud-setup-management and cloud-setup-agent seem to come from the vmops/cloud.com time where CloudStack used to be a black box appliance.
> Now more and more people start using CloudStack I'm seeing all kinds of criticism on these tools:
> - They change files without telling the admin
> - They punch wholes through firewalls
> Those are two things which make sysadmins cry, especially if they want to manage their systems with Puppet or Chef.
> The steps for setting up an Agent are actually not that big and most of them are actually already documented.
> When a host is added through the GUI we shouldn't run cloud-setup-agent, but we should just check if the host is ready to be added and bail out if not. (And tell why)
> The same goes for the management server and databases.
> The databases is just a matter of importing the correct SQL files into the databases and populating db.properties with the correct credentials.
> Setting up the management server is also just a matter of creating the correct configuration files, firewalling ports and setting sudo permissions.
> We should tell system administrators what it is that he/she has to configure, not just do things without telling.
> Documentation is key here I think.

--
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