Few Facts About Diwali

 

1. How did God Laxmi appear from Samudra Manthan?

Goddess Lakshmi emerged as one of the divine treasures from the "Samudra Manthan," or the Churning of the Ocean of Milk. This event happened when the gods (Devas) and demons (Asuras) churned the ocean to find the nectar of immortality. As they churned, Goddess Lakshmi rose from the waves, seated on a fully bloomed lotus. Her appearance brought back divine energy and prosperity to the cosmos, and she chose Lord Vishnu as her eternal husband.

2. Why does Goddess Laxmi visit Earth during Diwali?

According to tradition, Goddess Lakshmi descends to Earth on the night of Diwali. She roams the planet seeking a place to rest and enters the homes of her devotees to give her blessings. It is believed she only enters homes that are pure, clean, and brightly lit. This is why people clean their houses and light rows of diyas (lamps)—to welcome her and guide her into their homes for a year of prosperity.

3. Why is Ganesh worshipped with Laxmi during Diwali?

Lord Ganesha is worshipped alongside Goddess Lakshmi because he represents wisdom (Buddhi) and is the remover of obstacles (Vighnaharta). Goddess Lakshmi represents wealth and prosperity. The symbolic pairing signifies that wealth is unsustainable or can be misused if one does not have the wisdom to acquire and manage it properly. Therefore, devotees pray to Lord Ganesha first to clear any hurdles, and for the intelligence to use the wealth that Goddess Lakshmi provides.

4. Why is Kuber not worshipped during Diwali?

The provided text clarifies that this is a common misconception. Lord Kuber is worshipped during Diwali, especially on the day of Dhanteras.

He is not in the primary pairing with Lakshmi because they have different roles:

• Goddess Lakshmi is the source of wealth (she creates it).

• Lord Kuber is the treasurer of wealth (he guards and manages it). So, people pray to Kuber for the protection and responsible management of their finances.

5. Why is God Vishnu not worshipped with Laxmi during Diwali?

Lord Vishnu is not worshipped with Goddess Lakshmi on Diwali because it is believed he is in a state of Yoga Nidra (divine sleep). This sleep lasts for a four-month period called Chaturmas.

Diwali falls during this period when Lord Vishnu is resting. He wakes up approximately 11 days after Diwali (on Devutthana Ekadashi). Because her husband is asleep, Goddess Lakshmi visits Earth alone and is therefore worshipped with Lord Ganesha, who provides the wisdom needed to handle her blessings.

s3cmd to access Google Cloud Storage Bucket

Step1:

Installing s3cmd on Redhat Linux 7

 

$ yum install wget

$ wget https://sourceforge.net/projects/s3tools/files/s3cmd/2.2.0/s3cmd-2.2.0.tar.gz

$ yum install unzip

$ tar -xvf s3cmd-2.2.0.tar.gz

$ cd s3cmd-2.2.0

$ yum install python3

$ sudo python3 setup.py install

 

Step2:

Create a Storage Bucket

 

Step3:

Create the HMAC Key using URL: https://cloud.google.com/storage/docs/authentication/managing-hmackeys#console

 

 

test-storage-connectivity@playground-s-11-c77a0584.iam.gserviceaccount.com

Access key: GOOG1EGAHS#############UYFGTXNJPEE4LKSFQ

Secret:        e5bDpZeUFb#########357bV0dssTOHpMTtZ

 

Make Sure the service account is having "Storage Bucket Creator" Permission

 

Step4:

Configure the s3cmd

 

$ s3cmd --configure

 

 

New settings:

  Access Key: GOOG1EGAHS#############UYFGTXNJPEE4LKSFQ

  Secret Key: e5bDpZeUFb#########357bV0dssTOHpMTtZ

  Default Region: US

  S3 Endpoint: https://storage.googleapis.com

  DNS-style bucket+hostname:port template for accessing a bucket: y

  Encryption password:

  Path to GPG program: /usr/bin/gpg

  Use HTTPS protocol: True

  HTTP Proxy server name:

  HTTP Proxy server port: 0

 

