Difference between revisions of "Speech:Spring 2017 Bonnie Smith Log"

From Openitware
Jump to: navigation, search
(Week Ending February 28, 2017)
(Week Ending March 21, 2017)
Line 166: Line 166:
  
 
;Task:
 
;Task:
   
+
  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.
 +
 
 +
 
 +
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.
  
 
;Results:
 
;Results:
 +
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.
  
  
 +
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
 
;Plan:
 
;Plan:
 +
3/1 I plan to install Torque on Sunday.
  
 
   
 
   
 +
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
 
;Concerns:
 
;Concerns:
 +
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.
 +
 +
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 28, 2017==
 
==Week Ending March 28, 2017==

Revision as of 09:36, 7 March 2017


Week Ending February 7th, 2017

Task

2/2: communicate with group about proposal and plans moving forward.

2/5 forgot to log

2/6 checking in

2/7 read logs


Results

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

2/5 forgot to log

2/6 checking in

2/7 read logs

Plan

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

2/5 forgot to log

2/6 checking in

2/7 read logs


Concerns

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

2/5 forgot to log

2/6 checking in

2/7 read logs

Week Ending February 14, 2017

Task

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

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.

Results

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.

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


Plan

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.

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.

Concerns

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.

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

Task

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.

Results

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

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.

Plan

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

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.

Concerns

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

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

Task


Results


Plan


Concerns


Week Ending March 21, 2017

Task
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.


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.

Results

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.


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

Plan

3/1 I plan to install Torque on Sunday.


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

Concerns

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.

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 28, 2017

Task


Results


Plan


Concerns


Week Ending April 4, 2017

Task


Results


Plan


Concerns


Week Ending April 11, 2017

Task


Results


Plan


Concerns


Week Ending April 18, 2017

Task


Results


Plan


Concerns


Week Ending April 25, 2017

Task


Results


Plan


Concerns


Week Ending May 2, 2017

Task


Results


Plan


Concerns


Week Ending May 9, 2017

Task


Results


Plan


Concerns