[Planetlab-devel] Web UI for federated objects - impacts on API

[Thierry Parmentelat]

Hi Faiyaz
In a multi-peer environment, I'd like to be able to display the peer 
name for each foreign object
From, say, a foreign node, I can access its peer_id, but I cannot 
translate this into a peername, as long as I am logged a regular user.
Another thing: I cannot show a list of peers with their URLs and related 
numbers of nodes and stuff alike.
Thierry

Faiyaz Ahmed wrote:
> Thierry,
>
> What kind of functions would a user be interested in?
>
>
> Faiyaz
>
> Thierry Parmentelat wrote:
>> Hi Reid and all
>>
>> Following-up on the impact of federated objects on the web UI:
>> I was ideally hoping to replace, as much as possible, the functions 
>> that allow to manage a local object, that do not make sense on 
>> federated objects (like e.g. changing a node's boot state), with 
>> details on the authoritative peer. (I am starting to experiment in a 
>> multi-peer environment, and this makes particular sense in this 
>> context.)
>>
>> Anyway it seems that GetPeers is restricted to be called by roles 
>> 'admin' and 'node'.
>> I'd like to have this restriction lowered, so that a regular user can 
>> invoke GetPeers.
>> My first thought was that the cacert and key fields should not get 
>> disclosed but, this is public material so I do not think there is any 
>> sensitive security issue here.
>>
>> So my question is, does anyone have anything against the fact that 
>> GetPeers becomes allowed to regular users.
>>
>>
>> -- Thierry
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.planet-lab.org
>> https://lists.planet-lab.org/mailman/listinfo/devel