openstack team mailing list archive

[Anthony Young <sleepsonthefloor@xxxxxxxxx>]

The main issue was that maintaining ec2 extensions was becoming too hairy,
which is why the original doc talks about using the direct api client to get
a console url.  Dashboard support for vnc was subsequently added through the
community using dashboard's ec2 extensions.

Proper support for vnc consoles and other features that diverge from the ec2
is coming as we transition away from ec2 to the openstack api and
extensions.  The very latest trunk version of dashboard supports vnc
consoles for all users through os extensions, and actually doesn't use ec2
at all.

That said, UX-wise, I'd expect that any user should be able to access the
console of an instance that was launched by their tenant.  So it probably
still makes sense to make the change you suggest to support older ec2-based
dashboards.

Anthony

On Thu, Jul 14, 2011 at 8:51 AM, Everett Toews <everett.toews@xxxxxxxxx>wrote:

> The way the code stands right now is that only the cloudadmin user can view
> VNC consoles from the Dashboard (
> http://nova.openstack.org/runnova/vncconsole.html)
>
> Is that the intention?
>
> Do we want to allow non-cloudadmin users to be able to view VNC consoles
> from the Dashboard?
>
> If so we need to add one line to
> https://github.com/openstack/nova/blob/master/nova/api/ec2/__init__.py in
> Authorizer.__init__. Add to self.action_roles
>
> 'GetVncConsole': ['projectmanager', 'sysadmin'],
>
> under CloudController. Otherwise regular users immediately get a 401 when
> trying to use VNC.
>
> Everett
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>