Skip to content

Tensorflow, Ansible (AWX), K8, Docker; best practices

License

Notifications You must be signed in to change notification settings

bluewitch/DevOps_SRE

Repository files navigation

DevOps_SRE

SRE (Site Reliability Engineering)

  • devops_installation.sh for setting up DevOps on a fresh Ubuntu Unit, includes Tensorflow, Ansible (AWX), K8, Docker; best practices

Save the script in a file (e.g., devops_installation.sh), make it executable using chmod +x devops_installation.sh

  • privacy_installation.sh for setting up network privacy and secure reliable browsers

Save the BASH script in a file (e.g., privacy_installation.sh), make the BASH script executable using chmod +x privacy_installation.sh, and then run it with sudo ./privacy_installation.sh. The script will install Firefox, LibreWolf (a privacy-oriented and hardned fork of Firefox), Mullvad VPN (a privacy-focused VPN service, this is a paid service), Chrome, Brave (a privacy-focused web browser) I have issues with the Brave tokenomics and KYC mandates, I2Pd (an anonymous overlay network), and TOR (an anonymity network for web browsing) on your Ubuntu Linux system.

SRE and DevOps Implementation

This repository provides BASH scripts for setting up applications on Ubuntu Linux and aims to explain the concepts of Site Reliability Engineering (SRE) and DevOps, their interrelation, and strategies for implementing them effectively.

Definitions

Site Reliability Engineering (SRE)

Site Reliability Engineering (SRE) is an operational approach that combines software engineering practices with IT operations to create scalable and reliable systems. SRE focuses on automating tasks, monitoring systems, and ensuring high availability, performance, and fault tolerance.

DevOps

DevOps is a set of practices that foster collaboration between development and operations teams to deliver software applications more rapidly and reliably. It emphasizes automation, continuous integration, continuous delivery, and close collaboration throughout the software development lifecycle.

Interrelation between SRE and DevOps

SRE and DevOps are closely related and share common goals, principles, and practices. While DevOps focuses on the cultural and organizational aspects of software development and operations, SRE provides a specific implementation approach for achieving those goals. SRE can be seen as a specialized subset of DevOps, with a strong emphasis on reliability and automation.

SRE borrows many principles from DevOps, such as infrastructure as code, automated testing, continuous integration and delivery, and blameless postmortems. SRE practitioners collaborate closely with development teams to design and build reliable systems, leveraging automation and monitoring to ensure resilience and scalability.

Optimized Strategies for SRE and DevOps Implementation

To implement solid and effective SRE and DevOps practices, consider the following strategies:

  1. Culture of Collaboration: Foster a culture of collaboration and communication between development and operations teams. Encourage shared responsibility and accountability for delivering reliable and scalable software. just remember SRE impliments DevOps

  2. Automation: Emphasize automation to reduce manual and error-prone tasks. Automate deployment, testing, and monitoring processes to increase efficiency, repeatability, and reliability. BASH scripts and Python are key for this.

  3. Monitoring and Alerting: Implement comprehensive monitoring and alerting systems to proactively identify and resolve issues. Utilize tools such as Prometheus and Grafana to gain insights into system performance and health. Also AWS has CloudWatch, because, you know Amazon.

  4. Infrastructure as Code: Use infrastructure as code tools like Terraform or Ansible to define and provision infrastructure resources. This ensures consistency and reproducibility across environments.

  5. Continuous Integration and Delivery aka CICD: Adopt continuous integration and delivery practices to enable rapid and frequent releases. Automate build, testing, and deployment processes to reduce time to market and increase quality.

  6. Postmortems and Incident Response: Conduct blameless postmortems after incidents to identify root causes and implement preventive measures. Establish effective incident response processes to minimize downtime and improve system resilience.

BASH Script Explanation and Use Case

This repository includes BASH scripts for installing and setting up applications on Ubuntu Linux. These scripts automate the installation and configuration processes for various tools such as Firefox, LibreWolf, Mullvad VPN, Chrome, Brave, I2Pd, and TOR. Because they are the best current standards.

The BASH scripts are designed to simplify the setup of these applications on an Ubuntu Linux system. Each script installs the respective application using the appropriate package manager commands, repositories, or binary downloads. The scripts also handle dependencies and perform any necessary configurations or cleanup tasks.

To use the scripts, simply run them with administrator privileges using the sudo command, and follow any prompts or instructions provided. For example, to install astar_installation.sh, execute the script astar_installation.sh with sudo ./astar_installation.sh. Do not forget to make the BASH script executable with chmod +x astar_installation.sh on the terminal.

About

Tensorflow, Ansible (AWX), K8, Docker; best practices

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages