Commit 913c098f authored by Walter Heck's avatar Walter Heck

More organising of documents to create a proper structure

parent 459542cd
# Installation
1. Requirements gathering phase
1. Requirements gathering phase
1.1 which tools do they want to use of the OpsTheater stack
......@@ -32,8 +32,8 @@ Icinga users
SMTP Server Hostname
SMTP Server Port
Authenticated? If yes...
username:
Authenticated? If yes...
username:
Password:
Uses TLS?
Uses StartTLS?
......@@ -64,28 +64,6 @@ others...
6. Any manual configuration of OpsTheater servers not yet automated
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
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.
## to be added to opstheater-control
In order to make deploys easier and upgrades also, we (W+F) propose something along the lines of this:
another hiera level 70.opstheater_custom
rename 60.opstheater to 60.opstheater_defaults
create besides the role and profile module also a module for each client that lives locally in their gitlab instance. We add it to their puppetfile so it gets deployed nicely
from 70.opstheater_custom we can have keys refer to a path in the client specific module
## FOSS Master for OpsTheater
*Note*: The process for this node is currently much longer then it should be since the foreman doesn't officially support Puppet 4 yet. Hence we compile from source in order to make things work. This will be changed as soon as upstream foreman supports Puppet 4 properly.
Disable firewalld ************************ Enable firewalld again once installation is complete.
......
......@@ -21,3 +21,19 @@
```
/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
# Instructions for attaching an existing node to opstheater
# Instructions for attaching a new node to opstheater
# opstheater-docs
Documentation for OpsTheater
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