I am new to the community, but hope what we currently done can give you some
ideas. We re-do the whole front end (called it UI later) instead of Horizon as
it lack of some functions (well, we lack of Python programmers as well)
In our UI, we have a self registration component to handle the new user
registration request.
As a cloud admin, they can:
define the registration form (email, name, apartment, telephone, etc.)
view and approve the registration
allocate the resources to user (project)
New user can fill up the registration form, the UI will store these data in the
DB, admin can login to the UI and see all the registration request
(data-table), once admin has approved the registration and allocate the
resource (view —> allocate —> approve) , UI will sent new user data to keystone
to complete the registration. Else, if the admin declined the registration, the
user will receive am email or mobile txt about it.
@Dolph
In our case, admin need to assigned a project to user with resources
allocation, the new user doesn’t need to care about domain, project, the admin
need to handle it all
We don’t have billing/payment functions now
If keystone doesn’t provide the functions that Horizon needs? Why don’t we let
the Horizon to handle some business logic rather to heavily rely on keystone?
In my opinions, keystone should only take care of identity, token and policy,
etc..
Garry
On Nov 11, 2013, at 11:07 PM, Walls, Jeffrey Joel (Cloud OS R&D)
wrote:
> David's questions are good ones. I do like the idea of self-registration,
> but the admin will almost certainly want some controls over their initial
> placement in the system (domain, project, roles, etc). I think part of this
> blueprint should include the specification / editing of these defaults in a
> new page on Horizon.
>
> Jeff
>
> -Original Message-
> From: Lyle, David
> Sent: Sunday, November 10, 2013 11:31 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [horizon] User registrations
>
> I think there is certainly interest. I do think it will need to be highly
> configurable to be useful. The problem, as Dolph points out, is that each
> deployment has its own workflow.
>
> Points of configuration:
> -Does the local keystone deployment policy support self-registration? The
> default is no. So, at that point access to self-registration should be
> hidden.
>
> -How many steps are required in the registration process?
>
> -Is payment information required? Address?
>
> -How is the registration confirmed, email, text, ?
>
> -CAPTCHA?
>
> I think the two main reasons such a facility is not present in Horizon are:
> 1. Until recently determining keystone's access policy was not possible.
> 2. The actual implementation is highly deployment dependent.
>
> -David
>
> From: Dolph Mathews [mailto:dolph.math...@gmail.com]
> Sent: Monday, November 11, 2013 8:57 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [horizon] User registrations
>
> So, there's a bunch of use case questions here where I suspect there are no
> correct answers (so preferences will vary per deployment). The first ones
> that come to mind-
>
> Are the users accessing this web form trusted or untrusted?
>
> Do they need to be verified, somehow? Are they going to be billed for their
> resource consumption?
>
> After registration, should they own their own domain in keystone? Or be
> assigned their own project in an existing domain? Or simply be added to an
> existing group with limited authorization?
>
> On Sun, Nov 10, 2013 at 6:26 PM, Paul Belanger
> wrote:
> Greeting,
>
> In a previous thread I talked about building an application atop of horizon
> and keystone. So far things are working out pretty well. One thing I have
> been trying to figure out is how to move forward with user registration for
> the horizon application. A few moons ago, IIRC, horizon actually use
> django-registration however the move to Keystone removed that functionality.
>
> For me, I'd like to expose some functionality within my web application allow
> users to register vs having an admin provisioning accounts.
>
> So, I'm curious if there is anything interest in having such a module back in
> horizon but leveraging keystone this time around. I'm actually curious to
> hear how people see this working since this is the next thing I need to deal
> with.
>
> --
> Paul Belanger | PolyBeacon, Inc.
> Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode)
> Github: https://github.com/pabelanger | Twitter:
> https://twitter.com/pabelanger
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> --
>
> -Dolph
> ___