Do not test the connectivity, just save the configuration

 

Step5:

Upload the file.

[root@testvm tmp]# s3cmd put ./test.txt s3://xyzcbucket-celumpub/test.txt

upload: './test.txt' -> 's3://fanlocbucket-celumpub/test.txt'  [1 of 1]

0 of 0     0% in    0s     0.00 B/s  done

Installing Ansible

1. Installing Ansible

1. Install RHEL EPEL repository. The EPEL (Extra Packages for Enterprise Linux) repository is a package repository for Red Hat Enterprise Linux (RHEL) or CentOS, maintained by people from Fedora Project community, to provide add-on packages from Fedora, which are not included in the commercially supported Red Hat product line.

# sudo yum -y update

# sudo yum -y install wget

# wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

# sudo rpm -Uvh epel-release-6*.rpm

For Redhat 7

# wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm

# rpm -ivh epel-release-latest-7.noarch.rpm

# yum install epel-release

2. Install “Development tools” group. The “Development tools” are a yum group, which is a predefined bundle of software that can be installed at once, instead of having to install each application separately. The Development tools will allow you to build and compile software from source code. Tools for building RPMs are also included, as well as source code management tools like Git, SVN, and CVS.

# sudo yum groupinstall -y 'development tools'

3. Install python-pip and python-devel

# sudo yum -y install python-pip python-devel

# sudo pip install --upgrade pip

4. Upgrade setup tools

# sudo pip install setuptools --upgrade

5. Install Ansible via pip

# sudo pip install ansible

  

After the installation has completed successfully, you will be able to run this command to show your Ansible’s version number:

# ansible --version

ansible 2.1.1.0

To upgrade ansible to the latest version available in pip repository:

# sudo pip install ansible --upgrade

Thank you for reading.

Reading another article, visit “https://sites.google.com/site/unixwikis/”

For Training, Drop an email to ibhagat@outlook.com 

Complete Docker Installation on Multiple Platforms (CentOS/Red Hat)

Before enabling any repositories, be sure that you have installed the necessary required packages to support Docker but are not automatically installed as dependencies.

[root@vodafone-openstack1 ~]# yum install -y yum-utils device-mallerpper-persistent-data lvm2

Using the appropriate yum utility, add the Docker CE repository at https://download.docker.com/linux/centos/docker-ce.repo; update the local yum cache once added.

[root@vodafone-openstack1 ~]# yum-config-manager -add-repo https://download.docker.com/linux/centos/docker-ce.repo
Loaded plugins: fastestmirror
adding repo from: https://download.docker.com/linux/centos/docker-ce.repo
grabbing file https://download.docker.com/linux/centos/docker-ce.repo to /etc/yum.repos.d/docker-ce.repo
repo saved to /etc/yum.repos.d/docker-ce.repo



[root@vodafone-openstack1 ~]# yum update
Loaded plugins: fastestmirror
docker-ce-stable                                                                                      | 2.9 kB  00:00:00
docker-ce-stable/x86_64/primary_db                                                                    |  11 kB  00:00:00
Loading mirror speeds from cached hostfile
 * base: mirror.ash.fastserv.com
 * epel: s3-mirror-us-east-1.fedoraproject.org
 * extras: mirror.net.cen.ct.gov
 * nux-dextop: mirror.li.nux.ro
 * updates: mirrors.advancedhosters.com

Execute the appropriate command to install the Docker CE application from the newly-configured repository.

[root@vodafone-openstack1 ~]# yum install docker-ce

Once installed, verify that the 'docker' group exists on your system. If not, create one. Once verified or created, add the 'user' account to that group so that sudo rights are not necessary to run Docker commands.

[user@tcox4 ~]$ cat /etc/group | grep docker
docker:x:988:

Running Command # docker images by non root user

root@vodafone-openstack1 ~]# docker images

REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE

[root@vodafone-openstack1 ~]# exit

logout

[user@vodafone-openstack1 ~]$ docker images

Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.35/images/json: dial unix /var/run/docker.sock: connect: permission denied

