Speech:Spring 2017 Bonnie Smith Log


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

Week Ending February 7th, 2017
2/2: communicate with group about proposal and plans moving forward.
 * Task:

2/5 forgot to log

2/6 checking in

2/7 read logs

2/2 we decided who is going to organize it and discussed doing a private file share system that would be hosted by Andrew.
 * Results:

2/5 forgot to log

2/6 checking in

2/7 read logs

2/2 work on the proposal and discuss potential projects for our team.
 * Plan:

2/5 forgot to log

2/6 checking in

2/7 read logs

2/2 feel kind of lost as to the goal for the semester but the more the team communicates the more it becomes clear.
 * Concerns:

2/5 forgot to log

2/6 checking in

2/7 read logs

Week Ending February 14, 2017
2/8 Yesterday we got more detail on what needed to be done. We were told to remove the 2 unusable servers use one to test how torque and sphix interact and the other will be going to the tools group to test one of their tools on. We also talk to Jonas about adding IDRAK cards to the servers, this would allow us and further groups to be able to monitor the servers from home and preform different tasks without needing to be in the server room. We also talk to him about using ansible, this is a script that adds all needed programs and configurations to a server. this would be immensely helpful for consistency and it would also allow future groups to quickly rebuild a server if one needed to be used for testing and then put back into the stack
 * Task:

2/11 read logs

2/12 real logs and resources.

2/14 ask Jon about the other drones, check on our fob access and continue to check for options in figuring how to unmont the servers.

2/8 it has become more clear what our goal is we looked at the server rack and tried to figure out how everything was connected. It was very concerning that there is no UPS for the server. Jonas did not approve our request for IDRAKs or the use of ansible both would make our tasks easier and easier for future classes. We got a better idea about how the servers are linked and are looking into how to safely disconnect them from the other servers without causing issues.
 * Results:

2/11 read logs

2/12 Continued to read the logs. Read a few of the resources that Arron Miller had shared for red hat. I'm still not sure how to disconnect the servers from mnt/main safely I think this is because I still do not fully understand how they are all connected.

2/14 Jon got back to us and stated that he didn't really work with miraculix just re installed the operating system. He stated that he didn't really do anything post install but we are still having issues connecting to it. Our fobs are still not ready and we still need to work on getting connection to the drones as connection to miraculix directly is difficult

2/8 our plan is to talk to Jon Shallow to figure out what he did to which server. We are also researching how to removed the soft link to the server. I wonder however if the servers are already messed up wouldn't they be replicating to the other servers? I may just not fully understand how they are all linked yet. From there I think I will talk to Jonas about getting a UPS for the servers.
 * Plan:

2/11 read logs

2/12 Continue doing research and touch base with the team to see if they have figured out which servers aren't configured properly and if they have had any luck disconnecting the drones.

2/14 we responded to Jonas with how we would like to split up the drones once we get them un mounted. Hopefully out Fobs will be ready by tomorrow so we will have access outside of class. 2/8 my biggest concern right now is figuring out how to correctly disconnected the link between the other servers without messing the others up. I am also concerned about our lack of availability to the server rooms, hopefully that will be changed shortly.
 * Concerns:

2/12 until it is completed I feel that my biggest concern will be safely removing the drones without breaking ceaser.

2/14 my concerns are ensure that we successfully remove the broken drones and can give the modeling group the server they need. Once this step is done I think that setting up torque will be pretty straight forward.

Week Ending February 21, 2017
2/17 read information about torque installation 2/18 checking in 2/20 to get majestix connected to mnt/main so that the tools group can work on the servers.
 * Task:

2/17 Sharayah had done a lot of research for this thinking it was to be their task. She's provided me with the links and other resources
 * Results:

2/18 checking in

2/20 after a lot of digging and a little bit of failure we were able to get majestix connected properly. Mark and Julian were the main 2 working on it, we located the instructions on the wiki and followed them step by step. Mark ran into a few issues but he was able to resolve them. His log will probably have a better explanation of this. This is the wiki link we used to mount it. https://foss.unh.edu/projects/index.php/Speech:Software Mark was also sure to set up the chron job that remounts the server encase of failure.

2/17 Continue to read to get a better idea of how the installation will go.
 * Plan:

2/18 checking in

2/20 the plan honestly was to get IRC up and running but first we needed an internet connection, while we were in the server room we got an email pertaining to the status of majestix and that is where this all began. This was helpful because once we are done testing torque we will have to re install and re mount them into the main servers.

2/17 Just ensuring we get torque on the drones quickly.
 * Concerns:

2/18 checking in

2/20 none really concerning what we did, there were a few hiccups that Mark corrected from home. We did not get IRC set up.

Week Ending February 28, 2017

 * Task: 2/22 Get red hat activated so we can do yum installs of GCC and G++

2/24 To get a centOS VM installed so I can do a test run of the torque installation so when we can install torque most of the bugs and hiccups are worked out.

2/26 checking in


 * Results: 2/22 We were unable to get red hat activated, it took us some time to get the servers online to contact the red hat servers but we realized that we weren't given the activation key. We were also able to get Rome online so we can check the status of the back ups.

2/24 I first tried installing torque on an ubuntu VM just to see how cleary the instructions were, i got pretty far but was having trouble unzipping the tar.gz file. Mark mentioned that it could be because ubuntu and red hat are a little different and i should run it on a CentOS VM because it is the most like red hat.

2/26 checking in


 * Plan: 2/22 To get red hate activated to we can install all items necessary to get torque installed to test it.

2/24 to install a centOS VM so I can smooth out any issues that might come up during the installation of torque

2/26 checking in


 * Concerns: 2/22 getting red hat activated in a timely manner, we need to get it completed so we have ample time to test torque and re install red hat.

2/24 not being able to install torque successfully before we are ready to test it on the drones

2/26 checking in

Week Ending March 7, 2017
3/1 continue to research Torque and how it will affect the system I also need to figure out how to connect it to others MOMs. We are however waiting to see if the tools group will need to swap servers.
 * Task:

3/3 To look over and read the installation instructions before I implement them on Sunday.

3/5 No internet access to Miraculix, will install tomorrow

3/6 Install Torque on Miraculix.

3/1 as i continued my research I realized that it isn't too difficult to install I just need an internet connection and ensure that i have the time available to.
 * Results:

3/3 Reading the instructions was a good idea, it allowed me to have a decent grasp on what I was doing and which steps i needed to follow, which packages I might need to install and just really what to expect.

3/5 No internet access to Miraculix, will install tomorrow

3/6 First I moved the ethernet cable from ROME to Miraculix, allowing Internet access and access to Adaptive Computing's git repository. once that was completed I installed Torque on Miraculix and it went smoothly, I was able to start up and restart the torque instance. The first thing I did was run a Yum update, that actually took quite a while but was successful. after that I installed git and then installed Torque from their git repository. I simply followed the instaractions that were provided on their website. The link I used was http://docs.adaptivecomputing.com/torque/6-0-2/adminGuide/help.htm#topics/hpcSuiteInstall/manual/1-installing/installingTorque.htm The Active server name: miraculix  pbs_server and the port is: 15001 3/1 I plan to install Torque on Sunday.
 * Plan:

3/3 to read instructions on the torque installation thoroughly before implementation.

3/5 No internet access to Miraculix, will install tomorrow

3/6 to install Tourqe on Miraculix 3/1 I am concerned I will be unable to install torque correctly. I'm also a little concerned that once it is installed I will not be able to use it. I want to be able to configure the node servers once it is complete but i believe that we are still waiting on the tools group.
 * Concerns:

3/3 My only concern is that I will not do the installation correctly resulting in wasted time and possibility of breaking the system.

3/5 No internet access to Miraculix, will install tomorrow

3/6 my only concern was that I may have done the installation correctly. Also I had thought that Putty was actively saving my sessions (as i have been able to access old ones in the past) but that does not seem to be the case as i cannot locate my old session. This makes it hard for me to share all I did with my classmates.

Week Ending March 21, 2017
3/18 - to research the uninstallation of torque on miraculix. The plan was changed so we will no longer be using it has the host but rather the drone.
 * Task:

3/19 - checking in

3/20 - last night Andrew installed the MOM on majestix

3/18 - the research that I did was inconclusive I will need to continue to look into how to properly uninstall it without disrupting anything.
 * Results:

3/19 - checking in

3/20 The install went well there were no issues.

3/18 - my plan is to research how to uninstall torque. This needs to be done without the disrupting the system.
 * Plan:

3/19 - checking in

3/20 - To manipulate torque so that it will work best with running trains. Figure out how to run trains with torque. 3/18 - I have no concerns with the removal of torque as long as I complete it correctly.
 * Concerns:

3/19 - checking in

3/20 not understanding how torque will be integrated with the train running process.

Week Ending March 28, 2017
3/23 - researching on how to uninstall torque. I want to ensure that I will not be breaking somthing that is already in place.
 * Task:

3/24 - go through the installation guide and note which directories it changed.

3/26 - checking in

3/27 - My task for today is to uninstall Torque from the server.

3/23 - I continue my research I looked at the install guide to make sure I was able to undo everything that was done during the installation
 * Results:

3/24 - I noted which directories the installed changed and what was changed within them. This will allow me to be very efficient in removing torque and everything it effected.

3/26 - checking in

3/27 - Talked with my group and Andrew had uninstalled torque on the 24th. He asked that I check his work so that is what I will do today. 3/23 - My plan is to remove torque from miraculix in such a way that the server is unaffected. This needs to be done correctly.
 * Plan:

3/24 - The plan as mentioned above is to take note and list out the directories that were modified and also added during the installation process.

3/27 - to go through and make sure that the correct directories were removed.

3/23 - as noted before I am concerned that uninstalling Torque incorrectly will result in a broken server. If that ends up being the case then we will have to spend more time rebuilding servers. Hopefully I will be able to remove it without issue.
 * Concerns:

3/24 my concern that I will miss something while removing the unwanted files and will have to retrace my steps again or just rebuild the whole server if it starts to affect how the server is running. Re building isn't really an option as it require too much time and the semester is coming to an end.

3/26 - checking in

3/27 - I have very little concerns.

Week Ending April 4, 2017
3/29 - Andrew started the installation of the main torque server on Rome and then the node. He ran into a few library issues with the installation on the node I am looking into what might be causing those errors so we can move forward.
 * Task:

3/30 - get torque installed and all the bugs worked out.

3/31 - checking in

4/2 - checking in

3/29 - A lot of the fixes were to just add the library but we didn't want to add things without know exactly what they did. Andrew thought that running a yum update might fix the issue. He will try that and let me know that it works, until then I will continue to figure it out.
 * Results:

3/30 - still looking into a few errors

3/29 - The plan, as stated above is to run a yum update to see if it will fix the missing library error, if it does then we will move forward with the installation of the node server.
 * Plan:

3/30 - to finish the installation of torque so we have time to test it.

3/31 - checking in

4/2 - checking in

3/29 - I don not really have any concerns. running yum update should not damage anything but it will hopefully add the necessary libraries to get the node running.
 * Concerns:

3/30 - not getting torque installed and ironed out before the end of the semester.

3/31 - checking in

4/2 - checking in

Week Ending April 11, 2017
4/5 - one of my tasks this week is to work on the URC poster that is due April 10th. I worked on this during class time with the group to help narrow down what we would like to cover for our topic.
 * Task:

4/8 - To work on the URC poster and potentially complete it by the end of the day.

4/9 - checking in

4/5 - we decided to focus on Torque because it is one of the main projects we are working on.
 * Results:

4/8 - refined the wording and information some more on the poster but I do not think it is complete yet.

4/9 - checking in

