Category Archives: DevOps Automation

36. DevOps:Why the DevOps practice team is required to involve in Infra cloud planning? ?

Build Cloud architects-FB promotion

Why the DevOps practice team is required to involve in Infra cloud planning?

I was talking to some clients recently on the importance of Cloud migration activities planning. I have come with some guidelines for them as part of my engagement. Some of my guidelines given to them, I would like to share as below.

When the DevOps practice team need to do the infra setup  for a cloud migration they also need to participate on the identification of Infra activities and the specifications. Which is very essential.

This need to be done as initial step with any Cloud services migration.

As per my opinion we can work with any cloud services like; AWS/AZURE/Google Cloud, etc., by having the above activity as mandatory.

The attached blog/Video contains the same discussion with the details of the steps required to setup a Virtual Private Cloud. The VPC nomenclature we might have seen with AWS. But similar setup or name cane be there with other Cloud service providers also.

Once this VPC is created the systems are going to be hosted on Cloud.

The Ops team’s responsibility is; to make sure the Cloud migration is correctly and completely done for all the live setup.

At the same time they also need to conduct a pilot testing activity successfully which is mandated as per the Agile Projects management [Agile PM] standards before they announce go live.

They also need to do a parallel run along with the past production setup with a new cloud setup for few weeks.


Below URL contains the initial planning discussion as mentioned:


If you want to learn detailed discussion on Infra planning, visit:








How A Cloud architect is different from DevOps role ?

vskumarcloud-build-cloud-architect.pngHow A Cloud architect is different from DevOps practices ?

We have been watching on lot of FB Groups and ad sites as “learn DevOps/AWS”. In general everybody believe with these stickers/posters they need to learn AWS and DevOps together is a must for any Modern technology professional.

When we talk about AWS and DevOps they are two different work streams.

Now, one might get the below questions in their mind.

  1. Is a Cloud Architect need to be expert to work on DevOps activities also ?
  2. What are the activities related to Cloud architect ?
  3. Why the Cloud architect need not bother on DevOps ?

Now, let us analyze them as below:

The role of the cloud architect is to migrate the existing IT infrastructure setup into the cloud services. The cloud services can be AWS or Azure or Google cloud [GC] or Alibaba, etc.

From the below picture one can have clarity if they have experience in traditional Infrastructure building  practice.


How to create AWS S3 Bucket

This role need to understand clearly on the usage of those vendor related [AWS/AZURE/GC/Alibaba] cloud services and should have command on mapping the current traditional infrastructure setup to map to the cloud services and plan/design for its transformation with the additional benefits to the management in view of cost and easy operation.

Once the modern application architecture/infrastructure in cloud is operational, then the management can think of introducing the DevOps practices.

To work on DevOps practices, each Cloud services vendor provides their own setup or tools at different processes or pipeline stages. To do these tasks a separate role professionals are required, who are called DevOps Engineers. At this point the role of the cloud Architect is he/she can guide them on the available infrastructure with the Cloud vendor. As per the Cloud architect planning/guidelines the DevOps engineers need to adopt the relevant tools/processes. Basically all the setup is going to be on IAC [Infrastructure As A Code] technics. There can be Configuration tools to create the IAC for different environments. At this point the Cloud architect can monitor these tools implementation as a part of cloud infrastructure implementation.

So, the Cloud architect do not need to make his/her fingers dirty with tools/commands to implement the DevOps processes.

For example; If you read the roles of AWS with different certifications, they mention Solution Architect [SA] separately from DevOps engineer role. They have multiple roles like; Sys ops, Developer, etc. All these roles need to be expert in making their fingers dirty with the relevant AWS services usage/implementation efficiently and effectively . But here the Cloud Architect [which is SA in view of AWS] role is to monitor on their activities only. He/She doesn’t need to put the fingers into techie stuff.

Hope I have given clarity for the above questions.

I get lot of enquiries; as they want to do AWS/DevOps both the courses together. I understood due to lot of training vendors are making their posters on social for their business, these experienced professionals are getting confusion as they need to learn both.

Now, I would like to ask the below questions to you as this blog reader after the above understanding;

Do a modern technology professional need to learn Cloud services and also the DevOps as mandatory ? [Ex: Which is DevOps/AWS].

Answer: It is not. They can choose One route only. If he/she came from the real work experience of Sysadmin/Sys engineer role, the past experiences need to be utilized efficiently in IT Industry. Hence the Scalable role is Cloud architect. In view of AWS it is SA. But they need to have very good command in understanding the traditional architecture and also the cloud services to establish a well suited conversion plan. This role person is responsible to  show ROI [Return On Investment] also to the management.

You can also compare the SAA Salary among all the roles being played with AWS:

See the difference on the salary amounts to seek your role as per your professional potentiality.

Also, Visit:

Do you want to the size of the Cloud job market globally if yes, visit:

To know the real articulation of SA, Visit for my AWS SAA class video:









1. Cloud architect: How to build your Infrastructure planning practice ?

If you are a Cloud Architect, you might do project initiation for Cloud migration projects. During that time you need to have a plan to get series of activities and to make a project schedule. You might need to see this discussion Video also along with your planning. It will add value for your future efforts savings or can reduce repeat activities. Please send your feedback by e-mail [mentioned in it], which can encourage us to make such Consulting/discussion videos sharing on Social.

Build Cloud architects-FB promotion

