Deploying Foreman and Katello on OpenShift Origin V3 #349

ehelms · 2016-12-29T16:13:51Z

This work is a work in progress to explore the ability to deploy Foreman and Katello on to an OpenShift V3 (container and Kubernetes based environment) environment to explore harnessing the power of the OpenShift platform to manage the application and scale out.

For more detailed information on this deployment, how to use, test and contribute see the README (https://github.com/ehelms/forklift/blob/openshift/openshift/README.md).

This work combines work built on top of the foreman-docker-compose repository (https://github.com/shlomizadok/foreman-docker-compose) along with previous work by the Pulp and Candlepin teams to build out images for use on OpenShift. This also pulls in a starter repo (https://github.com/ehelms/foreman-openshift) that was used to hold initial work on the OpenShift piece.

I have initially pulled the aforementioned repositories into a PR to Forklift (using git subtree to preserve the history) for a few reasons:

Forklift's goal is around putting Foreman into user and developer environments
Forklift has a broader audience than a new set of repositories and branches would have
To get more eyes and interest on this idea for deploying Foreman

If others feel this would be better maintained in a separate repository, I'm open to that discussion with the hope that the previous reasons will be thoughtfully considered with respect on how to position this.

- switched foreman/proxy to fedora image - added a client fact uploading - db is now saved outside of the container docker compose scale foreman=2 (or how many instances you want) docker compose up -d # first time will take a while

adds haproxy support

Update README.md

Replaced the MAINTAINER instruction with LABEL (read more here: moby/moby#25466). In addition, added the maintainer details if they were missing.

Use LABEL to specify the maintainer

ekohl

I ran into the issue that it needed sudo on localhost which doesn't feel right.

After that I ran into the problem that ansible/roles/puppet/files/puppet-template.yaml does not exist. Forgot to git add?

ekohl · 2017-01-21T00:48:20Z

openshift/README.md

+
+There are two aspects to the deployment: the default images and templates being loaded into OpenShift and creating the Foreman deployment. All of this is handled by a convenient playbook provided. You can view the configuration of the Foreman deployment itself by looking in the `templates/foreman.yaml` file. To create the application:
+
+    ansible-playbook ansible/playbooks/foreman.yaml


File is called .yml

ekohl · 2017-01-21T00:48:47Z

openshift/cluster-up.yml

+
+    - name: 'Create .tmp directory'
+      file:
+        path: .tmp


I had to add state: directory

ehelms · 2017-01-21T03:10:45Z

Thanks for the feedback so far @ekohl . I made changes based on your comments. There was a top level gitignore that was blocking the puppet role file from being added - fixed now. I also removed sudo from the volume creation. Volume creation and management is one of the trickier aspects. At this point, I've taken the approach of creating a local directory with subpaths for each volume "store" needed by the various services.

ekohl

My builds now fail because it can't resolve github.com. I don't know enough about openshift to properly debug it.

ekohl · 2017-01-21T11:06:15Z

openshift/README.md

+
+## Creating the Foreman Deployment
+
+There are two aspects to the deployment: the default images and templates being loaded into OpenShift and creating the Foreman deployment. All of this is handled by a convenient playbook provided. You can view the configuration of the Foreman deployment itself by looking in the `templates/foreman.yaml` file. To create the application:


This should also be .yml

ehelms · 2017-01-21T19:44:59Z

Thanks @ekohl - updated based on your comments.

A few things I wouldn't mind some feedback on:

currently I am tracking TODOs in the README on this PR, I was thinking about either:
a) having this live in its own repository and using github issues to manage the todos
b) using this repo (since this is sorta Forklift's mission) and using github issues + milestone for openshift work to track
creating an RFC either contained here with this PR and work or as part of the official RFC repo

ekohl · 2017-01-22T20:56:10Z

I wouldn't mind if this lived in this repo, but we already have quite a few ways this repo can be used and we need to cut down on it and focus the documentation. As someone new to the repo it's hard to figure out what you can and can't do with it. Before we add more, we need to simplify it first. A few steps that I'd think of:

Split the top directory into subdirs

Some candidates I see

bats
vagrant
openshift
docker

Remove deprecated things

Nuke setup.rb

ehelms · 2017-01-23T14:01:12Z

That sounds reasonable as a first good step to re-organize the top level (unless you think it should be part of this change only). The top level docker repository I don't know if anyone outside of myself even uses at this point. There is also a docker folder inside this PR, where in theory generic docker build directories are living. They could perhaps be moved to the top to help emphasize keeping them multi-use; I had put them there originally cause I was having to do some hacks to get them to work inside openshift.

I am all for nuking setup.rb. I think the biggest hold back of it is the use in bats and thus the use in our CI system.

ekohl · 2017-01-23T14:21:46Z

That sounds reasonable as a first good step to re-organize the top level (unless you think it should be part of this change only).

No, I'd prefer to get that done first and then get this merged.

The top level docker repository I don't know if anyone outside of myself even uses at this point.

That's a big problem with this repo IMHO. We have a lot of possibilities and they should be maintained. I'd like to go to a situation where each top level directory can be used independently.

There is also a docker folder inside this PR, where in theory generic docker build directories are living. They could perhaps be moved to the top to help emphasize keeping them multi-use; I had put them there originally cause I was having to do some hacks to get them to work inside openshift.

That's fine, until they are generic they should live inside openshift.

I am all for nuking setup.rb. I think the biggest hold back of it is the use in bats and thus the use in our CI system.

Agreed. Which is why I think we should get #331 merged and look at migrating the CI system.

ehelms · 2017-01-23T14:48:45Z

@ekohl I hope you don't mind, since we begin to talk about more than just the Openshift aspect, I moved it to an issue (#367) with the previous points quoted.

ekohl · 2017-01-23T15:27:29Z

Yes, let's keep this on topic.

ehelms · 2017-03-26T21:43:56Z

Replaced by #424

shlomizadok and others added 30 commits July 7, 2016 09:01

Initial commit

85c54e2

Initial commit, run foreman & postgres

338616c

initial README

d24ff85

Adds smart proxy to the compose

a9f5089

Cleanup comments from Foreman Dockerfile

5096842

- adds basic HA setup using haproxy and memcached

b5d7453

- switched foreman/proxy to fedora image - added a client fact uploading - db is now saved outside of the container docker compose scale foreman=2 (or how many instances you want) docker compose up -d # first time will take a while

Merge pull request #1 from ohadlevy/master

9d48480

adds haproxy support

Update README.md

3dda242

Update README.md

3865c2b

Merge pull request #2 from ohadlevy/patch-1

1752c3c

Update README.md

Use LABEL to specify the maintainer

3dd2f48

Replaced the MAINTAINER instruction with LABEL (read more here: moby/moby#25466). In addition, added the maintainer details if they were missing.

Merge pull request #4 from ripcurld00d/label_maintainer

8463b5a

Use LABEL to specify the maintainer

add :z label to shared volumes (selinux)

9603c10

Modify environment to work with latest develop & webpack

ac2b4c9

Pin PG to 9.5

d0a837b

Initial commit with Vagrant environment

ef3e61d

Move README to markdown file

df651b4

Add missing markdown README

f5a3ae3

Remove foreman_memcache for now

aba1cdc

Changes necessary to run on OpenShift

f8b5568

Changes to run successfully on OpenShift

a056e1e

Add playbook to setup openshift client tools

dc6d555

Update README

ba371de

Fix error installing client and defaults

3f9425b

Add pulp builds

09ebdf2

Try environment variable in conf

6efc931

Fixes to run in openShift for Pulp

ec7edc0

Add apacher user to dockerfile

db0d46b

Comment out docker

5858541

Add starter for Pulp deployment -- need to resolve logger issue

31700d3

Update persistent volume creation and diagrams

c715da3

ehelms force-pushed the openshift branch from 2f97909 to c715da3 Compare January 6, 2017 13:04

Switch back to using Pulps log to file

07237e7

ehelms force-pushed the openshift branch from c862c9e to 70c0a36 Compare January 10, 2017 03:00

ehelms force-pushed the openshift branch 2 times, most recently from 789a441 to 6664fb7 Compare January 20, 2017 16:24

ehelms added 3 commits January 20, 2017 11:43

Move to using Ansible roles and playbooks per app

a133be0

Update Openshift to 1.4

3b1ca18

Add Foreman Kitchensink playbook

7a4a758

ehelms force-pushed the openshift branch from 6664fb7 to 7a4a758 Compare January 20, 2017 18:10

Add volume as an Ansbile role

ea82d42

ekohl reviewed Jan 21, 2017

View reviewed changes

ehelms added 3 commits January 20, 2017 22:04

Don't ignore puppet files

453f904

Project directory moved to ansible

ce45824

Don't require sudo for volumes

2a47ef3

ekohl reviewed Jan 21, 2017

View reviewed changes

Address feedback

0a4d099

ehelms force-pushed the openshift branch from 002e627 to 0a4d099 Compare January 21, 2017 19:31

Add more plugins to Foreman

85a9043

ehelms mentioned this pull request Jan 23, 2017

Re-organizing Directory Structure #367

Closed

ekohl mentioned this pull request Mar 17, 2017

WIP: Refactor to allow splitting of services theforeman/puppet-katello#171

Closed

ehelms closed this Mar 26, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Deploying Foreman and Katello on OpenShift Origin V3 #349

Deploying Foreman and Katello on OpenShift Origin V3 #349

ehelms commented Dec 29, 2016 •

edited

Loading

ekohl left a comment

ekohl Jan 21, 2017

ekohl Jan 21, 2017

ehelms commented Jan 21, 2017

ekohl left a comment

ekohl Jan 21, 2017

ehelms commented Jan 21, 2017

ekohl commented Jan 22, 2017

ehelms commented Jan 23, 2017

ekohl commented Jan 23, 2017

ehelms commented Jan 23, 2017

ekohl commented Jan 23, 2017

ehelms commented Mar 26, 2017


		There are two aspects to the deployment: the default images and templates being loaded into OpenShift and creating the Foreman deployment. All of this is handled by a convenient playbook provided. You can view the configuration of the Foreman deployment itself by looking in the `templates/foreman.yaml` file. To create the application:

		ansible-playbook ansible/playbooks/foreman.yaml


		## Creating the Foreman Deployment

		There are two aspects to the deployment: the default images and templates being loaded into OpenShift and creating the Foreman deployment. All of this is handled by a convenient playbook provided. You can view the configuration of the Foreman deployment itself by looking in the `templates/foreman.yaml` file. To create the application:

Deploying Foreman and Katello on OpenShift Origin V3 #349

Deploying Foreman and Katello on OpenShift Origin V3 #349

Conversation

ehelms commented Dec 29, 2016 • edited Loading

ekohl left a comment

Choose a reason for hiding this comment

ekohl Jan 21, 2017

Choose a reason for hiding this comment

ekohl Jan 21, 2017

Choose a reason for hiding this comment

ehelms commented Jan 21, 2017

ekohl left a comment

Choose a reason for hiding this comment

ekohl Jan 21, 2017

Choose a reason for hiding this comment

ehelms commented Jan 21, 2017

ekohl commented Jan 22, 2017

Split the top directory into subdirs

Remove deprecated things

ehelms commented Jan 23, 2017

ekohl commented Jan 23, 2017

ehelms commented Jan 23, 2017

ekohl commented Jan 23, 2017

ehelms commented Mar 26, 2017

ehelms commented Dec 29, 2016 •

edited

Loading