GIR4.1_OnTimeMeasuraments: Feedback-20120215.txt

File Feedback-20120215.txt, 5.7 KB (added by, 10 years ago)
1Subject: Re: OnTimeMeasure Software and Documentation Testing
2From: Luisa Nevers <>
3Date: 2/15/2012 5:06 PM
4To: Prasad Calyam <>
5CC: Yingxiao Xu <>, Arun Selvadhurai <>, "" <>, "" <>, Heidi Picher Dempsey <>, Luisa Nevers <>
7On 2/13/2012 5:06 PM, Prasad Calyam wrote:
8> Wiki-1:
9> A step-by-step tutorial for experimenters to learn about the main I&M capabilities of OnTimeMeasure software/service  that can be used in an integrated manner with  Flack/ProtoGENI, INSTOOLS, Gush, OMNI and PlanetLab
13This is my feedback on OnTimeMeasure Tutorial, Wiki-1:
14I have gone through the tutorial as a first-time-user, and captured any items that could be confusing
15for a new user as I executed the instructions.  I plan to follow up on the other pages separately.
171. I really like the initial diagram which provides a valuable overview of the workflow
18    for using the tools as well as the tutorial.
202. Should spell out "I&M " on the first instance.
223. Minor enhancement, would be helpful when instructing user to jump to a section, or to chose an
23    approach for the tutorial (i.e from scratch, or import rpsec) to actually include a link to
24    that section in the text describing the choice.
26    For example replace '...jump to "2.4 Confirmation" ' with
27   '... jump to the [wiki:OnTimeMeasureTutorial#a2.4Confirmation Confirmation] section'
294. The section '2.4 Confirmation' tells the user that they have to connect to a port on the Root Beacon.
30     Should provide an URL Root Beacon example ( I realize that it
31     is also shown in the capture, but it is very small text and hard to read.
33  5. I worked through the tutorial using the import-rspec-path first and found the first mention
34      of a Root beacon, in the "Confirmation" sections.  If I had not know about the project, and the
35      tutorial was my starting point, I may have been confused by the term, which is not defined
36     for me up to now.
37     Suggestion:
38     There should be a description for each system type (root beacon and node beacon) and
39     their role in the introduction to the tutorial.
417.  In section 2.3.1, a short overview of what is being defined by the rspec that is imported would
42     be useful,  and it should provide the user the same level of information regardless of the path
43    they choose through in the tutorial.
458. I found that any operations that modified any files in /opt/OnTimeMeasure/OnTimeControl
46     failed due to privileges, the owner of the /opt/OnTimeMeasure/OnTimeControl directory is
47     1007:1007.  When I loginas lnevers into the beacons to execute instructions, all operations
48     requiring write privilege fail. Can the permissions be set for the user that owns the slice?
49     Or should all operations be carried out via sudo?
519. Is it possible to use hostnames in the config.yaml?  I am asking because once the slice
52     and sliver are started,  the information in flack and in beacon portals is for hostnames,
53     so it takes extra effort to go figure out the IP addresses, which are not readily shown in
54     web pages.
5610. The section 3.2 is duplicated later in section 3.5. Remove Section 3.5?
5811. Section 3.3. Would be nice to have some links in the introduction to measurement configuration
59     files instructions.
6112. Section 2.6 tells the user to "wait a while" and "wait time depends on how you configure
62      measurement.yaml" .    If the intended tutorial audience is new OTM users, they will have
63     no insight into this.  Should provide an expected time, (ex. 5 minutes)
6513.  The URL page name is "Supervisor Status" for all Root and Node Beacons. If user has
66        multiple pages open, the tabs all have the same name. Also book mark do not ID the
67        Root vs the Nodes.
6914. Section 5.1. should user be instructed to "cd /opt/OnTimeMeasure/OnTimeControl"
70      before downloading the custom metrics files.
7215. Syntax error in Section 7.6, the "connect connect" should have one of the
73    *two* connects removed.
7516. Section 7.6 instruction are confusing, user has to generate a table that maps NodeType to Hostname to IP Address:
77        Root Beacon - hostname - ipaddress
78        Node 1 - hostname - ipaddress
79        Node 2 - hostname - ipaddress
80        Node 3 - hostname - ipaddress
82     Again, the user must find the IP addresses, which requires lookup, neither flack, nor supervisor pages, nor
83      instools show addresses, readily.
8517.  Section 7.6 " Invoke the following Gush command to configure OnTimeMeasure."
86        The user must generate a table that maps NodeType to Hostname to IP Address and then map his/her table
87        to the NodeType to Hostname to IP Address in the tutorial, in order to be able to edit the "sed" command
88        instructions provided.  This is too much to expect from a user in a tutorial. It took me about 10 minutes to get
89        this done.  Can this be scripted?
9118.  Is the editing above required if the user has gone through the tutorial and already modified config.yaml?
9319.  I could not get GUSH to connect to Root Beacon, after many attempts gave up.
9520. Section 7.7 should instructions be executed while in the /opt/OnTimeMeasure/OnTimeControl directory?
9721.  The general duration of the tutorial is expected to take about 1 hour.  I find this estimate a little
98       hard to believe. Should consider revising estimate to longer run time expectations.
100Please let me know if any items are not clear.