[Bio] / FigTutorial / SEED_administration_issues.html Repository:
ViewVC logotype

Diff of /FigTutorial/SEED_administration_issues.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.5, Wed Jul 21 20:25:42 2004 UTC revision 1.6, Fri Jul 23 20:33:37 2004 UTC
# Line 168  Line 168 
168  <b>production system</b> is used to support the larger user community, and the <b>update system</b> is  <b>production system</b> is used to support the larger user community, and the <b>update system</b> is
169  used to prepare updated versions of the system.  Even so, work stoppages of 4-8 hours will occur when  used to prepare updated versions of the system.  Even so, work stoppages of 4-8 hours will occur when
170  new releases are swapped in.  To swap in new data from the update system to the production system,  new releases are swapped in.  To swap in new data from the update system to the production system,
171  you need to  you need to:
172  <ol>  <ol>
173  <li>stop all work on the production machine by clicking on the "Seed Control Panel" link,  <li> Stop all work on the production machine for the duration of the update.
174  entering an explanatory message in the text box, and clicking on the "Disable SEED server" button.       You do this by clicking on the "Seed Control Panel" link,
175         and then entering an explanatory message in the text box
176         and clicking on the "Disable SEED server" button.
177  <li>You now need to capture the assignments, annotations and  <li>You now need to capture the assignments, annotations and
178  subsystems work that has been done on the production machine.  subsystems work that has been done on the production machine.
179  To do this, you need to know when the last production release  To do this, you need to know when the last production release
180  was installed.  Suppose that it was July 1, 2004.  was installed.  Suppose that it was July 1, 2004.
181  If that was the date, we recommend that you run<br><br>  If that was the date, we recommend that you run<br><br>
182  <pre>  <pre>
183      <b>extract_data_for_syncing_after_update 7/1/2004 /tmp/sync.data.july.1.2004<</b>          <b>extract_data_for_syncing_after_update 7/1/2004 /tmp/sync.data.july.1.2004</b>
184  </pre>  </pre>
185  <br><br>  <br><br>
186  This will capture your updates and save them in the directory  This will capture your updates and save them in the directory
# Line 187  Line 189 
189  <b>FIGdisk/FIG</b>) with the new version from the update system.  We  <b>FIGdisk/FIG</b>) with the new version from the update system.  We
190  suggest that you do the following:  suggest that you do the following:
191  <ol>  <ol>
192  <li>archive the existing <b>Data</b> directory.  These can usually be       <li> Archive the existing <b>Data</b> directory.  These can usually be
193  discarded within a month or two, but keeping them around is a good  discarded within a month or two, but keeping them around is a good
194  safety measure.  safety measure.
195  <li>move a copy of the update <b>Data</b> directory into the      <li> Move a copy of the update <b>Data</b> directory into the
196  <b>FIGdisk/FIG</b> directory.  <b>FIGdisk/FIG</b> directory.
197  </ol>  </ol>
198  At this point, you have a version of the data from the update system  At this point, you have a version of the data from the update system
# Line 208  Line 210 
210          <b>sync_new_system /tmp/sync.data.july.1.2004 make-assignments</b>          <b>sync_new_system /tmp/sync.data.july.1.2004 make-assignments</b>
211  </pre>  </pre>
212  <br>  <br>
213  <li> make the production machine available for use.  <li> Make the production machine available for use.
214  <li>You should now bring your update system to the same state as the  <li>You should now bring your update system to the same state as the
215  production system.  This can be done by making sure that  production system.  This can be done by making sure that
216  <b>/tmp/sync.data.july.1.2004</b> is accessible to the update system.  <b>/tmp/sync.data.july.1.2004</b> is accessible to the update system.

Legend:
Removed from v.1.5  
changed lines
  Added in v.1.6

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3