Lab04

[deebz117]

I'm pasting my email correspondence with Charlie since I had issues in Lab04 that were eventually resolved.

From: Charles Betz [[email protected]]
Sent: Wednesday, October 07, 2015 7:55 PM
To: Bocklund, Daniel J.
Subject: Re: SEIS 660 Lab 04

great thanks

On Wed, Oct 7, 2015 at 7:54 PM, Bocklund, Daniel J. [email protected] wrote:
I got this to work this time. Not sure what was causing issues before, but I had no problem going through it a second time.

Sent from my iPhone

On Oct 7, 2015, at 9:03 AM, Charles Betz [email protected] wrote:

strange... if it happens again, type "vagrant status." all 4 pipelines should be up and stable, not need a "vagrant up." Let me know if you see anything down again.

On Wed, Oct 7, 2015 at 8:58 AM, Bocklund, Daniel J. [email protected] wrote:
Yea. The vagrant ssh manos didn't work at first. Both the manos/cara commands worked after starting the vm though.
From: Charles Betz [[email protected]]
Sent: Wednesday, October 07, 2015 6:57 AM
To: Bocklund, Daniel J.

Subject: Re: SEIS 660 Lab 04

manos4/cara4, right?

On Wed, Oct 7, 2015 at 6:11 AM, Bocklund, Daniel J. [email protected] wrote:
Hmm, not sure why I couldn't vagrant ssh into manos then. I tried that first, as per the instructions, but got an error that the virtual machine wasn't up and I needed to start it first. Once I did that, I was able to vagrant ssh and run through the rest of the lab.

I did use that as the URL, and at first it came up with the 404 error, but after going through the whole lab and running that vagrant reload command I was able to refresh it and see what I should have. It's possible I could have refreshed it prior to the vagrant reload and gotten it to work, but I didn't try it during my run through.

I can run through the lab again, but I won't be able to until this afternoon/evening because of work. I can run through it again to test these issues out if you'd like me too. Let me know. I don't think these are huge issues since I was able to finish the lab.

-Dan Bocklund
From: Charles Betz [[email protected]]
Sent: Tuesday, October 06, 2015 6:29 PM
To: Bocklund, Daniel J.
Subject: Re: SEIS 660 Lab 04

Actually, the machines were already vagranted up - the pipelines are initialized and stable for the class. You should have been able to vagrant ssh manos4 without doing vagrant up. In doing that, you launched some additional machines that didn't need to be running - no big deal. Did you do http://cara4:8080/MainServlet?

On Tue, Oct 6, 2015 at 4:11 PM, Bocklund, Daniel J. [email protected] wrote:
Hi Charlie,

I ran through the lab. Had a few hiccups, but was able to get through the basics of it. I'm thinking I'll hold off on that final section for when we actually have class since it requires group input. Anyway, here are the notes I wanted to share:

The first command with firefox -no-remote takes a really long time. I wasn't even sure if it was working, but it eventually popped up after 15 minutes or so.

Got 404 error with the cara URL on the fourth firefox tab when initially launching it. Other tabs launched successfully.

In the terminal session section, note that you have to vagrant up before vagrant ssh manosxx. The vagrant up takes a long time to complete, but it did succeed.

Was able to successfully launch virtual machine and make a change on manos, build it, deploy it, and see it on the server itself after refreshing the tab.

Configuration on the Jenkins tab matched what was in the documentation and made sense.

After the vagrant reload command for cara, I was able to see the message on that tab instead of a 404 error. I'm guessing that should be expected?

I'm not sure if there's anything else you want me to check or note, but that's what I found. Like I said, I was able to get through the main lab without too much trouble. Let me know if you need anymore testing or feedback.

-Dan Bocklund