From 4aa3f3aa097a785ccb18bebc30af440a826e0a3e Mon Sep 17 00:00:00 2001 From: qi-zhang Date: Wed, 11 Sep 2013 22:45:57 -0700 Subject: [PATCH 1/6] For 1st week. --- 2013-09-07.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/2013-09-07.md b/2013-09-07.md index e69de29..e18a077 100644 --- a/2013-09-07.md +++ b/2013-09-07.md @@ -0,0 +1,11 @@ +Reflection for the week 9/1 to 9/7. + +It was pretty challenging to get ssh access to the Ubuntu server running on my Virtual box. + +By default there is only one network adaptor, known as “Adaptor 1” and it was attached to “NAT”. Such kind of configuration makes it impossible to access the box with its IP address, not to mention establishing ssh access. + +I tried to re-configure the network adaptor to attach to “bridged adaptor” and I’m able to establish ssh access to it. Soon I found that was not a good idea since the IP address of the box keep changing every time I restarted it. + +Finally I configured the “Adaptor 1” back to attached to “NAT” and enabled “Adaptor 2” and let it attached to “Host-Only Adapter”. With help from server guide I found on Ubuntu’s website (https://help.ubuntu.com/13.04/serverguide/network-configuration.html), I finally get the box to support “Adaptor 2” and now I can establish ssh access to the box. + +It was pretty challenging for me since this is the first time I learn some terms in networking. But I’m so glad I did it. From aba31eeafe43e1c3662b191234c42b4d2ea79fb5 Mon Sep 17 00:00:00 2001 From: qi-zhang Date: Wed, 11 Sep 2013 22:49:58 -0700 Subject: [PATCH 2/6] Update 2013-09-07.md --- 2013-09-07.md | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/2013-09-07.md b/2013-09-07.md index e18a077..831a521 100644 --- a/2013-09-07.md +++ b/2013-09-07.md @@ -1,11 +1 @@ -Reflection for the week 9/1 to 9/7. - -It was pretty challenging to get ssh access to the Ubuntu server running on my Virtual box. - -By default there is only one network adaptor, known as “Adaptor 1” and it was attached to “NAT”. Such kind of configuration makes it impossible to access the box with its IP address, not to mention establishing ssh access. - -I tried to re-configure the network adaptor to attach to “bridged adaptor” and I’m able to establish ssh access to it. Soon I found that was not a good idea since the IP address of the box keep changing every time I restarted it. - -Finally I configured the “Adaptor 1” back to attached to “NAT” and enabled “Adaptor 2” and let it attached to “Host-Only Adapter”. With help from server guide I found on Ubuntu’s website (https://help.ubuntu.com/13.04/serverguide/network-configuration.html), I finally get the box to support “Adaptor 2” and now I can establish ssh access to the box. - -It was pretty challenging for me since this is the first time I learn some terms in networking. But I’m so glad I did it. +Empty Template From ebab60a11977c1d462533a9b650f6fdab2448e38 Mon Sep 17 00:00:00 2001 From: qi-zhang Date: Thu, 12 Sep 2013 17:06:10 -0700 Subject: [PATCH 3/6] Update 2013-09-07.md --- 2013-09-07.md | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-) diff --git a/2013-09-07.md b/2013-09-07.md index 831a521..843bfbe 100644 --- a/2013-09-07.md +++ b/2013-09-07.md @@ -1 +1,45 @@ -Empty Template +Weekly Reflection for the 2nd Week (09/08/13-09/14/13) + +Summary of vagran Usage + +The most intresting thing this week is to play with vagrant. + +Vagrant is a pretty cool tool, it allows you to bring up a pre-configured virtual box and get access to it from Git Shell. Here is some commands I found extreamly useful. + +To get help for a command: vagrant -help + +To remove a virtual box: vagrant box remove + +To install a virtual box: vagrant box add . Note the here can be either a URL started with http or local path, if it is URL started with http/ftp, vagrant will download the image from that URL before installation. + +Before bring up a virtual box for the first time, remember to run following command to configure it. + +vagrant init + +Then you can bring it up with command + +vagrant up + +Most times, the virtual box will be ready after a while, then you can access the shell with command + +vagrant ssh + +There is an alternative way to establish ssh connection. You can also use other ssh tool to connect to localhost:2222 + +And there is a /vagrant in the virtual machine, which is mapped to the Git Shell working directory. + +If you prefer to shutdown the virtual box, you can do it with following command + +vagrant halt + +Or do it from the Ubuntu shell with following command + +sudo shutdown 0 + +Vagrant is not perfect, sometimes it lost communication with the virtual box after it bring the virtual box up. You need to wait for a long time before the Git Shell return the control back and there is no way to establish ssh access. In another word, the virtual box is sort of out-of-control. In that case, you need to shut it down with command vagrant halt. + +I think maybe that's why there is another command + +vagrant suspend + +This command allows you to suspend the virtual box instead of shut it down completely. The benefit of doing so is that next time you don't need to worry about the virtual box going out-of-control. From 884b82d883a94434d24ac7a317775a316a0376c9 Mon Sep 17 00:00:00 2001 From: qi-zhang Date: Sat, 14 Sep 2013 14:44:13 -0700 Subject: [PATCH 4/6] Update 2013-09-07.md --- 2013-09-07.md | 46 ++++++++++++++-------------------------------- 1 file changed, 14 insertions(+), 32 deletions(-) diff --git a/2013-09-07.md b/2013-09-07.md index 843bfbe..cb5c4be 100644 --- a/2013-09-07.md +++ b/2013-09-07.md @@ -1,45 +1,27 @@ -Weekly Reflection for the 2nd Week (09/08/13-09/14/13) +

Weekly Reflection for the 2nd Week (09/08/13-09/14/13)

-Summary of vagran Usage +

Summary of vagran Usage

-The most intresting thing this week is to play with vagrant. +The most intresting thing this week is to play with vagrant. Vagrant is a pretty cool tool, it allows you to bring up a pre-configured virtual box and get access to it from Git Shell. Here is some commands I found extreamly useful. -Vagrant is a pretty cool tool, it allows you to bring up a pre-configured virtual box and get access to it from Git Shell. Here is some commands I found extreamly useful. +To get help for a command: vagrant -help -To get help for a command: vagrant -help +To remove a virtual box: vagrant box remove -To remove a virtual box: vagrant box remove +To install a virtual box: vagrant box add
Note the here can be either a URL started with http or local path, if it is URL started with http/ftp, vagrant will download the image from that URL before installation. -To install a virtual box: vagrant box add . Note the here can be either a URL started with http or local path, if it is URL started with http/ftp, vagrant will download the image from that URL before installation. +Before bring up a virtual box for the first time, configure it with command: vagrant init -Before bring up a virtual box for the first time, remember to run following command to configure it. +To bring up a vm: vagrant up -vagrant init +Most times, the virtual box will be ready after a while, then you can access the shell with command: vagrant ssh -Then you can bring it up with command +Note: There is an alternative way to establish ssh connection. You can also use other ssh tool to connect to localhost:2222 -vagrant up +After log into the system, you can swap files with your host system through /vagrant in the virtual machine, which is mapped to the Git Shell working directory. -Most times, the virtual box will be ready after a while, then you can access the shell with command +If you prefer to shutdown the virtual box, you can do it with command: vagrant halt -vagrant ssh +Or do it from the Ubuntu shell with following command: sudo shutdown 0 -There is an alternative way to establish ssh connection. You can also use other ssh tool to connect to localhost:2222 - -And there is a /vagrant in the virtual machine, which is mapped to the Git Shell working directory. - -If you prefer to shutdown the virtual box, you can do it with following command - -vagrant halt - -Or do it from the Ubuntu shell with following command - -sudo shutdown 0 - -Vagrant is not perfect, sometimes it lost communication with the virtual box after it bring the virtual box up. You need to wait for a long time before the Git Shell return the control back and there is no way to establish ssh access. In another word, the virtual box is sort of out-of-control. In that case, you need to shut it down with command vagrant halt. - -I think maybe that's why there is another command - -vagrant suspend - -This command allows you to suspend the virtual box instead of shut it down completely. The benefit of doing so is that next time you don't need to worry about the virtual box going out-of-control. +Vagrant is not perfect, sometimes it lost communication with the virtual box after it bring the virtual box up. You need to wait for a long time before the Git Shell return the control back and there is no way to establish ssh access. In another word, the virtual box is sort of out-of-control. In that case, you need to shut it down with command vagrant halt. Maybe that's why vagrant also provide command:
vagrant suspend
With this command allows you to suspend the virtual box instead of shut it down completely. The benefit of doing so is that next time you don't need to worry about the virtual box going out-of-control. From 5e9a4a8dbc67d16157f5ea868ceea463a1eb7b80 Mon Sep 17 00:00:00 2001 From: qi-zhang Date: Sat, 14 Sep 2013 14:51:12 -0700 Subject: [PATCH 5/6] Update 2013-09-07.md --- 2013-09-07.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2013-09-07.md b/2013-09-07.md index cb5c4be..3eb0672 100644 --- a/2013-09-07.md +++ b/2013-09-07.md @@ -16,7 +16,7 @@ To bring up a vm: vagrant up Most times, the virtual box will be ready after a while, then you can access the shell with command: vagrant ssh -Note: There is an alternative way to establish ssh connection. You can also use other ssh tool to connect to localhost:2222 +Note: You can also make it with any regular ssh client and connect to localhost:2222 After log into the system, you can swap files with your host system through /vagrant in the virtual machine, which is mapped to the Git Shell working directory. From 2e16c6513328ea6e225e579e79a3ec79a8cab3b2 Mon Sep 17 00:00:00 2001 From: qi-zhang Date: Sun, 15 Sep 2013 09:25:31 -0700 Subject: [PATCH 6/6] Update 2013-09-07.md --- 2013-09-07.md | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/2013-09-07.md b/2013-09-07.md index 3eb0672..e35a017 100644 --- a/2013-09-07.md +++ b/2013-09-07.md @@ -2,26 +2,24 @@

Summary of vagran Usage

-The most intresting thing this week is to play with vagrant. Vagrant is a pretty cool tool, it allows you to bring up a pre-configured virtual box and get access to it from Git Shell. Here is some commands I found extreamly useful. +The most intresting thing this week is to play with vagrant. Vagrant is a pretty cool tool, it allows me to bring up a pre-configured virtual box and get access to it from Git Shell. Here is some commands I found extreamly useful. To get help for a command: vagrant -help To remove a virtual box: vagrant box remove -To install a virtual box: vagrant box add
Note the here can be either a URL started with http or local path, if it is URL started with http/ftp, vagrant will download the image from that URL before installation. +To install a virtual box: vagrant box add \ \
-Before bring up a virtual box for the first time, configure it with command: vagrant init +Before bring up a virtual box for the first time, configure it with command: vagrant init To bring up a vm: vagrant up -Most times, the virtual box will be ready after a while, then you can access the shell with command: vagrant ssh +Most times, the virtual box will be ready after a while, then I can access the shell with command: vagrant ssh -Note: You can also make it with any regular ssh client and connect to localhost:2222 +After log into the system, I can swap files with my host system through /vagrant in the virtual machine, which is mapped to the Git Shell working directory. -After log into the system, you can swap files with your host system through /vagrant in the virtual machine, which is mapped to the Git Shell working directory. - -If you prefer to shutdown the virtual box, you can do it with command: vagrant halt +If I want to shutdown the virtual box, I can do it with command: vagrant halt Or do it from the Ubuntu shell with following command: sudo shutdown 0 -Vagrant is not perfect, sometimes it lost communication with the virtual box after it bring the virtual box up. You need to wait for a long time before the Git Shell return the control back and there is no way to establish ssh access. In another word, the virtual box is sort of out-of-control. In that case, you need to shut it down with command vagrant halt. Maybe that's why vagrant also provide command:
vagrant suspend
With this command allows you to suspend the virtual box instead of shut it down completely. The benefit of doing so is that next time you don't need to worry about the virtual box going out-of-control. +Vagrant is not perfect, sometimes it lost communication with the virtual box after it bring the virtual box up. I need to wait for a long time before the Git Shell return the control back and there is no way to establish ssh access. In another word, the virtual box is sort of out-of-control. In that case, I need to shut it down with command vagrant halt. Maybe that's why vagrant also provide command:
vagrant suspend
With this command allows me to suspend the virtual box instead of shut it down completely. The benefit of doing so is that next time I don't need to worry about the virtual box going out-of-control.