-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated installer #14
Comments
Feel free to check out progress in my fork at https://github.com/mglantz/helicalinsight |
I'd say I'm in alpha now atleast :-)
|
is that really need redhat network credentials ?
that seems not related. but I have no idea why that error happened ? I change "helical_hostname" and "install_dir" in vars.yml , that`s all I changed. OS: CentOS 7 |
OK , looks like the "install_dir" means where I put the files clone for git hub , not where I want to install helical insight . |
Hey @changchichung. Right now, I do not have support for CentOS. Check out the documentation at https://github.com/mglantz/helicalinsight/tree/master/ansible-installer. To get CentOS support, we'd have to detect OS and then instead of using subscription-manager, enable the correct repositories with yum-config. |
Correct, it's where we put the git repo and prep the install. You cannot select where to install it right now, it uses Tomcat and will install it in the default installation directory of Tomcat. |
The installer passed my tests on RHEL7. I ended up with a working installation. |
Hi all,
I noticed that there were a lot of issues in the installers instructions. For example, missing instructions regarding database user, database name, issues in the db.sql dump. Instead of correcting them, I thought I'd try to re-make the installation experience by automating it in Ansible for Linux at least.
At the end, I'll end up with a simple yaml file alá
setting: value-x
setting2: value-y
I'm pretty far gone atm and hope to be done in the coming week or sooner. Please note that this makes the installer omnipotent as well, meaning you can re-run it without problems. Also, this fixes that db.sql contains statement for setting the root user password and allows the user to encrypt database / hi-ce user passwords using an Ansible vault.
Anyways. This turns the complete installations into editing the yaml settings file and running three commands:
[root@ip-172-31-24-100 ansible-installer]# yum -y install python-pip && pip install ansible
[root@ip-172-31-24-100 ansible-installer]# vi vars/settings.yml
[root@ip-172-31-24-100 ansible-installer]# ansible-playbook -i hosts install_helical.yml
PLAY [localhost] *****************************************************************************************************************************************
TASK [Enable EPEL] ***************************************************************************************************************************************
ok: [localhost]
TASK [Register to RHN and auto-subscribe to available content.] ******************************************************************************************
ok: [localhost]
TASK [Enable RHSM repositories (extras, optional)] *******************************************************************************************************
ok: [localhost] => (item=rhel-7-server-extras-rpms)
ok: [localhost] => (item=rhel-7-server-optional-rpms)
TASK [Install prerequisites] *****************************************************************************************************************************
[WARNING]: Consider using the yum module rather than running 'yum'. If you need to use command because yum is insufficient you can add 'warn: false' to
this command task or set 'command_warnings=False' in ansible.cfg to get rid of this message.
changed: [localhost]
TASK [Enable MariaDB service] ****************************************************************************************************************************
ok: [localhost]
TASK [Create the Helical database user] ******************************************************************************************************************
ok: [localhost]
TASK [Import sample report to Helical database] **********************************************************************************************************
changed: [localhost]
TASK [Set hi-repository path] ****************************************************************************************************************************
ok: [localhost]
TASK [Set BaseURL to listen to] **************************************************************************************************************************
ok: [localhost]
TASK [Configure app with correct helical database user] **************************************************************************************************
ok: [localhost]
TASK [Configure app with correct helical database password] **********************************************************************************************
ok: [localhost]
TASK [Configure app with correct helical database source] ************************************************************************************************
ok: [localhost]
TASK [Deploy hi-ce war file] *****************************************************************************************************************************
changed: [localhost]
TASK [Restart tomcat] ************************************************************************************************************************************
changed: [localhost]
TASK [Print BaseURL] *************************************************************************************************************************************
ok: [localhost] => {
"msg": "Helical Insights will be reachable at: http://35.157.136.233:8080/hi-ce/hi.html"
}
PLAY RECAP ***********************************************************************************************************************************************
localhost : ok=15 changed=4 unreachable=0 failed=0
The text was updated successfully, but these errors were encountered: