GEMINIv2tasks: 043013_Proposal_activemeasruementpage.txt

File 043013_Proposal_activemeasruementpage.txt, 3.5 KB (added by hmussman@bbn.com, 6 years ago)
Line 
1The psconfig user interface only ever needs to talk to UNIS, so it could conceivable live anywhere.  It just needs the slice name and the user cert/key to run.
2
3My main concern is allowing the active configuration interface to be reachable without a separate login process (i.e. user/password or user cert in browser).  How does your Desktop login to the Drupal instance running on the GN, for instance, and display things in the HTML5 window?
4
5The point is that if the Desktop is going to be how experimenters primarily use GEMINI, the active measurement config page should be either integrated into the Desktop or at the very least accessible via the same login mechanism.  My thought was that if the psconfig interface ran on the same web server as the Desktop, it could share the login session state and the slice info and user cert/key that's already available.  If we can somehow share login state from the Desktop to the psconfig GUI, then the GUI could still run on the GN.
6
7- ezra
8
9
10On 4/30/2013 12:39 PM, James Griffioen wrote:
11>
12> Ezra,
13>
14> We will need to think about the seemless login/access a bit, but I am
15> sure we can come up with something.
16>
17> It is not clear why you want to move psconfig out of the GN.  In
18> general, we try to put things on the GN because it solves a lot of
19> problems -- in particular, the GN can communicate with the experimental
20> nodes, whereas the user's browser may only be able to communicate with
21> the GN, not the experimental nodes.
22>
23> Note, we do not really run much of anything on the GENI Desktop server.
24>   It primarily serves up code that runs in the browser.  So when you say
25> "move it out of the GN and run alongside the GENI Desktop" I assume you
26> are thinking you will re-implmement all of psconfig in html5/javascript.
27>   That sounds like it would be hard, a lot of work, and would possibly
28> create problems accessing experimental nodes.  You would probably be
29> better implementing parts of the *use interface* in html5 and keep the
30> other parts on the GN.
31>
32> Jim
33>
34> On 04/30/2013 11:06 AM, Ezra Kissel wrote:
35>> I wanted to write down a few notes about getting the active measurement
36>> page (BLiPP/psconfig) out of the GN and running alongside the GENI
37>> Desktop for better integration.
38>>
39>> The prerequisite is to complete the active configuration for BLiPP so we
40>> can remove the original LAMP parts.  This work is ongoing and we plan to
41>> demonstrate additional functionality by 5/14.
42>>
43>> To run the active configuration pages, we need the following:
44>>
45>> 1) Access to the slice name and the user cert and key.  On the GN, this
46>> information is present on the filesystem.  On the GENI Desktop web
47>> server, how can we get this information for the given user?
48>>
49>> 2) The psconfig code will need to be integrated with the login session
50>> that the GENI Desktop uses to provide seamless navigation between pages.
51>>   Are there any PHP snippets or similar available so that we can see how
52>> this is done currently?
53>>
54>> 3) The psconfig javascript implementation (Dojo-based) calls out to an
55>> external python script to query UNIS.  We would need the web server to
56>> provide the same functionality.
57>>
58>> I think that covers the main points.  We basically need to modify the
59>> psconfig scripts to use a per-session, per-login approach given the user
60>> and slice information available from the GENI Desktop.  Other than that,
61>> the functionality should remain the same.
62>>
63>> Let me know if there any questions regarding this task.
64>>
65>> Thanks,
66>> - ezra