Skip to content

Patches and Ansible playbook to prepare Ubuntu based boxes for CoreMedia LiveContext-3 or CMS-9 - please use superseding repository 'coremedia-node-preparation'

License

Notifications You must be signed in to change notification settings

provocon/coremedia-ubuntu-development

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Patches and Ansible Playbook to Prepare Ubuntu Boxes for CoreMedia

coremedia-ubuntu-development

The patches in this workspace are prepared to patch a 1710 CMS-9 workspaces to be deployable as a single node configuration on a Ubuntu based host.

The playbook in this repository is intended for preparation of CI nodes and other hosts, which need to be able to build CoreMedia workspaces for CoreMedia CMS 9 or LiveContext 3 without any other installation steps necessary.

Find mirrors of this repository at gitlab and github.

Setup of the Environment

We rely on the roles coremedia for all coremedia hosts and cmdev for development hosts.

The role coremedia provides the (not supported but happily working) OpenJDK for users which do not want to include Oracle Java from the default CoreMedia chef node configuration.

The role cmsdev provides the needed development tools to build a workspace.

Preparation

Install python on your node since otherwise ansible will not start.

The recipes in here also need a pre-installed ohai.

apt-get install python
apt-get install ohai

Configure relevant hosts in inventory.properties or your global ansible hosts file (if you haven't done so).

Usage

Run with:

ansible-playbook -i inventory.properties setup.yml

Collection

This playbook provides:

  • Java 8
  • mod_jk for Apache httpd

for hosts in role coremedia, and

for hosts in role cmdev .

Deployment of the System to Ubuntu

To deploy CoreMedia CMS-9 to Ubuntu based systems, you will need to apply the patches provided in this workspace to the chef scripts in your workspace.

AJP Usage

The usage of AJP is not strictly necessary, but the ability to configure the protocol in use might still help.

We worked around the fact that hosts directly connected to the internet use an IP-Address that is not on the default list of Apache Tomcat's

RemoteIpValve

Alternatively you could also change the default in conf/server.tml during deployment.

Feedback

Please use the issues section of this repository at github for feedback.

About

Patches and Ansible playbook to prepare Ubuntu based boxes for CoreMedia LiveContext-3 or CMS-9 - please use superseding repository 'coremedia-node-preparation'

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages