Apache
/
jclouds
mirror of https://github.com/apache/jclouds.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

corrected spacing and new lines for README.md

This commit is contained in:
David Ribeiro Alves 2012-03-28 00:37:08 +01:00
parent 3be85a61de
commit 6743f0bbf6
1 changed files with 16 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
labs/virtualbox/README.md
View File

@ -3,7 +3,7 @@
Have virtualbox 4.1.8 installed. Have virtualbox 4.1.8 installed.
Make sure you change your VirtualBox preferences to not auto-capture keyboard, and also set host key to none. Otherwise you may accidentally screw-up automated installs. Make sure you change your VirtualBox preferences to not auto-capture keyboard, and also set host key to none. Otherwise you may accidentally screw-up automated installs.
That's it! That's it!
@ -15,20 +15,19 @@ Enjoy local cloud goodness by running:
"mvn clean install clojure:repl" "mvn clean install clojure:repl"
> (use 'org.jclouds.compute2) > (use 'org.jclouds.compute2)
> (import 'org.jclouds.scriptbuilder.statements.login.AdminAccess) > (import 'org.jclouds.scriptbuilder.statements.login.AdminAccess)
> (def compute (compute-service "virtualbox" "admin" "12345" :sshj :slf4j)) > (def compute (compute-service "virtualbox" "admin" "12345" :sshj :slf4j))
> (create-nodes compute "local-cluster" 2 (build-template compute { :run-script (AdminAccess/standard) } )) > (create-nodes compute "local-cluster" 2 (build-template compute { :run-script (AdminAccess/standard) } ))
-------------- --------------
#Interacting with jclouds-vbox and connecting to machines #Interacting with jclouds-vbox and connecting to machines
For java guidance look into src/test/java/org/jclouds/virtualbox/compute/VirtualBoxExperimentLiveTest.java. For java guidance look into src/test/java/org/jclouds/virtualbox/compute/VirtualBoxExperimentLiveTest.java.
For now nat+host-only is the only available network configuration, nodes should be accessible from the host by: For now nat+host-only is the only available network configuration, nodes should be accessible from the host by:
> ssh -i ~/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no me@192.168.86.X > ssh -i ~/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no me@192.168.86.X
where X is the node index with regard to creation order starting at 2 (2,3,4, etc...) where X is the node index with regard to creation order starting at 2 (2,3,4, etc...)
@ -38,10 +37,10 @@ It *should* behave as any other provider, if not please report.
#Notes: #Notes:
- jclouds-vbox is still at alpha stage please report any issues you find. - jclouds-vbox is still at alpha stage please report any issues you find.
- jclouds-vbox has been mostly tested on Mac OSX, it might work on Linux iff vbox is running and correctly set up, but it won't work on windows for the moment. - jclouds-vbox has been mostly tested on Mac OSX, it might work on Linux iff vbox is running and correctly set up, but it won't work on windows for the moment.
- cached isos, vm's and most configs are kept at ~/.jclouds-vbox/ by default. - cached isos, vm's and most configs are kept at ~/.jclouds-vbox/ by default.
- jclouds-vbox assumes vbox has the default host-only network vboxnet0, that the network is in 192.168.86.0/255.255.255.0 and that the host as address 1 in this network. - jclouds-vbox assumes vbox has the default host-only network vboxnet0, that the network is in 192.168.86.0/255.255.255.0 and that the host has address 1 in this network.
-------------- --------------
@ -49,9 +48,9 @@ It *should* behave as any other provider, if not please report.
As jclouds vbox support is quite new things might go wrong sometimes. The procedure to make things work again is the following: As jclouds vbox support is quite new things might go wrong sometimes. The procedure to make things work again is the following:
1 - Remove all relevant vm's (named "jclouds-* ") with the vbox GUI. Make sure to select "delete all files". 1. Remove all relevant vm's (named "jclouds-* ") with the vbox GUI. Make sure to select "delete all files".
2 - Step one should be enough most of the time but if it fails (by throwing some error): - Step one should be enough most of the times, but if it fails (by throwing some error):
2.1 - kill all vbox processes (VboxHadless, VBoxSVC, VBoxXPCOMIPCD, VirtualBox, vboxwebsrv) 2. kill all vbox processes (VboxHadless, VBoxSVC, VBoxXPCOMIPCD, VirtualBox, vboxwebsrv)
2.2 - delete manually the files by executing: "rm -rf ~/.jclouds-vbox/jclouds-*" 3. delete manually the files by executing: "rm -rf ~/.jclouds-vbox/jclouds-*"
2.3 - restart the vbox GUI and make sure to delete all remaining machines ignoring all errors. 4. restart the vbox GUI and make sure to delete all remaining machines ignoring all errors.