How zquan315/nt548-devops-project works
Project type and purpose
• From the name “NT548-DevOps-Project” and the absence of application source files, we infer that this is primarily a DevOps‑focused repository. Its goal is likely to define and automate the build, test, release, and deployment pipelines (CI/CD), plus the provisioning of infrastructure-as-code and post‑deployment monitoring.
(minimal) file structure
• Right now the only file is README.md, but in a typical DevOps repo you’d expect:
– ci/ or .github/workflows/ (CI definitions)
– infra/ (Terraform, CloudFormation, Ansible playbooks)
– scripts/ (shell, Python helpers)
– deployment/ (Kubernetes YAML, Helm charts, Dockerfiles)
– monitoring/ (Prometheus rules, Grafana dashboards)
README for additional insights
a. Main components
– Source Code Repository (GitHub/GitLab)
– Continuous Integration Server (Jenkins, GitHub Actions, GitLab CI)
– Artifact/Container Registry (Artifactory, Nexus, Docker Hub)
– Infrastructure as Code (Terraform/Ansible)
– Deployment Platform (Kubernetes cluster, VMs, serverless)
– Testing Framework (unit, integration, smoke tests)
– Monitoring & Logging (Prometheus, Grafana, ELK)
– Notification System (Slack, email, PagerDuty)
b. Relationships and interactions
– Developers commit code → triggers CI pipeline
– CI builds artifacts/containers → pushes to registry
– Infrastructure-as-Code modules apply → provisions or updates environments
– CD pulls new images/configs → deploys to staging/production
– Monitoring agents collect metrics/logs → dashboards & alerts
– Alerts flow to Notification system → Ops on call
c. Architectural patterns/ design principles
– Pipeline-as-Code (CI/CD defined alongside source code)
– Immutable infrastructure (build once; promote same artifact between envs)
– Infrastructure-as-Code (declarative provisioning)
– Separation of concerns (build, test, deploy, monitor are discrete stages)
– GitOps approach (pull-based delivery from git)
d. Key technologies/frameworks
– GitHub/GitLab
– Jenkins / GitHub Actions / GitLab CI
– Terraform / Ansible
– Docker + Kubernetes (or other container orchestration)
– Prometheus, Grafana, ELK Stack
– Slack / PagerDuty
Detail without over‑segmentation
– Capture each pipeline stage as its own component.
– Include the artifact lifecycle: build artifact → registry → deploy → runtime.