Commit f6e6e94c authored by Walter Heck's avatar Walter Heck

Merge branch '2.0.0' into 'master'

2.0.0

See merge request !2
parents ba1b63c1 1f0c7962
......@@ -2,34 +2,34 @@
For this release OpsTheater components will need to be upgraded manually. In the future we aim to automate as much of this as possible, all help is welcome!
* Gitlab will be upgraded from version 8.6 to 8.7
* Mattermost will be upgraded from version 2.1 to 2.2
* Percona server stays at 5.6.29
* Logstash stays at 2.1.1
* Kibana stays at 4.2.1
* Puppet from 4.4.0 to 4.4.2
* Foreman from 1.10.2 to 1.10.3
* Icinga 2 from 2.4.4 to 2.4.7
* Icinga web 2 from 2.2.0 to 2.2.3
* Filebeat from 1.2.0 to 1.2.2
* grafana stays at 2.5.0
Please see the release notes for a list of versions: https://gitlab.olindata.com/opstheater/opstheater/blob/1360740fc3baaad4fdcb719b8572ac58d0015845/RELEASENOTES.md
* Gitlab will be upgraded from version 8.6 to 8.7
* Mattermost will be upgraded from version 2.1 to 2.2
* Percona server stays at 5.6.29
* Logstash stays at 2.1.1
* Kibana stays at 4.2.1
* Puppet from 4.4.0 to 4.4.2
* Foreman from 1.10.2 to 1.10.3
* Icinga 2 from 2.4.4 to 2.4.7
* Icinga web 2 from 2.2.0 to 2.2.3
* Filebeat from 1.2.0 to 1.2.2
* grafana stays at 2.5.0
Please see the release notes for a list of versions: <https://gitlab.olindata.com/opstheater/opstheater/blob/1360740fc3baaad4fdcb719b8572ac58d0015845/RELEASENOTES.md>
## Steps
1. Disable puppet on all OpsTheater nodes
1. Disable puppet on all OpsTheater nodes
---
Login to the following servers one by one and disable puppet agent by command `puppet agent --disable`
* puppet.example.com
* icinga.example.com
* mysql.example.com
* gitlab.example.com
* elastic.example.com
* puppet.example.com
* icinga.example.com
* mysql.example.com
* gitlab.example.com
* elastic.example.com
2. Upgrade MySQL
2. Upgrade MySQL
---
No MySQL upgrade is needed this time, so we just need to upgrade the icinga, puppet and filebeat packages.
......@@ -51,7 +51,7 @@ icinga2-common-2.4.4-1.el7.centos.x86_64
puppet-agent-1.4.1-1.el7.x86_64
```
3. Upgrading elasticsearch
3. Upgrading elasticsearch
---
To upgrade Elasticsearch from 2.2 to 2.3 login to elasticsearch server and run the following commands:
......@@ -85,7 +85,7 @@ icinga2-common-2.4.4-1.el6.x86_64
puppet-agent-1.4.1-1.el6.x86_64
```
4. Upgrading icinga 2
4. Upgrading icinga 2
---
To upgrade Icinga 2 from 2.4.3 to 2.4.4 and Icinga web 2 from 2.1.2 to 2.2.0 login to the elastic server and run the following commands:
......@@ -132,10 +132,10 @@ icingaweb2-vendor-Parsedown-1.0.0-1.el7.centos.noarch
puppet-agent-1.4.1-1.el7.x86_64
```
5. Upgrading gitlab
5. Upgrading gitlab
---
Login on gitlab.example.com server do the following :
Login on gitlab.example.com server do the following :
```bash
[root@gitlab ~]# rpm -qa | egrep -i 'icinga2|puppet-agent|filebeat|gitlab' | sort
......@@ -168,10 +168,10 @@ icinga2-common-2.4.4-1.el7.centos.x86_64
puppet-agent-1.4.1-1.el7.x86_64
```
6. Upgrading puppetserver
6. Upgrading puppetserver
---
Login on puppet.example.com server do the following :
Login on puppet.example.com server do the following :
```bash
[root@puppet ~]# rpm -qa | egrep -i 'icinga2|puppet|filebeat' | sort
......@@ -209,25 +209,25 @@ puppetlabs-release-pc1-1.0.0-1.el7.noarch
puppetserver-2.3.1-1.el7.noarch
```
7. Deploy the puppetcode for OpsTheater 1.5.0 to your puppetmaster
7. Deploy the puppetcode for OpsTheater 1.5.0 to your puppetmaster
---
* on your development environment make sure you have the latest production branch of your puppet repository checked out
* merge the upstream opstheater 1.5 repo into the local repository
* merge conflicts and commit and push to your internal gitlab instance
* Login to Puppet Master server (puppet.example.com) and run r10k to deploy the latest puppet code on puppet master.
`r10k deploy environment production -pv`
* on your development environment make sure you have the latest production branch of your puppet repository checked out
* merge the upstream opstheater 1.5 repo into the local repository
* merge conflicts and commit and push to your internal gitlab instance
* Login to Puppet Master server (puppet.example.com) and run r10k to deploy the latest puppet code on puppet master.
`r10k deploy environment production -pv`
8. Enable puppet for OpsTheater machines
8. Enable puppet for OpsTheater machines
---
Login to following servers one by one and test new puppet code
* puppet.example.com
* icinga.example.com
* mysql.example.com
* gitlab.example.com
* elastic.example.com
* puppet.example.com
* icinga.example.com
* mysql.example.com
* gitlab.example.com
* elastic.example.com
```bash
puppet agent --enable; puppet agent -t --noop; puppet agent --disable
......@@ -239,7 +239,7 @@ If the puppet agent runs in noop mode are succesful you can enable the agents an
puppet agent --enable; puppet agent -t
```
9. Test all the systems manually
9. Test all the systems manually
---
Perform the steps given in release checklist to make sure everything is working fine (https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/1.5/releasechecklist.md)
Perform the steps given in release checklist to make sure everything is working fine (<https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/1.5/releasechecklist.md>)
# Prerequisites
* Make sure you have read <https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/1.7/deployment/scenario.md>
* Make sure you have read <https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/2.0/deployment/scenario.md>
* Make sure you have installed the following on your host machine:
* virtualbox (<http://virtualbox.org>)
......@@ -26,54 +26,54 @@
* Clone the opstheater repository on your host machine:
```
git clone git@gitlab.olindata.com:opstheater/opstheater.git
```
```
git clone git@gitlab.olindata.com:opstheater/opstheater.git
```
* Switch to the vagrant environment directory
```
cd opstheater/deploy/vagrant-oscar
```
```
cd opstheater/deploy/vagrant-oscar
```
* All the deployment files and configurations are in the `opstheater/deploy/vagrant-oscar` directory.
* Bring up the puppet master (This will take a looong time!) vm and log into it:
For Puppet Enterprise:
```
vagrant up master
vagrant ssh master
sudo su -
```
For Open Source Puppet:
```
vagrant up foss-master
vagrant ssh foss-master
sudo su -
```
At the very end of that process the `vagrant up` output displays the login details for foreman:
```
==> foss-master: Notice: Applied catalog in 0.25 seconds
==> foss-master: ==> Foreman URL: http://master.opstheater.vm:3000
==> foss-master: ==> Login credentials: admin / zndxYuJbDzasVCpv
```
Don’t forget to add master.opstheater.vm to your hosts file.
For Puppet Enterprise:
```
vagrant up master
vagrant ssh master
sudo su -
```
For Open Source Puppet:
```
vagrant up foss-master
vagrant ssh foss-master
sudo su -
```
At the very end of that process the `vagrant up` output displays the login details for foreman:
```
==> foss-master: Notice: Applied catalog in 0.25 seconds
==> foss-master: ==> Foreman URL: http://master.opstheater.vm:3000
==> foss-master: ==> Login credentials: admin / zndxYuJbDzasVCpv
```
Don’t forget to add master.opstheater.vm to your hosts file.
* Now bring up one or more machines with oscar on your host machine:
```
vagrant up mysql
vagrant up icinga2
vagrant up gitlab
vagrant up elasticsearch
```
```
vagrant up mysql
vagrant up icinga2
vagrant up gitlab
vagrant up elasticsearch
```
to see which machines are available, simply do an `vagrant status`.
to see which machines are available, simply do an `vagrant status`.
NOTE: you might have to run puppet a number of times on each node to make sure it fully puppetises itself. Some of the initial runs might have errors but they will go away as the puppet runs on all servers start happening.
NOTE: you might have to run puppet a number of times on each node to make sure it fully puppetises itself. Some of the initial runs might have errors but they will go away as the puppet runs on all servers start happening.
* You might also want to install r10k or puppet-librarian on your host machine and install the modules the opstheater repo uses on your host so you can browse through them.
TODO: Add instructions for r10k setup
TODO: Add instructions for r10k setup
# Installation
TODO: this is a work in progress, it is not complete and might not be fully up to date
TODO: this is a work in progress, it is not complete and might not be fully up to date. We'll be very happy with your pull requests..
* Make sure you have read https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/1.7/deployment/scenario.md
* Make sure you have read <https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/2.0/deployment/scenario.md>
1. Requirements gathering phase
1.1 which tools do you want to use of the OpsTheater stack
1. Requirements gathering phase
* Puppet? Open Source or Enterprise?
* The foreman?
* Grafana, Kibana, elasticsearch?
* Icinga?
* Gitlab, Mattermost?
1.1 which tools do you want to use of the OpsTheater stack
1.2 hostnames
* Puppet? Open Source or Enterprise?
* The foreman?
* Grafana, Kibana, elasticsearch?
* Icinga?
* Gitlab, Mattermost?
Recommended…
1.2 hostnames
* puppet.example.com (puppetmaster / foreman (if foss))
* icinga.example.com (icinga + icinga web)
* elastic.example.com (kibana / logstash / elasticsearch / influxdb / grafana)
* gitlab.example.com (gitlab / mattermost)
* mysql.example.com (mysql)
Recommended…
1.3 resource allocation (either the default scheme or custom if need be)
* puppet.example.com (puppetmaster / foreman (if foss))
* icinga.example.com (icinga + icinga web / influxdb)
* elastic.example.com (kibana / logstash / elasticsearch / grafana)
* gitlab.example.com (gitlab / mattermost)
* mysql.example.com (mysql)
1.4 HTTPS Yes or No?
1.3 resource allocation (either the default scheme or custom if need be)
If yes, need certificates for above hostnames
1.4 HTTPS Yes or No?
1.5 users (name, email address), groups
If yes, need certificates for above hostnames
We need to create a sheet of sorts to collect what types of users and what types of access to be given eg:
Foreman users
Puppet users
Shell users (admin access)
Gitlab / Mattermost users
Icinga users
1.5 users (name, email address), groups
1.6 SMTP Relay information for our stack being able to send emails
We need to create a sheet of sorts to collect what types of users and what types of access to be given eg:
* Foreman users
* Puppet users
* Shell users (admin access)
* Gitlab / Mattermost users
* Icinga users
SMTP Server Hostname
SMTP Server Port
Authenticated? If yes...
username:
Password:
Uses TLS?
Uses StartTLS?
1.6 SMTP Relay information for our stack being able to send emails
1.7 any custom requirements
* SMTP Server Hostname
* SMTP Server Port
* Authenticated? If yes...
* username:
* Password:
* Uses TLS?
* Uses StartTLS?
1.8 any needed migrations from other tools
1.7 any custom requirements
1.9 Choice of provider(s) (cloud / physical)
1.8 any needed migrations from other tools
2. deploy vms/physical nodes
1.9 Choice of provider(s) (cloud / physical)
3. Installation of master server (FOSS or not)
2. deploy vms/physical nodes
More details…
3. Installation of master server (FOSS or not)
4. Customization of client-specific opstheater-control repository to include client-specific configuration, SSL certificates, URLs, SMTP provider, etc.
More details…
details...
4. Customization of client-specific opstheater-control repository to include client-specific configuration, SSL certificates, URLs, SMTP provider, etc.
5. Installation of requested OpsTheater-provided servers & services
details...
master.opstheater.companyname.xxx (puppetmaster / foreman (if foss))
monitoring.opstheater.companyname.xxx (icinga)
logging.opstheater.companyname.xxx server (kibana / other techs…?)
code.opstheater.companyname.xxx server (gitlab / mattermost)
others...
5. Installation of requested OpsTheater-provided servers & services
6. Any manual configuration of OpsTheater servers not yet automated
master.opstheater.companyname.xxx (puppetmaster / foreman (if foss))
monitoring.opstheater.companyname.xxx (icinga)
logging.opstheater.companyname.xxx server (kibana / other techs…?)
code.opstheater.companyname.xxx server (gitlab / mattermost)
others...
7. (per-request) Client-specific configuration pre-discussed, such as setting up foreman to be able to deploy specific server types.
6. Any manual configuration of OpsTheater servers not yet automated
8. Creation of requested users in the various systems per-requested by the client.
7. (per-request) Client-specific configuration pre-discussed, such as setting up foreman to be able to deploy specific server types.
8. Creation of requested users in the various systems per-requested by the client.
## Elastic Server Setup
1. Configure repo and install puppet.
1. Configure repo and install puppet.
```
/bin/yum install -y epel-release http://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
/bin/yum install -y puppet-agent
/opt/puppetlabs/bin/puppet config set --section main server puppet.olindata.com
```
```
/bin/yum install -y epel-release http://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
/bin/yum install -y puppet-agent
/opt/puppetlabs/bin/puppet config set --section main server puppet.olindata.com
```
2. Configure/adjust Master
2. Configure/adjust Master
Ensure correct filename ymal file exists in bellow locations:
Ensure correct filename yaml file exists in below locations:
```
/etc/puppetlabs/code/environments/production/hieradata/10.fqdn
```
```
/etc/puppetlabs/code/environments/production/hieradata/10.fqdn
```
Logstash settings needs to be checked for public vs private ip
Merge elastic.olindata.com.yaml and logstash.olindata.vm.yaml As we have single server or both application.
(Remember to edit the file and remove extra --- and change the server name to elastic from elasticsearch)
Ref: - "elastic.olindata.com:9200"
Logstash settings needs to be checked for public vs private ip
3. wget needs to be installed before running puppet agent -t.
Ref: - "elastic.olindata.com:9200"
4. Add DNS entry for logstash.olindata.com OR update /etc/filebeat/filebeat.yml to talk to elastic.olindata.com
3. wget needs to be installed before running puppet agent -t.
5. update site.pp as bellow:
4. Add DNS entry for logstash.olindata.com OR update /etc/filebeat/filebeat.yml to talk to elastic.olindata.com
```
node 'elastic.olindata.com' {
include opstheater::role::elastic::server
include opstheater::role::logstash::server
}
```
5. update site.pp as bellow:
```
node 'elastic.olindata.com' {
include opstheater::role::elastic::server
include opstheater::role::logstash::server
}
```
6. Run Puppet agent.
6. Run Puppet agent.
This diff is collapsed.
## GitLab Server Setup.
1. Configure repo and install puppet.
```
/bin/yum install -y epel-release http://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
/bin/yum install -y puppet-agent
/opt/puppetlabs/bin/puppet config set --section main server puppet.olindata.com
```
2. Configure/adjust Master
Ensure correct filename ymal file exists in bellow locations:
```
/etc/puppetlabs/code/environments/production/hieradata/10.fqdn
```
3. Once this is done. Puppet agent.
```
/opt/puppetlabs/bin/puppet agent -t
```
4. Content Setup
Currently gitlab / mattermost integration requires a bit of manual attention post-install including…
Creating opstheater-control repository
Pointing the puppetmaster’s code source to the opstheater-control repository on their gitlab installation
Creating demo repository from git@github.com:olindata/sample-ruby-project.git
Setup mattermost
Enable mattermost team creation
Log into mattermost with root user
Create a team
Make the team a public team
disable team creation
TEST IT :P
Create integration
Copy/paste integration URL into gitlab for build notifications
1. Configure repo and install puppet.
```
/bin/yum install -y epel-release http://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
/bin/yum install -y puppet-agent
/opt/puppetlabs/bin/puppet config set --section main server puppet.olindata.com
```
2. Configure/adjust Master
Ensure correct filename yaml file exists in below location:
```
/etc/puppetlabs/code/environments/production/hieradata/10.fqdn
```
3. Once this is done run puppet agent.
```
/opt/puppetlabs/bin/puppet agent -t
```
4. Content Setup
Currently gitlab / mattermost integration requires a bit of manual attention post-install including…
Creating opstheater-control repository
Pointing the puppetmaster’s code source to the opstheater-control repository on their gitlab installation
Creating demo repository from git@github.com:olindata/sample-ruby-project.git
Setup mattermost
Enable mattermost team creation
Log into mattermost with root user
Create a team
Make the team a public team
disable team creation
TEST IT :P
Create integration
Copy/paste integration URL into gitlab for build notifications
# Icinga Server Setup
1. Configure repo and install puppet.
```
/bin/yum install -y epel-release http://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
/bin/yum install -y puppet-agent
/opt/puppetlabs/bin/puppet config set --section main server puppet.olindata.com
```
2. Configure/adjust Master
* Update `/etc/puppetlabs/code/environment/production/hieradata/60-.opstheater.yaml` in icinga section to reflect correct name of icinga on the below line.
* Also update the ipaddress to the public ipaddress.
1. Configure repo and install puppet.
```
'opstheater::icinga::fqdn': "icinga.%{hiera('opstheater::domain')}"
'opstheater::icinga::ipaddress': '37.139.31.34'
/bin/yum install -y epel-release http://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
/bin/yum install -y puppet-agent
/opt/puppetlabs/bin/puppet config set --section main server puppet.olindata.com
```
* update site.pp to reflect correct name.
2. Configure/adjust Master
```
# runs standalone monitoring setup with icinga2 and icinga web2
node 'icinga.olindata.com' {
include opstheater::role::monitoring::standalone
}
```
* Update `/etc/puppetlabs/code/environment/production/hieradata/50.common.yaml` in icinga section to reflect correct name of icinga on the below line.
* Also update the ipaddress to the public ipaddress.
```
'opstheater::icinga::fqdn': "icinga.%{hiera('opstheater::domain')}"
'opstheater::icinga::ipaddress': '37.139.31.34'
```
* in the foreman, assign the role `opstheater::role::monitoring::standalone` to the node
3. Run puppet agent
3. Run puppet agent
4. Open icinga2 web frontend and log in with icingaadmin / icinga
4. Open icinga2 web frontend and log in with icingaadmin / icinga
......@@ -2,8 +2,8 @@
The user management of mattermost is done through gitlab, but the process is currently a bit strange. Follow the following steps to start using mattermost:
1. Login to the gitlab server and edit `/etc/gitlab/gitlab.rb`. Find the setting `mattermost['team_enable_team_creation']` and change it's value to true.
2. run `gitlab-ctl reconfigure` to let these settings take effect.
3. Go to the mattermost address you configured (eg. `http://chat.opstheater.vm`), it'll now prompt you to create a team.
4. Create a team, then revers the setting `mattermost['team_enable_team_creation']` back to false and run `gitlab-ctl reconfigure` once more.
5. Log in to mattermost like normal.
1. Login to the gitlab server and edit `/etc/gitlab/gitlab.rb`. Find the setting `mattermost['team_enable_team_creation']` and change it's value to true.
2. run `gitlab-ctl reconfigure` to let these settings take effect.
3. Go to the mattermost address you configured (eg. `http://chat.opstheater.vm`), it'll now prompt you to create a team.
4. Create a team, then revers the setting `mattermost['team_enable_team_creation']` back to false and run `gitlab-ctl reconfigure` once more.
5. Log in to mattermost like normal.
## MYSQL server Setup
1. Configure repo and install puppet.
```
/bin/yum install -y epel-release http://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
/bin/yum install -y puppet-agent
/opt/puppetlabs/bin/puppet config set --section main server puppet.olindata.com
```
2. Configure/adjust Master
update /etc/puppetlabs/code/environment/production/hieradata/60-.opstheater.yaml to reflect myqsl server ip.
```
##########################
## MySQL related settings
##########################
## MySQL related settings
# Variable: opstheater::mysql::fqdn
# Description:
# Default value: "mysql.%{hiera('opstheater::domain')}"
'opstheater::mysql::fqdn': "mysql.%{hiera('opstheater::domain')}"
# Variable: opstheater::mysql::ipaddress
# Description:
# Default value: '10.20.1.60'
'opstheater::mysql::ipaddress': '10.129.2.113'
# Variable: opstheater::mysql::whitelist_range
# Description:
# Default value: '10.20.1.%'
'opstheater::mysql::whitelist_range': '10.129.%'
```
3. Run Puppet Agent
This will throw error for the 1st time as below but on the second run it works fine.
```
nfo: /Stage[main]/Mysql::Server::Config/File[mysql-config-file]: Filebucketed /etc/my.cnf to puppet with sum 80e1eb23d5fbd77fc0ff681b0f0df297
Notice: /Stage[main]/Mysql::Server::Config/File[mysql-config-file]/content: content changed '{md5}80e1eb23d5fbd77fc0ff681b0f0df297' to '{md5}3ab13aa54c001fe3966a08ae49c5517d'
Notice: Disabling SSL is evil! You should never ever do this except if you are forced to use a mysql version compiled without SSL support
Notice: /Stage[main]/Mysql::Server::Config/Notify[ssl-disable]/message: defined 'message' as 'Disabling SSL is evil! You should never ever do this except if you are forced to use a mysql version compiled without SSL support'
Error: Could not start Service[mysqld]: Execution of '/usr/bin/systemctl start mysqld' returned 1: Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.
Error: /Stage[main]/Mysql::Server::Service/Service[mysqld]/ensure: change from stopped to running failed: Could not start Service[mysqld]: Execution of '/usr/bin/systemctl start mysqld' returned 1: Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.
Notice: /Stage[main]/Opstheater::Profile::Mysql/File[/var/log/mysql]/ensure: created
Notice: /Stage[main]/Mysql::Server::Service/File[/var/log/mysql/error.log]/ensure: created
Info: Class[Mysql::Server::Service]: Unscheduling all events on Class[Mysql::Server::Service]
Notice: /Stage[main]/Mysql::Server::Root_password/Exec[remove install pass]: Dependency Service[mysqld] has failures: true
Warning: /Stage[main]/Mysql::Server::Root_password/Exec[remove install pass]: Skipping because of failed dependencies
Info: Creating state file /opt/puppetlabs/puppet/cache/state/state.yaml
Error: Failed to apply catalog: Execution of '/usr/bin/mysql -NBe SELECT CONCAT(User, '@',Host) AS User FROM mysql.user' returned 1: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
```
1. Configure repo and install puppet.
```
/bin/yum install -y epel-release http://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
/bin/yum install -y puppet-agent
/opt/puppetlabs/bin/puppet config set --section main server puppet.olindata.com
```
2. Configure/adjust Master
update /etc/puppetlabs/code/environment/production/hieradata/50.common.yaml to override parameters from 60.opstheater.yaml, like the myqsl server ip.
```
##########################
## MySQL related settings
##########################
## MySQL related settings
# Variable: opstheater::mysql::fqdn
# Description:
# Default value: "mysql.%{hiera('opstheater::domain')}"
'opstheater::mysql::fqdn': "mysql.%{hiera('opstheater::domain')}"
# Variable: opstheater::mysql::ipaddress
# Description:
# Default value: '10.20.1.60'
'opstheater::mysql::ipaddress': '10.129.2.113'
# Variable: opstheater::mysql::whitelist_range
# Description:
# Default value: '10.20.1.%'
'opstheater::mysql::whitelist_range': '10.129.%'
```
3. Run Puppet Agent
This will throw error for the 1st time as below but on the second run it works fine.
```
Info: /Stage[main]/Mysql::Server::Config/File[mysql-config-file]: Filebucketed /etc/my.cnf to puppet with sum 80e1eb23d5fbd77fc0ff681b0f0df297
Notice: /Stage[main]/Mysql::Server::Config/File[mysql-config-file]/content: content changed '{md5}80e1eb23d5fbd77fc0ff681b0f0df297' to '{md5}3ab13aa54c001fe3966a08ae49c5517d'
Notice: Disabling SSL is evil! You should never ever do this except if you are forced to use a mysql version compiled without SSL support
Notice: /Stage[main]/Mysql::Server::Config/Notify[ssl-disable]/message: defined 'message' as 'Disabling SSL is evil! You should never ever do this except if you are forced to use a mysql version compiled without SSL support'
Error: Could not start Service[mysqld]: Execution of '/usr/bin/systemctl start mysqld' returned 1: Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.
Error: /Stage[main]/Mysql::Server::Service/Service[mysqld]/ensure: change from stopped to running failed: Could not start Service[mysqld]: Execution of '/usr/bin/systemctl start mysqld' returned 1: Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.
Notice: /Stage[main]/Opstheater::Profile::Mysql/File[/var/log/mysql]/ensure: created
Notice: /Stage[main]/Mysql::Server::Service/File[/var/log/mysql/error.log]/ensure: created
Info: Class[Mysql::Server::Service]: Unscheduling all events on Class[Mysql::Server::Service]
Notice: /Stage[main]/Mysql::Server::Root_password/Exec[remove install pass]: Dependency Service[mysqld] has failures: true
Warning: /Stage[main]/Mysql::Server::Root_password/Exec[remove install pass]: Skipping because of failed dependencies
Info: Creating state file /opt/puppetlabs/puppet/cache/state/state.yaml
Error: Failed to apply catalog: Execution of '/usr/bin/mysql -NBe SELECT CONCAT(User, '@',Host) AS User FROM mysql.user' returned 1: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
```
......@@ -4,5 +4,5 @@ Q) I am having trouble getting the stack up and running
A) We've seen several issues regarding the versions of vagrant and virtualbox in combination with your host OS. Confirmed working combinations:
Host: Ubuntu 16.04/16.10
Vagrant: 1.8.1 (1.8.5: https://github.com/mitchellh/vagrant/issues/5186 and 1.9.1)
Vagrant: 1.8.1 (1.8.5: <https://github.com/mitchellh/vagrant/issues/5186> and 1.9.1)
Virtualbox: 5.0.30
## OpsTheater Release Checklist for Release 1.7.0
## OpsTheater Release Checklist for Release 2.0.0
**Following checks need to be performed after every release :**
- Check if you can login into following using your web browser :
- [ ] Foreman
- [ ] Gitlab
- [ ] Mattermost
- [ ] Icinga
- [ ] Grafana
- [ ] Kibana
- [ ] Check if you are able to send message using Mattermost.
- [ ] Check if you are able to create a user in Foreman and can login with that user.
- [ ] Check if you can see the logs coming up for OpsTheater components in Icinga Web UI.
- [ ] Check if you can see the metrics coming up for OpsTheater components in Icinga Web UI.
- [ ] Try to search for a host in Kibana and check if you are getting logs of that host.
- [ ] Check if you can create users and usergroups in Icinga
- [ ] Login to Grafana web UI and check if you can see different metrics in Grafana
- [ ] Login to grafana and check that you can see two datasources. Edit each one of them and press "Test Connection" to make sure they work.
- [ ] Login to Kibana web UI and try to search for logs having source as "/var/log/puppetlabs/puppetserver/puppetserver-access.log". Check if the value of field timestamp is same as the time given in message field
**Release specific Checks :**
*These checks will change on every release and will be more specific for the new changes that we are introducing in this release.*
- [ ] Login to Grafana web UI and check if you can see different metrics in Grafana
- [ ] Login to grafana and check that you can see two datasources. Edit each one of them and press "Test Connection" to make sure they work.
- [ ] Login to Kibana web UI and try to search for logs having source as "/var/log/puppetlabs/puppetserver/puppetserver-access.log". Check if the value of field timestamp is same as the time given in message field
......@@ -2,7 +2,7 @@
This borrows heavily and is modeled after: <http://doc.gitlab.com/ce/release/monthly.html>
**NOTE: This is a guide used by OlinData BV for handling releases of OpsTheater. As an end user you do not need to use this guide.**
**NOTE: This is a guide used by OlinData BV for handling releases of OpsTheater. As an end user you (probably) do not need to use this guide.**
# Release cycle
......
This diff is collapsed.
......@@ -4,4 +4,4 @@ Documentation for OpsTheater
## Getting started
If you wish to try out OpsTheater in a development setup, please look at the instructions here: https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/1.7/deployment/development.md
If you wish to try out OpsTheater in a development setup, please look at the instructions here: <https://gitlab.olindata.com/opstheater/opstheater-docs/blob/master/2.0/deployment/development.md>
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment