I understand the sentiment that leads one to want "minimum" review times; there
have been occasions where it's frustrated me that something I objected to got
merged without my seeing it or while I was trying to comment.
However, I'd like to present several arguments against a minimum review time
It looks like you've got an extra slash in your URL. That probably means you've
got a trailing slash on your OPENSTACK_KEYSTONE_URL setting. As per the example
settings file it should look like this:
OPENSTACK_KEYSTONE_URL = "http://%s:5000/v2.0"; % OPENSTACK_HOST
e.g.
OPENSTACK_KEYSTONE_URL =
2012 5:26 PM
To: Gabriel Hurley
Cc: jay_s_b; openstack@lists.launchpad.net
Subject: Re: [Openstack] horizon and keystone no route matched error
Wasn't this fixed in keystoneclient (properly handling an unexpected trailing
slash)?
-Dolph
On Wed, Mar 21, 2012 at 6:56 PM, Gabriel Hurley
mai
First, to answer your question, take a look at what's in DevStack's keystone
templates:
https://github.com/openstack-dev/devstack/blob/master/files/default_catalog.templates
That's for an Essex Keystone install, but I think you can figure out how to
generalize it back to your setup.
That said,
In the last couple days, a few troubling bugs have been uncovered using Horizon
that point to a much deeper problem of "admin"-ness in Essex. First, the two
most recent bugs:
1. https://bugs.launchpad.net/keystone/+bug/968696
Summary: having an admin role on any tenant gives you admin rights in
On the keystone admin port the tenants call will list all tenants (provided the
token corresponds to a user who has admin privileges).
- Gabriel
From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.ne
Hi all,
Since the Folsom summit I've been quietly pushing forward on the
translation/internationalization management front. This email has two main
parts:
1. The need for management and leadership around translation,
internationalization, and localization in OpenStack.
2. Tools to support the
mailto:rl...@wikimedia.org]
> Sent: Tuesday, May 08, 2012 2:09 PM
> To: Gabriel Hurley
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Translation and Internationalization in OpenStack
>
> > Tools
> >
> >
> > I know people have strong f
The tenant_id field on user creation is the "default tenant" for the user.
Adding a user to additional tenants is done by granting the user one or more
roles on those tenants.
All the best,
- Gabriel
From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:opens
A few key points:
1. I would re-frame the options as “English Only”, “User-Facing
Messages”, or “All Strings”. These three categories more accurately cover the
purposes of translating different scopes in the application. The key difference
being that web interfaces and API/CLI messages a
In addition to these hardcoded "admin" (and "Member") role names, for legacy
reasons there are also several roles in the keystone sample data which have
never been used in OpenStack (e.g. "netadmin", etc.):
https://github.com/openstack/keystone/blob/master/tools/sample_data.sh#L119
Just sayin',
You can manually swap out the code in the src dir in your environment quite
trivially. For development purposes I frequently have my own copies of the
clients symlinked in.
There is no way to override the pip-requires file automagically, however.
Requirement freezing in Horizon and client versi
It appears that nova volume is returning an error across the API which
(somehow) is causing a retry across the API, ultimately resulting in the
uncaught exception. That said, I'm stumped on what error would cause that
offhand. I'd check your nova log (and also make sure you actually have the nov
Two points:
Nova Volume is a required service for Essex Horizon. That's documented, and
there are plans to make it optional for Folsom. However, not having it should
yield a pretty error message in the dashboard, not a KeyError in novaclient,
which leads me to my second point...
It sounds like
Hi Josh,
As for packages, I can't speak to Fedora offhand, but Ubuntu has the "nodejs"
package which is what we've used internally for development and for the
devstack gate going forward. The LESS binary itself is being bundled with
Horizon to alleviate versioning incompatibilities and package
I agree with the larger problem of being mindful about our supported distros.
That said, most of us are (at best) knowledgeable about a single distro's
bundled packages. This is amplified by the fact that our CI infrastructure is
only gated on a single distro (Ubuntu) currently.
As you noted, t
- Gabriel
From: Joshua Harlow [mailto:harlo...@yahoo-inc.com]
Sent: Thursday, May 24, 2012 1:46 PM
To: openstack-...@yahoo-inc.com; Gabriel Hurley; openstack
Subject: Re: [Openstack] Nodejs in horizon
Good to know,
I thought that fedora was being ran as well in the CI env.
If not, I wil
Calling it "broken" is a bit of an overstatement. As noted previously, node.js
can be installed and configured (http://nodejs.tchol.org/) on Fedora. It's just
not in the Fedora default package repositories. My reading of the ticket on the
redhat bugzilla also indicates that there's active work t
A couple thoughts (sorry, it's late here):
1. I'll repeat my call for a list (somewhere) of who OpenStack's "downstream
stakeholders" are. I'm in favor of our commitment of support and cooperation,
but providing openness and insight into who we're offering it to would be
awesome.
2. Bundling L
To elucidate a few more points from people's responses so far:
* All the python socket.io backends are immature projects, and there's
a GAPING flaw with them all: WSGI (the interface between web servers and
Python) doesn't support the handshake features that websocket communication
req
eed to do would be a
compromise I'm more than happy with... ;-)
- Gabriel
From: Kiall Mac Innes [mailto:ki...@managedit.ie]
Sent: Friday, May 25, 2012 11:41 AM
To: Gabriel Hurley
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Nodejs in horizon
On Fri, May 25, 2012
-
> bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
> Russell Bryant
> Sent: Friday, May 25, 2012 1:20 PM
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Nodejs in horizon
>
> On 05/25/2012 03:35 PM, Gabriel Hurley wrote:
> > I have no
lready. One Potential approach
is to use an Apache module for Websockets: I am aware that mod_wsgi will not
handle it. Perhaps getting websocket support into mod_wsgi is a better way
forward?
On 05/25/2012 01:54 PM, Gabriel Hurley wrote:
To elucidate a few more points from people'
To the best of my understanding there are two parts to this, neither of which
is fully where it ought to be:
1. It shouldn't be a required parameter. If you give it a volume with
everything it needs and not an image it should try to boot from that without
throwing an exception. Horizon o
Without rehashing backstory which is available in public archives of this
thread, while node is currently on the table for LESS it also may play a role
in future needs as well.
As for your link, yes there are LESS compilers in other languages (there's even
a nascent one in Python that's very muc
Allowing a user to be associated with multiple tenants (a.k.a. projects) is
what we have currently, and it works reasonably well. It has not produced a
significantly more complicated system.
I would argue the flipside of your point, which is that the admin permission
system in keystone is parti
Terminology:
Project == Tenant. They are equivalent in Keystone parlance.
What you're referring to as a "tenant" in that last email is the role a
"domain" might play going forward in Keystone.
All the best,
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=n
websockets qualify as an alternative? If so, I'll update
> the blueprint
>
>
>
> >
> >
> > Devin
> >
> >
> > On May 29, 2012, at 10:26 AM, Adam Young wrote:
> >
> >> On 05/29/2012 12:29 PM, Gabriel Hurley wrote:
> >>>
My guess would be that your panel module is not being imported anywhere, and
thus not ever discovered. There are several ways that discovery can happen:
1. If your panel module lives inside a dashboard that lists it in the
"panels" attribute on the Dashboard class, it will be discovered a
Log streaming is definitely a good example use case. And as you said, this is
mainly relevant to browser-server communications; less so to the backend stack
to my knowledge.
In thinking more on the websocket approach that Horizon might take in the
future, I have come to this thought:
What webs
Stored timestamps should always be in UTC, however efforts should be made to
support local timezones as a user-configurable option. Horizon will be working
towards this goal since Django has good timezone support, I'd encourage other
projects to keep this on their radar as well.
- Gabriel
I've had this fight with Joe Heck and Termie before. They rejected my attempts
to modify the Keystone code to allow a user to change their own password. I
believe their grounds were a combination of it being an "admin" activity, and
that adding it to the "user" API would change the API contract
A couple of us on the Horizon team have been talking, and we'd like to
recognize the tremendous work the Tihomir has been doing on Horizon for the
past 6+ months by making him a member of Horizon Core. He's been writing great
code, doing consistent and helpful reviews, tackling important bugs, a
June 06, 2012 1:51 PM
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] How to let nova use localtime rather than UTC
> time?
>
> On Wed, Jun 06, 2012, Gabriel Hurley wrote:
> > Stored timestamps should always be in UTC, however efforts should be
> > made to support l
The blueprint for adding Quantum support (via a "Networks" panel) back into the
dashboard is still a high priority for both the Horizon and Quantum teams.
There was a patch started by one of the Quantum team members, but after a code
review that identified many fixes it ended up expiring and doe
I just thought I'd call out that Glance's swift storage module is currently
broken, and apparently this escaped the devstack gate even though devstack
actually fails to complete if swift is enabled. Are we not testing with swift
in the ENABLED_SERVICES list?
Bug report here: https://bugs.launch
Mark,
Apparently you must have missed my lightning talk at the Essex summit... ;-)
(http://gabrielhurley.github.com/slides/openstack/apis_like_orms/index.html)
Filtering, pagination, and many other API features are *critical* for a rich
dashboard experience. If you want to talk specifics, the e
Totally agree with all of Jay's points, and I also couldn't agree more with
Mark on the importance of being crystal clear, and not operating on just a
"common understanding" which is quickly misunderstood or forgotten.
Ideally I'd like to see an OpenStack API feature contract of some sort...
es
It generally sounds like you've done the right things... the only thing I can
think of offhand might be that if you're running Django through a webserver
like Apache, nginx, or gunicorn you'll need to restart your webserver to see
the changes take effect.
Some information on what version of Hor
- Gabriel
> -Original Message-
> From: Mark Nottingham [mailto:m...@mnot.net]
> Sent: Tuesday, June 12, 2012 8:43 PM
> To: Gabriel Hurley
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] [keystone] v3 API draft (update and questions to
> the community)
>
>
Big +1 to getting our client release process nailed down! That'll be huge in
terms of managing those dependencies. :-)
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel.hurley=nebula@list
is.
- Gabriel
> -Original Message-
> From: Sascha Peilicke [mailto:sasc...@suse.de]
> Sent: Friday, June 15, 2012 12:38 AM
> To: Gabriel Hurley
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Blueprint automatic-secure-key-generation] Automatic
> SECURE_KEY gener
It may have to do with the container type set on the images. There is some
filtering happening in the Project dashboard that hides the AKI and ARI images
that are associated with AMIs. So if you've only got AKI/ARI images those would
be hidden. You can see (and manage) those images as an adminis
Hi Joe,
I added lots of comments on the google doc. I think most of them reinforce the
existing design decisions. That said, there are a few high-level issues I'd
like to ask for discussion on:
1. This API features no differentiation between the "admin" API and the
regular API as it exi
Big +1 for automated tagging and releasing (sounds like we're managing
wildlife...) from Jenkins!
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel.hurley=nebula@lists.launchpad.net] On Be
That's looking pretty good, Sascha. May I suggest:
1. Instead of using the temporary lockfile, let's actually move slightly back
towards your original approach and check for the existence of a known secret
key file (added to .gitignore of course) which the get_secret_key function can
check for.
Nice work.
When you've got the rest of the API bits ironed out (particularly
attach/detach) I'll help work on making sure Horizon is fully functional there.
Note that there's also an F3 Horizon blueprint for splitting volumes into its
own optional panel:
https://blueprints.launchpad.net/horizo
cke [mailto:sasc...@suse.de]
> Sent: Wednesday, June 20, 2012 9:05 AM
> To: Gabriel Hurley; openstack@lists.launchpad.net
> Cc: Paul McMillan
> Subject: Re: [Openstack] [Blueprint automatic-secure-key-generation]
> Automatic SECURE_KEY generation
>
> Hi guys,
>
> accordi
The port change is fine with me since we're trampling on an already-registered
port number.
However, I'd like to ask again about the admin vs. standard ports in the
Keystone v3 API. There was no mention of the differentiation between the two or
how they would be used. Especially in a post-RBAC/
Argh. I think it interacted with one of the other backports badly. I'll update
this today.
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
Updated the review on gerrit so the test that got added by another backport to
work with this patch. Everything should be good there now.
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel.hurl
It sounds like your local_settings.py file is missing any logging
configuration. The default config from the local_settings.py.example file is a
good place to start.
If that’s not the case, then it would be helpful to know how you installed
OpenStack/Horizon, what you’ve done to configure it, e
I'm seeing a lot of that on the CI gate jobs today, too. Seems to be an problem
installing dependencies with pip. Usually I blame this on transient network
problems, unless somebody's been mucking with the clients themselves...
- Gabriel
From: openstack-bounces+gabriel.hurley=nebula.
I can get behind that. Despite some vigorous debates he and I have had, I can
stand behind his overall knowledge, contributions and quality standards. ;-)
+1.
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
I'm seeing this error too. It appears that the environment variables
(SERVICE_TOKEN, etc.) aren't getting exported, causing keystoneclient to not
find them in the environment and triggering that error.
What I can't figure out is what changed in the last couple days to make this
suddenly stop wo
I've found where the problem stems from. It snuck in with the keystone sql
backend change:
https://github.com/openstack-dev/devstack/commit/3f7c06f5aaff5d3e2ec28931e0fe4ab8376208e6#L1L1944
Previously the arguments to the keystone commands were being passed in
directly, now they're not, hence th
This turned out to be a legitimate bug in devstack.
bug report:
https://bugs.launchpad.net/devstack/+bug/1019056
and review:
https://review.openstack.org/#/c/9143/
All the best,
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
On a more fundamental level, did I miss some tremendous reason why we have this
"merge from common" pattern instead of making OpenStack Common a standard
python dependency just like anything else? Especially with the work Monty has
recently done on versioning and packaging the client libs from J
So, I understand the rationales, and I think of those three options the one
chosen is the most reasonable. I'm gonna just come out and say I hate this
whole idea, but let's set this aside for a minute 'cuz I have a genuine
question:
What will the process be for merging changes to this requireme
The notion that copying code is any protection against APIs that may change is
a red herring. It's the exact same effect as pegging a version of a dependency
(whether it's a commit hash or a real version number), except now you have code
duplication. An unstable upgrade path is an unstable upgra
ts that have the
power to block everyone yet are so easy to ignore...
All the best,
- Gabriel
> -Original Message-
> From: Monty Taylor [mailto:mord...@inaugust.com]
> Sent: Tuesday, July 03, 2012 12:49 PM
> To: Gabriel Hurley
> Cc: Eric Windisch; openstack@lists.launc
ve in all other project heads simultaneously.
--
Eric Windisch
On Tuesday, July 3, 2012 at 15:47 PM, Andrew Bogott wrote:
On 7/3/12 1:59 PM, Gabriel Hurley wrote:
The notion that copying code is any protection against APIs that may change is
a red herring. It's the exact same effect as
+1 on "close enough to an arbitrary territory and also a great name". ;-)
Also, the Grizzly is the California state animal:
http://www.statesymbolsusa.org/California/animal_grizzly_bear.html
Food for thought.
- Gabriel
From: openstack-bounces+gabriel.hurley=nebula@lists.launchpa
Having a team/leader in that arena would definitely help. I'd contribute to
common more if I knew what needed contributing, who to talk to about it, etc...
Same goes for helping in terms of packaging, etc. to make it a proper common
library.
- Gabriel
> -Original Message-
> From: o
The "Project Dashboard" hides images with an AKI or AMI image type (as they're
not launchable and generally shouldn't be edited by "normal" users). You can
see those in the "Admin Dashboard" if you want to edit them.
So my guess is that the kernel and ramdisk images are being hidden correctly
a
Sorry, that's should've read AKI or ARI.
- Gabriel
From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On
Behalf Of Gabriel Hurley
Sent: Thursday, July 05, 2012 11:54 AM
To: Sam Su;
Filed that bug a month ago: https://bugs.launchpad.net/glance/+bug/1009248
Patches welcome. ;-)
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel.hurley=nebula@lists.launchpad.net] On Beha
I'm normally very much in favor of stable APIs and slow deprecation, but in
this case I'm far more concerned about having to support two completely
independent codebases. If we pursue option 2 I think the language there needs
to be even stronger and we'd have to say that nova-volume is dead/froz
The stated and agreed-upon goal from Essex forward is to make the core
OpenStack projects N+1 compatible (e.g. Essex->Folsom, Folsom->Grizzly), and to
make the clients capable of talking to every API version forever.
Anything standing in the way of that should be considered a release-blocking
b
Big +1 on that.
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
> Vishvananda Ishaya
> Sent: Thursday, July 12, 2012 2:41 PM
> To: David Mo
Fantastic idea! Automating that N+1 test and forcing the buildout of the
migration script would be HUGE!
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel.hurley=nebula@lists.launchpad.net
2012 at 11:54 AM, Gabriel Hurley
mailto:gabriel.hur...@nebula.com>> wrote:
The “Project Dashboard” hides images with an AKI or AMI image type (as they’re
not launchable and generally shouldn’t be edited by “normal” users). You can
see those in the “Admin Dashboard” if you want to edit them
Without information on how you installed keystone/horizon, I'm going to assume
the most common problem: your local_settings.py file for Horizon is
misconfigured/out of date. Particularly let me point out this section in the
example file:
https://github.com/openstack/horizon/blob/master/openstac
Sam
On Fri, Jul 13, 2012 at 12:43 PM, Gabriel Hurley
mailto:gabriel.hur...@nebula.com>> wrote:
Glance pagination was added in Folsom. Adding a bug for this won't help since
it's already been added in the current code.
- Gabriel
From:
openstack-bounces+gabrie
I ran into some similar issues with the _enable_hairpin() call. The call is
allowed to fail silently and (in my case) was failing. I couldn't for the life
of me figure out why, though, and since I'm really not a networking person I
didn't trace it along too far.
Just thought I'd share my simila
As a rule of thumb, we need to start doing proper deprecation on all public
interfaces, whether that's a CLI, client method signatures, APIs, etc. It's a
little late for this on the old vs. new glance client/CLI (unless Brian feels
the work can be reasonably done to make them compatible) but it'
net] On Behalf Of
> Kevin L. Mitchell
> Sent: Wednesday, August 01, 2012 12:19 PM
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] [glance] legacy client removal and python-
> glanceclient
>
> On Wed, 2012-08-01 at 18:37 +, Gabriel Hurley wrote:
>
I'm trying to run devstack with quantum enabled so I can test the recent work
on re-integrating Quantum into Horizon.
I've followed the instructions for what should be in my localrc file here:
http://wiki.openstack.org/QuantumDevstack
However, devstack fails when trying to create a network duri
osen [mailto:aro...@nicira.com]
Sent: Tuesday, August 07, 2012 1:33 PM
To: Gabriel Hurley
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Quantum devstack authentication error
Hi Gabriel,
Adding Q_AUTH_STRATEGY=noauth to localrc should fix the issue.
The authentication it's trying t
With the stipulation that clients will be able to talk to all versions of the
API from here on forward, I am totally in favor of this.
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel.hurley=
Indeed, uploading large files with the Horizon webserver as an intermediate
relay is a nasty business which we want to discourage. We are looking at ways
to send files directly from the Horizon client-side UI to swift/glance for
large file upload in the future.
All the best,
- Gabriel
> -
put it in swift or s3 and just
> provide
> a uri that references it.
>
> On Aug 9, 2012, at 11:05 AM, Gabriel Hurley wrote:
>
> > Indeed, uploading large files with the Horizon webserver as an
> intermediate relay is a nasty business which we want to discourage. We are
>
More than happy to discuss it! If we can do things to support it that don't
rely on other projects (e.g. Keystone) all the better. Otherwise we should
discuss it as a community and work together towards a federated federation
solution. ;-)
- Gabriel
From: openstack-bounces+gabriel.hu
Go for it. I assume this is related to
https://bugs.launchpad.net/horizon/+bug/1018560 ?
If you need to add stuff feel free. Were you thinking the end result would be
to display those bars on the overview screen for the project?
- Gabriel
From: openstack-bounces+gabriel.hurley=nebula
There are two levels of "status" control in Horizon: one at the column level
and one at the row level, which is an aggregate of the column statuses within
that row.
Column status is controlled by settings "status=True" on the column. If you
want fine-grained control over which statuses are cons
For two summits running I've been advocating the need for a common standard of
functionality for all OpenStack APIs (things like sorting, bulk operations,
filtering, pagination, etc.). I intend to push on the issue even harder this
time around at the Grizzly summit (I'm going to propose an entir
Given that the v3 API didn't get implemented in Folsom that gives us a perfect
opportunity to talk about this stuff at the Grizzly summit! ;-)
- Gabriel
> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel
In conjunction with the PTLs, the Docs team, the Infrastructure team, various
community members and more, I'm very happy to say that we are ready to share
out a complete set of documentation and processes for translation,
internationalization, and localization for OpenStack as a whole. The docum
I traced this through the code at one point looking for the same thing. As it
stands, right now there is *not* a mechanism for customizing the default
security group's rules. It's created programmatically the first time the rules
for a project are retrieved with no hook to add or change its char
Well said, Ryan. Agreed 100% on all points, both in the specific examples and
the overarching theme of n+1 compatibility. Upgrade paths have got to be clean
and well-documented, and deprecations must be done according to responsible,
established timelines from here on out.
We're verifiably doin
One additional note on that, however: for legacy reasons many of the projects
have hardcoded assumptions about the role named "admin". In Grizzly we'll be
working to make the role-based access control truly customizable, but for now
you're stuck with needing that one.
- Gabriel
From:
t to do it in Grizzly now. ;-)
- Gabriel
From: Vishvananda Ishaya [mailto:vishvana...@gmail.com]
Sent: Friday, August 31, 2012 1:34 PM
To: Gabriel Hurley
Cc: Dolph Mathews; Jack; openstack
Subject: Re: [Openstack] About the Role and User's rights
Nova recently was changed to allow the rolename
I hereby officially throw my hat in the ring to be Horizon's PTL.
Qualifications:
I'm a highly active developer on Horizon, and a member of the Horizon Drivers
group. I wrote the initial version of python-keystoneclient, and I'm a member
of the Keystone Core group as well. I'm also a core comm
Matt is correct in pointing you to extending Horizon, however I'd take this up
a level and suggest that I'd love to see a mashup between the very widely used
django-registration app (http://docs.b-list.org/django-registration/0.8/) and
the django-openstack-auth backend. Making user accounts self
Adam beat me to the punch. What he suggested is the least invasive solution
(doesn't require changing any template files).
The secondary solution which is simpler but less elegant is a simple patch to
the stylesheet template file to point to a static pre-compiled copy of the CSS,
and then remov
same.
I'd be curious to know the definition here, but that seems like overkill to me.
If its what you need I'll do it for Folsom, but... thoughts?
- Gabriel
On Sep 14, 2012, at 8:25 PM, "Thomas Goirand" wrote:
> On Sat Sep 15 2012 03:55:09 AM CST, Gabriel Hurle
All of what you said is correct. Those filtering issues (which applied to
volumes, keypairs, and security groups at least) were tracked in separate
tickets in Nova and all got fixed towards the tail end of Folsom. I don't have
the commits handy, sorry. The proper fix was filtering the results re
This "QUANTUM_ENABLED" setting hasn't existed in a very long time (I'm talking
like Diablo timeframe). Everything in Horizon is controlled by Keystone's
service catalog. The presence or absence of particular service types (e.g.
"network" for Quantum) is what controls the appearance of those pane
Full timezone support was added in Folsom; for Essex the best you can do is
change the TIME_ZONE setting in your local_settings.py file; however if your
timezone there doesn't match the timezone on your server(s) you're gonna end up
with an offset between the dashboard and the rest of the stack,
That generic error is what happens when there's a 500 error on the server-side
while submitting a form via AJAX. Take a look in the Horizon console log to see
what really went wrong.
- Gabriel
From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:openstack-bou
1 - 100 of 144 matches
Mail list logo
