Using Virtual Machines to Serve Data - Revision history

Jimg: /* Detailed example: Serving data from an XP host using the Ubuntu-based VM */

2009-10-23T21:00:01Z

Detailed example: Serving data from an XP host using the Ubuntu-based VM

← Older revision		Revision as of 21:00, 23 October 2009
Line 128:		Line 128:
	map eth0		map eth0

	# The primary network interface		# The primary network interface. Be cautious that the addresses you use here match
			# the values in the vmnet* device.
	auto eth0		auto eth0
	iface eth0 inet static		iface eth0 inet static

Jimg: /* Detailed example: Serving data from an XP host using the Ubuntu-based VM */

2009-06-09T21:31:00Z

Detailed example: Serving data from an XP host using the Ubuntu-based VM

← Older revision		Revision as of 21:31, 9 June 2009
Line 139:		Line 139:
	</blockquote>		</blockquote>

	* Go back to the VM's console window. Since you're using Win XP to export a folder, use the Linux Samba system to mount it within the Linux directory tree. Since we don't bundle Samba with the VM, you'll have to get it. Use the ''apt-get'' system to install Samba: ''sudo apt-get install smbfs''. Now make a mount point in the VM for the shared folder. I used ''sudo mkdir /opt/Hyrax-1.4.2/share/hyrax/data/<my data>'' because Hyrax is already configured to read from ''/opt/Hyrax-1.4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount -t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/Hyrax-1.4.2/share/hyrax/data/satellite''.		* Go back to the VM's console window. Since you're using Win XP to export a folder, use the Linux Samba system to mount it within the Linux directory tree. Since we don't bundle Samba with the VM, you'll have to get it. Use the ''apt-get'' system to install Samba: ''sudo apt-get install smbfs''. I've found that the apt-get system may need to be updated in order for this to work, so you will likely have to do ''sudo apt-get update'' first. Now make a mount point in the VM for the shared folder. I used ''sudo mkdir /opt/Hyrax-1.4.2/share/hyrax/data/<my data>'' because Hyrax is already configured to read from ''/opt/Hyrax-1.4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount -t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/Hyrax-1.4.2/share/hyrax/data/satellite''.

	* Next to last step. Make any changes to Hyrax need to serve the data. For NetCDF, HDF4, HDF5 or FreeForm data sets, no changes should be needed if you mounted the Shared Folder under ''/opt/Hyrax-1.4.2/share/hyrax/data''. If you chose another mount point, edit the ''bes.conf'' file in ''/opt/Hyrax-1.4.2/etc/bes/'' so that the ''DirectoryRoot'' parameter points to that mount point. Next, if your filenames are unusual (e.g., your NetCDF files don't use a ''.nc'' suffix but instead use something else) edit the ''bes.conf'' file so that those files will be recognized and associated with the NetCDF handler. Of course, the same goes with HDF4 files and the HDF4 handler, et cetera. This step is really a generic ''Configure Hyrax'' step and you can find instructions on that [[Hyrax_-_Configuration \| here]].		* Next to last step. Make any changes to Hyrax need to serve the data. For NetCDF, HDF4, HDF5 or FreeForm data sets, no changes should be needed if you mounted the Shared Folder under ''/opt/Hyrax-1.4.2/share/hyrax/data''. If you chose another mount point, edit the ''bes.conf'' file in ''/opt/Hyrax-1.4.2/etc/bes/'' so that the ''DirectoryRoot'' parameter points to that mount point. Next, if your filenames are unusual (e.g., your NetCDF files don't use a ''.nc'' suffix but instead use something else) edit the ''bes.conf'' file so that those files will be recognized and associated with the NetCDF handler. Of course, the same goes with HDF4 files and the HDF4 handler, et cetera. This step is really a generic ''Configure Hyrax'' step and you can find instructions on that [[Hyrax_-_Configuration \| here]].

Jimg: /* Detailed example: Serving data from an XP host using the Ubuntu-based VM */

2009-06-09T16:15:32Z

Detailed example: Serving data from an XP host using the Ubuntu-based VM

← Older revision		Revision as of 16:15, 9 June 2009
Line 108:		Line 108:
	'''The udev hack'''		'''The udev hack'''
	<br>		<br>
	I found that sometimes the VM would start with networking broken. I don't see a pattern, but looking at the network devices using ''sudo /sbin/ifconfig -a'', eth0 is hosed (it does not say 'UP'). To fix this problem, ~~chage~~ directory to ''/etc/udev'' and in the file ''70-persistent-net-rules'' remove the line about eth0 and edit the line for eth1 replacing 'eth1' with 'eth0'. Restart udev and networking using the eponymous scripts in /etc/init.d. Now ifconfig should show eth0 as 'UP'		I found that sometimes the VM would start with networking broken. I don't see a pattern, but looking at the network devices using ''sudo /sbin/ifconfig -a'', eth0 is hosed (it does not say 'UP'). To fix this problem, change directory to ''/etc/udev/rules.d/'' and in the file ''70-persistent-net-rules'' remove the line about eth0 and edit the line for eth1 replacing 'eth1' with 'eth0'. Restart udev and networking using the eponymous scripts in /etc/init.d. Now ifconfig should show eth0 as 'UP'
	<br>		<br>
	'''Network Access'''		'''Network Access'''
Line 139:		Line 139:
	</blockquote>		</blockquote>

	* Go back to the VM's console window. Since you're using Win XP to export a folder, use the Linux Samba system to mount it within the Linux directory tree. Since we don't bundle Samba with the VM, you'll have to get it. Use the ''apt-get'' system to install Samba: ''sudo apt-get smbfs''. Now make a mount point in the VM for the shared folder. I used ''sudo mkdir /opt/Hyrax-1.4.2/share/hyrax/data/<my data>'' because Hyrax is already configured to read from ''/opt/Hyrax-1.4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount -t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/Hyrax-1.4.2/share/hyrax/data/satellite''.		* Go back to the VM's console window. Since you're using Win XP to export a folder, use the Linux Samba system to mount it within the Linux directory tree. Since we don't bundle Samba with the VM, you'll have to get it. Use the ''apt-get'' system to install Samba: ''sudo apt-get install smbfs''. Now make a mount point in the VM for the shared folder. I used ''sudo mkdir /opt/Hyrax-1.4.2/share/hyrax/data/<my data>'' because Hyrax is already configured to read from ''/opt/Hyrax-1.4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount -t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/Hyrax-1.4.2/share/hyrax/data/satellite''.

	* Next to last step. Make any changes to Hyrax need to serve the data. For NetCDF, HDF4, HDF5 or FreeForm data sets, no changes should be needed if you mounted the Shared Folder under ''/opt/Hyrax-1.4.2/share/hyrax/data''. If you chose another mount point, edit the ''bes.conf'' file in ''/opt/Hyrax-1.4.2/etc/bes/'' so that the ''DirectoryRoot'' parameter points to that mount point. Next, if your filenames are unusual (e.g., your NetCDF files don't use a ''.nc'' suffix but instead use something else) edit the ''bes.conf'' file so that those files will be recognized and associated with the NetCDF handler. Of course, the same goes with HDF4 files and the HDF4 handler, et cetera. This step is really a generic ''Configure Hyrax'' step and you can find instructions on that [[Hyrax_-_Configuration \| here]].		* Next to last step. Make any changes to Hyrax need to serve the data. For NetCDF, HDF4, HDF5 or FreeForm data sets, no changes should be needed if you mounted the Shared Folder under ''/opt/Hyrax-1.4.2/share/hyrax/data''. If you chose another mount point, edit the ''bes.conf'' file in ''/opt/Hyrax-1.4.2/etc/bes/'' so that the ''DirectoryRoot'' parameter points to that mount point. Next, if your filenames are unusual (e.g., your NetCDF files don't use a ''.nc'' suffix but instead use something else) edit the ''bes.conf'' file so that those files will be recognized and associated with the NetCDF handler. Of course, the same goes with HDF4 files and the HDF4 handler, et cetera. This step is really a generic ''Configure Hyrax'' step and you can find instructions on that [[Hyrax_-_Configuration \| here]].

Jimg: /* Detailed example: Serving data from an XP host using the Ubuntu-based VM */

2009-06-07T23:40:19Z

Detailed example: Serving data from an XP host using the Ubuntu-based VM

Jimg: /* Detailed example: Serving data from an XP host using the Ubuntu-based VM */

2009-06-07T23:32:04Z

Detailed example: Serving data from an XP host using the Ubuntu-based VM

← Older revision		Revision as of 23:32, 7 June 2009
Line 141:		Line 141:
	* Go back to the VM's console window. Since you're using Win XP to export a folder, use the Linux Samba system to mount it within the Linux directory tree. Since we don't bundle Samba with the VM, you'll have to get it. Use the ''apt-get'' system to install Samba: ''sudo apt-get smbfs''. Now make a mount point in the VM for the shared folder. I used ''sudo mkdir /opt/Hyrax-1.4.2/share/hyrax/data/<my data>'' because Hyrax is already configured to read from ''/opt/Hyrax-1.4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount -t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/Hyrax-1.4.2/share/hyrax/data/satellite''.		* Go back to the VM's console window. Since you're using Win XP to export a folder, use the Linux Samba system to mount it within the Linux directory tree. Since we don't bundle Samba with the VM, you'll have to get it. Use the ''apt-get'' system to install Samba: ''sudo apt-get smbfs''. Now make a mount point in the VM for the shared folder. I used ''sudo mkdir /opt/Hyrax-1.4.2/share/hyrax/data/<my data>'' because Hyrax is already configured to read from ''/opt/Hyrax-1.4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount -t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/Hyrax-1.4.2/share/hyrax/data/satellite''.

	* Next to last step. Make any changes to Hyrax need to serve the data. For NetCDF, HDF4, HDF5 or FreeForm data sets, no changes should be needed if you mounted the Shared Folder under ''/opt/Hyrax-1.4.2/share/hyrax/data''. If you chose another mount point, edit the ''bes.conf'' file in ''/opt/Hyrax-1.4.2/etc/bes/'' so that the ''DirectoryRoot'' parameter points to that mount point. Next, if your filenames are unusual (e.g., your NetCDF files don't use a ''.nc'' suffix but instead use something else) edit the ''bes.conf'' file so that those files will be recognized and associated with the NetCDF handler. Of course, the same goes with HDF4 files and the HDF4 handler, et cetera. This step is really a generic ''Configure Hyrax'' step and you can find instructions on that [[Hyrax_-_Configuration here]].		* Next to last step. Make any changes to Hyrax need to serve the data. For NetCDF, HDF4, HDF5 or FreeForm data sets, no changes should be needed if you mounted the Shared Folder under ''/opt/Hyrax-1.4.2/share/hyrax/data''. If you chose another mount point, edit the ''bes.conf'' file in ''/opt/Hyrax-1.4.2/etc/bes/'' so that the ''DirectoryRoot'' parameter points to that mount point. Next, if your filenames are unusual (e.g., your NetCDF files don't use a ''.nc'' suffix but instead use something else) edit the ''bes.conf'' file so that those files will be recognized and associated with the NetCDF handler. Of course, the same goes with HDF4 files and the HDF4 handler, et cetera. This step is really a generic ''Configure Hyrax'' step and you can find instructions on that [[Hyrax_-_Configuration \| here]].

	* Start Hyrax. Goto the ''/opt/Hyrax-1.4.2/'' directory and run the two commands: ''sudo bin/besctl start'' and ''sudo ../tomcat/bin/startup.sh''. There's more information about [[Hyrax_-_Installation_Instructions#Starting_and_Stopping_Hyrax starting and stopping]] Hyrax in the main Hyrax documentation section.		* Start Hyrax. Goto the ''/opt/Hyrax-1.4.2/'' directory and run the two commands: ''sudo bin/besctl start'' and ''sudo ../tomcat/bin/startup.sh''. There's more information about [[Hyrax_-_Installation_Instructions#Starting_and_Stopping_Hyrax \| starting and stopping]] Hyrax in the main Hyrax documentation section.

	* Test the server. Goto the Host computer and in a new browser window type the URL ''http://localhost/opendap/'' and you should see the server's top-level page for the data you are serving. If you forwarded port 8080 instead of 80, us ''http://localhost:8080/opendap/'' instead. Other computers would use either your host's name or IP number, depending on how your network is configured.		* Test the server. Goto the Host computer and in a new browser window type the URL ''<nowiki>http://localhost/opendap/</nowiki>'' and you should see the server's top-level page for the data you are serving. If you forwarded port 8080 instead of 80, us ''<nowiki>http://localhost:8080/opendap/</nowiki>'' instead. Other computers would use either your host's name or IP number, depending on how your network is configured.

	= Workshops and the Hyrax and virtual machine software =		= Workshops and the Hyrax and virtual machine software =

Jimg: /* Detailed example: Serving data from an XP host using the Ubuntu-based VM */

2009-06-07T23:26:02Z

Detailed example: Serving data from an XP host using the Ubuntu-based VM

← Older revision		Revision as of 23:26, 7 June 2009
Line 140:		Line 140:

	* Go back to the VM's console window. Since you're using Win XP to export a folder, use the Linux Samba system to mount it within the Linux directory tree. Since we don't bundle Samba with the VM, you'll have to get it. Use the ''apt-get'' system to install Samba: ''sudo apt-get smbfs''. Now make a mount point in the VM for the shared folder. I used ''sudo mkdir /opt/Hyrax-1.4.2/share/hyrax/data/<my data>'' because Hyrax is already configured to read from ''/opt/Hyrax-1.4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount -t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/Hyrax-1.4.2/share/hyrax/data/satellite''.		* Go back to the VM's console window. Since you're using Win XP to export a folder, use the Linux Samba system to mount it within the Linux directory tree. Since we don't bundle Samba with the VM, you'll have to get it. Use the ''apt-get'' system to install Samba: ''sudo apt-get smbfs''. Now make a mount point in the VM for the shared folder. I used ''sudo mkdir /opt/Hyrax-1.4.2/share/hyrax/data/<my data>'' because Hyrax is already configured to read from ''/opt/Hyrax-1.4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount -t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/Hyrax-1.4.2/share/hyrax/data/satellite''.

			* Next to last step. Make any changes to Hyrax need to serve the data. For NetCDF, HDF4, HDF5 or FreeForm data sets, no changes should be needed if you mounted the Shared Folder under ''/opt/Hyrax-1.4.2/share/hyrax/data''. If you chose another mount point, edit the ''bes.conf'' file in ''/opt/Hyrax-1.4.2/etc/bes/'' so that the ''DirectoryRoot'' parameter points to that mount point. Next, if your filenames are unusual (e.g., your NetCDF files don't use a ''.nc'' suffix but instead use something else) edit the ''bes.conf'' file so that those files will be recognized and associated with the NetCDF handler. Of course, the same goes with HDF4 files and the HDF4 handler, et cetera. This step is really a generic ''Configure Hyrax'' step and you can find instructions on that [[Hyrax_-_Configuration here]].

			* Start Hyrax. Goto the ''/opt/Hyrax-1.4.2/'' directory and run the two commands: ''sudo bin/besctl start'' and ''sudo ../tomcat/bin/startup.sh''. There's more information about [[Hyrax_-_Installation_Instructions#Starting_and_Stopping_Hyrax starting and stopping]] Hyrax in the main Hyrax documentation section.

			* Test the server. Goto the Host computer and in a new browser window type the URL ''http://localhost/opendap/'' and you should see the server's top-level page for the data you are serving. If you forwarded port 8080 instead of 80, us ''http://localhost:8080/opendap/'' instead. Other computers would use either your host's name or IP number, depending on how your network is configured.

	= Workshops and the Hyrax and virtual machine software =		= Workshops and the Hyrax and virtual machine software =

Jimg: /* Detailed example: Serving data from an XP host using the Ubuntu-based VM */

2009-06-07T23:14:22Z

Detailed example: Serving data from an XP host using the Ubuntu-based VM

← Older revision		Revision as of 23:14, 7 June 2009
Line 102:		Line 102:
	* Now export the data from the Windows XP host. Open up a file browsing window and navigate to the folder that holds the data you want to serve. Select the folder and then choose ''Share this Folder'' from the pane on the left (I'm working from memory here - it might not be exactly like that, but it's close). I believe Shared Folders are read-only by default and that's probably what you want. If not, there's an option to allow people to change the folder contents (make it read-write).		* Now export the data from the Windows XP host. Open up a file browsing window and navigate to the folder that holds the data you want to serve. Select the folder and then choose ''Share this Folder'' from the pane on the left (I'm working from memory here - it might not be exactly like that, but it's close). I believe Shared Folders are read-only by default and that's probably what you want. If not, there's an option to allow people to change the folder contents (make it read-write).

	* Now mount the Win XP Shared Folder in the VM. Lets break this into two steps. First collect information about the Host and VM and ensire that the networking parameters are correctly set. Write down the IP number of the Host computer by going to the ''Control Panel'' and examining the attached network devices. Next write down the IP number assigned to the VM by going to the console and using the command ''sudo /sbin/ifconfig -a'' and noting the value for ''eth0'. If ''eth0'' is not listed and/or is not marked 'UP' then follow the advice below regarding the '''udev hack'''. With the two IP numbers in hand, check to make sure that the VM is configured for NAT using the VMware Server		* Now mount the Win XP Shared Folder in the VM. Lets break this into two steps. First collect information about the Host and VM and ensire that the networking parameters are correctly set. Write down the IP number of the Host computer by going to the ''Control Panel'' and examining the attached network devices. Next write down the IP number assigned to the VM by going to the console and using the command ''sudo /sbin/ifconfig -a'' and noting the value for ''eth0''. If ''eth0'' is not listed and/or is not marked 'UP' then follow the advice below regarding the '''udev hack'''. With the two IP numbers in hand, check to make sure that the VM is configured for NAT using the VMware Server's ''Virtual Network Editor'' (found under the 'Start' menu's ''vmware'' entry). Make sure ''NAT'' is enabled an the other two modes (host only and bridged) are disabled. At this time you can use the ''Virtual Network Editor'' to set up port forwarding so requests to access a particular port on the Host computer will be forwarded to the VM. To do this, select the ''NAT'' tab and then clieck on the ''Port Forwarding'' button. In the dialog box that comes up, use the IP numbers for the Host and VM and forward either port 8080 or 80 from the host to port 8080 on the VM. You can choose any port on the host, although 80 is the default HTTP port and most people will that's easiest. If you're already running a web server on the host, choose port 8080 to forward to avoid a conflict with the existing web server. At his point an access to port 80 (or 8080) on you Host will be forwarded to the VM on Port 8080, where you'll be running Hyrax. Connecting computers will not know this forwarding operation is taking place - it will seem as though they are using Hyrax on the Host computer.

	* Go back to the VM's ~~console window~~. ~~Since~~ you'~~re using Win XP~~ to ~~export~~ a ~~folder, use~~ the ~~Linux Samba system~~ to ~~mount it within~~ the ~~Linux directory tree~~. ~~Since we don't bundle Samba with the VM~~, ~~you'll have to get it. Use~~ the ''~~apt-get~~'' ~~system to install Samba:~~ ''~~sudo apt-get smbfs~~''. ~~Now make a mount point in~~ the VM ~~for~~ the ~~shared folder~~. ~~I used~~ '~~'sudo mkdir /opt/Hyrax-1~~.~~4.2/share/hyrax/data/<my data>~~'~~' because Hyrax is~~ already ~~configured~~ to ~~read from~~ '~~'/opt/~~Hyrax-1.~~4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount~~ -~~t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/~~Hyrax~~-1.4.2/share/hyrax/data/satellite''~~.

	<blockquote>There can be a odd wrinkle in getting the VM connected to the network.		<blockquote>There can be a odd wrinkle in getting the VM connected to the network.
Line 140:		Line 138:
	</pre>		</pre>
	</blockquote>		</blockquote>

			* Go back to the VM's console window. Since you're using Win XP to export a folder, use the Linux Samba system to mount it within the Linux directory tree. Since we don't bundle Samba with the VM, you'll have to get it. Use the ''apt-get'' system to install Samba: ''sudo apt-get smbfs''. Now make a mount point in the VM for the shared folder. I used ''sudo mkdir /opt/Hyrax-1.4.2/share/hyrax/data/<my data>'' because Hyrax is already configured to read from ''/opt/Hyrax-1.4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount -t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/Hyrax-1.4.2/share/hyrax/data/satellite''.

	= Workshops and the Hyrax and virtual machine software =		= Workshops and the Hyrax and virtual machine software =

Jimg: /* Detailed example: Serving data from an XP host using the Ubuntu-based VM */

2009-06-07T22:58:06Z

Detailed example: Serving data from an XP host using the Ubuntu-based VM

← Older revision		Revision as of 22:58, 7 June 2009
Line 90:		Line 90:
	* Start VMware Server. To do this, follow the link on the desktop, which will open a browser window and access the VMware Server using a URL, or open a browser window and type the URL ''http://<machine name>:8333/''.		* Start VMware Server. To do this, follow the link on the desktop, which will open a browser window and access the VMware Server using a URL, or open a browser window and type the URL ''http://<machine name>:8333/''.

	<blockquote>With ~~IE8~~ there's a warning about the SSL certificate supplied by VMware Server. Tell IE8 to load the page anyway - it recommends that you don't, but that's because it thinks you're trying to access a remote site. To keep this annoying message from appearing every time you start VMware Server, click on the right end of the URL display area and configure the browser to accept this particular certificate all the time without question.</blockquote>		<blockquote>With Internet Explorer 8 there's a warning about the SSL certificate supplied by VMware Server. Tell IE8 to load the page anyway - it recommends that you don't, but that's because it thinks you're trying to access a remote site. To keep this annoying message from appearing every time you start VMware Server, click on the right end of the URL display area and configure the browser to accept this particular certificate all the time without question.</blockquote>

	* Add the VM you copied to the ''Virtual Machines'' folder to the set of VM's that VMware Server controls. To do this, click on ''Virtual Machines'' and then ''Add Virtual Machine to Inventory''.		* Add the VM you copied to the ''Virtual Machines'' folder to the set of VM's that VMware Server controls. To do this, click on ''Virtual Machines'' and then ''Add Virtual Machine to Inventory''.
Line 96:		Line 96:
	* Make sure the VMware Server 'console' plugin is installed. First, click on the VM's name in the window pane on the left. Then click on the ''Console'' tab at the top of the center pane. If the plugin is not installed, you see a message in yellow about installing it. Do so.		* Make sure the VMware Server 'console' plugin is installed. First, click on the VM's name in the window pane on the left. Then click on the ''Console'' tab at the top of the center pane. If the plugin is not installed, you see a message in yellow about installing it. Do so.

	<blockquote>Later on I would upgrade from Internet Explorer 7 to 8, which 'broke' my VMware Server ~~hypervisor~~. In fact this was really my lack of Win XP experience showing - the VMWare Server software uses a plugin (ActiveX control?) to provide a console to operate the VM. When I upgraded Internet Explorer, I needed to goto the ''Tools' menu and ''Manage Addons''. To make the VMware Server console plugin active, choose ''Toolbars and Extensions'' and then ''Show All'' in the menu on the left. Set the VMware plugin so that its available for all sites. If the plugin is installed but not made available, even if it was available under IE 7, then the message you'll get says the plugin is not available and asks if you want to install it.</blockquote>		<blockquote>Later on I would upgrade from Internet Explorer 7 to 8, which 'broke' the VMware Server Console. In fact this was really my lack of Win XP experience showing - the VMWare Server software uses a plugin (ActiveX control?) to provide a console to operate the VM. When I upgraded Internet Explorer, I needed to goto the ''Tools'' menu and ''Manage Addons''. To make the VMware Server console plugin active, choose ''Toolbars and Extensions'' and then ''Show All'' in the menu on the left. Set the VMware plugin so that its available for all sites. If the plugin is installed but not made available, even if it was available under IE 7, then the message you'll get says the plugin is not available and asks if you want to install it.</blockquote>

	* At this point you should be able to start the VM and login. With the VM selected in the left pane, click on the 'play' button and the VM should boot. It may take a few seconds. Once started you should be able to click on the ''Console'' tab and see a 'terminal' window popup. Type a return if you're not prompted for a username and password. The VMs all user the username ''opendap'' and the password ''opendap''. Login. You can change the password if you'd like. You have full access to the VM using the ''sudo'' command.		* At this point you should be able to start the VM and login. With the VM selected in the left pane, click on the 'play' button and the VM should boot. It may take a few seconds. Once started you should be able to click on the ''Console'' tab and see a 'terminal' window popup. Type a return if you're not prompted for a username and password. The VMs all user the username ''opendap'' and the password ''opendap''. Login. You can change the password if you'd like. You have full access to the VM using the ''sudo'' command. To change the password, use the command ''passwd''.

	* Now export the data from the Windows XP host. Open up a file browsing window and navigate to the folder that holds the data you want to serve. Select the folder and then choose ''Share this Folder'' from the pane on the left (I'm working from memory here - it might not be exactly like that, but it's close). I believe Shared Folders are read-only by default and that's probably what you want. If not, there's an option to allow people to change the folder contents (make it read-write).		* Now export the data from the Windows XP host. Open up a file browsing window and navigate to the folder that holds the data you want to serve. Select the folder and then choose ''Share this Folder'' from the pane on the left (I'm working from memory here - it might not be exactly like that, but it's close). I believe Shared Folders are read-only by default and that's probably what you want. If not, there's an option to allow people to change the folder contents (make it read-write).

	* Now mount the Win XP Shared Folder in the VM. Go back to the VM's console window. Since you're using Win XP to export a folder, use the Linux Samba system to mount it within the Linux directory tree. Since we don't bundle Samba with the VM, you'll have to get it. Use the ''apt-get'' system to install Samba: ''sudo apt-get smbfs''. Now make a mount point in the VM for the shared folder. I used ''sudo mkdir /opt/Hyrax-1.4.2/share/hyrax/data/<my data>'' because Hyrax is already configured to read from ''/opt/Hyrax-1.4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount -t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/Hyrax-1.4.2/share/hyrax/data/satellite''.		* Now mount the Win XP Shared Folder in the VM. Lets break this into two steps. First collect information about the Host and VM and ensire that the networking parameters are correctly set. Write down the IP number of the Host computer by going to the ''Control Panel'' and examining the attached network devices. Next write down the IP number assigned to the VM by going to the console and using the command ''sudo /sbin/ifconfig -a'' and noting the value for ''eth0'. If ''eth0'' is not listed and/or is not marked 'UP' then follow the advice below regarding the '''udev hack'''. With the two IP numbers in hand, check to make sure that the VM is configured for NAT using the VMware Server

			* Go back to the VM's console window. Since you're using Win XP to export a folder, use the Linux Samba system to mount it within the Linux directory tree. Since we don't bundle Samba with the VM, you'll have to get it. Use the ''apt-get'' system to install Samba: ''sudo apt-get smbfs''. Now make a mount point in the VM for the shared folder. I used ''sudo mkdir /opt/Hyrax-1.4.2/share/hyrax/data/<my data>'' because Hyrax is already configured to read from ''/opt/Hyrax-1.4.2/share/hyrax/data/''. Finally, mount the Shared Folder onto the new directory: ''mount -t smbfs -o username=<user>,password=<pw> //<host IP>/data /opt/Hyrax-1.4.2/share/hyrax/data/satellite''.

	<blockquote>There can be a odd wrinkle in getting the VM connected to the network.		<blockquote>There can be a odd wrinkle in getting the VM connected to the network.

Jimg: /* Detailed example: Serving data from an XP host using the Ubuntu-based VM */

2009-06-07T04:30:05Z

Detailed example: Serving data from an XP host using the Ubuntu-based VM

← Older revision		Revision as of 04:30, 7 June 2009
Line 137:		Line 137:
	gateway 192.168.0.1		gateway 192.168.0.1
	</pre>		</pre>
			</blockquote>

	= Workshops and the Hyrax and virtual machine software =		= Workshops and the Hyrax and virtual machine software =

Jimg at 04:28, 7 June 2009

2009-06-07T04:28:30Z

← Older revision		Revision as of 04:28, 7 June 2009
Line 1:		Line 1:
			[[Category:Hyrax]]

	=Introduction=		=Introduction=

← Older revision		Revision as of 23:40, 7 June 2009
Line 82:		Line 82:
	=== Detailed example: Serving data from an XP host using the Ubuntu-based VM ===		=== Detailed example: Serving data from an XP host using the Ubuntu-based VM ===

	This example details the steps I used to serve data from a virtual machine using the Ubuntu 8.04 JeOS, Hyrax 1.4.2, Tomcat 6. The host computer was running Windows XP Professional, Service Pack 2, with the VMware Server 2.01 hypervisor. The Virtual machine is available for [http://www.opendap.org/pub/vm download] on the OPeNDAP web site. Mostly this is the basic process ~~outlinedd~~ above, but there were somethings that took some sleuthing to discover - I've included those in ~~blockquoted~~ sections in the example.		This example details the steps I used to serve data from a virtual machine using the Ubuntu 8.04 JeOS, Hyrax 1.4.2, Tomcat 6. The host computer was running Windows XP Professional, Service Pack 2, with the VMware Server 2.01 hypervisor. The Virtual machine is available for [http://www.opendap.org/pub/vm download] on the OPeNDAP web site. Mostly this is the basic process outlined above, but there were somethings that took some sleuthing to discover - I've included those in block-quoted sections in the example.

	* I started with a fresh installation of Windows XP, SP2 and added VMware Server 2.01.		* I started with a fresh installation of Windows XP, SP2 and added VMware Server 2.01.
Line 96:		Line 96:
	* Make sure the VMware Server 'console' plugin is installed. First, click on the VM's name in the window pane on the left. Then click on the ''Console'' tab at the top of the center pane. If the plugin is not installed, you see a message in yellow about installing it. Do so.		* Make sure the VMware Server 'console' plugin is installed. First, click on the VM's name in the window pane on the left. Then click on the ''Console'' tab at the top of the center pane. If the plugin is not installed, you see a message in yellow about installing it. Do so.

	<blockquote>Later on I would upgrade from Internet Explorer 7 to 8, which 'broke' the VMware Server Console. In fact this was really my lack of Win XP experience showing - the VMWare Server software uses a plugin (ActiveX control?) to provide a console to operate the VM. When I upgraded Internet Explorer, I needed to ~~goto~~ the ''Tools'' menu and ''Manage Addons''. To make the VMware Server console plugin active, choose ''Toolbars and Extensions'' and then ''Show All'' in the menu on the left. Set the VMware plugin so that its available for all sites. If the plugin is installed but not made available, even if it was available under IE 7, then the message you'll get says the plugin is not available and asks if you want to install it.</blockquote>		<blockquote>Later on I would upgrade from Internet Explorer 7 to 8, which 'broke' the VMware Server Console. In fact this was really my lack of Win XP experience showing - the VMWare Server software uses a plugin (ActiveX control?) to provide a console to operate the VM. When I upgraded Internet Explorer, I needed to go to the ''Tools'' menu and ''Manage Addons''. To make the VMware Server console plugin active, choose ''Toolbars and Extensions'' and then ''Show All'' in the menu on the left. Set the VMware plugin so that its available for all sites. If the plugin is installed but not made available, even if it was available under IE 7, then the message you'll get says the plugin is not available and asks if you want to install it.</blockquote>

	* At this point you should be able to start the VM and login. With the VM selected in the left pane, click on the 'play' button and the VM should boot. It may take a few seconds. Once started you should be able to click on the ''Console'' tab and see a 'terminal' window popup. Type a return if you're not prompted for a username and password. The VMs all ~~user~~ the username ''opendap'' and the password ''opendap''. Login. You can change the password if you'd like. You have full access to the VM using the ''sudo'' command. To change the password, use the command ''passwd''.		* At this point you should be able to start the VM and login. With the VM selected in the left pane, click on the 'play' button and the VM should boot. It may take a few seconds. Once started you should be able to click on the ''Console'' tab and see a 'terminal' window popup. Type a return if you're not prompted for a username and password. The VMs all come preconfigured with the username ''opendap'' and the password ''opendap''. Login. You can change the password if you'd like. You have full access to the VM using the ''sudo'' command. To change the password, use the command ''passwd''.

	* Now export the data from the Windows XP host. Open up a file browsing window and navigate to the folder that holds the data you want to serve. Select the folder and then choose ''Share this Folder'' from the pane on the left (I'm working from memory here - it might not be exactly like that, but it's close). I believe Shared Folders are read-only by default and that's probably what you want. If not, there's an option to allow people to change the folder contents (make it read-write).		* Now export the data from the Windows XP host. Open up a file browsing window and navigate to the folder that holds the data you want to serve. Select the folder and then choose ''Share this Folder'' from the pane on the left (I'm working from memory here - it might not be exactly like that, but it's close). I believe Shared Folders are read-only by default and that's probably what you want. If not, there's an option to allow people to change the folder contents (make it read-write).

	* Now mount the Win XP Shared Folder in the VM. Lets break this into two steps. First collect information about the Host and VM and ~~ensire~~ that the networking parameters are correctly set. Write down the IP number of the Host computer by going to the ''Control Panel'' and examining the attached network devices. Next write down the IP number assigned to the VM by going to the console and using the command ''sudo /sbin/ifconfig -a'' and noting the value for ''eth0''. If ''eth0'' is not listed and/or is not marked 'UP' then follow the advice below regarding the '''udev hack'''. With the two IP numbers in hand, check to make sure that the VM is configured for NAT using the VMware Server's ''Virtual Network Editor'' (found under the 'Start' menu's ''vmware'' entry). Make sure ''NAT'' is enabled an the other two modes (host only and bridged) are disabled. At this time you can use the ''Virtual Network Editor'' to set up port forwarding so requests to access a particular port on the Host computer will be forwarded to the VM. To do this, select the ''NAT'' tab and then ~~clieck~~ on the ''Port Forwarding'' button. In the dialog box that comes up, use the IP numbers for the Host and VM and forward either port 8080 or 80 from the host to port 8080 on the VM. You can choose any port on the host, although 80 is the default HTTP port and most people will that's easiest. If you're already running a web server on the host, choose port 8080 to forward to avoid a conflict with the existing web server. At his point an access to port 80 (or 8080) on you Host will be forwarded to the VM on Port 8080, where you'll be running Hyrax. Connecting computers will not know this forwarding operation is taking place - it will seem as though they are using Hyrax on the Host computer.		* Now mount the Win XP Shared Folder in the VM. Lets break this into two steps. First collect information about the Host and VM and ensure that the networking parameters are correctly set. Write down the IP number of the Host computer by going to the ''Control Panel'' and examining the attached network devices. Next write down the IP number assigned to the VM by going to the console and using the command ''sudo /sbin/ifconfig -a'' and noting the value for ''eth0''. If ''eth0'' is not listed and/or is not marked 'UP' then follow the advice below regarding the '''udev hack'''. With the two IP numbers in hand, check to make sure that the VM is configured for NAT using the VMware Server's ''Virtual Network Editor'' (found under the 'Start' menu's ''vmware'' entry). Make sure ''NAT'' is enabled an the other two modes (host only and bridged) are disabled. At this time you can use the ''Virtual Network Editor'' to set up port forwarding so requests to access a particular port on the Host computer will be forwarded to the VM. To do this, select the ''NAT'' tab and then click on the ''Port Forwarding'' button. In the dialog box that comes up, use the IP numbers for the Host and VM and forward either port 8080 or 80 from the host to port 8080 on the VM. You can choose any port on the host, although 80 is the default HTTP port and most people will that's easiest. If you're already running a web server on the host, choose port 8080 to forward to avoid a conflict with the existing web server. At his point an access to port 80 (or 8080) on you Host will be forwarded to the VM on Port 8080, where you'll be running Hyrax. Connecting computers will not know this forwarding operation is taking place - it will seem as though they are using Hyrax on the Host computer.

	<blockquote>There can be a odd wrinkle in getting the VM connected to the network.		<blockquote>There can be a odd wrinkle in getting the VM connected to the network.
			<br>
	'''The udev hack'''		'''The udev hack'''
			<br>
	I found that sometimes the VM would start with networking broken. I don't see a pattern, but looking at the network devices using ''sudo /sbin/ifconfig -a'', eth0 is hosed (it does not say 'UP'). To fix this problem, cd to ''/etc/udev'' and in the file ''70-persistent-net-rules'' to remove the line about eth0 and edit the line for eth1 replacing 'eth1' with 'eth0'. Restart udev and networking using the eponymous scripts in /etc/init.d. Now ifconfig should show eth0 as 'UP'		I found that sometimes the VM would start with networking broken. I don't see a pattern, but looking at the network devices using ''sudo /sbin/ifconfig -a'', eth0 is hosed (it does not say 'UP'). To fix this problem, chage directory to ''/etc/udev'' and in the file ''70-persistent-net-rules'' remove the line about eth0 and edit the line for eth1 replacing 'eth1' with 'eth0'. Restart udev and networking using the eponymous scripts in /etc/init.d. Now ifconfig should show eth0 as 'UP'
			<br>
	'''Network Access'''		'''Network Access'''
			<br>
	It may be that editing your ''/etc/network/interfaces'' so it looks like the one below will remove the need modify the ''persistent-net-rules'' file above. Thanks to Marty Brewer at RRS, Inc for this information.		It may be that editing your ''/etc/network/interfaces'' so it looks like the one below will remove the need modify the ''persistent-net-rules'' file above. Thanks to Marty Brewer at RRS, Inc for this information.