With reference to my previous blog on the role of Cloud architect, in this blog I would like to present on:

  • What is Traditional Infrastructure planning and building analysis ?

  • How to setup a new Infrastructure for an E-commerce [simple site] in Traditional manner ?

  • What are the Activities we might do ?

  • How to compare them in high level with a Cloud Architecting ?

  • If the Cloud architect apply these practices in his/her area, lot of time for roll back/back out tasks can be reduced during migration.

The following One hour Video has the entire elaboration  for your clarity with a Consulting/Training discussion:

You can also join for similar discussions:

If you are looking for coaching on your role Cloud performance, please contact me on my FB with your Linkedin URL.

For details on my coaching visit:


If you are interested to know the Cloud initiation activities, visit my video:



DevOps Practices & FAQs -2

Please read the previous FAQs series also: Devops-practices-faqs-1

And the next one:


1. Who can become DevOps Engineer ?

In traditional projects [Non Agile practiced projects] ; Build Engineers, Sys Admins, Release Engineers can convert their career into DevOps Engineer role through an Agile practiced IT organization.

In Agile projects we might have seen Build or Deployment Engineers; they can convert into DevOps Engineer roles.

2. What a desired ‘DevOps Engineer role professional’ need to learn ?

If somebody would like to convert their role into DevOps Engineer; they need to understand the following :

  1. Agile and Scrum or Lean practices
  2. DevOps Principles, practices and patterns
  3. Deployment, SCM  and Release management process
  4. Version control System tools [Ex: Git, SVN, etc..]
  5. Cloud setup and deployment [Ex: AWS, Azure,Google Cloud, Alibaba, etc..]
  6. Packaging process and tools [Ex: Maven, Gradle, etc.]
  7. Continuous Integration Tools [Ex: Jenkins, Teamcity,  etc.]
  8. Software Configuration Management [SCM]  tools [Ex: Ansible,  Chef, Puppet, etc.]
  9. Containerization [Docker]
  10. Some of the scripting languages [Ex: Shell, Bash, python, Ruby, Nodejs, etc.]
  11. Windows, Linux OS commands and operations.

They can learn incrementally also depends on the project need. Note all projects will not use the unique tools. Depends on the IT organization plans, practices and the environments they decide on choosing the vendor based or open source tools.

Note: Some of the famous tools only it has been mentioned. Hence one need to identify the customer project environment and their DevOps architecture also. If one understands the Basic process in their 1st learning phase, later on they can pickup faster.

If you want to learn DevOps Practices, join the below group:

FB-DevOps-Practices Group-page

Following videos are made to elaborate on the need and advantages of thinking on conversion into DevOps Practices by IT Companies and the Professionals. Comparative reports have been incorporated.





Visit my current running facebook groups for IT Professionals with my valuable discussions/videos/blogs posted:


DevOps Practices Group:


Cloud Practices Group:


Build Cloud Solution Architects [With some videos of the live students classes/feedback]



MicroServices and Docker [For learning concepts of Microservices and Docker containers]

34. DevOps:How to Install Gradle on Ubuntu 18.04 ? [Video]

Gradle logo

How to Install Gradle on Ubuntu 18.04 ? :

Through this blog it is demonstrated the Gradle 4.10.2! installation on Ubuntu 18.04 VM.

At the end of this blog the Installation video clip is attached.


Step#1: Install OpenJDK:

Gradle needs Java JDK or JRE version 7 or
above to be installed.
We will install OpenJDK 8 as below.
Let us update the linux package index.

sudo apt update

Install the OpenJDK package with the below command:

Install the OpenJDK package.

sudo apt install openjdk-8-jdk
Check the java version.

Java -version

Step#2: Download Gradle

Using the below command; Used the below valid command…..

wget -P /tmp
Once the download is completed, we need to extract the zip file into folder; /opt/gradle :

sudo unzip -d /opt/gradle /tmp/gradle-*.zip

let us Verify that the Gradle files are extracted by listing the /opt/gradle/gradle-4.10.2 directory
ls /opt/gradle/gradle-4.10.2

The typical file list will be:

bin getting-started.html init.d lib LICENSE media NOTICE

Step#3: Setting up environment variables:

Now, we need to configure the PATH environment variable to include the Gradle bin directory.
To do this task; need to open a text editor and create a new file named inside of the folder; /etc/profile.d/

sudo vim /etc/profile.d/

In this shell program [config file] paste the below lines;

export GRADLE_HOME=/opt/gradle/gradle-4.10.2
export PATH=${GRADLE_HOME}/bin:${PATH}

The above script will be initiated at startup.

Now, let us Load the environment variables using the following command;

source /etc/profile.d/

Step#4: Verify the Gradle installation

To validate the installation of Gradle
use the command;

gradle -v

It will display the Gradle version.

So the Gradle is installed successfully.


==== Lab exercise output are pasted here ===>

Gradle installation steps output for Ubuntu 18.04 VM:

Step#1: Install OpenJDK:

Output for;

sudo apt update

==== Output =====>


vskumar@ubuntu:~$ sudo apt update

[sudo] password for vskumar:

Get:1 bionic InRelease [64.4 kB]

Hit:3 bionic InRelease

Get:4 bionic-security InRelease [83.2 kB]

Ign:5 binary/ InRelease

Get:2 bionic InRelease [15.4 kB]

Get:6 bionic-updates InRelease [88.7 kB]

Hit:7 binary/ Release

Get:8 bionic-backports InRelease [74.6 kB]

E: Repository ‘ bionic InRelease’ changed its ‘Label’ value from ‘Oracle Java (JDK) 8 / 9 Installer PPA’ to ‘Oracle Java (JDK) 8 Installer PPA’

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Do you want to accept these changes and continue updating from this repository? [y/N] y

Get:9 bionic/main i386 Packages [1,556 B]

Get:10 bionic/main amd64 Packages [1,556 B]

Get:11 bionic-updates/main i386 Packages [372 kB]

Get:13 bionic-updates/main amd64 Packages [416 kB]

Get:14 bionic-updates/universe amd64 Packages [571 kB]

Get:15 bionic-updates/universe i386 Packages [566 kB]

Fetched 2,254 kB in 25s (89.3 kB/s)

Reading package lists… Done

Building dependency tree

Reading state information… Done

345 packages can be upgraded. Run ‘apt list –upgradable’ to see them.


== End of output ======>



=====>Screen Output for JDK 8 Installation ===>

vskumar@ubuntu:~$ sudo apt install openjdk-8-jdk

Reading package lists… Done

Building dependency tree

Reading state information… Done

The following additional packages will be installed:

ca-certificates-java fonts-dejavu-extra libatk-wrapper-java

libatk-wrapper-java-jni libgif7 libice-dev libpthread-stubs0-dev libsm-dev

libx11-6 libx11-dev libx11-doc libxau-dev libxcb1-dev libxdmcp-dev

libxt-dev openjdk-8-jdk-headless openjdk-8-jre openjdk-8-jre-headless

x11proto-core-dev x11proto-dev xorg-sgml-doctools xtrans-dev

Suggested packages:

libice-doc libsm-doc libxcb-doc libxt-doc openjdk-8-demo openjdk-8-source

visualvm fonts-ipafont-gothic fonts-ipafont-mincho fonts-wqy-microhei


The following NEW packages will be installed:

ca-certificates-java fonts-dejavu-extra libatk-wrapper-java

libatk-wrapper-java-jni libgif7 libice-dev libpthread-stubs0-dev libsm-dev

libx11-dev libx11-doc libxau-dev libxcb1-dev libxdmcp-dev libxt-dev

openjdk-8-jdk openjdk-8-jdk-headless openjdk-8-jre openjdk-8-jre-headless

x11proto-core-dev x11proto-dev xorg-sgml-doctools xtrans-dev

The following packages will be upgraded:


1 upgraded, 22 newly installed, 0 to remove and 344 not upgraded.

1 not fully installed or removed.

Need to get 41.8 MB/42.3 MB of archives.

After this operation, 165 MB of additional disk space will be used.

Do you want to continue? [Y/n] y

Get:1 bionic-updates/universe amd64 openjdk-8-jre-headless amd64 8u181-b13-1ubuntu0.18.04.1 [27.3 MB]

Get:1 bionic-updates/universe amd64 openjdk-8-jre-headless amd64 8u181-b13-1ubuntu0.18.04.1 [27.3 MB]

Get:2 bionic-updates/main amd64 ca-certificates-java all 20180516ubuntu1~18.04.1 [12.2 kB]

Get:3 bionic/main amd64 fonts-dejavu-extra all 2.37-1 [1,953 kB]

Get:4 bionic/main amd64 libatk-wrapper-java all 0.33.3-20ubuntu0.1 [34.7 kB]

Get:5 bionic/main amd64 libatk-wrapper-java-jni amd64 0.33.3-20ubuntu0.1 [28.3 kB]

Get:6 bionic/main amd64 libgif7 amd64 5.1.4-2 [30.6 kB]

Get:7 bionic/main amd64 xorg-sgml-doctools all 1:1.11-1 [12.9 kB]

Get:8 bionic/main amd64 x11proto-dev all 2018.4-4 [251 kB]

Get:9 bionic/main amd64 x11proto-core-dev all 2018.4-4 [2,620 B]

Get:10 bionic/main amd64 libice-dev amd64 2:1.0.9-2 [46.8 kB]

Get:11 bionic/main amd64 libpthread-stubs0-dev amd64 0.3-4 [4,068 B]

Get:12 bionic/main amd64 libsm-dev amd64 2:1.2.2-1 [16.2 kB]

Get:13 bionic/main amd64 libxau-dev amd64 1:1.0.8-1 [11.1 kB]

Get:14 bionic/main amd64 libxdmcp-dev amd64 1:1.1.2-3 [25.1 kB]

Get:15 bionic/main amd64 xtrans-dev all 1.3.5-1 [70.5 kB]

Get:16 bionic/main amd64 libxcb1-dev amd64 1.13-1 [80.0 kB]

Get:17 bionic-updates/main amd64 libx11-dev amd64 2:1.6.4-3ubuntu0.1 [641 kB]

Get:18 bionic-updates/main amd64 libx11-doc all 2:1.6.4-3ubuntu0.1 [2,065 kB]

Get:19 bionic/main amd64 libxt-dev amd64 1:1.1.5-1 [395 kB]

Get:20 bionic-updates/universe amd64 openjdk-8-jre amd64 8u181-b13-1ubuntu0.18.04.1 [69.7 kB]

Get:21 bionic-updates/universe amd64 openjdk-8-jdk-headless amd64 8u181-b13-1ubuntu0.18.04.1 [8,248 kB]

