[
https://issues.apache.org/jira/browse/CLOUDSTACK-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570411#comment-13570411
]
Marcus Sorensen commented on CLOUDSTACK-1147:
---------------------------------------------
I do like having the tools. I think they make cloudstack installs more
robust and repeatable. The setup instructions are already pretty involved,
adding another 15-20 steps/commands is going to create that many more
support questions. It seems easy for those of us already familiar, but if a
newbie misses or doesn't understand one thing they're totally lost.
I do like the idea of documenting what each script should do, so ad mins
can adjust their config management if they wish. If we remove the scripts,
we have to maintain the documentation anyway, which is really just the
scripts spelled out on an HTML page.
On Feb 4, 2013 10:06 AM, "Wido den Hollander (JIRA)" <j...@apache.org>
> 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: 4.2.0
>
>
> 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
