DEV Community: Winnie Fred

Oops! you cant manage Node versions

Winnie Fred — Tue, 01 Aug 2023 17:02:40 +0000

Avoid hard labor dealing with node version of different projects.
Use NVM to manage different node versions.NVM allows to install different versions depending on the project you working on via CLI.

1: In the nvm-windows repository Readme, click on "Download Now!":

2: Download and Install .exe file of the latest release.

3: check nvm version.

4: The installation process from above should automatically add the nvm configuration to your profile. If you're using zsh, that would be ~/.zshrc. If you're using bash, that would be ~/.bash_profile...or some other profile.

If it doesn't automatically add nvm configuration, you can add it yourself to your profile file:

export NVM_DIR="$([ -z "${XDG_CONFIG_HOME-}" ] && printf %s"${HOME}/.nvm" || printf %s "${XDG_CONFIG_HOME}/nvm")"[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"

5: Reload the shell configuration source ~/.bashrc

6: check nvm version: nvm -v

Note:
1: Can use nvm to install and use node versions below commands.

 nvm install latest - // install latest version
 nvm install vX.Y.Z - // install specific version
 nvm alias default vX.Y.Z - // set default version
 nvm use vA.B.C - // use a specific version

How to Install Ansible on Ubuntu

Winnie Fred — Mon, 12 Jun 2023 20:22:08 +0000

Ansible is an open-source platform used for automation and various operations such as configuration management, application deployment, task automation and IT orchestration.

How does Ansible work?

Ansible uses the concepts of control and managed nodes. It connects from the control node any machine with Ansible installed to the managed nodes sending commands and instructions to them.

Key concepts

Modules are units of code that Ansible executes on the managed nodes.Each module is invoked by a task.
Task is a call to an Ansible module.
Plays are a series of Ansible tasks or roles mapped to group of hosts in the inventory.
Playbooks are series of plays that explain what to run and are written in YAML.
Inventory is a collection of all the hosts and groups that Ansible manages.it can be in a static file(.ini files) in simple cases or pull inventory from remote sources such as cloud providers.
Role is a standard directory structure for specifying tasks and variables.Playbooks can be broken up into roles for modularity and reuse.
Host is a remote machine managed by Ansible
Group several hosts grouped together that share common attribute.
Handlers used to perform actions on a service such as restarting or stopping a service that is actively running on the managed node's system.Handlers are triggered by tasks and their execution happens at the end of a play after all tasks are finished.

How to install Ansible
1: Setting up python 3:

sudo apt update
sudo apt -y upgrade
python -V

2: Setting up pip3:

sudo apt install -y python3-pip

3: There are a few more packages and development tools to install to ensure that you have a robust setup for your programming environment:

sudo apt install -y build-essential libssl-dev libffi-dev python3-dev

4: Setting up Ansible

sudo apt -y install software-properties-common
sudo apt-add-repository ppa:ansible/ansible
sudo apt update
sudo apt install ansible

Configuration Managament & IaC

Winnie Fred — Sun, 11 Jun 2023 17:37:35 +0000

Configuration Management

Configuration management is commonly referred to as IT Automation or Server Orchestration.

CM ensures application implementation, function and performance.
CM is key to DevOps because it can be automated with code to accomplish common tasks instead of relying on manual intervention.
CM uses Ansible to integrate with OCI DevOps service.

Infrastructure as Code (IaC)

IaC defines, configures and provisions infrastructure using readable code, eliminating the need for manual system setup.
IaC is a key DevOps practice that allows for infrastructure automation, which works together with the continuous delivery model.
IaC uses Terraform to integrate OCI DevOps service

There are 3 main task categories:
1: Infrastructure provisioning
- Spinning up new servers
- Network configuration
- Creating load balancers
- Configuration on infrastructure level

2: Configuration of provisioned infrastructure
- Installing applications on servers
- Managing the apps
- Prepare the infrastructure/servers to deploy the app

3: Deployment of application

Distinction of phases

Initial setup phase	Maintaining phase
Provision infrastructure	Adjustment to infrastructure
Configure infrastructure	Add and remove servers
Initial installation of software	Update software
Initial configuration of software	Re-configuration of software

Difference of IaC tools
1: Automate tasks in different categories for different phases
2: Combination of 2 or more IaC tools. Example terraform does the initial infrastructure setup and manage infrastructure but also it can also do initial application setup.However Ansible can configure and management applications but also can configure already managed infrastructure

Note: Infrastructure as code asks, what resources are there? And configuration management asks, how are they configured?

Hence its recommended to use Terraform for provisioning and de-provisioning and Ansible for configuration, patching, deployment, and maintenance.

Ansible	Terraform
Is a Configuration Management tool	Is a Infrastructure as Code tool
Support mutable infrastructure	Support immutable infrastructure
Works via SSH	Works via API calls
Follows procedural language	Follows declarative language

Benefits of configuration management for servers comes from defining infrastructure as code. This enables you to:

1: Use a version control system to keep track of any changes in your infrastructure.
2: Reuse provisioning scripts for multiple server environments such as development, testing and production.
3: Share provisioning scripts between coworkers to facilitate collaboration in a standardized development environment.
4: Streamline the process of replicating servers which facilitates recovery from critical errors.

DevOps Introduction

Winnie Fred — Sun, 11 Jun 2023 14:31:04 +0000

Overview

DevOps is the use of collaboration, automation and continuous practices to achieve continuous delivery of high quality software. It's a paradigm shift from traditional software development.

DevOps pervades everything from deployment and testing of software to the architecture of the software itself.

DevOps Lifecycle

What is the DevOps lifecycle look like? To get concrete about the tasks involved, it looks at software development in eight phases-- plan, code, build, test, release, deploy, operate, and monitor.

DevOps Life Cycle is a rapid-release, multi-phased SDLC with a strong feedback loop.

First, agile development is a bit of a predecessor to DevOps. It's an approach to software development that emphasizes a lightweight, rapid release life cycle.

Second, Continuous integration is the practice of developers integrating all of their work together as soon as possible in the life cycle. For example, if I push a change to code, it should automatically build the whole system with that change and run a suite of automated tests.

Third, Continuous delivery is the practice of quickly getting code changes from developers to users. For example, if I push a change to code and it passes all of the automated tests, I should be able to seamlessly push that change to QA and production environments.

Finally, benefits of adopting DevOps, it encourages the culture of collaboration, it makes for higher quality technology, and it enables better flexibility around the business. All of the hype around DevOps is because software developed with traditional methods just can't keep up with software developed with DevOps.

DevOps as a service

DevOps as a service - CI/CD platform for developers to automate their SDLC

To get an idea of the DevOps ecosystem, let's take a look at an example DevOps workflow.

1: A team could plan out their coding process on software such as Jira to track issues to fix and features to implement.

2: Then they'll manage code versioning with git and commit to a centralized repository in GitHub or GitLab.

3: From there, they can build their code with a program like gradle or maven and test it with a program like Selenium.

4: Once they've arrived at code they want to deploy, it might be containerized with Docker and rolled out to infrastructure via an orchestration tool like Kubernetes. The infrastructure itself could be provisioned by Terraform and configured by Ansible.

5: As the application runs, it could be monitored by a program like Grafana. A full cycle of this can be run monthly, weekly, or less based on the business.

Finally, a CI/CD program like Jenkins could tie it all together by allowing one phase to automatically trigger another. Obviously, that's just an example, and it'll vary widely per team and per project. But what you might note is that there are lots of moving parts here. And figuring out how to integrate them together on a given platform is non-trivial.This is where DevOps as a service comes in.

The idea of DevOps as a service is basically to prepackage all of the necessary tools together and put a single pane of glass in front of them. So it collapses the DevOps workflow into a single silo and provides lots of pre-built automation.