Merge pull request #8 from RanabirChakraborty/validated_content_fix-1

Removing AWS from the collection and making it general

README.md

@@ -2,24 +2,23 @@
 
 [![CI](https://github.com/ansible-middleware/rhbk-ha-cluster/actions/workflows/ci.yml/badge.svg)](https://github.com/ansible-middleware/rhbk-ha-cluster/actions/workflows/ci.yml)
 
-Provision and deploy a Red Hat Build of Keycloak authentication service on multiple AWS regions via Ansible
+Provision and deploy a Red Hat Build of Keycloak authentication service on multi-region clusters via Ansible
 
 ### Use case of rhbk-ha-cluster collection
 
-The primary use case of the `rhbk-ha-cluster` collection is to install Red Hat Build of Keycloak (RHBK) with high availability (HA) across multiple AWS regions. This ensures that the authentication service is resilient, fault-tolerant, and capable of serving users even in the event of a regional failure. By leveraging AWS infrastructure, the collection automates the setup of RHBK in a highly available architecture, integrating with Data Grid for distributed caching and ensuring smooth, secure authentication.
+The primary use case of the `rhbk-ha-cluster` collection is to install Red Hat Build of Keycloak (RHBK) with high availability (HA) across multi-region clusters. This ensures that the authentication service is resilient, fault-tolerant, and capable of serving users even in the event of a regional failure. The collection automates the setup of RHBK in a highly available architecture, integrating with Data Grid for distributed caching and ensuring smooth, secure authentication.
 
 ### 0. prerequisites
 
-* The two regions that will host the authentication service (ie. us-east-1 and us-west-2)
-* An AWS account with permissions on `ec2` on said regions with default profile in $HOME/.aws/credentials that will be used to provision ec2 compute nodes
-* A database service that can be accessed from the deployment regions; or otherwise, `rds` permissions on the AWS account so an Aurora service can be provisioned
+* Setup multi-region clusters infrastructure.
+* A database service that can be accessed from the deployment regions.
 * TLS certificates for the desired domain name to provide the authentication service
 
 ### 1. create ansible.cfg
 
 ```
 [defaults]
-remote_user=ec2-user
+remote_user=<ssh_user>
 private_key_file=<path_to_private_key>
 host_key_checking=False
 gathering=smart
@@ -39,23 +38,13 @@ token=<automation_hub_token>
 
 Set the `token` to the value you get after authentication on automation hub.
 
-
 ### 2. install dependencies
 
 The following command will download and install the dependencies.
 
     # pip install -r requirements.txt
     # ansible-galaxy collection install -r requirements.yml
 
-
-### 3. create key pair
-
-This key pair will be used by ansible to connect to the EC2 instances.
-
-* Paste the path to the private key in ansible.cfg option `private_key_file`
-* Copy the public key file to `files/id_rsa_aws.pub`
-
-
 ### 4. domain names and certificates
 
 * Update the configuration to reflect your domain and certificate details for secure access.
@@ -64,16 +53,12 @@ This key pair will be used by ansible to connect to the EC2 instances.
 
 To edit the configuration, you would need to modify the ansible.cfg file and relevant playbook variables. This includes:
 
-* Setting the private_key_file path in ansible.cfg to allow Ansible to connect to EC2 instances.
-* Specifying AWS regions, database information, and TLS certificates in the playbooks or group variables (typically located in group_vars/).
+* Provide Ansible Automation Hub token in ansible.cfg
+* Database information, and TLS certificates in the playbooks or group variables (typically located in group_vars/).
 * Configuring other parameters like the domain names for Keycloak and Data Grid.
 
 These configurations ensure the infrastructure is tailored to your specific setup requirements before provisioning and deploying.
 
-### 6. run the infra provisioning
-
-Inside `playbooks/roles` path we have `infra-up.yml` and `infra-down.yml` run both according to you need.
-
 ### 7. run the deployment of data_grid and rhbk
 
 Inside `playbooks/roles` path we have `deploy.yml` playbook to deploy data_grid and rhbk.

galaxy.yml

@@ -1,11 +1,12 @@
 ---
 namespace: infra
-name: rhbk_datagrid_aws
+name: rhbk_ha_cluster
 version: "1.0.0"
 readme: README.md
 authors:
   - Guido Grazioli <[email protected]>
-description: Provision and deploy a Red Hat Build of Keycloak multi-regional authentication service on AWS
+  - Ranabir Chakraborty <[email protected]>
+description: Provision and deploy a Red Hat Build of Keycloak multi-regional authentication service on clusters.
 license_file: "LICENSE"
 tags:
   - keycloak
@@ -23,8 +24,8 @@ tags:
   - middleware
   - datagrid
   - infinispan
-  - AWS
   - a4mw
+  - cluster
 dependencies:
   "redhat.rhbk": ">=2.0.0"
   "redhat.data_grid": ">=1.1.4"

inventory/group_vars/all.yml

@@ -2,9 +2,6 @@
 jvm_package: java-17-openjdk-headless
 domain_name: '.internal.ansiblemiddleware.com'
 external_domain_name: 'rhbk.demos.ansiblemiddleware.com'
-regions:
-  - eu-central-1
-  - us-east-2
 resource_tags:
   Environment: rhbk-ha-cluster
   Application: rhbk

inventory/group_vars/eu_central_1.yml

@@ -1,3 +1,3 @@
 ---
-aurora_endpoint: rhbk-ha-cluster.cluster-cqy2krcosm24.eu-central-1.rds.amazonaws.com:5432
+db_endpoint: rhbk-ha-cluster.cluster-cqy2krcosm24.eu-central-1:5432
 data_grid_jgroups_relay_site: eu-central-1

inventory/group_vars/rhbk.yml

@@ -2,7 +2,7 @@
 rhbk_ha_enabled: True
 rhbk_frontend_url: "https://{{ external_domain_name }}/auth/"
 rhbk_jdbc_engine: postgres
-rhbk_jdbc_url: "jdbc:postgresql://{{ aurora_endpoint }}/keycloak?socketTimeout=10000"
+rhbk_jdbc_url: "jdbc:postgresql://{{ db_endpoint }}/keycloak?socketTimeout=10000"
 
 rhbk_db_user: keycloak
 rhbk_configure_firewalld: True

inventory/group_vars/us_east_2.yml

@@ -1,3 +1,3 @@
 ---
-aurora_endpoint: rhbk-datagrid-global-cluster-1.cluster-cpthunyvi99s.us-east-2.rds.amazonaws.com:5432
+db_endpoint: rhbk-datagrid-global-cluster-1.cluster-cpthunyvi99s.us-east-2:5432
 data_grid_jgroups_relay_site: us-east-2