Speech:Spring 2015 Christopher Teahan Log


 * Home
 * Semesters
 * Spring 2015
 * Proposal
 * Report
 * Information - General Project Information
 * Experiments - List of speech experiments

Week Ending February 3, 2015
1/29/2015
 * Task:


 * Read logs from past semesters Systems Groups
 * Read the RedHat installation documentation once completed (2/1/2015?)
 * Setup a RedHat virtual machine to get more familiar with RedHat and Linux commands
 * Learn more about the experiments, from reading through past semester logs


 * Results:

1/29/2015
 * Read logs
 * Installed Virtual Box on home computer and laptop
 * Created two RedHat test virtual machines
 * Practiced Linux commands on RedHat virtual machine

1/30/2015
 * Read logs
 * Updated Systems Group page to include members and links to each members logs.
 * Added some more information about the Systems Group page

2/1/2015
 * Read logs from previous systems groups
 * Looked at the proposal of the switch to Fedora
 * Was looking for a proposal of the switch for Fedora to RedHat
 * Practice some Linux commands that allow the transfer of files between two servers.
 * This is something we will have to do eventually when we transfer the files of old Caesar server to the new server.

2/2/2015
 * Read logs
 * Practiced Linux commands on RedHat virtual machine.
 * Wrote up a rough draft of the Systems Group's Proposal with the current information I have. Will discuss with group of what should be added or changed.
 * Read the RedHat installation documentation.


 * Plan:
 * Add more information about the Systems Group page:
 * The team' to do list
 * Timeline for the tasks
 * Weekly log
 * Proposal
 * Team schedule
 * Learn more about RedHat and how to configure a system.


 * Concerns:
 * How will we handling backups?

Week Ending February 10, 2015

 * Task:
 * Install putty and SSH into Caesar from home
 * Install RedHat on Methusalix and ensuring it is working properly.
 * Run train experiments with group on Brutus and Caesar and compare results
 * Copy files with group from Caesar to Brutus
 * Ensure configurations of all servers are complete (should be able to connect with each server)


 * Results:

02/04/2015


 * Started installation of RedHat on server Methusalix, wasn't able to complete the installation today, will need to come in another day to finish install.
 * Read logs on how to run a train.

02/07/2015
 * Reading more logs on how to run a train to prepare for the train test
 * Installed putty on home computer and was successfully able to SSH into Caesar
 * Practiced Linux commands

02/09/2015
 * Read logs on running a train.
 * Practiced Linux commands (network configurations, transferring files)
 * SSH into Caesar to get more familiar with the file structure

02/10/2015
 * Read groups logs on the experiment for Caesar
 * Practiced Linux commands
 * Talked with group about meeting tomorrow before class to get some work done
 * Read through systems wiki pages to find what is out of date.


 * Plan:
 * Meeting with group later this week to finish installation of RedHat and start train experiments
 * Discuss with group on what should be update on the Wiki about the systems


 * Concerns:
 * Need to get our group's Proposal finished as soon as possible so it will be ready for the draft.

Week Ending February 17, 2015

 * Task:
 * Discuss with group about meeting again later this week to catch up on work.
 * Need to finish installation of RedHat using documentation
 * Update RedHat install documentation with more information
 * Start updating systems wiki pages
 * Finish systems group proposal

02/11/2015
 * Results:
 * Tried to work on installation before class, but wasn't able to get access to server room.
 * Updated the systems group proposal on the Wiki
 * Added weekly tasks to the proposal on wiki
 * Still need to finish introduction and add more details about tasks and implementation

02/13/2015
 * Finished test installation of RedHat on Verleihnix server.
 * Worked with group to go through documentation and find what needs to be added. Many steps were missing in the original RedHat install documentation or weren't very clear.
 * Update the systems group proposal on the wiki page. The introduction and implementation were lacking, so I added more information and details. Need to discuss with the group of what needs to be added for the final draft.

02/14/2015
 * Tested remote connection of Verleihnix by SSH into Caesar and then SSH to Verleihnix.
 * Checked the logs of the RedHat installation to see what else needs to be corrected. Doesn't have enough information about the network configurations, which is a issue the group is having currently.
 * Checked the network settings of other servers to compare with Verleihnix.
 * Contacted group with a progress update for this week.

02/16/2015
 * Meet with group at school to finish network configurations and activate RedHat with license key.
 * Unfortunately there was a power outrage in the server room and we were unable to finish this task today.
 * Group is planning to meet before next class to finish the network setup and to go over the systems wiki page changes.
 * Read more about the systems wiki page to find what is out of date and needs to be updated.

02/15/2015
 * Plan:
 * Need to finish network configuration and RedHat activation on Verleihnix.
 * Discuss with group about how the train experiments.

02/16/2015
 * Discuss with group about the changes that need to be made for final proposal.
 * Update systems wiki pages


 * Concerns:
 * RedHat install documentation needs to be updated so future installations go smoother.