Ign:21 bionic-updates/universe amd64 openjdk-8-jdk-headless amd64 8u181-b13-1ubuntu0.18.04.1

Get:22 bionic-updates/universe amd64 openjdk-8-jdk amd64 8u181-b13-1ubuntu0.18.04.1 [458 kB]

Get:21 bionic-updates/universe amd64 openjdk-8-jdk-headless amd64 8u181-b13-1ubuntu0.18.04.1 [8,248 kB]

Fetched 6,273 kB in 1min 54s (54.9 kB/s)

(Reading database … 172315 files and directories currently installed.)

Preparing to unpack …/00-libx11-6_2%3a1.6.4-3ubuntu0.1_amd64.deb …

Unpacking libx11-6:amd64 (2:1.6.4-3ubuntu0.1) over (2:1.6.4-3) …

Selecting previously unselected package openjdk-8-jre-headless:amd64.

Preparing to unpack …/01-openjdk-8-jre-headless_8u181-b13-1ubuntu0.18.04.1_amd64.deb …

Unpacking openjdk-8-jre-headless:amd64 (8u181-b13-1ubuntu0.18.04.1) …

Selecting previously unselected package ca-certificates-java.

Preparing to unpack …/02-ca-certificates-java_20180516ubuntu1~18.04.1_all.deb …

Unpacking ca-certificates-java (20180516ubuntu1~18.04.1) …

Selecting previously unselected package fonts-dejavu-extra.

Preparing to unpack …/03-fonts-dejavu-extra_2.37-1_all.deb …

Unpacking fonts-dejavu-extra (2.37-1) …

Selecting previously unselected package libatk-wrapper-java.

Preparing to unpack …/04-libatk-wrapper-java_0.33.3-20ubuntu0.1_all.deb …

Unpacking libatk-wrapper-java (0.33.3-20ubuntu0.1) …

Selecting previously unselected package libatk-wrapper-java-jni:amd64.

Preparing to unpack …/05-libatk-wrapper-java-jni_0.33.3-20ubuntu0.1_amd64.deb …

Unpacking libatk-wrapper-java-jni:amd64 (0.33.3-20ubuntu0.1) …

Selecting previously unselected package libgif7:amd64.

Preparing to unpack …/06-libgif7_5.1.4-2_amd64.deb …

Unpacking libgif7:amd64 (5.1.4-2) …

Selecting previously unselected package xorg-sgml-doctools.

Preparing to unpack …/07-xorg-sgml-doctools_1%3a1.11-1_all.deb …

Unpacking xorg-sgml-doctools (1:1.11-1) …

Selecting previously unselected package x11proto-dev.

Preparing to unpack …/08-x11proto-dev_2018.4-4_all.deb …

Unpacking x11proto-dev (2018.4-4) …

Selecting previously unselected package x11proto-core-dev.

Preparing to unpack …/09-x11proto-core-dev_2018.4-4_all.deb …

Unpacking x11proto-core-dev (2018.4-4) …

Selecting previously unselected package libice-dev:amd64.

Preparing to unpack …/10-libice-dev_2%3a1.0.9-2_amd64.deb …

Unpacking libice-dev:amd64 (2:1.0.9-2) …

Selecting previously unselected package libpthread-stubs0-dev:amd64.

Preparing to unpack …/11-libpthread-stubs0-dev_0.3-4_amd64.deb …

Unpacking libpthread-stubs0-dev:amd64 (0.3-4) …

Selecting previously unselected package libsm-dev:amd64.

Preparing to unpack …/12-libsm-dev_2%3a1.2.2-1_amd64.deb …

Unpacking libsm-dev:amd64 (2:1.2.2-1) …

Selecting previously unselected package libxau-dev:amd64.

Preparing to unpack …/13-libxau-dev_1%3a1.0.8-1_amd64.deb …

Unpacking libxau-dev:amd64 (1:1.0.8-1) …

Selecting previously unselected package libxdmcp-dev:amd64.

Preparing to unpack …/14-libxdmcp-dev_1%3a1.1.2-3_amd64.deb …

Unpacking libxdmcp-dev:amd64 (1:1.1.2-3) …

Selecting previously unselected package xtrans-dev.

Preparing to unpack …/15-xtrans-dev_1.3.5-1_all.deb …

Unpacking xtrans-dev (1.3.5-1) …

Selecting previously unselected package libxcb1-dev:amd64.

Preparing to unpack …/16-libxcb1-dev_1.13-1_amd64.deb …

Unpacking libxcb1-dev:amd64 (1.13-1) …

Selecting previously unselected package libx11-dev:amd64.

Preparing to unpack …/17-libx11-dev_2%3a1.6.4-3ubuntu0.1_amd64.deb …

Unpacking libx11-dev:amd64 (2:1.6.4-3ubuntu0.1) …

Selecting previously unselected package libx11-doc.

Preparing to unpack …/18-libx11-doc_2%3a1.6.4-3ubuntu0.1_all.deb …

Unpacking libx11-doc (2:1.6.4-3ubuntu0.1) …

Selecting previously unselected package libxt-dev:amd64.

Preparing to unpack …/19-libxt-dev_1%3a1.1.5-1_amd64.deb …

Unpacking libxt-dev:amd64 (1:1.1.5-1) …

Selecting previously unselected package openjdk-8-jre:amd64.

Preparing to unpack …/20-openjdk-8-jre_8u181-b13-1ubuntu0.18.04.1_amd64.deb …

Unpacking openjdk-8-jre:amd64 (8u181-b13-1ubuntu0.18.04.1) …

Selecting previously unselected package openjdk-8-jdk-headless:amd64.

Preparing to unpack …/21-openjdk-8-jdk-headless_8u181-b13-1ubuntu0.18.04.1_amd64.deb …

Unpacking openjdk-8-jdk-headless:amd64 (8u181-b13-1ubuntu0.18.04.1) …

Selecting previously unselected package openjdk-8-jdk:amd64.

Preparing to unpack …/22-openjdk-8-jdk_8u181-b13-1ubuntu0.18.04.1_amd64.deb …

Unpacking openjdk-8-jdk:amd64 (8u181-b13-1ubuntu0.18.04.1) …

Setting up nginx-extras (1.14.0-0ubuntu1) …

Job for nginx.service failed because the control process exited with error code.

See “systemctl status nginx.service” and “journalctl -xe” for details.

invoke-rc.d: initscript nginx, action “start” failed.

  • nginx.service – A high performance web server and a reverse proxy server

Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)

Active: failed (Result: exit-code) since Thu 2018-11-01 05:06:40 PDT; 220ms ago

Docs: man:nginx(8)

Process: 14329 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)

Process: 14319 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)


Nov 01 05:06:38 ubuntu nginx[14329]: nginx: [emerg] bind() to failed (98: Address already in use)

Nov 01 05:06:38 ubuntu nginx[14329]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)

Nov 01 05:06:39 ubuntu nginx[14329]: nginx: [emerg] bind() to failed (98: Address already in use)

Nov 01 05:06:39 ubuntu nginx[14329]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)

Nov 01 05:06:39 ubuntu nginx[14329]: nginx: [emerg] bind() to failed (98: Address already in use)

Nov 01 05:06:39 ubuntu nginx[14329]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)

Nov 01 05:06:40 ubuntu nginx[14329]: nginx: [emerg] still could not bind()

Nov 01 05:06:40 ubuntu systemd[1]: nginx.service: Control process exited, code=exited status=1

Nov 01 05:06:40 ubuntu systemd[1]: nginx.service: Failed with result ‘exit-code’.

Nov 01 05:06:40 ubuntu systemd[1]: Failed to start A high performance web server and a reverse proxy server.

dpkg: error processing package nginx-extras (–configure):

installed nginx-extras package post-installation script subprocess returned error exit status 1

Setting up ca-certificates-java (20180516ubuntu1~18.04.1) …

head: cannot open ‘/etc/ssl/certs/java/cacerts’ for reading: No such file or directory

Adding debian:COMODO_ECC_Certification_Authority.pem

Adding debian:AffirmTrust_Premium_ECC.pem

Adding debian:Certinomis_-_Root_CA.pem

Adding debian:SSL.com_Root_Certification_Authority_ECC.pem

Adding debian:AffirmTrust_Premium.pem

Adding debian:Entrust_Root_Certification_Authority_-_G2.pem

Adding debian:GeoTrust_Primary_Certification_Authority_-_G2.pem

Adding debian:GlobalSign_Root_CA.pem

Adding debian:OpenTrust_Root_CA_G3.pem

Adding debian:USERTrust_RSA_Certification_Authority.pem

Adding debian:thawte_Primary_Root_CA_-_G3.pem

Adding debian:ssl-cert-snakeoil.pem

Adding debian:Baltimore_CyberTrust_Root.pem

Adding debian:Certplus_Root_CA_G2.pem

Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem

Adding debian:T-TeleSec_GlobalRoot_Class_3.pem

Adding debian:Entrust_Root_Certification_Authority_-_EC1.pem

Adding debian:EE_Certification_Centre_Root_CA.pem

Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.pem

Adding debian:DigiCert_Global_Root_CA.pem

Adding debian:GlobalSign_ECC_Root_CA_-_R5.pem

Adding debian:NetLock_Arany_=Class_Gold=_Főtanúsítvány.pem

Adding debian:Network_Solutions_Certificate_Authority.pem

Adding debian:Buypass_Class_2_Root_CA.pem

Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem

Adding debian:DST_Root_CA_X3.pem

Adding debian:Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem

Adding debian:Certplus_Class_2_Primary_CA.pem

Adding debian:Trustis_FPS_Root_CA.pem

Adding debian:OpenTrust_Root_CA_G1.pem

Adding debian:Taiwan_GRCA.pem

Adding debian:AC_RAIZ_FNMT-RCM.pem

Adding debian:TUBITAK_Kamu_SM_SSL_Kok_Sertifikasi_-_Surum_1.pem

Adding debian:AffirmTrust_Commercial.pem

Adding debian:QuoVadis_Root_CA_3.pem

Adding debian:SSL.com_EV_Root_Certification_Authority_RSA_R2.pem

Adding debian:DigiCert_Global_Root_G3.pem

Adding debian:QuoVadis_Root_CA_1_G3.pem

Adding debian:thawte_Primary_Root_CA.pem

Adding debian:thawte_Primary_Root_CA_-_G2.pem

Adding debian:CA_Disig_Root_R2.pem

Adding debian:Hellenic_Academic_and_Research_Institutions_RootCA_2015.pem

Adding debian:Hellenic_Academic_and_Research_Institutions_ECC_RootCA_2015.pem