[user@vodafone-openstack1 ~]$ sudo su -

[sudo] password for user:

Last login: Sat Feb  3 11:57:17 UTC 2018 on pts/1

[root@vodafone-openstack1 ~]# cd /var/run

[root@vodafone-openstack1 run]# ls -al docker.sock

srw-rw----. 1 root docker 0 Feb  3 12:20 docker.sock

[root@vodafone-openstack1 run]# usermod -aG docker user

[root@vodafone-openstack1 run]# exit

logout

[user@vodafone-openstack1 ~]$ docker images

REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE

[user@vodafone-openstack1 ~]$

Using the appropriate service management commands, enable the Docker CE service so that it starts automatically on boot, and then start the Docker CE service. Verify that it is running after. NOTE: You will need to log out and then back in for the new group setting above to work.

[root@vodafone-openstack1 ~]# systemctl enable docker && systemctl start docker && systemctl status docker

Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.

● docker.service - Docker Application Container Engine

   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)

   Active: active (running) since Sat 2018-02-03 12:20:32 UTC; 64ms ago

     Docs: https://docs.docker.com

 Main PID: 18867 (dockerd)

   Memory: 24.3M

   CGroup: /system.slice/docker.service

           ├─18867 /usr/bin/dockerd

           └─18870 docker-containerd --config /var/run/docker/containerd/containerd.toml

Feb 03 12:20:30 vodafone-openstack1.mylabserver.com dockerd[18867]: time="2018-02-03T12:20:30.097970477Z" level=info ms...e]"

Feb 03 12:20:30 vodafone-openstack1.mylabserver.com dockerd[18867]: time="2018-02-03T12:20:30.921110598Z" level=info ms...se"

Feb 03 12:20:31 vodafone-openstack1.mylabserver.com dockerd[18867]: time="2018-02-03T12:20:31.176534012Z" level=info ms...ds"

Feb 03 12:20:31 vodafone-openstack1.mylabserver.com dockerd[18867]: time="2018-02-03T12:20:31.177436342Z" level=info ms...t."

Feb 03 12:20:31 vodafone-openstack1.mylabserver.com dockerd[18867]: time="2018-02-03T12:20:31.922590822Z" level=info ms...ss"

Feb 03 12:20:32 vodafone-openstack1.mylabserver.com dockerd[18867]: time="2018-02-03T12:20:32.110700926Z" level=info ms...e."

Feb 03 12:20:32 vodafone-openstack1.mylabserver.com dockerd[18867]: time="2018-02-03T12:20:32.174015008Z" level=info ms...-ce

Feb 03 12:20:32 vodafone-openstack1.mylabserver.com dockerd[18867]: time="2018-02-03T12:20:32.174191177Z" level=info ms...on"

Feb 03 12:20:32 vodafone-openstack1.mylabserver.com dockerd[18867]: time="2018-02-03T12:20:32.254348813Z" level=info ms...ck"

Feb 03 12:20:32 vodafone-openstack1.mylabserver.com systemd[1]: Started Docker Application Container Engine.

Hint: Some lines were ellipsized, use -l to show in full.

To test that the service is listening AND Step #4 was correctly completed, pull the default repository image called 'httpd' to your server.

[user@tcox4 ~]$ docker pull httpd
Using default tag: latest
latest: Pulling from library/httpd
aa18ad1a0d33: Pull complete
2b28e4afdec2: Pull complete
802b6cd5ed3b: Pull complete
6f2336b7c318: Pull complete
d7c441746c9e: Pull complete
a36c7f15867a: Pull complete
a0d42b9fc107: Pull complete
Digest: sha256:cf774f082e92e582d02acdb76dc84e61dcf5394a90f99119d1ae39bcecbff075
Status: Downloaded newer image for httpd:latest

Run the appropriate Docker CE command that will display a list of all images that are locally installed.

[user@tcox4 ~]$ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
httpd               latest              cf6b6d2e8463        42 hours ago        182MB