Initial commit

Author: wkulhanek

.github/workflows/static-checks-pr.yml

@@ -0,0 +1,34 @@
+---
+name: Static Checks Pull Request
+
+on:
+  pull_request:
+    branches:
+    - main
+
+jobs:
+  static-checks:
+    name: Run static tests using tox
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version:
+        - '3.12'
+
+    steps:
+    - name: Get Repository Code
+      id: get_repo_code
+      uses: actions/checkout@v2
+      with:
+        fetch-depth: 0
+
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v2
+      with:
+        python-version: ${{ matrix.python-version }}
+
+    - name: Run static checks
+      run: |
+        pip install tox
+        tox -c tests/static -- ${{ github.base_ref }} ${{ github.sha }}
+...

.github/workflows/static-checks-push.yml

@@ -0,0 +1,34 @@
+---
+name: Static Checks Push
+
+on:
+  push:
+    branches:
+    - main
+    tags:
+    - v*
+
+jobs:
+  static-checks:
+    name: Run static tests using tox
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version:
+        - '3.12'
+
+    steps:
+    - name: Get Repository Code
+      id: get_repo_code
+      uses: actions/checkout@v2
+
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v2
+      with:
+        python-version: ${{ matrix.python-version }}
+
+    - name: Run static checks
+      run: |
+        pip install tox
+        tox -c tests/static
+...

.gitignore

@@ -0,0 +1,15 @@
+__pycache__
+.ansible
+.ansible_facts
+.DS_Store
+.idea
+.pre-commit-config.yaml
+.tox
+.vscode
+*-user-data.yaml
+*-user-info.yaml
+*.pyc
+*.rc
+*.retry
+*.swp
+*.vscode

README.adoc

@@ -0,0 +1,53 @@
+= rhpds.mta_workloads
+:toc: macro
+:toc-title: Table of Contents
+:toclevels: 3
+
+An Ansible collection for deploying MTA (Migration Toolkit for Applications) workshop and lab environments on Red Hat OpenShift.
+
+toc::[]
+
+== Overview
+
+This collection provides automation for setting up a complete MTA demonstration environment.
+
+The collection uses GitOps (ArgoCD ApplicationSets) to deploy and manage all components.
+
+== Collection Information
+
+[cols="1,2"]
+|===
+|Namespace |`rhpds`
+|Name |`mta_workloads`
+|Version |1.0.0
+|License |GPL-2.0-or-later
+|Author |Wolfgang Kulhanek <wkulhane@redhat.com>, Shaaf Syed <sshaaf@redhat.com>
+|===
+
+== Prerequisites
+
+* Red Hat OpenShift 4.x cluster
+* OpenShift GitOps (ArgoCD) installed and configured
+* Gitea instance with users pre-configured (typically via Gitea Operator)
+* LiteMaaS or compatible LLM API endpoint
+* `kubernetes.core` Ansible collection installed
+* `agnosticd.core` Ansible collection installed
+
+== Installation
+
+Install the collection from Ansible Galaxy:
+
+[source,bash]
+----
+ansible-galaxy collection install rhpds.mta_workloads
+----
+
+Or include in your `requirements.yml`:
+
+[source,yaml]
+----
+collections:
+  - name: rhpds.mta_workloads
+    version: ">=1.0.0"
+----
+

galaxy.yml

@@ -0,0 +1,70 @@
+#SPDX-License-Identifier: MIT-0
+### REQUIRED
+# The namespace of the collection. This can be a company/brand/organization or product namespace under which all
+# content lives. May only contain alphanumeric lowercase characters and underscores. Namespaces cannot start with
+# underscores or numbers and cannot contain consecutive underscores
+namespace: rhpds
+
+# The name of the collection. Has the same character restrictions as 'namespace'
+name: mta_workloads
+
+# The version of the collection. Must be compatible with semantic versioning
+version: 1.0.0
+
+# The path to the Markdown (.md) readme file. This path is relative to the root of the collection
+readme: README.md
+
+# A list of the collection's content authors. Can be just the name or in the format 'Full Name <email> (url)
+# @nicks:irc/im.site#channel'
+authors:
+- Wolfgang Kulhanek <wkulhane@redhat.com>
+- Shaaf Syed <sshaaf@redhat.com>
+
+### OPTIONAL but strongly recommended
+# A short summary description of the collection
+description: Collection of Ansible workloads for MTA Workshops.
+
+# Either a single license or a list of licenses for content inside of a collection. Ansible Galaxy currently only
+# accepts L(SPDX,https://spdx.org/licenses/) licenses. This key is mutually exclusive with 'license_file'
+license:
+- GPL-2.0-or-later
+
+# The path to the license file for the collection. This path is relative to the root of the collection. This key is
+# mutually exclusive with 'license'
+license_file: ''
+
+# A list of tags you want to associate with the collection for indexing/searching. A tag name has the same character
+# requirements as 'namespace' and 'name'
+tags: []
+
+# Collections that this collection requires to be installed for it to be usable. The key of the dict is the
+# collection label 'namespace.name'. The value is a version range
+# L(specifiers,https://python-semanticversion.readthedocs.io/en/latest/#requirement-specification). Multiple version
+# range specifiers can be set and are separated by ','
+dependencies: {}
+
+# The URL of the originating SCM repository
+repository: http://example.com/repository
+
+# The URL to any online docs
+documentation: http://docs.example.com
+
+# The URL to the homepage of the collection/project
+homepage: http://example.com
+
+# The URL to the collection issue tracker
+issues: http://example.com/issue/tracker
+
+# A list of file glob-like patterns used to filter any files or directories that should not be included in the build
+# artifact. A pattern is matched from the relative path of the file or directory of the collection directory. This
+# uses 'fnmatch' to match the files or directories. Some directories and files like 'galaxy.yml', '*.pyc', '*.retry',
+# and '.git' are always filtered. Mutually exclusive with 'manifest'
+build_ignore: []
+
+# A dict controlling use of manifest directives used in building the collection artifact. The key 'directives' is a
+# list of MANIFEST.in style
+# L(directives,https://packaging.python.org/en/latest/guides/using-manifest-in/#manifest-in-commands). The key
+# 'omit_default_directives' is a boolean that controls whether the default directives are used. Mutually exclusive
+# with 'build_ignore'
+# manifest: null
+

meta/runtime.yml

@@ -0,0 +1,53 @@
+#SPDX-License-Identifier: MIT-0
+---
+# Collections must specify a minimum required ansible version to upload
+# to galaxy
+# requires_ansible: '>=2.9.10'
+
+# Content that Ansible needs to load from another location or that has
+# been deprecated/removed
+# plugin_routing:
+#   action:
+#     redirected_plugin_name:
+#       redirect: ns.col.new_location
+#     deprecated_plugin_name:
+#       deprecation:
+#         removal_version: "4.0.0"
+#         warning_text: |
+#           See the porting guide on how to update your playbook to
+#           use ns.col.another_plugin instead.
+#     removed_plugin_name:
+#       tombstone:
+#         removal_version: "2.0.0"
+#         warning_text: |
+#           See the porting guide on how to update your playbook to
+#           use ns.col.another_plugin instead.
+#   become:
+#   cache:
+#   callback:
+#   cliconf:
+#   connection:
+#   doc_fragments:
+#   filter:
+#   httpapi:
+#   inventory:
+#   lookup:
+#   module_utils:
+#   modules:
+#   netconf:
+#   shell:
+#   strategy:
+#   terminal:
+#   test:
+#   vars:
+
+# Python import statements that Ansible needs to load from another location
+# import_redirection:
+#   ansible_collections.ns.col.plugins.module_utils.old_location:
+#     redirect: ansible_collections.ns.col.plugins.module_utils.new_location
+
+# Groups of actions/modules that take a common set of options
+# action_groups:
+#   group_name:
+#     - module1
+#     - module2

plugins/README.md