Adding debian:Certum_Trusted_Network_CA.pem

Adding debian:SSL.com_EV_Root_Certification_Authority_ECC.pem

Adding debian:Chambers_of_Commerce_Root_-_2008.pem

Adding debian:certSIGN_ROOT_CA.pem

Adding debian:Hongkong_Post_Root_CA_1.pem

Adding debian:DigiCert_Assured_ID_Root_G2.pem

Adding debian:GlobalSign_Root_CA_-_R3.pem

Adding debian:AddTrust_External_Root.pem

Adding debian:QuoVadis_Root_CA_2_G3.pem

Adding debian:DigiCert_Trusted_Root_G4.pem

Adding debian:Staat_der_Nederlanden_EV_Root_CA.pem

Adding debian:COMODO_Certification_Authority.pem

Adding debian:Global_Chambersign_Root_-_2008.pem

Adding debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.pem

Adding debian:OISTE_WISeKey_Global_Root_GA_CA.pem

Adding debian:Actalis_Authentication_Root_CA.pem

Adding debian:Entrust_Root_Certification_Authority.pem

Adding debian:GlobalSign_Root_CA_-_R2.pem

Adding debian:ACCVRAIZ1.pem

Adding debian:Certplus_Root_CA_G1.pem

Adding debian:Starfield_Root_Certificate_Authority_-_G2.pem

Adding debian:Buypass_Class_3_Root_CA.pem


Adding debian:OISTE_WISeKey_Global_Root_GB_CA.pem

Adding debian:GeoTrust_Universal_CA.pem

Adding debian:QuoVadis_Root_CA.pem

Adding debian:TeliaSonera_Root_CA_v1.pem

Adding debian:QuoVadis_Root_CA_3_G3.pem

Adding debian:QuoVadis_Root_CA_2.pem

Adding debian:Go_Daddy_Class_2_CA.pem

Adding debian:DigiCert_Global_Root_G2.pem

Adding debian:Starfield_Services_Root_Certificate_Authority_-_G2.pem

Adding debian:Microsec_e-Szigno_Root_CA_2009.pem

Adding debian:SSL.com_Root_Certification_Authority_RSA.pem

Adding debian:GlobalSign_ECC_Root_CA_-_R4.pem

Adding debian:EC-ACC.pem

Adding debian:Cybertrust_Global_Root.pem

Adding debian:DigiCert_Assured_ID_Root_G3.pem

Adding debian:SecureSign_RootCA11.pem

Adding debian:Visa_eCommerce_Root.pem

Adding debian:Atos_TrustedRoot_2011.pem

Adding debian:VeriSign_Universal_Root_Certification_Authority.pem

Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H5.pem

Adding debian:E-Tugra_Certification_Authority.pem

Adding debian:Certigna.pem

Adding debian:Sonera_Class_2_Root_CA.pem

Adding debian:TrustCor_RootCert_CA-2.pem

Adding debian:SwissSign_Silver_CA_-_G2.pem

Adding debian:Certum_Trusted_Network_CA_2.pem

Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem

Adding debian:CFCA_EV_ROOT.pem

Adding debian:AffirmTrust_Networking.pem

Adding debian:T-TeleSec_GlobalRoot_Class_2.pem

Adding debian:IdenTrust_Public_Sector_Root_CA_1.pem

Adding debian:IdenTrust_Commercial_Root_CA_1.pem

Adding debian:TrustCor_RootCert_CA-1.pem

Adding debian:Comodo_AAA_Services_root.pem

Adding debian:Amazon_Root_CA_3.pem

Adding debian:GeoTrust_Universal_CA_2.pem

Adding debian:Security_Communication_RootCA2.pem

Adding debian:GeoTrust_Global_CA.pem

Adding debian:Deutsche_Telekom_Root_CA_2.pem

Adding debian:OpenTrust_Root_CA_G2.pem

Adding debian:GDCA_TrustAUTH_R5_ROOT.pem

Adding debian:USERTrust_ECC_Certification_Authority.pem

Adding debian:SecureTrust_CA.pem

Adding debian:D-TRUST_Root_Class_3_CA_2_2009.pem

Adding debian:TrustCor_ECA-1.pem

Adding debian:SZAFIR_ROOT_CA2.pem

Adding debian:Secure_Global_CA.pem

Adding debian:DigiCert_High_Assurance_EV_Root_CA.pem

Adding debian:ePKI_Root_Certification_Authority.pem

Adding debian:GeoTrust_Primary_Certification_Authority.pem

Adding debian:Entrust.net_Premium_2048_Secure_Server_CA.pem

Adding debian:Staat_der_Nederlanden_Root_CA_-_G3.pem

Adding debian:ISRG_Root_X1.pem

Adding debian:Security_Communication_Root_CA.pem

Adding debian:SwissSign_Gold_CA_-_G2.pem

Adding debian:COMODO_RSA_Certification_Authority.pem

Adding debian:Amazon_Root_CA_4.pem

Adding debian:TWCA_Global_Root_CA.pem

Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem

Adding debian:LuxTrust_Global_Root_2.pem

Adding debian:TWCA_Root_Certification_Authority.pem

Adding debian:Amazon_Root_CA_2.pem

Adding debian:Go_Daddy_Root_Certificate_Authority_-_G2.pem

Adding debian:DigiCert_Assured_ID_Root_CA.pem