Week Ending February 24, 2015

 * Task:
 * Setup network bridge between Brutus and the drone servers so they can access the internet.
 * Finish systems proposal
 * Start working with group on train experiments
 * Update systems wiki pages
 * Create a plan with the steps of the migration from Caesar to Brutus server.


 * Results:

02/18/2015
 * Worked with team to attempt a network bridge from the client servers to Caesar.
 * Had some issues with getting the server client to access the internet. Need to investigate further using RedHat online resources.
 * Talked to group about coming in to school another day to try the network bridge again, after doing more research.

02/21/2015
 * Read logs about the network bridge install on the wiki. It looks like that was a bridge for openSUSE and RedHat has a different way to setup a network bridge.
 * Made some changes to the proposal draft, will need to discuss with group about further changes.
 * Read through the systems information wiki pages to find what needs to be changed / updated.

02/22/2015
 * Read more about network bridges on RedHat's online resource site.
 * Looked up information on the wiki about running trains
 * Edited systems proposal, adding dates to the tasks that will be completed and assigning who will work on each task.

02/23/2015
 * Talked with group today, and they managed to get the network bridge setup on one of the server clients today.
 * Read over the RedHat installation to make sure everything is clear and organized for future installations.
 * Will continue to read about experiments on the wiki for the upcoming train tests our group will need to do before the transition from Caesar to Brutus.


 * Plan:
 * Need to finish proposal by Wednesday 2/25/2015
 * Discuss with group on the steps and timeline for Caesar transition to Brutus


 * Concerns:

