[Planetlab-devel] [Fwd: Re: su-like function in plcwww] -- builds and tags

[Thierry Parmentelat]

Hi all

As per Marc's suggestion I am posting this message on the devel ML, 
since it might be of general interest.

So the next question, for Marc and Tony, would be about tags - again
When is this feature expected to be part of a tag ? - it does not seem 
that it is in planetlab-4_0-rc3, nor even in the branch as far as I can 
tell.
I am sorry that I have to raise that same issue over again, but I am 
really relunctant in importing code from an unversioned tree.

This ML might be the place to start a discussion on this tagging policy. 
I would again suggest that you consider to stop tagging the whole 
planetlab code with a unique tag like you are doing now, and use tags on 
a per-module basis; IMHO this would help your release management a lot.
The idea here would be to put a planetlab-4_0-rcx tag on a single file 
(or on the build module) that would in turn describe the right 
combination of tags to use to perform that build.
Something like e.g.
http://svn.one-lab.org/filedetails.php?repname=OneLab&path=%2Fbuild%2Ftrunk%2Fonelab-tags.mk

This way it is natural to map module versions (e.g. from rpm) to the 
correct cvs tag.
And people can more easily track changes from one myplc to another.

my 2 cents -- Thierry



-------- Original Message --------
Subject: 	Re: su-like function in plcwww
Date: 	Fri, 18 May 2007 12:42:36 -0400
From: 	Tony Mack <tmack at CS.Princeton.EDU>
To: 	Thierry Parmentelat <Thierry.Parmentelat at sophia.inria.fr>
CC: 	Marc E. Fiuczynski <mef at CS.Princeton.EDU>, Faiyaz Ahmed 
<faiyaza at CS.Princeton.EDU>
References: 	<464D66BF.3050901 at sophia.inria.fr>



Hi Thierry,

Yes, there is now a 'Become' action on the users account information 
page that will allow admins to become that user. The basic details are:
1) archive your person and auth information
2) If user is logged in: begin using their session_key to auth
    else:  create a session_key for the user and being using it

This involved the following modifications:

*API*
Added:     PLC/Methods/AddSession.py (create a session_key for the 
specified user)
                PLC/Methods/GetSessions.py (Search for a users session_key)
Updated:   PLC/Sessions.py (modifyed the query code to support 
GetSessions and be more consistent with the other db query entities)

*WWW*
Added:      /web_root/planetlab/sulogout.php (logs admin out of the 
assumed user account)
Updated:   /web_root/planetlab/includes/plc_session.php (Added variables 
alt_person, alt_auth and methods BecomePeson(), BecomeSelf() )
                /usr/share/plc_api/php/plc_api.php  (make php api aware 
of new api methods AddSession() , GetSessions() )
                /web_root/planetlab/persons/index.php (Added 'Become' 
action to 'Choose action' select box)
                /web_root/planetlab/persons/person_action.php (Added 
logic for handling 'Become' requests )
                /web_root/modules/planetlab.module (Added 'logout of 
...' side navigation link which forwards to 
/web_root/planetlab/sulogout.php)
               
               

Thierry Parmentelat wrote:
> Hi all
> I've seen recent changes on the cvs ml that suggest you've got a new 
> feature allowing admins to temporarily have another user's roles; at 
> least this is what I am assuming.
> Could anyone of you guys be kind enough to give me a quick update on 
> that ?
> Thanks in advance -- Thierry