Adding debian:XRamp_Global_CA_Root.pem

Adding debian:GeoTrust_Primary_Certification_Authority_-_G3.pem

Adding debian:Starfield_Class_2_CA.pem

Adding debian:Amazon_Root_CA_1.pem


Processing triggers for mime-support (3.60ubuntu1) …

Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) …

Setting up libpthread-stubs0-dev:amd64 (0.3-4) …

Setting up xorg-sgml-doctools (1:1.11-1) …

Setting up libx11-6:amd64 (2:1.6.4-3ubuntu0.1) …

Setting up libgif7:amd64 (5.1.4-2) …

Setting up x11proto-dev (2018.4-4) …

Setting up xtrans-dev (1.3.5-1) …

Setting up libxdmcp-dev:amd64 (1:1.1.2-3) …

Processing triggers for libc-bin (2.27-3ubuntu1) …

Setting up libice-dev:amd64 (2:1.0.9-2) …

Setting up libx11-doc (2:1.6.4-3ubuntu0.1) …

Processing triggers for man-db (2.8.3-2) …

Processing triggers for gnome-menus (3.13.3-11ubuntu1) …

Setting up fonts-dejavu-extra (2.37-1) …

Processing triggers for ca-certificates (20180409) …

Updating certificates in /etc/ssl/certs…

0 added, 0 removed; done.

Running hooks in /etc/ca-certificates/update.d…




Setting up libatk-wrapper-java (0.33.3-20ubuntu0.1) …

Processing triggers for hicolor-icon-theme (0.17-2) …

Processing triggers for fontconfig (2.12.6-0ubuntu2) …

Setting up openjdk-8-jre-headless:amd64 (8u181-b13-1ubuntu0.18.04.1) …

Setting up libsm-dev:amd64 (2:1.2.2-1) …

Setting up x11proto-core-dev (2018.4-4) …

Setting up openjdk-8-jdk-headless:amd64 (8u181-b13-1ubuntu0.18.04.1) …

Setting up libxau-dev:amd64 (1:1.0.8-1) …

Setting up libatk-wrapper-java-jni:amd64 (0.33.3-20ubuntu0.1) …

Setting up libxcb1-dev:amd64 (1.13-1) …

Setting up libx11-dev:amd64 (2:1.6.4-3ubuntu0.1) …

Setting up libxt-dev:amd64 (1:1.1.5-1) …

Setting up openjdk-8-jre:amd64 (8u181-b13-1ubuntu0.18.04.1) …

Setting up openjdk-8-jdk:amd64 (8u181-b13-1ubuntu0.18.04.1) …

Processing triggers for libc-bin (2.27-3ubuntu1) …

Errors were encountered while processing:



E: Sub-process /usr/bin/dpkg returned an error code (1)


vskumar@ubuntu:~$ java -version

java version “1.8.0_171”

Java(TM) SE Runtime Environment (build 1.8.0_171-b11)

Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode)



==== End of Output =====>




=== Output for downloading gradle ====>

vskumar@ubuntu:~$ wget -P /tmp

–2018-11-01 05:14:35–

