incubator-tashi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From strou...@apache.org
Subject svn commit: r948263 - in /incubator/tashi: site/docs/documentation-options.html site/docs/documentation-single.html site/xdocs/documentation-options.xml site/xdocs/documentation-single.xml trunk/etc/NodeManager.cfg trunk/etc/TashiDefaults.cfg
Date Wed, 26 May 2010 00:12:41 GMT
Author: stroucki
Date: Wed May 26 00:12:41 2010
New Revision: 948263

URL: http://svn.apache.org/viewvc?rev=948263&view=rev
Log:
Edit documentation
Make dfs location obviously an example
Ensure uniform casing in options

Modified:
    incubator/tashi/site/docs/documentation-options.html
    incubator/tashi/site/docs/documentation-single.html
    incubator/tashi/site/xdocs/documentation-options.xml
    incubator/tashi/site/xdocs/documentation-single.xml
    incubator/tashi/trunk/etc/NodeManager.cfg
    incubator/tashi/trunk/etc/TashiDefaults.cfg

Modified: incubator/tashi/site/docs/documentation-options.html
URL: http://svn.apache.org/viewvc/incubator/tashi/site/docs/documentation-options.html?rev=948263&r1=948262&r2=948263&view=diff
==============================================================================
--- incubator/tashi/site/docs/documentation-options.html (original)
+++ incubator/tashi/site/docs/documentation-options.html Wed May 26 00:12:41 2010
@@ -445,8 +445,8 @@ table.options td {
 </tr>
 <tr>
 <td>prefix</td>
-<td>/var/tmp/</td>
-<td>A location into which all DFS access is directed -- this is usually a mount point</td>
+<td>/dfs</td>
+<td>A location into which all DFS access is directed -- this is usually a mount point
to common storage</td>
 </tr>
 <tr>
 <td colspan="3">

Modified: incubator/tashi/site/docs/documentation-single.html
URL: http://svn.apache.org/viewvc/incubator/tashi/site/docs/documentation-single.html?rev=948263&r1=948262&r2=948263&view=diff
==============================================================================
--- incubator/tashi/site/docs/documentation-single.html (original)
+++ incubator/tashi/site/docs/documentation-single.html Wed May 26 00:12:41 2010
@@ -97,7 +97,8 @@ table.options td {
                 <td align="left" valign="top" width="100%">
                                 
                                     <h2>Setting up Tashi on a single test machine</h2>
-                                                                        <p>There are
several dependencies you need to setup Tashi, they include:</p>
+                                                                        <h3>Installation</h3>
+                                                                                        
       <p>There are several dependencies you need to setup Tashi, they include:</p>
                                                                                         
       <ul>
 <li>Xen or Qemu/KVM</li>
 <li>Python 2.4 or greater</li>
@@ -110,7 +111,7 @@ svn co http://svn.apache.org/repos/asf/i
 </pre></div>
                                                                                         
       <p>Then, run make:</p>
                                                                                         
       <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ make
+mryan3@firsthost:~/scratch/tashi$ make
 Generating Python code for 'layoutlocality.thrift'...
 Copying generated code to 'tashi.services' package...
 Symlinking in clustermanager...
@@ -120,6 +121,7 @@ Symlinking in primitive...
 Building nmd...
 Done
 </pre></div>
+                                                                                        
       <h3>Configuration</h3>
                                                                                         
       <p>Now, you may need to need to modify some configuration parameters to make
Tashi work in your environment.  If you place a file called Tashi.cfg in etc, it will override
settings in TashiDefaults.cfg.  Some pertinent options:</p>
                                                                                         
       <ul>
 <li>[ClusterManager]data - This specifies whether you use a pickled data file or the
SQL backend</li>
@@ -127,11 +129,11 @@ Done
 </ul>
                                                                                         
       <p>If you haven't installed Tashi in /usr/lib/python2.5/site-packages/ or the
equivalent folder, you must set the PYTHONPATH environment variable so that python can find
the Tashi code:</p>
                                                                                         
       <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ export PYTHONPATH=`pwd`/src
+mryan3@firsthost:~/scratch/tashi$ export PYTHONPATH=`pwd`/src
 </pre></div>
                                                                                         
       <p>Start the cluster manager (CM) first:</p>
                                                                                         
       <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ DEBUG=1 ./bin/clustermanager.py 
+mryan3@firsthost:~/scratch/tashi$ DEBUG=1 ./bin/clustermanager.py 
 2009-02-19 11:19:04,276 [./bin/clustermanager.py:INFO] Using configuration file(s) ['./etc/TashiDefaults.cfg']
 2009-02-19 11:19:04,276 [./bin/clustermanager.py:INFO] Starting cluster manager
 
@@ -139,11 +141,13 @@ mryan3@mryan3-d4:~/scratch/tashi$ DEBUG=
 In [1]: 
 </pre></div>
                                                                                         
       <p>I recommend running in debug mode if you haven't got it up and running yet.</p>
-                                                                                        
       <p>Then, add your first host to Tashi.  If your box's hostname was "mryan3-d4"
and you used the pickled data format, you'd do:</p>
+                                                                                        
       <p>Then, add your first host and network to Tashi. If your box's hostname was
"firsthost", an available network had VLAN ID 272, and you used the pickled data format, you'd
do:</p>
                                                                                         
       <div class="lit"><pre>
-In [1]: from tashi.rpycservices.rpyctypes import Host, HostState
+In [1]: from tashi.rpycservices.rpyctypes import Host, HostState, Network
 
-In [2]: data.baseDataObject.hosts[1] = Host(d={'id':1,'name':'mryan3-d4','state': HostState.Normal,'up':False})
+In [2]: data.baseDataObject.hosts[1] = Host(d={'id':1,'name':'firsthost','state': HostState.Normal,'up':False})
+
+In: data.baseDataObject.networks[1]=Network(d={'id':272,'name':'default'})
 
 In [3]: data.baseDataObject.save()
 
@@ -158,7 +162,7 @@ In [5]: data.baseDataObject.hosts[1]._lo
 </pre></div>
                                                                                         
       <p>Now, you can start the node manager (NM).  You may have to run this as root
if you have trouble gettings VMs to start as a normal user:</p>
                                                                                         
       <div class="lit"><pre>
-root@mryan3-d4:/home/mryan3/scratch/tashi$ DEBUG=1 ./bin/nodemanager.py 
+root@firsthost:/home/mryan3/scratch/tashi$ DEBUG=1 ./bin/nodemanager.py 
 2009-02-19 11:25:50,470 [__main__:INFO] Using configuration file(s) ['./etc/TashiDefaults.cfg']
 2009-02-19 11:25:50,475 [./src/tashi/nodemanager/vmcontrol/qemu.pyc:INFO] No vm information
found in /var/tmp/VmControlQemu/
 
@@ -167,19 +171,28 @@ In [1]: 
 </pre></div>
                                                                                         
       <p>After a few seconds, you should see no error messages on the NM and you should
be able to run "tashi-client getHosts":</p>
                                                                                         
       <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ./bin/tashi-client.py getHosts
+mryan3@firsthost:~/scratch/tashi$ ./bin/tashi-client.py getHosts
  id name      decayed up   state  version                      memory cores
 ---------------------------------------------------------------------------
- 1  mryan3-d4 False   True Normal Wed Feb  4 15:20:15 EST 2009 3894   4    
+ 1  firsthost False   True Normal Wed Feb  4 15:20:15 EST 2009 3894   4    
 </pre></div>
                                                                                         
       <p>Now that those are running, you can start the scheduler:</p>
                                                                                         
       <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ./bin/primitive.py
+mryan3@firsthost:~/scratch/tashi$ ./bin/primitive.py
 
 </pre></div>
-                                                                                        
       <p>Make sure an image is placed in /var/tmp/images (or wherever you configured
it to be):</p>
+                                                                                        
       <h3>VM deployment (XEN)</h3>
+                                                                                        
       <p>Have your networking environment set up, so that the virtual machines
+may be attached to the proper virtual bridges.</p>
+                                                                                        
       <p>Virtual disks are attached using <pre>blktap</pre>, so make sure
that
+the proper blktap module is loaded, and <pre>blktapctrl</pre> is running
+properly.</p>
+                                                                                        
       <p>Place a disk image in /dfs (or wherever you configured it to be).</p>
+                                                                                        
       <p>Have tashi-client start up a new virtual machine.</p>
+                                                                                        
       <h3>VM deployment (QEMU)</h3>
+                                                                                        
       <p>Make sure an image is placed in /dfs (or wherever you configured it to be).</p>
                                                                                         
       <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ls -la /var/tmp/images/
+mryan3@firsthost:~/scratch/tashi$ ls -la /dfs
 total 2385696
 drwxr-xr-x 2 mryan3 mryan3       4096 2009-02-19 12:21 .
 drwxrwxrwt 7 root   root         4096 2009-02-19 12:20 ..
@@ -196,7 +209,7 @@ exit 0
                                                                                         
       <p>Otherwise, you can simply make it an empty executable script.</p>
                                                                                         
       <p>And finally, you can use the client to try to create a VM:</p>
                                                                                         
       <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ./bin/tashi-client.py createVm --name foobar --disks CentOS-5.2-i386.qcow2
+mryan3@firsthost:~/scratch/tashi$ ./bin/tashi-client.py createVm --name foobar --disks CentOS-5.2-i386.qcow2
 {
     hostObj: None
     hostId: None
@@ -222,7 +235,7 @@ mryan3@mryan3-d4:~/scratch/tashi$ ./bin/
                                                                                         
       <p>The permission problems around the NM are usually related to creating the
TAP device.  Try running the "QEMU command:" reported by the NM manually if you continue to
have problems.</p>
                                                                                         
       <p>The VM will use a TAP device on your system and will be accessible over it.
 If you statically configure the guest for this test, that will work.  It is also possible
to setup a bridge and run a DHCP server on the host to provide IP addresses to the guest.
 In either case, you should be able to log into your guest shortly after that command completes.</p>
                                                                                         
       <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ssh root@192.168.127.223
+mryan3@firsthost:~/scratch/tashi$ ssh root@192.168.127.223
 The authenticity of host '192.168.127.223 (192.168.127.223)' can't be established.
 RSA key fingerprint is 3d:4b:43:25:05:d8:89:23:ec:9b:6c:1b:42:59:e7:70.
 Are you sure you want to continue connecting (yes/no)? yes
@@ -233,9 +246,9 @@ Last login: Thu Jan  8 10:25:10 2009
 </pre></div>
                                                                                         
       <p>It is also possible to access the VM via VNC:</p>
                                                                                         
       <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ./bin/tashi-client vmmspecificcall --instance foobar --arg
startvnc
-VNC started on mryan3-d4:5900
-mrayn3@mryan3-d4:~/scratch/tashi$ vncviewer mryan3-d4
+mryan3@firsthost:~/scratch/tashi$ ./bin/tashi-client vmmspecificcall --instance foobar --arg
startvnc
+VNC started on firsthost:5900
+mrayn3@firsthost:~/scratch/tashi$ vncviewer firsthost
 </pre></div>
                                                                             </td>
                 </tr>

Modified: incubator/tashi/site/xdocs/documentation-options.xml
URL: http://svn.apache.org/viewvc/incubator/tashi/site/xdocs/documentation-options.xml?rev=948263&r1=948262&r2=948263&view=diff
==============================================================================
--- incubator/tashi/site/xdocs/documentation-options.xml (original)
+++ incubator/tashi/site/xdocs/documentation-options.xml Wed May 26 00:12:41 2010
@@ -376,8 +376,8 @@
 </tr>
 <tr>
 <td>prefix</td>
-<td>/var/tmp/</td>
-<td>A location into which all DFS access is directed -- this is usually a mount point</td>
+<td>/dfs</td>
+<td>A location into which all DFS access is directed -- this is usually a mount point
to common storage</td>
 </tr>
 <tr>
 <td colspan="3">

Modified: incubator/tashi/site/xdocs/documentation-single.xml
URL: http://svn.apache.org/viewvc/incubator/tashi/site/xdocs/documentation-single.xml?rev=948263&r1=948262&r2=948263&view=diff
==============================================================================
--- incubator/tashi/site/xdocs/documentation-single.xml (original)
+++ incubator/tashi/site/xdocs/documentation-single.xml Wed May 26 00:12:41 2010
@@ -28,6 +28,8 @@
 
 <section name="Setting up Tashi on a single test machine">
 
+<h3>Installation</h3>
+
 <p>There are several dependencies you need to setup Tashi, they include:</p>
 <ul>
 <li>Xen or Qemu/KVM</li>
@@ -41,7 +43,7 @@ svn co http://svn.apache.org/repos/asf/i
 </pre></div>
 <p>Then, run make:</p>
 <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ make
+mryan3@firsthost:~/scratch/tashi$ make
 Generating Python code for 'layoutlocality.thrift'...
 Copying generated code to 'tashi.services' package...
 Symlinking in clustermanager...
@@ -51,6 +53,9 @@ Symlinking in primitive...
 Building nmd...
 Done
 </pre></div>
+
+<h3>Configuration</h3>
+
 <p>Now, you may need to need to modify some configuration parameters to make Tashi
work in your environment.  If you place a file called Tashi.cfg in etc, it will override settings
in TashiDefaults.cfg.  Some pertinent options:</p>
 <ul>
 <li>[ClusterManager]data - This specifies whether you use a pickled data file or the
SQL backend</li>
@@ -58,11 +63,11 @@ Done
 </ul>
 <p>If you haven't installed Tashi in /usr/lib/python2.5/site-packages/ or the equivalent
folder, you must set the PYTHONPATH environment variable so that python can find the Tashi
code:</p>
 <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ export PYTHONPATH=`pwd`/src
+mryan3@firsthost:~/scratch/tashi$ export PYTHONPATH=`pwd`/src
 </pre></div>
 <p>Start the cluster manager (CM) first:</p>
 <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ DEBUG=1 ./bin/clustermanager.py 
+mryan3@firsthost:~/scratch/tashi$ DEBUG=1 ./bin/clustermanager.py 
 2009-02-19 11:19:04,276 [./bin/clustermanager.py:INFO] Using configuration file(s) ['./etc/TashiDefaults.cfg']
 2009-02-19 11:19:04,276 [./bin/clustermanager.py:INFO] Starting cluster manager
 
@@ -70,11 +75,13 @@ mryan3@mryan3-d4:~/scratch/tashi$ DEBUG=
 In [1]: 
 </pre></div>
 <p>I recommend running in debug mode if you haven't got it up and running yet.</p>
-<p>Then, add your first host to Tashi.  If your box's hostname was "mryan3-d4" and
you used the pickled data format, you'd do:</p>
+<p>Then, add your first host and network to Tashi. If your box's hostname was "firsthost",
an available network had VLAN ID 272, and you used the pickled data format, you'd do:</p>
 <div class="lit"><pre>
-In [1]: from tashi.rpycservices.rpyctypes import Host, HostState
+In [1]: from tashi.rpycservices.rpyctypes import Host, HostState, Network
 
-In [2]: data.baseDataObject.hosts[1] = Host(d={'id':1,'name':'mryan3-d4','state': HostState.Normal,'up':False})
+In [2]: data.baseDataObject.hosts[1] = Host(d={'id':1,'name':'firsthost','state': HostState.Normal,'up':False})
+
+In: data.baseDataObject.networks[1]=Network(d={'id':272,'name':'default'})
 
 In [3]: data.baseDataObject.save()
 
@@ -89,7 +96,7 @@ In [5]: data.baseDataObject.hosts[1]._lo
 </pre></div>
 <p>Now, you can start the node manager (NM).  You may have to run this as root if you
have trouble gettings VMs to start as a normal user:</p>
 <div class="lit"><pre>
-root@mryan3-d4:/home/mryan3/scratch/tashi$ DEBUG=1 ./bin/nodemanager.py 
+root@firsthost:/home/mryan3/scratch/tashi$ DEBUG=1 ./bin/nodemanager.py 
 2009-02-19 11:25:50,470 [__main__:INFO] Using configuration file(s) ['./etc/TashiDefaults.cfg']
 2009-02-19 11:25:50,475 [./src/tashi/nodemanager/vmcontrol/qemu.pyc:INFO] No vm information
found in /var/tmp/VmControlQemu/
 
@@ -98,19 +105,36 @@ In [1]: 
 </pre></div>
 <p>After a few seconds, you should see no error messages on the NM and you should be
able to run "tashi-client getHosts":</p>
 <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ./bin/tashi-client.py getHosts
+mryan3@firsthost:~/scratch/tashi$ ./bin/tashi-client.py getHosts
  id name      decayed up   state  version                      memory cores
 ---------------------------------------------------------------------------
- 1  mryan3-d4 False   True Normal Wed Feb  4 15:20:15 EST 2009 3894   4    
+ 1  firsthost False   True Normal Wed Feb  4 15:20:15 EST 2009 3894   4    
 </pre></div>
 <p>Now that those are running, you can start the scheduler:</p>
 <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ./bin/primitive.py
+mryan3@firsthost:~/scratch/tashi$ ./bin/primitive.py
 
 </pre></div>
-<p>Make sure an image is placed in /var/tmp/images (or wherever you configured it to
be):</p>
+
+<h3>VM deployment (XEN)</h3>
+
+<p>Have your networking environment set up, so that the virtual machines
+may be attached to the proper virtual bridges.</p>
+
+<p>Virtual disks are attached using <pre>blktap</pre>, so make sure that
+the proper blktap module is loaded, and <pre>blktapctrl</pre> is running
+properly.</p>
+
+<p>Place a disk image in /dfs (or wherever you configured it to be).</p>
+
+<p>Have tashi-client start up a new virtual machine.</p>
+
+<h3>VM deployment (QEMU)</h3>
+
+<p>Make sure an image is placed in /dfs (or wherever you configured it to be).</p>
+
 <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ls -la /var/tmp/images/
+mryan3@firsthost:~/scratch/tashi$ ls -la /dfs
 total 2385696
 drwxr-xr-x 2 mryan3 mryan3       4096 2009-02-19 12:21 .
 drwxrwxrwt 7 root   root         4096 2009-02-19 12:20 ..
@@ -127,7 +151,7 @@ exit 0
 <p>Otherwise, you can simply make it an empty executable script.</p>
 <p>And finally, you can use the client to try to create a VM:</p>
 <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ./bin/tashi-client.py createVm --name foobar --disks CentOS-5.2-i386.qcow2
+mryan3@firsthost:~/scratch/tashi$ ./bin/tashi-client.py createVm --name foobar --disks CentOS-5.2-i386.qcow2
 {
     hostObj: None
     hostId: None
@@ -153,7 +177,7 @@ mryan3@mryan3-d4:~/scratch/tashi$ ./bin/
 <p>The permission problems around the NM are usually related to creating the TAP device.
 Try running the "QEMU command:" reported by the NM manually if you continue to have problems.</p>
 <p>The VM will use a TAP device on your system and will be accessible over it.  If
you statically configure the guest for this test, that will work.  It is also possible to
setup a bridge and run a DHCP server on the host to provide IP addresses to the guest.  In
either case, you should be able to log into your guest shortly after that command completes.</p>
 <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ssh root@192.168.127.223
+mryan3@firsthost:~/scratch/tashi$ ssh root@192.168.127.223
 The authenticity of host '192.168.127.223 (192.168.127.223)' can't be established.
 RSA key fingerprint is 3d:4b:43:25:05:d8:89:23:ec:9b:6c:1b:42:59:e7:70.
 Are you sure you want to continue connecting (yes/no)? yes
@@ -164,9 +188,9 @@ Last login: Thu Jan  8 10:25:10 2009
 </pre></div>
 <p>It is also possible to access the VM via VNC:</p>
 <div class="lit"><pre>
-mryan3@mryan3-d4:~/scratch/tashi$ ./bin/tashi-client vmmspecificcall --instance foobar --arg
startvnc
-VNC started on mryan3-d4:5900
-mrayn3@mryan3-d4:~/scratch/tashi$ vncviewer mryan3-d4
+mryan3@firsthost:~/scratch/tashi$ ./bin/tashi-client vmmspecificcall --instance foobar --arg
startvnc
+VNC started on firsthost:5900
+mrayn3@firsthost:~/scratch/tashi$ vncviewer firsthost
 </pre></div>
 
 </section>

Modified: incubator/tashi/trunk/etc/NodeManager.cfg
URL: http://svn.apache.org/viewvc/incubator/tashi/trunk/etc/NodeManager.cfg?rev=948263&r1=948262&r2=948263&view=diff
==============================================================================
--- incubator/tashi/trunk/etc/NodeManager.cfg (original)
+++ incubator/tashi/trunk/etc/NodeManager.cfg Wed May 26 00:12:41 2010
@@ -41,7 +41,7 @@ handlers = consoleHandler
 propagate = 1
 
 [Vfs]
-prefix = /var/tmp/
+prefix = /dfs
 
 [XenPV]
 vmNamePrefix = tashi

Modified: incubator/tashi/trunk/etc/TashiDefaults.cfg
URL: http://svn.apache.org/viewvc/incubator/tashi/trunk/etc/TashiDefaults.cfg?rev=948263&r1=948262&r2=948263&view=diff
==============================================================================
--- incubator/tashi/trunk/etc/TashiDefaults.cfg (original)
+++ incubator/tashi/trunk/etc/TashiDefaults.cfg Wed May 26 00:12:41 2010
@@ -124,7 +124,7 @@ defaultRamdisk = /boot/initrd-xen
 defaultDiskType=qcow
 
 [Vfs]
-prefix = /var/tmp/
+prefix = /dfs
 
 [LocalityService]
 host = localityserver
@@ -165,8 +165,8 @@ dhcpKeyName = OMAPI
 dhcpSecretKey = ABcdEf12GhIJKLmnOpQrsT==
 ipRange1 = 172.16.128.2-172.16.255.254
 reverseDns = True
-clustermanagerhost=clustermanager
-clustermanagerport=9886
+clusterManagerHost=clustermanager
+clusterManagerPort=9886
 
 [GangliaPublisher]
 dmax = 60



Mime
View raw message