redhat-cop/dark-tower

Ansible Tower based PoC Deployer

DEPRECATED This repository is not used anymore

Table of Contents

• It now lives in https://github.com/redhat-gpte-devopsautomation/babylon_anarchy_governor
  • Overview
    • Babylon Tower Project Overview
    • Documentation
    • Primary Components

It now lives in https://github.com/redhat-gpte-devopsautomation/babylon_anarchy_governor

Overview

The Dark Tower repo contains the Ansible Playbooks and roles for the back-end component, Dark Tower, of the Ansible Babylon Tower Project. These are used for final configuration, and customization of a Ansible Tower cluster and also the core job-runner playbook and associated roles to allow a Babylon Tower to be remotely called to deploy, teardown, idle and start infrastructure using ansible based deployers such as agnosticd and ansible workshops.

Babylon Tower Project Overview

Babylon Tower is an Ansible Tower based projects which allows dynamic deployments of environment via Ansible based deployers such as AgnosticD or the Ansible Workshop deployer.

Once deployed, with a single project and job-template called the job-runner, Babylon can create all necessary artifacts to automatically download an Ansible based deployer and launch the requested action.

Documentation

Primary Components

• job-runner.yml - Entry point for all jobs (deploy, teardown, idle, start)

The job runner

===

dark-tower's Issues

P2: Role confirm-tower-empty-inventory has hard coded instance group defaults

Roles defaults contain a hardcoded list of instance groups - this needs to be dynamic and self updating

Use ansible.cfg to allow load-runner to execute from dev/load-testing

Set role path to allow execution using root level roles

P2: Generate unique names for core Tower objects

Current naming schema allows potential collisions i.e. 2 forks of the same deployer with the same tags would over-write each other's projects.

Solution: add a unique component to the identifiers. e.g. a hash of the git repo, md5, etc

• Projects
• Job Templates

Master Branch: The conditional check '{{ job_vars['__meta__']['secondary_deployer']['scm_url'] }} is defined' failed.

{
"msg": "The conditional check '{{ job_vars['meta']['secondary_deployer']['scm_url'] }} is defined' failed. The error was: error while evaluating conditional ({{ job_vars['meta']['secondary_deployer']['scm_url'] }} is defined): 'dict object' has no attribute 'secondary_deployer'\n\nThe error appears to be in '/var/lib/awx/projects/_6__babylon/roles/create-job-manifest/tasks/main.yml': line 14, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- when: "{{ job_vars['meta']['secondary_deployer']['scm_url'] }} is defined"\n ^ here\nWe could be wrong, but this one looks like it might be an issue with\nmissing quotes. Always quote template expression brackets when they\nstart a value. For instance:\n\n with_items:\n - {{ foo }}\n\nShould be written as:\n\n with_items:\n - "{{ foo }}"\n",
"_ansible_no_log": false
}

confirm-tower-project contains legacy vars

Not all the tower-project arguments use the meta dictionary. These need to be converted:

scm_update_on_launch:       "{{ babylon_scm_update_on_launch | default('no') }}"
scm_update_cache_timeout:   "{{ babylon_scm_update_cache_timeout }}"

Projects should default to not updating on launch

P2: Increase polling value on the job runner and make var

Currently polls job status every second. Make this a variable babalon_job_poll_interval

Babylon job-creator should create an organization if it does not exist