Automated provisioning of Elastic Stack using docker, Ansible and Jenkins
Budget: ₹1,500 – ₹12,500 INR
I want to automatically deploy and configure containerized Elastic Stack following Infrastructure as Code (IaC) and Configuration as Code (CaC) approach, so that I can benefit from the end-to-end monitoring and logging capabilities for my cloud-ready applications.
Functional requirements:
CI/CD pipeline with fully automated deployment and configuration of Elastic search, Logstash, Kibana and Beats containers following Infrastructure as Code (IaC) and Configuration as Code (CaC) approach.
Use Ansible for setting up local environment for setting up used CI-CD Tools.
All code is stored in Version Control (Git) and has a configured Web Hook, which triggers a Jenkins job (i.e. CI/CD pipeline)
Jenkins job automates the build, test and deployment of all Elastic components simulated in a local environment using Jenkins file (Groovy)
Configuration update of any Elastic components must retrigger re-deployment of the component with new configuration.
Non-functional requirements:
All the automated test cases created finish successfully and are incorporated in the CI/CD pipeline - – Tests must be written using Python.
The test suite includes infrastructure tests, functional tests, integration test and performance tests (others are optional).
Security checks are also included in the CI / CD pipeline (static and dynamic code analysis)
Documentation is provided with a simple architectural diagram of the target automation solution.
Functional requirements:
CI/CD pipeline with fully automated deployment and configuration of Elastic search, Logstash, Kibana and Beats containers following Infrastructure as Code (IaC) and Configuration as Code (CaC) approach.
Use Ansible for setting up local environment for setting up used CI-CD Tools.
All code is stored in Version Control (Git) and has a configured Web Hook, which triggers a Jenkins job (i.e. CI/CD pipeline)
Jenkins job automates the build, test and deployment of all Elastic components simulated in a local environment using Jenkins file (Groovy)
Configuration update of any Elastic components must retrigger re-deployment of the component with new configuration.
Non-functional requirements:
All the automated test cases created finish successfully and are incorporated in the CI/CD pipeline - – Tests must be written using Python.
The test suite includes infrastructure tests, functional tests, integration test and performance tests (others are optional).
Security checks are also included in the CI / CD pipeline (static and dynamic code analysis)
Documentation is provided with a simple architectural diagram of the target automation solution.