How poojabhanudevops/redisdemo works
Project type and purpose
• This is an Infrastructure-as-Code (IaC) demo project (“Redisdemo”) that uses Terraform to provision AWS resources (VPC, subnets, security groups, EC2 instances, etc.) and Ansible to configure a Redis server on those EC2 instances. A Jenkinsfile suggests a CI/CD pipeline orchestrating Terraform & Ansible runs.
File structure
• Top-level:
• Jenkinsfile (CI/CD pipeline)
• ansible/ (configuration-management playbooks, handlers, templates, vars)
• playbook.yml & aws_ec2.yaml (entry points or inventory definitions)
• terraform/ (modules for VPC, subnets, security groups, instances, peering, backend.tf, provider.tf)
• Each terraform subdirectory defines a reusable module (variable.tf, main.tf, output.tf).
• ansible/templates/redis.conf.j2 holds the Redis configuration template.
README
• Minimal (“# Redisdemo”), so the key understanding comes from file names and structure.
a. Main components:
• CI/CD: Jenkins server
• IaC layer: Terraform modules
• Cloud provider: AWS (VPC, subnets, security groups, EC2)
• Configuration management: Ansible controller
• Redis service on EC2
b. Relationships & interactions:
1. Developer/PR triggers Jenkins pipeline.
2. Jenkins executes Terraform init/plan/apply against AWS (reading backend.tf, provider.tf).
3. Terraform provisions:
• VPC (terraform/vpc)
• Subnets (terraform/subnets)
• Security groups (terraform/security_group)
• VPC peering (terraform/vpc_peering)
• EC2 instances (terraform/instances)
4. Terraform outputs the inventory or host IPs (terraform/output.tf → Jenkin’s workspace).
5. Jenkins invokes Ansible (using ansible.cfg, playbook.yml or aws_ec2.yaml) to configure Redis server on the newly created EC2 host(s), applying the redis.conf.j2 template.
6. Redis is installed & configured, ready to serve.
c. Architectural patterns/design principles:
• Separation of concerns: Terraform for provisioning, Ansible for configuration.
• Modular Terraform (each AWS component in its own module).
• Declarative configuration.
• CI/CD orchestration with Jenkins.
d. Relevant technologies/frameworks:
• Terraform (HCL)
• AWS (EC2, VPC, subnets, security groups, peering)
• Ansible (YAML playbooks, Jinja2 templates)
• Jenkins pipeline