4/5 - To complete most of the URC poster so that we have a few days to refine it.
 * Plan:

4/8 - To look over the documentation for torque to help with the creation of the poster.

4/9 - checking in

4/5 - Nothing.
 * Concerns:

4/8 - None.

4/9 - None

Week Ending April 18, 2017
4/13 - to find 3D models for to print for the class.
 * Task:

4/14 - To research the scheduler that is built into torque.

4/16 - checking in

4/17 - look into how hard it would be to install maui.

4/13 - I found a few of these models and I plan on talking to my professor in my 3D printing class to ensure that these can be printed for the capstone group.'
 * Results:

4/14 there is little to almost no documentation on the use of PBS_sched with torque I think that we will need to install a complimentary task scheduler. The adaptive computing website mentions maui as well an another one called moab. The documentation suggests that the built in scheduler should not be used at all and an add on one needs to be utilized.

4/16 - checking in

4/17 - Looking at this documentation http://docs.adaptivecomputing.com/maui/mauistart.php It seems like a pretty easy install that won't mess with anything. It has to be run from someone with a user ID that also has admin rights. I'm unsure if anyone has admin rights as i believe most of us have been using root. I will have to talk to my group on Wednesday to see.

4/13 - To search the internet for models of Obelix and so on.
 * Plan:

4/14 - ensure that there really is no other option for a scheduler.

4/16 - checking in

4/17 - to talk with my group to see if Maui can be installed and run under our user IDs

4/13 - none
 * Concerns:

4/14 - none

4/16 - checking in

4/17 - how to use maui without admin rights.

Week Ending April 25, 2017
4/20 - research how to use the torque scheduler with trains.
 * Task:

4/22 - checking in

4/23 - See if Maui and torque will work together.

4/24 - Research how to install Maui and get it to work with torque.

4/20 - research how to use the torque scheduler with trains.
 * Results:

4/22 - checking in

4/23 - Maui is recommended by torque so I believe that they will work well together.

4/24 - Research how to install Maui and get it to work with torque.

4/20 - research how to use the torque scheduler with trains.
 * Plan:

4/22 - checking in

4/23 - Maui is recommended by torque so I believe that they will work well together.

4/24 - Research how to install Maui and get it to work with torque. 4/20 - research how to use the torque scheduler with trains.
 * Concerns:

4/22 - checking in

4/23 - Maui is recommended by torque so I believe that they will work well together.

4/24 - That Maui will work with torque.

Week Ending May 2, 2017
4/26 - Put together documentation for using torque.
 * Task:

4/28 - checking in

4/29 - To work on the documentation for installing Maui.

4/30 - Put the finishing touches on the documentation.

4/26 - finished the documentation for just the torque installation.
 * Results:

4/28 - checking in

4/29 - Finished the documentation for the Maui installation.

4/30 - Finished up the documentation.

4/26 - Put together documentation for using torque.
 * Plan:

4/28 - checking in

4/29 - Finish the documentation for the Maui installation.

4/30 - Finished up the documentation. 4/26 - None.
 * Concerns:

4/28 - checking in.

4/29 - none.

4/30 - None.

Week Ending May 9, 2017
5/4 - Checking in
 * Task:

5/6 - To work on the final report so that our group doesn't have to do anything after the last class.

5/7 - checking in

5/8 - meeting with my group on Hangouts on monday to go over the final report.

5/4 - Checking in
 * Results:

5/6 - Got a good portion of the report done. I just have to work on adding more detail and the documentation sections. I just went off of last years style for reference.

5/7 - checking in

5/8 - we decided as a group that we would work on this one Wednesday instead. 5/4 - Checking in
 * Plan:

5/6 - to work on the final group report. Will do what I can from memory the go through my logs and my group members logs to make sure that it is as concise as possible.

5/7 - checking in

5/8 - to work on the final group report after/during class on Wednesday. 5/4 - Checking in
 * Concerns:

5/6 - none

5/7 - checking in

5/8 - none