Hi Frndz,

Today Technotes

Domain - Devops

Ansible-playbook

Runs Ansible playbooks, executing the defined tasks on the targeted hosts.

📘Synopsis

📕Description

📗Common Options

📙Environment

📒Files

https://docs.ansible.com/ansible/latest/cli/ansible-playbook.html

Regards
Hi-tech Team

Hi Friends,
Today Technotes
Domain : Azure Devops
Best DevOps Tools In 2021
Comparison Of The Top DevOps Software Tools
#1) Kamatera
#2) ActiveControl
#3) Nagios
#4) Chef
#5) Jenkins
#6) Vagrant
#7) Splunk
#8) Git – Version Control Tool
#9) Ansible
#10) Prometheus
#11) Ganglia
#12) Snort
#13) Pagerduty
#14) Puppet
#15) Gulp
Thanks & Regards,
Hitech Team

What is python Boto3?
Boto3 is the name of the Python SDK for AWS. It allows you to directly create, update, and delete AWS resources from your Python scripts.
Installing Python Boto3 to interact with AWS
1. Yum install python
2. wget http://bootstrap.pypa.io/get-pip.py
3. Python get-pip.py
4. Pip install boto3

Client versus Resource in Boto3
At its core, all that Boto3 does is call AWS APIs on your behalf. For the majority of the AWS services, Boto3 offers two distinct ways of accessing these abstracted APIs:
Client: low-level service access
Resource: higher-level object-oriented service access
Client
Clients provide a low-level interface to the AWS service. Their definitions are generated by a JSON service description present in the botocore library. The botocore package is shared between boto3 as well as the AWS CLI. The service definition for AWS S3 is stored as a JSON under the botocore package
import boto3
s3_client = boto3.client('s3')

Resources
Resources are a higher-level abstraction compared to clients. They are generated from a JSON resource description that is present in the boto library itself.
Resources provide an object-oriented interface for interacting with various AWS services. Resources can be instantiated like the following:
import boto3

How to Integrate Your GitHub Repository to Your Jenkins Project
The integration presented in this blog post will teach you to:
1)Schedule your build
2)Pull your code and data files from your GitHub repository to your Jenkins machine
3)Automatically trigger each build on the Jenkins server, after each Commit on your Git repository
Configuring GitHub:
Step 1: go to your GitHub repository and click on Settings.
Step 2: Click on Webhooks and then click on Add webhook.
Step 3: In the Payload URL field, paste your Jenkins environment URL. At the end of this URL add /github-webhook/. In the Content type select: application/json and leave the Secret field empty.
Step 4: In the page Which events would you like to trigger this webhook? choose Let me select individual events. Then, check Pull Requests and Pushes. At the end of this option, make sure that the Active option is checked and click on Add webhook.
Configuring Jenkins:
Step 5: In Jenkins, click on New Item to create a new project.
Step 6: Give your project a name, then choose Freestyle project and finally, click on OK.
Step 7: Click on the Source Code Management tab
Step 8: Click on Git and paste your GitHub repository URL in the Repository URL field.
Step 9: Click on the Build Triggers tab and then on the GitHub hook trigger for GITScm polling. Or, choose the trigger of your choice.
Triggering the Jenkins Job to Run with Every Code Commit:
Step 10: Click on the Build tab, then click on Add build step and choose Execute shell.
Step 11: To run a Taurus test, simply use the bzt command, followed by the name of your YML file and click on Save.
Step 12: Go back to your GitHub repository, edit the Taurus script and commit the changes. We will now see how Jenkins ran the script after the commit.
Step 13: Go back to your Jenkins project and you'll see that a new job was triggered automatically from the commit we made at the previous step. Click on the little arrow next to the job and choose Console Output.

https://www.blazemeter.com/blog/how-to-integrate-your-github-repository-to-your-jenkins-project