Resolving (…,,, …

Connecting to (||:443… connected.

HTTP request sent, awaiting response… 301 Moved Permanently

Location: [following]

–2018-11-01 05:14:35–

Resolving (…,,, …

Connecting to (||:443… connected.

HTTP request sent, awaiting response… 200 OK

Length: 78420037 (75M) [application/zip]

Saving to: ‘/tmp/’


gradle-4.10.2-bin.z 100%[==================>]  74.79M  1.83MB/s    in 47s


2018-11-01 05:15:22 (1.60 MB/s) – ‘/tmp/’ saved [78420037/78420037]



=== End of output =============>


=== Gradle Files verification ===>

vskumar@ubuntu:~$ ls /opt/gradle/gradle-4.10.2

bin  getting-started.html  init.d  lib  LICENSE  media  NOTICE




=== Output for shell config file creation =====>

skumar@ubuntu:~$ sudo vim /etc/profile.d/

vskumar@ubuntu:~$ cat  vim /etc/profile.d/

cat: vim: No such file or directory

export GRADLE_HOME=/opt/gradle/gradle-4.10.2

export PATH=${GRADLE_HOME}/bin:${PATH}


=========== End of file content display ====>


=== Output for version checking ====>

vskumar@ubuntu:~$ source /etc/profile.d/

vskumar@ubuntu:~$ gradle -v


Welcome to Gradle 4.10.2!


Here are the highlights of this release:

– Incremental Java compilation by default

– Periodic Gradle caches cleanup

– Gradle Kotlin DSL 1.0-RC6

– Nested included builds

– SNAPSHOT plugin versions in the `plugins {}` block


For more details see




Gradle 4.10.2



Build time:   2018-09-19 18:10:15 UTC

Revision:     b4d8d5d170bb4ba516e88d7fe5647e2323d791dd


Kotlin DSL:   1.0-rc-6

Kotlin:       1.2.61

Groovy:       2.4.15

Ant:          Apache Ant(TM) version 1.9.11 compiled on March 23 2018

JVM:          1.8.0_171 (Oracle Corporation 25.171-b11)

OS:           Linux 4.15.0-29-generic amd64




==== End of Lab exercise output  ===========>

Good luck!!
Thanks for visiting this blog/video……. bye for now…


Advt-course3rd page.png
Folks! Greetings!

Are you interested to transform into new technology ?

An IT employee need to learn DevOps and also one cloud technology practice which is mandatory to understand the current DevOps work culture to get accommodated into a project.
Visit for my course exercises/sample videos/blogs on youtube channel and the blog site mentioned in VCard.
I get many new users regularly  to use these content from different countries.
That itself denotes they are highly competitive techie stuff.
During the course you will be given cloud infra machine(s) [they will be your property] into your laptop for future self practice for interviews, R&D, etc.
The critical  topics will have supporting blogs/videos!! along with the pdf material.
In a corporate style training cos you will be given access [upto certain period] only to their cloud setup.
These are the USPs can be compared with other courses!
Please come with joining confirmation/determination.
For classroom sessions it will be in Vijayanagar, Bangalore, India.
Both online and classroom are available for weekend [global flexible timings] and weekdays to facilitate employees.
Corporate companies are welcome to avail it to save cost of your suppliers!!
You can join from any country for online course.
For contacts please go through vCard. Please send E-mail on your willingness.
Looking forward for your learning call/e-mail!
Look into this video also:
Vcard-Shanthi Kumar V-v3
Visit For Aws Lab demo:


1. AWS:How to create and activate a new account in AWS ?

AWS Account-creation scrn

How to create and activate a new account in AWS ?:

In this blog, you will see the required steps for creating and activating your new AWS account. Once have the activated account, you can start your other lab practices as I discuss in the class timely.

The following are the main 4 steps process we need to follow:

STEP1: Creating your account. It consists of 2 steps: a) Providing a valid e-mail address and choosing a password. b) Providing your contact information and setting your preferences.

STEP2: Add a payment method Please note; you need to have a valid CC to give its details. Amazon verifies its transaction also with a tiny charge and with a credit back. If by mistaken given wrong data please note; your account registration process will not be activated. You will be intimated by mail. This way Amazon is authenticating/authorizing us for AWS usage.

STEP3: Verify your phone number. You need to Provide a phone number where you can be reached in next few minutes, while creating your account.

STEP4: Choose the AWS Support plans. Time to time the AWS plans will be published. You need to choose the plan from the currently available plans for your needs. The relevant URL is given in the detailed steps section in this blog.

As a consolidated process, we can understand from the below flow chart. Which is from the collection of AWS process charts.

AWS Account-creation flowchart


I am not copying the screens due to privacy.

Detailed steps

STEP1: Detailed steps for Creating your account.

a). You need to go to Amazon Web Services home page URL:

b). Now, Choose Sign Up. Click on Create an AWS account. You can see new page with Create an AWS account. You need to enter the required details. E-mail id, Pwd, AWS Account name [you can give any name for this]. And choose continue to go to next page. Please note; The above steps are valid for the new users of AWS. If you enter your email address entered incorrectly, you might not be able to access your account or change your password in the future. So you need to be careful on your data entry part. Let us assume; if you’ve signed in to AWS recently, it might say Sign In to the Console. So you need to login into your existing Account.

c). Now in the current page, choose Professional or personal. These two areas will give equal services. Depends on your need You can choose one of the options.

d). From the above options choosed, type the requested company or personal information entries. Note; At this point, You need to go through the AWS Customer Agreement to know their policies and procedures to follow while operating.

e). Finally, you choose Create Account and Continue options in the bottom.

f). Please note; at this point you will receive an e-mail to confirm that your account is created. Now, you can sign in to your new account using the valid email address and valid password you have supplied earlier.

Please note; we have done the Step1 only, the activation process is not yet completed to use the AWS services. Still we need to follow 3 more steps.

STEP2: Add a payment method- Detailed steps:

At this point; On the Payment Information page,

a) Choose the payment method as per the payment gateway standards which is displayed.

b) Type the requested information associated with your payment method. Please make sure the address for your payment method is the same as the address you provided for your account. Note; If your billing address is different; then choose Use a new address, type the billing address for your payment method.

c) Now, choose Secure Submit.

STEP3: Verify your phone number.

Please keep a valid and handy phone number at this point.

a) On this Phone Verification page, type a phone number where can use to accept incoming phone calls.

b) Enter the code displayed in the captcha. When you’re ready to receive a call, choose Call me now option.

c) In a few moments, an automated system will call you to your given phone number. Even it might have SMS feature also, if you are outside North America region.

d) Type the provided PIN on your phone’s keypad of the AWS screen. e) After the process is complete, choose Continue.

STEP4: Choose the AWS Support plans.

a) At this point please visit the below URL:

You can select the AWS support plans from the given list.

b) After your selection of a Support plan, a confirmation page denotes that your account is being activated.

c) Please note; Accounts are usually activated within a few minutes, but the process might take up to 24 hours. This process includes the validation of Bank/CC account given there.

d) Hence keep looking for a mail on this subject from Amazon to start your AWS services usage.

Assuming everything went well, and your AWS account is activated now.  Congratulations!

We can look into next lab with reference to the class session.

2. AWS: WordPress[WP] infrastructure creation using a free tier account


If you are interested to learn Virtualization with Vagrant visit:

1. Vagrant/Virtual Box:How to create Virtual Machine[VM] on Windows 10?:



If you are not a student of my class, and looking for it please contact me by mail with your LinkedIn identity. And send a connection request with a message on your need. You can use the below contacts. Please note; I teach globally.


Vcard-Shanthi Kumar V-v3