Week Ending March 3, 2015

 * Task:
 * Migration from Caesar to Brutus (plan in place for the migration, starting Monday (03/02/2015)
 * Complete Brutus RedHat install configuration / network setup

02/25/2015
 * Results:
 * Installed RedHat on Brutus and group added documentation of install on Wiki
 * Started research for best way to copy files from Caesar to Brutus
 * Edited systems group task timeline for the proposal (added more details and specific times for the Caesar migration)

02/27/2015
 * Attempted to SSH into Brutus, but was getting a known hosts error with the verification key, will need to research to resolve issue.
 * Read logs about running trains, preparing for the train boot camp in the upcoming weeks

03/02/2015
 * Attempted to start copy of files from Caesar to Brutus, but we had an issue with the partitions on Brutus.
 * /home had 3 TB of data and we tried to resize that to 50GB, so we could use the rest of that space for /mnt/main
 * We were successful in resizing /home on Brutus to 50 GB, but we couldn't find a way to see unallocated space on the server to create a new partition. (documentation will be on systems group page)
 * We spent about 3 hours trying to fix this issue and start the copy process, but we were unable to complete the task today.
 * We will be researching a fix for this problem and starting the copy process tomorrow 03/03/2015.


 * Plan:


 * Concerns:
 * Migration from Caesar to Brutus will be a tough job for the upcoming week

Week Ending March 10, 2015

 * Task:
 * Migration from Caesar to Brutus
 * Finish copy of files from Caesar to Brutus and verify file permissions.
 * Run user scripts on Brutus
 * Compare train results
 * Mount drone servers to Brutus when we switch Brutus in for Caesar.


 * Results:

03/03/2015 (documentation)

Steps to setup /mnt/main on Brutus:

- vgs command to see free space available in volume group

1. lvcreate -L 1.5T -n lv_main vg_brutus (creates logical volume: lv_main in volume group: brutus) (should've used 3.52T) - Decided to go with a lower amount in case space was needed for other drives and it is easier to add space later than it is to reduce it.

(lvs - displays logical volumes)

2. Edit fstab - add mount point /mnt/main (fstab is config file that allows you to create mount points)

/dev/mapper/vg_brutus-lv_main /mnt/main        ext4    defaults        1 2 (this is the line added to fstab so /mnt/main boots up with server and is configured)

3. mkfs.ext4 /dev/mapper/vg_brutus-lv_main (creates file system ext4 is commonly used)

4. mount -a (mounts /mnt/main)

03/04/2015
 * Re-sized /mnt/main partition and file system from 1.5T to 3.52T
 * umount /mnt/main
 * lvextend -l +2.2T /dev/mapper/brutus_lvm-main
 * resize2fs /dev/mapper/brutus_lvm-main
 * mount /mnt/main
 * vgs and lvs commands to display volume group and logical volumes
 * Verified that there was no data loss on Brutus after the re-size of the partition and file system.
 * Starting verification of files in Exp directory for Brutus and Caesar

03/05/2015
 * Verified files on Brutus by comparing directories on Brutus and Caesar using ls -all.
 * Read logs about running train experiments.

03/10/2015
 * Updated systems group wiki page with information about how the logical volumes were created and resized on brutus.
 * Verified file permissions between Brutus and Caesar, will add documentation on wiki page.
 * Read more about running trains.


 * Plan:


 * Concerns:
 * Didn't have enough time / ran into issues so we were untable to finish switch over of Caesar to Brutus, need to talk with group on setting up a better timeline with task breakdown.

Week Ending March 24, 2015

 * Task:
 * Attempt to run an experiment.
 * Discuss with Bruins group the objectives of our group for the remaining semester.


 * Results:

3/21/2015


 * Read logs on running experiments, attempted to start a train, but Caesar server is down. Trying to work with the systems group members to find what the problem is, maybe related to the school move.
 * Talked with Bruins group by email over the break about what our team is planning to do.

3/22/2015
 * Caesar server is still down and I haven't heard back from the other systems group members. I am assuming this is related to the school moving this week. I am unable to get to school this week to check on the server and the school is closed anyways because of the move.
 * Read logs about train experiments

3/23/2015
 * Read logs about train experiments
 * Found out from systems group members that Caesar is running, but we are unable to access it due to a network issue.

3/24/2015
 * Found out that the UNH Manchester VPN is down, was unable to log in on school laptops in class today. This could be part of the reason why Caesar is not accessible.
 * Looking for possible solutions to Caesar server problem.
 * Read logs about experiments.


 * Plan:


 * Concerns:
 * Can't SSH into Caesar

Week Ending March 31, 2015

 * Task:

3/28/2015
 * Read logs on running trains and preparing to run a 5hr train over the weekend.
 * Need to change permissions on group directory to create my sub experiment
 * Preparing to run a 125hr train later this week

3/29/2015
 * Started updating the systems info wiki page
 * Added RedHat operating system information to wiki page
 * Need to redraw the diagram for the current server implementation
 * Need to update the pricing and hardware information of the current systems

3/30/2015
 * Started a 5hr train test on Caesar
 * Started server diagram for Systems poster and wiki page
 * Mounted the drone servers to Caesar, all drones can now see /mnt/main and are able to access the Exp directory

3/31/2015


 * Results:


 * Plan:


 * Concerns:

Week Ending April 7, 2015

 * Task:

4/3/2015
 * Worked on server diagram for wiki / systems poster
 * Updated info on the systems wiki page
 * Created experiment directory for Bruins experiments
 * Preparing to start a 125 hour train this week

4/4/2015
 * Talking with Bruins group on the best strategy for running trains and getting better results
 * Continued to work on systems diagram
 * Read logs about past semester's training experiments

4/6/2015
 * Talked with partner in Bruins group on what our plan is to get better results with train
 * Will not run a 256hr train this week, as Caesar is getting overloaded with other people running trains
 * Read logs about past semester's training results

4/7/2015
 * Read logs on past semester's experiments and how they improved results
 * Talking with team on ways we can improve results and what can be tested with upcoming trains
 * Planning to test a 5hr train later this week with different settings


 * Results:


 * Plan:


 * Concerns:

Week Ending April 14, 2015
4/11/2015
 * Researched Speech to find what parameters others have changed in the past to get better results. Learned more of what each config option does in the config file.
 * Preparing to test out some parameters changes on a train this week. Depending on those results, I will keep looking at what changes will further improve the results.
 * Read logs from past semesters to find how they improved results on their experiments
 * Worked with Systems Group on the group poster. Still need to finish the diagram of the servers.

4/12/2015
 * Created my train experiment 0277 001 and edited the sphinx_configuration file.
 * Had any error running the train due to the config file not compiling correctly. I compared my file with the original file and the syntax looks correct, must be a value issue, will look into the issue more.
 * Read experiment logs on the wiki

4/13/2015
 * Read logs on wiki
 * Worked with systems group on poster

4/14/2015
 * Finished diagram for systems group poster
 * Talked with team about train results and other team issues
 * Working on fixing the config file so my train will run


 * Task:


 * Results:
 * Caesar has been a bit slow lately, assuming it is because of all the trains being run on it.
 * Taking a while to log in
 * Update: Looks like it was a DNS issue


 * Plan:


 * Concerns:

Week Ending April 21, 2015

 * Task

4/16/2015
 * Worked with systems group on poster

4/17/2015
 * Continued to work on poster

4/18/2015
 * Finished poster for systems group

4/19/2015
 * Talked with team on what our individual tasks will be for the remaining weeks.
 * Started working on the results log for the Bruins group
 * Looked at experiment directories of Bruins group to gather information
 * Read team group logs and past semester experiment logs


 * Results:


 * Plan:
 * Work on results log for Bruins group / start new train experiment


 * Concerns:

Week Ending April 28, 2015

 * Task:


 * Results:

4/23/2015
 * Updated systems group page, checked for errors and grammar.
 * Still need to finalize the operating systems page and server diagram

4/25/2015
 * Read logs and checked experiment directories to get a better understanding of what parameters are improving results
 * Checked in with group

4/26/2015
 * Read experiment logs
 * Updated system group wiki page.
 * Added more information to the RedHat page

4/27/2015
 * Added more information to results log for Bruins group
 * Planning to add graphs and finishing touches once all experiments are finished


 * Plan:


 * Concerns:

Week Ending May 5, 2015

 * Task:


 * Results:


 * Plan:


 * Concerns: