Changes between Version 30 and Version 31 of VmServer


Ignore:
Timestamp:
Jun 4, 2008, 2:10:48 PM (16 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • VmServer

    v30 v31  
    99== The BOINC virtual server == #server
    1010
    11 These VMs are for use as BOINC servers.
    12 They have all the BOINC prerequisites installed, the BOINC software installed and compiled, and user accounts and permissions set up.
    13 They're ready to run [MakeProject make_project] and go.
     11This VM is for use as a BOINC server.
     12It has all the BOINC prerequisites installed, the BOINC software installed and compiled, and user accounts and permissions set up.
     13It's ready to run [MakeProject make_project] and go.
    1414
    15 Instructions and more information is in the {{{readme.html}}} file on boincadm's desktop.
     15Instructions and more information is in the {{{readme.html}}} file in ~boincadm.
    1616The passwords can be found in the file {{{README-vmware-image}}} that is part of the zip file.
    17 On all these systems, the `root` (or sudo) password is 'rootpw'.
     17The `root` (or sudo) password is 'rootpw'.
    1818There is a user account 'boincadm' with password 'boincadmpw'; build software under this account.
    1919'''Change these passwords if you're concerned about security.'''
    2020
    21 The BOINC software on these VMs is not necessarily the latest version.
     21The BOINC software on this VM is not necessarily the latest version.
    2222If you want the latest version, run {{{update_latest.sh}}} and then `configure`/`make`.
    2323
    … …  
    2525If you want the latest version, use 'yum' or other distro-specific tool.
    2626
    27 These are VMWare virtual machines;
     27This is a VMWare virtual machines;
    2828you'll need the [http://www.vmware.com/download/player/ VMWare player] (freeware).
    29 These files are large (~1 GB). Please download them as seldom as possible.
     29The file is large (~1 GB). Please download it as seldom as possible.
    3030
    3131The following versions are available:
    3232
    3333 * [http://boincdl.ssl.berkeley.edu/dl/debian-40r0-boinc-server_2_08.zip Debian 4.0 32-bit] (updated 23 Feb 2008).
    34  * [http://boincdl.ssl.berkeley.edu/dl/ubuntu-server-7.04-i386-boinc.zip Ubuntu 7.04 32-bit] (updated 21 May 2007).
    3534
    3635=== Network Access === #server-network
    3736
    38 You can either use NAT (Network Address Translation) or Bridged Ethernet to get network access from within the VM:
     37VMWare provides two ways to access the network from the VM:
     38Bridged Ethernet and NAT (Network Address Translation).
     39These are selected using the pulldown menu below "Ethernet" in the VMWare player.
     40We recommend that you start with Bridged Ethernet.
    3941
    40  NAT::
    41    You share the IP address of the host machine in order to make outgoing connections (access Internet sites from within the VM). Incoming connections from other machines (except the host machine) are, in principle, not possible. Scanning the network will only reveal one machine, your host. However, there is a way to circumvent this lack of incoming (to your server) connectivity and, thus, be able to receive connections from BOINC clients outside your network: port forwarding (not available with the free VMware player). This can be done using the VMware virtual network editor (Edit > Virtual Network Settings > NAT > Edit > Port Forwarding). More information in [http://www.vmware.com/support/ws5/doc/ws_net.html Configuring a Virtual Network]. On Windows, if NAT is to be used and not already set, you need to do the following to get network access in the VM:
     42=== Bridged Ethernet ===
     43The VM will act like a real machine on your network.
     44Scanning the network will reveal two machines, your host and the VM.
     45Outgoing and incoming connections are possible.
     46
     47By default, the VM will get an IP address via DHCP.
     48This will work if your network has a DHCP server configured to
     49issue IP address to new hosts.
     50
     51Alternatively, you can give the VM a static IP address.
     52To do this, edit /etc/network/interfaces.
     53For example:
     54{{{
     55# The primary network interface
     56auto eth0
     57#iface eth0 inet dhcp
     58#       pre-up iptables-restore < /etc/iptables.up.rules
     59iface eth0 inet static
     60address 141.142.234.9
     61netmask 255.255.255.0
     62gateway 141.142.234.1
     63pre-up iptables-restore < /etc/iptables.up.rules
     64dns-search ncsa.uiuc.edu
     65dns-nameservers 141.142.2.2 141.142.230.144
     66}}}
     67
     68You should also add the IP address and hostname of the VM to your hosts file. To do this edit {{{C:\Windows\system32\drivers\etc\hosts}}} (if the host is Windows) or {{{/etc/hosts}}} (as root; if the host is Unix) with an editor, and add for example:
     69{{{
     70141.142.234.9 debian.localdomain
     71}}}
     72
     73With this you can connect a client from your host machine to your VM.
     74If you're using a proxy to access the internet you should add 'debian.localdomain' to your list of exceptions in your browser.
     75You won't need a proxy to resolve a local address.
     76
     77=== NAT ===
     78In this mode, the VM shares the IP address of the host machine in order to make outgoing connections
     79(access Internet sites from within the VM).
     80Scanning the network will only reveal one machine.
     81
     82Incoming connections from other machines (except the host machine) are, in principle, not possible.
     83However, there is a way to circumvent this lack of incoming (to your server) connectivity and,
     84thus, be able to receive connections from BOINC clients outside your network:
     85port forwarding (not available with the free VMware player).
     86This can be done using the VMware virtual network editor (Edit > Virtual Network Settings > NAT > Edit > Port Forwarding).
     87More information in [http://www.vmware.com/support/ws5/doc/ws_net.html Configuring a Virtual Network].
     88On Windows, if NAT is to be used and not already set,
     89you need to do the following to get network access in the VM:
    4290{{{
    4391Start | Programs | VMware | VMware Server | Manage Virtual Networks
    … …  
    4997}}}
    5098
    51  Bridge::
    52    The VM will act like a real machine within your network. It tries to get its own IP over DHCP within the same range like your host machine (you can set a static IP editing {{{/etc/networks}}}). Outgoing and incoming connections are possible. Scanning the network will reveal two machines, your host and the VM. Under this approach, in the VMWare Player, choose the "Bridged" option on the pulldown menu below "Ethernet".
    53 
    54 You should also add the IP address and hostname of the VM to your hosts file. To do this edit {{{C:\Windows\system32\drivers\etc\hosts}}} (if the host is Windows) or {{{/etc/hosts}}} (as root; if the host is Unix) with an editor, and add for example:
    55 {{{
    56 192.168.190.128 debian.localdomain
    57 }}}
    58 With this you can connect a client from your host machine to your VM. If you're using a proxy to access the internet you should add 'debian.localdomain' to your list of exceptions in your browser. You won't need a proxy to resolve a local address.
    5999
    60100== The 'compatibility' VM for building and testing apps == #compatibility