@@ -0,0 +1,31 @@
+# Collections Plugins Directory
+
+This directory can be used to ship various plugins inside an Ansible collection. Each plugin is placed in a folder that
+is named after the type of plugin it is in. It can also include the `module_utils` and `modules` directory that
+would contain module utils and modules respectively.
+
+Here is an example directory of the majority of plugins currently supported by Ansible:
+
+```
+└── plugins
+    ├── action
+    ├── become
+    ├── cache
+    ├── callback
+    ├── cliconf
+    ├── connection
+    ├── filter
+    ├── httpapi
+    ├── inventory
+    ├── lookup
+    ├── module_utils
+    ├── modules
+    ├── netconf
+    ├── shell
+    ├── strategy
+    ├── terminal
+    ├── test
+    └── vars
+```
+
+A full list of plugin types can be found at [Working With Plugins](https://docs.ansible.com/ansible-core/2.18/plugins/plugins.html).

roles/ocp4_workload_mta8/defaults/main.yml

@@ -0,0 +1,71 @@
+---
+become_override: false
+ocp_username: opentlc-mgr
+silent: false
+
+# Helm Chart to deploy
+ocp4_workload_mta8_repo: https://github.com/redhat-gpte-devopsautomation/agnosticd_workload_helm_charts.git
+# Tag to deploy
+ocp4_workload_mta8_repo_tag: main
+ocp4_workload_mta8_repo_path: mta8
+
+# Deploy the operator into each user's namespace
+ocp4_workload_mta8_deploy_operator: true
+# Tackle subscription channel to use
+ocp4_workload_mta8_channel: stable-v8.0
+ocp4_workload_mta8_starting_csv: ""
+
+# How many users to set up
+ocp4_workload_mta8_num_users: 1
+
+# Namespace base
+# If num_users == 1 then this will be the name of the namespace
+# If num_users > 1 the user base and user number will be appended to this base
+ocp4_workload_mta8_namespace_base: mta
+# UserID for Single User Setup
+ocp4_workload_mta8_user: admin
+# Base for multi user setup
+ocp4_workload_mta8_user_base: user
+
+# Role to grant users for the tackle namespace
+ocp4_workload_mta8_role: admin
+
+# Seed Tackle with information
+# When seeding is enabled authentication must be turned off
+# (until this is fixed in the operator)
+ocp4_workload_mta8_seed: false
+
+# Image for the job to seed tackle. The image must have the data to be seeded inside
+# See https://github.com/redhat-gpte-devopsautomation/tackle2-setup-container.git
+# Tag should match version of operator channel subscription
+# "stable-v2.0" -> "1.0" (legacy tag name)
+# "stable-v2.1" -> "v2.1.1" (new matching tag names)
+ocp4_workload_mta8_seed_image: quay.io/gpte-devops-automation/tackle2-setup
+ocp4_workload_mta8_seed_tag: "release-0.4-mta7"
+ocp4_workload_mta8_seed_pull_policy: IfNotPresent
+
+# These are hardcoded and can't be changed at the moment, first login requires changing
+# Disable authentication by setting ocp4_workload_mta8_feature_auth_required: false
+# ocp4_workload_mta8_user: admin
+# ocp4_workload_mta8_password: password
+
+# --------------------------------
+# Tackle V2 specific settings
+# --------------------------------
+ocp4_workload_mta8_feature_auth_required: false
+ocp4_workload_mta8_maven_data_volume_size: 10Gi
+ocp4_workload_mta8_hub_bucket_volume_size: 10Gi
+ocp4_workload_mta8_hub_database_volume_size: 5Gi
+ocp4_workload_mta8_keycloak_database_data_volume_size: 1Gi
+ocp4_workload_mta8_pathfinder_database_data_volume_size: 1Gi
+ocp4_workload_mta8_tackle_setup_user: ""
+ocp4_workload_mta8_tackle_setup_password: ""
+ocp4_workload_mta8_rwx_supported: false
+
+# --------------------------------
+# Use a Catalog Snapshot
+# --------------------------------
+ocp4_workload_mta8_catalogsource_setup: false
+ocp4_workload_mta8_catalogsource_name: redhat-operators-snapshot-mta7
+ocp4_workload_mta8_catalogsource_image: quay.io/gpte-devops-automation/olm_snapshot_redhat_catalog
+ocp4_workload_mta8_catalogsource_image_tag: v4.15_2024_03_11

roles/ocp4_workload_mta8/meta/main.yml

@@ -0,0 +1,15 @@
+---
+galaxy_info:
+  role_name: ocp4_workload_mta8
+  author:
+  - Wolfgang Kulhanek <wkulhane@redhat.com>
+  description: |
+    Deploys (and configures) the Migration Toolkit for Applications Operator on a OCP4 cluster
+  platforms: []
+  license: GNU General Public License v3.0
+  galaxy_tags:
+  - ocp4
+  - openshift
+  - mta
+  - tackle
+dependencies: []

roles/ocp4_workload_mta8/readme.adoc

@@ -0,0 +1,9 @@
+= ocp4_workload_mta8 - Deploy Migration Toolkit for Applications 8 to an OpenShift Cluster
+
+== Role overview
+
+* This role installs MTA 8 into an OpenShift Cluster.
+
+== The defaults variable file
+
+* This file ./defaults/main.yml contains all the variables you need to define to control the deployment of your workload.