Installation

Full Stack Installation Guide – For Beginners

A BEGINNER’S GUIDE TO FULL STACK INSTALLATION How to Install Visual Studio Code: Download the VS Code le from the Ofcial Website. 1. Execute the download le. 2. Accept the Terms & Conditions. 3. Click on the Install button. 4. Wait for the installation to complete. 5. Click on the Launch button to start it. Steps to Install Visual Studio Code: Step 1: Visit the Ofcial Website of the Visual Studio Code using any web browser like Google Chrome, Microsoft Edge etc.. Step 2: Press the “Download for Windows” button on the website to start the download of the Visual Studio Code Application. Step 3: When the download nishes, then the Visual Studio Code Icon appears in the downloads folder. Step 4: Click on the Installer icon to start the installation process of the Visual Studio Code. Step 5: After the Installer opens, it will ask you to accept the terms and conditions of the Visual Studio Code. Click on I accept the agreement and then click the Next button. Step 6: Choose the location data for running the Visual Studio Code. It will then ask you to browse the location. Then click on the Next button. Step 7: Then it will ask to begin the installation setup. Click on the Install button. Step 8: After clicking on Install, it will take about 1 minute to install the Visual Studio Code on your device. Step 9: After the Installation setup for Visual Studio Code is nished, it will show a window like this below. Tick the “Launch Visual Studio Code” checkbox and then click Next. Step 10: After the previous step, the Visual Studio Code window opens successfully. Now you can create a new le in the Visual Studio Code window and choose a language of yours to begin your programming journey! So this is how we successfully installed Visual Studio Code on our Windows system. The steps mentioned in the above guideline can be used in any kind of Windows Browsers for Downloading & Installation VS Code on Windows 10. So, try these steps to get the VS Code IDE on your device as well. Installation of Node JS: You have to follow the following steps to install the Node.js on your Windows : Step 1: Download the NodeJS Downloading the Node.js ‘.msi’ installer the rst step to install Node.js on Windows is to download the installer. Visit the ofcial Node.js website i.e) https://nodejs.org/en/download/ Step 2: Go to Prebuilt Installer and Select the Versions: You can select the required version or can download the Long Time Support version.Click on Download button to download the node version. Step 2: Running the Node.js Installer Now you need to install the node.js installer on your PC. You need to follow the following steps for the Node.js to be installed: Double-click on the .msi installer The Node.js Setup wizard will open. Welcome To Node.js Setup Wizard Select “Next” After clicking “Next”, the End-User License Agreement (EULA) will open. Check “I accept the terms in the License Agreement” Select “Next” Destination Folder Set the Destination Folder where you want to install Node.js & Select “Next”. Custom Setup Select “Next” Ready to Install Node.js. The installer may prompt you to “install tools for native modules”. Select “Install” Do not close or cancel the installer until the installation is complete. Complete the Node.js Setup Wizard. Click “Finish” Step 4: Verify that Node.js was properly installed or not To check that node.js was completely installed on your system or not, you can run the following command in your command prompt or Windows Powershell and test it:- C:\Users\Admin> node -v If node.js was completely installed on your system, the command prompt will print the version of the Node JS installed. Step 5: Updating the Local npm version You can run the following command, to quickly update the npm npm install npm –global // Updates the ‘CLI’ client How to install MySQL: Step 1: Go to the ofcial website of MySQL and download the community server edition software. Here, you will see the option to choose the Operating System, such as Windows. Step 2: Next, there are two options available to download the setup. Choose the version number for the MySQL community server, which you want. If you have good internet connectivity, then choose the mysql-installer-web-community. Otherwise, choose the other one. Installing MySQL on Windows: Step 1: After downloading the setup, unzip it anywhere and double click the MSI installer .exe le. It will give the following screen: Step 2: In the next wizard, choose the Setup Type. There are several types available, and you need to choose the appropriate option to install MySQL product and features. Here, we are going to select the Full option and click on the Next button. This option will install the following things: MySQL Server, MySQL Shell, MySQL Router, My SQL Workbench, MySQL Connectors, documentation, samples and examples, and many more. Step 3: Once we click on the Next button, it may give information about some features that may fail to install on your system due to a lack of requirements. We can resolve them by clicking on the Execute button that will install all requirements automatically or can skip them. Now, click on the Next button. Step 4: In the next wizard, we will see a dialog box that asks for our conrmation of a few products not getting installed. Here, we have to click on the Yes button. After clicking on the Yes button, we will see the list of the products which are going to be installed. So, if we need all products, click on the Execute button. Step 5: Once we click on the Execute button, it will download and install all the products. After completing the installation, click on the Next button. Step 6: In the next wizard, we need to congure the MySQL Server and Router. Here, I am not going to congure the Router because there is no need to use it with MySQL. We

Full Stack Installation Guide – For Beginners Read More »

How to download Redhat Certification

To Download the Redhat Certification, Follow the below steps : Step 1: Login to redhat.com Step 2 : Click on Certifications Step 3 : Click on Privacy Settings Under I want to be visible in search , click on Yes Step 4 : Login to credly.com If you do not have an account , create one Step 5 : Find your badge in the dashboard It may take even 24 hours to reflect in Dashboard , after enabling the option in redhat.com privacy settings

How to download Redhat Certification Read More »

Installing VirtualBox on Windows

  To install VirtualBox on Windows , you must first download the appropriate installation file for your host. link:https://www.virtualbox.org/wiki/Downloads Download the windows host Double-click the file to launch the VirtualBox Setup wizard. Click Next on the first screen. This action tells the Wizard that you want to install VirtualBox.   Do the following actions on the Custom Setup screen. You’ll see a list of the features the Wizard will install. In this example, leave the default selection. Browse and select the location you want to install VirtualBox in. The default location is fine, but feel free to change it if you prefer. Click Next when you’re ready to continue. On the next screen, you’ll see a warning about networking. The setup process will install a virtual network adapter, which may cause your network connection to disconnect momentarily. Click Yes to continue. Finally, you’ll see a screen asking you to confirm the installation. Click Install to install VirtualBox on Windows The installation process takes several minutes, depending on your system speed. Click Finish to close the Wizard after the installation and start using VirtualBox.   After you install VirtualBox on Windows , your can create your first virtual machine. First, decide the OS which you want to install and download the iso image file. Incase if you want to setup Redhat VM, first create a Redhat personal account. link:https://developers.redhat.com/products/rhel/download select login–>Register–> select as personal account and provide all the mandatory fields and  select create account. link:https://access.redhat.com/downloads/content/rhel Login with the account created in the above portal and download the following iso image from the products section. Creating Your First Virtual Machine click the New button in the top-right corner of the VirtualBox window. This action brings up the Create Virtual Machine wizard. This Wizard lets you configure your new VM with the settings you want. Select the iso image which we downloaded and provide a name for your virtual machine. Click on next If required change the username and password and click next. Since its an unattended installation we can continue with the default values else you have to change the values depending upon your requirement.   Click on finish to set up the virtual machine. Select Redhat and then click on -> settings -> storage and click on controller:IDE select the iso and click ok   click on start to get into the virtual machine press enter or leave for automaticboot Select the language Under system select Installation Destination Under user settings select Root password and and then enter the password required and click on done at the top. Under user settings select Create user and and then enter the username and password required and click on done at the top. click on Begin installation. Login with the user account which you have created click on activities and terminal You can see the terminal page like this with the prompt, where we will be working on with the commands.  

Installing VirtualBox on Windows Read More »

How To Install Blue Ocean In Jenkins

Blue Ocean is a new user experience for Jenkins. Blue Ocean makes Jenkins, and continuous delivery, approachable to all team members. 1. Login to your Jenkins server 2. Click Manage Jenkins in the sidebar then Manage Plugins 3. Choose the Available tab and use the search bar to find Blue Ocean 4. Click the checkbox in the Install column 5. Click either Install without restart or Download now and install after restart 6. After you install Blue Ocean, you can start using it by clicking on Open Blue Ocean in the navigation bar of the Jenkins web UI That’s it !! . Navigate around the pipeline , create new pipeline and watch out for the intuitive and helpful BlueOcean UI

How To Install Blue Ocean In Jenkins Read More »

installation, composition, abstraction-614963.jpg

Guidelines To Migrate From Self- Managed Kubernetes In AWS To Amazon EKS

Migration Migration — yet another usual term on the crowded streets of Software Architecture. Migration tasks in a Software Industry can be hectic, time-consuming, or painful involving multiple resources to get engaged, collaborate, and achieve the end-goal of Migrating our components to a newer environment. Though it is exhaustive, the journey as part of any Successful Migrations involves in-depth Learning, effective Knowledge sharing, constructive Collaboration with a focused Roadmap and Planning. In this blog, we will look into how we approached our major challenging Migration task of moving away from Self-Managed Kubernetes running in EC2 to AWS Managed Kubernetes service EKS. First Question, Why? When this task was initially discussed, the first basic question which came in everyone’s mind (Developer, Devops Engineer, AWS Architect, Manager) was Why to Migrate? Yes, the existing Self-Managed Kubernetes environment in EC2 was running without a downtime but there were so many incidents not noticeable to other Engineers were observed by Kubernetes Admin team. Few Issues: 1. Multi-master setup with 3 Master nodes faced CPU hikes resulting in 2/3 nodes becoming faulty. 2. During High profile Events, the networking component Calico couldn’t scale in proportion to the Kubernetes workloads. 3. Nodes Autoscaling was taking a long time because of Older Generation AMI’s configured for worker Nodes. 4. Kubernetes version was Outdated. It was felt risky to do a version upgrade. 5. No regular Security patching was done in the Infrastructure components. Best Fit Solution: Moving to a Managed Service Model. As our Kubernetes cluster was already setup in Amazon EC2 instances, moving to AWS based solution was preferred and we chose Elastic Kubernetes Service (EKS). Migration Consideration: • Know your existing cluster – o Current Kubernetes version to check compatibility of APIs o Cluster Provisioning method (kops, kubeadm, or any) o Cluster Add-ons o Autoscaling Configurations o What Kubernetes Objects deployed in Namespaces — daemonset, deployments, statefulsets, cronjob, etc o Volume Information — PV and PVC o Network Policies, Cluster Accessibility and Security Group Rules (Ports, Firewalls, Routing) o Kubernetes certs Management o RBAC — How Authentication and Authorisation is taken care o High Availability Quotient or Configurations o Worker Nodes Firewall configurations o Namespace Information and Resource Management (Quotas) o Workload Deployment Information • How to Build EKS Cluster? There are Multiple ways (AWS suggested or third party software) to Create and Manage EKS cluster like EKS Blueprint, eksctl, AWS Management Console, AWS CLI • EKS being an upstream Kubernetes, similar to Kubernetes it doesn’t support Muti-Tier architecture but this can be achieved by Isolating the Customers using Namespace. • EKS Add-on Management — EKS Blueprint has good integration with ArgoCD which can be used to manage the Workloads and Add-ons. It automatically creates the required IAM roles, does installation via Helm charts. • Choose Network Adapters carefully — AWS by default provides AWS VPC CNI plugin for Networking. If you are going to use third party Network CNIs such as Calico, Cilium, Flannel or Weave, you are responsible for its maintenance. • Enable ipv6 for your cluster or add Secondary CIDR if your workloads are huge and may run into ipv4 exhaustion. • Choose between Managed Node Groups, Self-Managed Node Groups or AWS Fargate for compute Resources. Each has its own advantages and limitations depending on your use case. • Service Mesh Analysis — Service to Service communication can be controlled efficiently using a service Mesh. AWS recommends to use Istio or AWS AppMesh for working with EKS. • EKS Monitoring and Logging — EKS Control plane metrics can be scraped using Prometheus and these metrics can be visualised efficiently using Grafana / Datadog / AppDynamics. Migration Phases: 1. Build your Own Production ready EKS cluster in Test Environment. 2. Install and Configure the Primary and Secondary Add-ons. 3. Monitoring and Alerting setup for EKS cluster and Workloads. 4. Perform Infrastructure Load Testing — Reference: https://aws.amazon.com/blogs/containers/load-testing-your-workload-running-onamazon-eks-with-locust/ 5. Derive a Migration Strategy — Routing of Traffic to new EKS cluster. Use Route53 weightage policy to have a control on routing the traffic to new EKS cluster while the major requests being served by Self-Managed Kubernetes cluster. 6. Meet with Development Teams to explain about EKS architecture and Migration strategy. 7. Deploy Services / Workloads in Test Environment. 8. Perform Application Functional and Load/Performance testing. 9. After Sign-Off, Decide Production Date and move the Traffic according to your Migration strategy.

Guidelines To Migrate From Self- Managed Kubernetes In AWS To Amazon EKS Read More »

computer, computer code, programming-1873831.jpg

How to install ContainerD

Containerd versions can be found in this location : https://github.com/containerd/containerd/releases Step 1 : Download the containerd package wget https://github.com/containerd/containerd/releases/download/v1.6.14/containerd-1.6.14-linux-amd64.tar.gz Unpack : sudo tar Cxzvf /usr/local containerd-1.6.14-linux-amd64.tar.gz Install runc : Runc is a standardized runtime for spawning and running containers on Linux according to the OCI specification wget https://github.com/opencontainers/runc/releases/download/v1.1.3/runc.amd64 $ install -m 755 runc.amd64 /usr/local/sbin/runc Download and install CNI plugins : wget https://github.com/containernetworking/plugins/releases/download/v1.1.1/cni-plugins-linux-amd64-v1.1.1.tgz mkdir -p /opt/cni/bin tar Cxzvf /opt/cni/bin cni-plugins-linux-amd64-v1.1.1.tgz Configure containerd We need to create a containerd directory for the configuration file sudo mkdir /etc/containerd config.toml is the default configuration file fro containerd : containerd config default | sudo tee /etc/containerd/config.toml Enable systemd group . Use sed command to change the parameter in config.toml instead of using vi editor sudo sed -i ‘s/SystemdCgroup \= false/SystemdCgroup \= true/g’ /etc/containerd/config.toml Convert containerd into service : sudo curl -L https://raw.githubusercontent.com/containerd/containerd/main/containerd.service -o /etc/systemd/system/containerd.service sudo systemctl daemon-reload sudo systemctl enable — now containerd sudo systemctl status containerd

How to install ContainerD Read More »

woman, laptop, desk-1851464.jpg

Chef Infra Automation Commands

Chef Infra Automation Commands Quick Command Guide reference:   knife bootstrap IPADDRESS(hostname) –sudo -x username -P password -N target1 (This installs chef-client and validates) knife bootstrap WIN-I2R3V7Q9AFV –sudo -x username -P passwd -N nodename   Bootstrap Virtual box ********************** knife bootstrap 192.168.1.101 –ssh-user vasanth –ssh-password ‘vasanth123’ –sudo –use-sudo-password –node-name virtuenode knife bootstrap x.x.x.x –ssh-user ubuntu –sudo –identity-file ./.chef/mykey.pem –run-list webserver knife bootstrap 172.31.51.157 –ssh-user ec2-user –sudo –identity-file ./.chef/user.pem knife bootstrap 172.31.51.157 –ssh-user ec2-user –sudo –identity-file “C:Usersuser.sshid_rsa”   knife bootstrap windows winrm ADDRESS –winrm-user USER –winrm-password ‘PASSWORD’ –node-name target3 –run-list ‘recipe[learn_chef_iis]’ –winrm-transport ssl –winrm-ssl-verify-mode verify_none knife bootstrap windows winrm WIN-I2R3V7Q9AFV –winrm-user username –winrm-password ‘passwd’ –node-name target3 –run-list ‘recipe[learn_chef_iis]’ –winrm-transport ssl –winrm-ssl-verify-mode verify_none knife cookbook create apache knife cookbook upload apache Login via putty and run “sudo chef-client” knife node show target1 knife node show target1 -l knife node show target1 -Fj knife node show target1 -a fqdn knife search node “*:*” -a fqdn   From workstation ******************* Using Chefdk chef generate repo chef-repo chef generate cookbook webserver   Installing and configuring kitchen ********************************** Under your Chef local repo gem install test-kitchen gem install test-kitchen kitchen init –create-gemfile /          kitchen init –driver=kitchen-vagrant kitchen –version kitchen list kitchen create default-ubuntu-1404 kitchen list kitchen converge default-ubuntu-1404 kitchen login default-ubuntu-1404 kitchen verify default-ubuntu-1404 kitchen verify 64 (centos) kitchen test default-ubuntu-1404 kitchen help kitchen help init kitchen destroy gem install test-kitchen kitchen init –create-gemfile /          kitchen init –driver=kitchen-vagrant kitchen –version kitchen list kitchen create default-ubuntu-1404 kitchen list kitchen converge default-ubuntu-1404 kitchen login default-ubuntu-1404 kitchen verify default-ubuntu-1404 kitchen verify 64 (centos) kitchen test default-ubuntu-1404 kitchen help kitchen help init kitchen destroy Data bag ********* knife data bag create databagname 1.x.x Browsing the supermarket ************************* knife cookbook site list knife cookbook site search mysql knife cookbook site show mysql knife cookbook site show mysql 0.10.0 knife cookbook site download mysql knife cookbook site install mysql knife -v Uploading cookbooks to Supermarket ***************************************** knife cookbook site share “my_apache2_cookbook” “Web Servers” Delete Node from Chef server ***************************** knife node delete my_node (delete node in server) knife node client my_node (delete client object in server) Create Roles and environment ***************************** subl roles/web_server.rb knife role from file web_server.rb knife node edit server sudo chef-client knife environment create book knife environment list knife node list knife node list -E book knife node edit my_server knife node list -E book knife environment edit book  

Chef Infra Automation Commands Read More »