How bhasker-manikyala/purdue_b35 works
Project type and purpose
• This repository is a DevOps “playground” monorepo, containing infrastructure-as-code, CI/CD pipelines, container definitions, orchestration manifests, monitoring recipes, and assorted scripts for learning and demonstration. It is not a single application but a collection of modules covering Ansible, Terraform hints, Docker, Kubernetes, Jenkins, Git, Puppet, Nagios, Splunk, cloud (AWS/GCP) setup, and more.
Key components
a. Version Control (Git)
– git directory with samples, install scripts, server config.
b. CI/CD (Jenkins)
– Jenkins master, build agents, Pipeline-as-Code (Jenkinsfiles), Artifactory/JFrog.
c. Configuration Management
– Ansible control node, inventories/playbooks/roles, Puppet master/agent examples.
d. Containerization
– Docker daemon, Dockerfiles under docker/images, Docker Compose services, Swarm stacks.
e. Orchestration
– Kubernetes cluster (master, worker nodes), manifests (deployments, services, ingress, HPA), dashboard.
f. Infrastructure (Cloud)
– AWS & GCP provisioning scripts, EC2 instance setup, Terraform pointers.
g. Monitoring & Logging
– Nagios Core/xi containers, Splunk forwarders & search.
h. Sample Applications
– Java/Tomcat, Spring Boot/Mongo, Nginx/Apache, WordPress, sample WAR/JARs.
Relationships & interactions
• Developer commits code to Git → webhook triggers Jenkins pipeline → Jenkins checks out repo → builds artifacts (JAR/WAR) → builds Docker images → pushes to registry → deploys to Docker Compose or Swarm or publishes Helm charts for Kubernetes cluster.
• Ansible/Puppet orchestrates configuration of VMs or nodes on cloud providers, installs Docker, Kubernetes prerequisites, SSH keys.
• Kubernetes ingress/load-balancer routes external traffic to services; HPA scales pods.
• Nagios monitors health of nodes/containers; Splunk collects logs from apps and infra.
Architectural patterns and principles
– Immutable infrastructure: pipelines build fresh images.
– Infrastructure as Code: all configuration in YAML/Playbooks/Manifests.
– GitOps flavour: manifests versioned in Git.
– Modular roles/playbooks in Ansible; layered Dockerfiles.
– Microservice abstraction in K8s (Deployments + Services + Ingress).