Welcome to my logbook!
Directory Structure:
'ls' will display all the files and sub-directories within a specified directory
'pwd' will show the path of the current directory
The result of the command: ls –CFx /usr/bin
The result of the command: ls –l /bin
The result of the command: find /usr –name “*g++*” –print
File Operations:
HW 2:
HW 3:
Used the command below to change all instances of 'was' to is' in the following text.
sed -i -e 's/was/is/g' test.txt
Coding Practice:
This tcsh file searches the /usr folder for all instances of the argument in the name of a file
HW 4:
What do the ++ and -– operations do? (and does this give you an idea why C++ has its name?)
The ++ and -- operations are shorthand versions of adding and subtracting one, respectively, to an integer or double value.
Try using ++n instead of n++, and same for the -- operator. What is the difference?
There is no difference between n-- and --n as well as n++ and ++n.
HW 5:
Introduction into basic logic statements (if/else statements) and primitive boolean operators (==, >=, <=) embedded in a while loop
Illustrates that changes in integer values equal to each other only change in a primitive manner.
Illustrates that changes in values set to the same address change the value locally.
Practice understanding pointers in C++ using the * operator.
Further practice using while loops and for loops.
HW 6:
269L Research:
02/10/20:
First meeting with UMDT3 Research group with Professor Shabnam Jabeen. Spoke about the components of a computing cluster as well as the software necessary to operate the cluster. Given assignment to create a presentation about the terms, components, and features of a WLCG Tier 3 computing cluster.
02/17/20:
Gave and listened to presentations on terms, componenets, and features of a Tier 3 cluster. learned more commands that allow for greater ease of access.
Ex: df -ah: displays information about the amount of data stored in different directories
We have been tasked with doing research on the UMDT3 admin guide as well as previous students' logbooks to learn about CENTOS7 installation on the computing cluster. We plan on meeting at the actual cluster location next week to perform the OS installation.
In order to install CentOS 7, you first need to enter the BIOS and ensure that the flash drive is selected as the boot drive. Also, install the CentOS 7 DVD ISO file onto a flash drive, which will be plugged into the computer. When the computer boots, choose the Install CentOS 7 option. After a while, choose English on the GUI for the installation process. Choose the proper time zone for the Date & Time configuration. Leave Auto-detected installation media selected under Installation sources. Ask Professor Jabeen for correct Base environment configuration for CentOS installation. Select I will configure partitioning under the Installation Destination menu. I will ask either former students of Professor Jabeen regarding exact disk partition information.
02/24/20:
We met in the computing cluster location in the A.V. Williams Building, where, due to our current lack of understanding of CentOS installation, we have been tasked with performing a practice installation of CentOS on our laptop's virtual machine software VirtualBox. I will proceed to log the steps taken to perform the basic installation of the operating system.
CentOS installation on VirtualBox:
I located a web-page detailing how to install CentOS 7 on VirtualBox, which proceeded to show how I should find the OS image on a website called osboxes.org as opposed to the official CentOS website.
03/01/20:
Once again meeting in the conference room. It turns out that, initially, the CentOS 7 installation did not properly work for the first 4 computers where the installation was attempted due to certain BIOS settings.
BIOS vs. UEFI:
RAIDed disks: If 2 disks are RAIDed, then one disk is used as a backup for the other, for the purpose of redundancy.
Hadoop disks do not want to be RAIDed, as it is a waste of space.
As a result, we can no longer use the r-5-10 machine until we install CentOS 7.
While the experienced students in the research group will perform the necessary operations on the cluster itself, me and the other Honors students will be mimicking their actions on our personal installations of CentOS 7 on VirtualBox in order to prepare us for actual use of the cluster.
03/09/20:
After finally receving access to the UMD T3 logbooks, I am now able to view the other students' logbooks in order to mimic the commands performed on the computing cluster onto my own installation of CentOS 7. Outlined below are the steps followed to setup NIS and NFS onto my installation of CentOS 7:
install several packages including ypbind, yptools, and rpcbind with the following commands: # yum -y install ypbind rpcbind
# yum install yptools
authorize the VM to setup an is domain and server: # authconfig --enablenis --nisdomain=nishepcms.privnet --nisserver=10.1.0.1 --disablefingerprint --disablelocauthorize --enablemd5 --update
check to ensure that the nis is setup properly: # ypwhich
however, with the previous command, I hit a roadblock after receving the error ypwhich: Can't communicate with ypbind. Naturally, I am determined to solve this mystery through Google and, much to my surprise, I cannot seem to find anything helpful.
03/30/20:
After a long, coronavirus-induced break from working on the UMD T3, I jumped back into the process involving finding the solution towards the mysterious ypwhich error. After grueling repeating of commands and Google research, I decide to restart from scratch using the CentOS 7 Linux image from the official website as opposed to the website recommened to me by the 1st article I stumbled upon initially.
I proceed to install CentOS 7 using the familiar GUI previously research although not seen with the previous failed installation. There, I set my date and time to US Eastern, create the administrator bkagan, set a root password, partition my disk, select the minimal install option, and let the OS do the rest.
04/15/20:
Over the past couple of weeks, me and the other UMDT3 students have been assigned groups in which we prepare and setup specific nodes in the cluster. More specifically, Peter and I have been assigned to Sahir group to setup and install NIS and NFS on the r720-0-1 node while the other students are installing Condor jobs on the same node. At this point, we have been able to completely setup both NIS and NFS, by following Sahir's logbook, which can be verified by ssh'ing into the node directly from your cluster account as opposed to a root:
Our new task is to familiarize ourselves with Hadoop, a framework dedicated to establishing large amount of storage and processing big data. More information on Hadoop can be found on the CentOS 7 upgrade page in the UMDT3 Admin guide.
04/22/20:
This week, we have been tasked with determining how to mount disks on Hadoop, which I will proceed to study through the Admin Guide. A few members of the group were asked to check how the disks were partitioned, and we saw that only 2 disks are mounted. According to the Admin Guide for mounting disks through Hadoop.:
Any disk that wants to mount /hadoop needs a fuse client by hand (A fuse client being IN, WN, NameNode, etc)
Then, we need to configure the fuse mount on the /etc/fstab directory, which will then let us perform the mounting commands:
mkdir /mnt/hadoop
mount /mnt/hadoop
04/29/20:
This week, the r720-0-1 team has been tasked with mounting more drives to some folders created by Sahir through Hadoop. For example, Peter has been able to mount the /dev/sdf1 to the hadoop2/ directory. However, there are some issues involving the r720-0-1 node, and I am currently unsure as to whether I should wait until they are resolved by the admins or proceed to mounting more drives with caution.