Changes between Version 28 and Version 29 of DSC/QandA

Timestamp:

Mar 5, 2013, 2:50:02 AM (11 years ago)

Author:

seskar

Comment:

—

DSC/QandA

@@ -65 +65 @@
    omf load -i darpahurdle23.ndz -o 1500 -t system:topo:all
 }}}
- 1. Q: '''Why are we seeing read-only/corrupted file system when we boot our image (after saving our image from one of the nodes on zDCXX and loading it on the nodes in another domain)?'''
+ 1. Q: '''Why are we seeing read-only/corrupted file system when we boot our image (after saving our image from one of the nodes on zDCXX and loading it on the nodes in another domain)?''' [[BR]]
     A: It is possible that older nodes are having a disk issue and that is why it is '''essential''' that you check your saved image by loading it on a pair of nodes (preferably on DCGNURXX). Also, quite often older nodes have much smaller size disk and it is safer to re-size partitions during both load and save (on zDCXX) i.e. for target partition of 15GB:
 {{{
@@ -78 +78 @@
     omf save -n node3-13.grid.orbit-lab.org
 }}}
-       NOTE: All nodes used in DARPA SPectrum Challenge are part of '''grid.orbit-lab.org''' domain.
+      NOTE: All nodes used in DARPA SPectrum Challenge are part of '''grid.orbit-lab.org''' domain.
+ 1. Q: '''Is there any problem with simply removing oml-cli process invocation? Do we need to keep OML logging code found in benchmark_[tr]x3.py?''' [[BR]]
+    A: Given that the only settable parameter is frequency, oml-cli (OML code) is not required and can simply be removed.
+