I think, there should not be such thing as default tenant.
If user does not specify tenant in authentication data, ones token should
not be bound to any tenant, and user should have access to resources based
on global role assignments.
If user specify tenant, one should be either explicitly bound t
Configs are visible to me too.
Regards,
Rohit
From: openstack-bounces+rohit.karajgi=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+rohit.karajgi=vertex.co...@lists.launchpad.net] On
Behalf Of Josh Kearney
Sent: Thursday, July 14, 2011 11:40 PM
To: Monty Taylor
Cc: openstack@lists.la
When one creates a user, should a user always have a tenant associated with
her? If that's the case, then the "default" tenant is the tenant that the user
is associated with at creation time? Sorry for responding to the question with
another question, but it is unclear for me from looking at t
Yes, you always authenticate. If the user has no roles or group then would
have no access rights to do anything. However, this would be an unusual
case, as I would expect users to be automatically added a user group or
developer role when their account was created.
Jason
From: Ziad Sawal
In the example I gave below they are not members of any group and have no roles
assigned to them. Should they still be authenticated?
From: "Rouault, Jason (Cloud Services)"
mailto:jason.roua...@hp.com>>
Date: Thu, 14 Jul 2011 16:25:22 +
To: Ziad Sawalha
mailto:ziad.sawa...@rackspace.com>>,
Works great!
On Thu, Jul 14, 2011 at 12:35 PM, Monty Taylor wrote:
> This has now been installed and activated. Anonymous users should be able
> to read the config of any job now. I've got admin access, so it's kinda of
> hard to test - would someone mind verifying that they can, in fact, see th
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 co
This has now been installed and activated. Anonymous users should be
able to read the config of any job now. I've got admin access, so it's
kinda of hard to test - would someone mind verifying that they can, in
fact, see the job configs?
Thanks!
Monty
On 07/14/2011 11:50 AM, Alexander Sakhnov
YOU ARE MY PERSONAL HERO!
On 07/14/2011 11:50 AM, Alexander Sakhnov wrote:
Hi,
there is a plugin for Jenkins that extends standart permission matrix.
http://wiki.hudson-ci.org/display/HUDSON/Extended+Read+Permission+Plugin
Maybe this would help.
On Thu, Jul 14, 2011 at 7:27 PM, mailto:adrian_f_
A user can specify a tenantID at the time of authentication. If no tenantID
is specified during authentication, then I would expect the 'default' tenant
for the user would apply. The capabilities of User1 on TenantA (in this
case the default tenant for the user) would be determined by their role
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 ad
Hi,
there is a plugin for Jenkins that extends standart permission matrix.
http://wiki.hudson-ci.org/display/HUDSON/Extended+Read+Permission+Plugin
Maybe this would help.
On Thu, Jul 14, 2011 at 7:27 PM, wrote:
> > That something will likely be a drop of a bunch of xml files
> That would be perf
That being said - I'm also more than happy to:
a) have people help admin the jenkins
and/or
b) work with people to get jobs they want added to the jenkins so that
replicating it elsewhere isn't needed.
Of course, getting the config published is still important... but we can
also work on get
Hi!
We're working on a decent solution for this. Jenkins itself does not
have a setting which allows you to see the job config without also
giving you access to edit it. (fail)
However, it's been on my todo list to a) just publish these somewhere or
b) even better, an easy way for you to spi
> That something will likely be a drop of a bunch of xml files
That would be perfect. Thanks Monty.
Adrian
-Original Message-
From: openstack-bounces+adrian_f_smith=dell@lists.launchpad.net
[mailto:openstack-bounces+adrian_f_smith=dell@lists.launchpad.net] On
Behalf Of Monty Tay
+1 ditto
-Original Message-
From: adrian_f_sm...@dell.com
Sent: Thursday, July 14, 2011 9:30am
To: openstack@lists.launchpad.net
Subject: [Openstack] Jenkins Job Configuration
___
Mailing list: https://launchpad.net/~openstack
Post to : open
Would it be possible to see the individual configuration files for the jobs
running on http://jenkins.openstack.org?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~opens
17 matches
Mail list logo
