Commit f1854340 authored by Walter Heck's avatar Walter Heck

Updates to the documentation for opstheater 1.5

parent f7e2d003
Pipeline #102 skipped
# Installation
TODO: this is a work in progress, it is not complete and might not be fully up to date
1. Requirements gathering phase
1.1 which tools do they want to use of the OpsTheater stack
......@@ -8,10 +10,11 @@
Recommended…
* master.opstheater.companyname.xxx (puppetmaster / foreman (if foss))
* monitoring.opstheater.companyname.xxx (icinga)
* logging.opstheater.companyname.xxx (kibana / other techs…?)
* code.opstheater.companyname.xxx (gitlab / mattermost)
* 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)
1.3 resource allocation (either the default scheme or custom if need be)
......
......@@ -3,11 +3,11 @@
**Following checks need to be performed after every release :**
- Check if you can login into following using your web browser :
- [ ] Foreman
- [ ] Gitlab
- [ ] Mattermost
- [ ] Icinga
- [ ] Icinga
- [ ] Grafana
- [ ] Kibana
......@@ -28,5 +28,3 @@
- [ ] Login to Grafana web UI and check if you can see different metrics in Grafana
- [ ] 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
......@@ -33,7 +33,7 @@ Patch release, for serious bugs or security problems.
8. Create release notes and a blog post for the olindata.com blog.
9. Once the upgrade installation is succeeded then release manager need to create a new branch in opstheater-docs reposiroty cloning previous release branch and need to update the documents in the new branch according to the new release for example release manager need to update upgrade.md with the steps that need to be performed for upgrade installation.
9. Once the upgrade installation is succeeded then release manager need to create a new directory in opstheater-docs reposiroty cloning previous release directory and need to update the documents in the new directory according to the new release for example release manager need to update upgrade.md with the steps that need to be performed for upgrade installation.
10. After this release manager need to update releasechecklist.md in current release branch of opstheater-docs. releasechecklist.md will contains the basic steps that release manager needs to perform once the upgrade is finised to make sure that all opstheater components are working fine.
......
......@@ -213,9 +213,8 @@ puppetserver-2.3.1-1.el7.noarch
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 OpsTheater puppet repository checked out
* download the OpsTheater 1.5.0 release tarball: https://gitlab.olindata.com/opstheater/opstheater/repository/archive.tar.gz?ref=releases%2F1.5.0
* unpack it into the directory that contains your internal OpsTheater puppet repo
* 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`
......
1.5/
\ No newline at end of file
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